Help with a BSOD

deturbanator · 14 Feb 2010

Here is the mini-dump analysis from Windows Debugging Tools:

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

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

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c59000 PsLoadedModuleList = 0xfffff800`02e96e50
Debug session time: Sat Feb 13 22:55:25.226 2010 (GMT-8)
System Uptime: 0 days 5:24:29.504
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800790d028, b2000040, 800}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware

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

3: 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: fffffa800790d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, 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: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`031dda58 fffff800`02c22903 : 00000000`00000124 00000000`00000000 fffffa80`0790d028 00000000`b2000040 : nt!KeBugCheckEx
fffff880`031dda60 fffff800`02ddf513 : 00000000`00000001 fffffa80`0796f620 00000000`00000000 fffffa80`0796f670 : hal!HalBugCheckSystem+0x1e3
fffff880`031ddaa0 fffff800`02c225c8 : 00000000`00000728 fffffa80`0796f620 fffff880`031dde30 fffff880`031dde00 : nt!WheaReportHwError+0x263
fffff880`031ddb00 fffff800`02c21f1a : fffffa80`0796f620 fffff880`031dde30 fffffa80`0796f620 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031ddc50 fffff800`02c21dd5 : 00000000`00000004 00000000`00000001 fffff880`031ddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031ddc90 fffff800`02c15e88 : fffffa80`0a402ed0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`031ddcc0 fffff800`02cc97ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031ddcf0 fffff800`02cc9613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dde30 fffff880`04ae445a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`062b38e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xb345a

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS

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

Here is more Crash info:

Crash List

Created by using BlueScreenView

Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Computer Name Full Path Processors Count Major Version Minor Version 021310-33134-01.dmp2/13/2010 10:59:58 PM 0x0000012400000000`00000000fffffa80`0790d02800000000`b200004000000000`00000800hal.dllhal.dll+12903 x64 C:\Windows\minidump\021310-33134-01.dmp4157600

usasma · 14 Feb 2010

This is a STOP 0x124 error. More info on troubleshooting them is at this link: https://www.sevenforums.com/crash-loc...-what-try.html

Also, at the bottom of the debugging windows is a blank spot to enter commands.
Please enter this command there:

lmtsmn

And then press Enter

This will list all the drivers that are loaded in the current process.
Check and see if there are any that are dated from 2008 or earlier.
If so, use this list to figure out how to update them: Driver Reference
FYI - the secdrv.sys file dated 2006 is a Windows file and you won't be able to update it.

Updating the rest of the 3rd party drivers will help to ensure that there's nothing older on your system.
And it's the older drivers that are most likely to have compatibility issues with Win7

Also, the video card driver (nvlddmkm.sys) is listed in the stack text - so the video card or it's driver is high on the list of possibilities for this issue. FWIW - I installed a video card in a Dell computer not long ago and got STOP 0x124 errors until I reseated it.