Overclock.net › Forums › Intel › Intel - General › Need Help: Diagnose BSOD
New Posts  All Forums:Forum Nav:

Need Help: Diagnose BSOD

post #1 of 3
Thread Starter 
I've been doing some reading lately in an attempt to learn how to analyze my own BSOD crashes while overclocking. So far ive got my dump file, and had it analyzed by WinDbg. ill copy and paste the result here, if anyone can help me to the next step it would be greatly appreciated.
-------------------------------------------------------------------------------

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\\Windows\\Minidump\\081911-9048-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03066000 PsLoadedModuleList = 0xfffff800`032ab670
Debug session time: Fri Aug 19 03:07:38.341 2011 (UTC - 7:00)
System Uptime: 0 days 1:28:28.138
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
...................................
Loading User Symbols
Loading unloaded module list
......
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800710a028, be000000, 800400}

Probably caused by : hardware

Followup: MachineOwner
---------

1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800710a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: linpack_xeon64

CURRENT_IRQL: f

STACK_TEXT:
fffff880`009f3b58 fffff800`0302fa3b : 00000000`00000124 00000000`00000000 fffffa80`0710a028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009f3b60 fffff800`031f3513 : 00000000`00000001 fffffa80`0710da60 00000000`00000000 fffffa80`0710dab0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f3ba0 fffff800`0302f700 : 00000000`00000728 fffffa80`0710da60 fffff880`009f3f30 fffff880`009f3f00 : nt!WheaReportHwError+0x263
fffff880`009f3c00 fffff800`0302f052 : fffffa80`0710da60 fffff880`009f3f30 fffffa80`0710da60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f3d50 fffff800`0302ef0d : 00000000`00000008 00000000`00000001 fffff880`009f3fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f3d90 fffff800`03022e88 : 00000000`02949480 00000000`000266a8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f3dc0 fffff800`030e152c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f3df0 fffff800`030e1393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f3f30 00000000`005cac19 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0195e730 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5cac19


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------

1: kd> lmvm hardware
start end module name
post #2 of 3
I've been learning how to analyze dump files as well. I'm alright with it so far, but there's still much more I need to learn. Anyways...

After you load up the DMP file you want to analyze, you'll want to !analyze -v which will bring up detailed debugging information. Once you've done that, it'll give you a detailed list of the process that crashed, the bug string, etc. If that's not enough I believe you have to !errec the arguments, but I have not yet fully learned how to do that.

Anyways, your code was 0x124, which in almost all cases is directly related (in overclocking situations) to CPU voltage, usually requiring more of. Also, the process that crashed which inevitably caused the BSOD was linpack_xeon64 (which is LinX).
post #3 of 3
Thread Starter 
ty
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel - General
Overclock.net › Forums › Intel › Intel - General › Need Help: Diagnose BSOD