Recent BSOD problems - nvlddmkm.sys

anaxerxes · 09 Sep 2010

In the past few days, I've been receiving BSODs when running something graphically intensive, referring to a driver called "nvlddmkm.sys" and "BCCode: 116". This has also coincided with occasional black screens that last for a few seconds before recovering. Windows will pop up a message stating something along the lines of "nvidia driver nvlddmkm.sys has recently stopped responding and has recovered".

A couple of months ago, I replaced my graphics card, as the old one failed on me. The system has been perfectly stable since the installation of the new card...until this week. I have a horrible feeling that the new card is also about to fail on me, but I'd like to be sure it's not software related.

I've attached the files mentioned in the sticky, and would love some help with the troubleshooting process.

Lemur · 09 Sep 2010

Welcome to SF!
Please install the newest video driver.
NVIDIA DRIVERS 258.96 WHQL

Here is the error below:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800592a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800ffe8cf8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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

FAULTING_IP:
nvlddmkm+119cf8
fffff880`0ffe8cf8 4883ec28 sub rsp,28h

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

anaxerxes · 09 Sep 2010

Hi Lemur,

Thanks for the speedy response. I'm not actually on that PC at this moment, but I'm 99.9% sure that those are the drivers that I have installed already.

The PC in question has just done the strangest thing. The screen went black, the fan on the graphics card jumped up to 100% and the system stopped responding. I reset, and now as soon as I turn the PC on, the fan on the card immediately spins up to 100% and there is no display. I have one of those LCD Poster things on the motherboard, and that goes through all the steps as normal (until it reaches the system clock), at which point the system becomes unresponsive (the caps lock light, for example, is frozen). Obviously, as I have no display output, I can't really give any more infomation than this.

I hate to sound pessimistic, but this is probably indicative of the card failing, isn't it?

richc46 · 09 Sep 2010

I checked about 25% of your numerous BSODs. They show code 124

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_nvlddmkmbsod[1].zip\072110-16738-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50
Debug session time: Wed Jul 21 15:22:53.942 2010 (GMT-4)
System Uptime: 0 days 3:19:27.862
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80063ec028, b2000040, 800}
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: fffffa80063ec028, 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:  svchost.exe
CURRENT_IRQL:  f
STACK_TEXT:  
fffff880`02fdca58 fffff800`03203903 : 00000000`00000124 00000000`00000000 fffffa80`063ec028 00000000`b2000040 : nt!KeBugCheckEx
fffff880`02fdca60 fffff800`02d9b4d3 : 00000000`00000001 fffffa80`063edce0 00000000`00000000 fffffa80`063edd30 : hal!HalBugCheckSystem+0x1e3
fffff880`02fdcaa0 fffff800`032035c8 : 00000000`00000728 fffffa80`063edce0 fffff880`02fdce30 fffff880`02fdce00 : nt!WheaReportHwError+0x263
fffff880`02fdcb00 fffff800`03202f1a : fffffa80`063edce0 fffff880`02fdce30 fffffa80`063edce0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fdcc50 fffff800`03202dd5 : 00000000`00000004 00000000`00000001 fffff880`02fdceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fdcc90 fffff800`031f6e88 : fffff880`02fd4180 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02fdccc0 fffff800`02c83eac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02fdccf0 fffff800`02c83d13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdce30 fffff800`02c44999 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`067857d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x65
 
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
---------

Stop 0x124 - what it means and what to try

Read this excellent analysis. I would start with memory if the video card does not solve the problem

Lemur · 09 Sep 2010

By reset, did you reseat the card? Perhaps the card is failing. You could always try the card in another pc. Hopefully you can rma it if the card's bad.

anaxerxes · 09 Sep 2010

I've just tried the card in the other PCI-E slot on the board. It's still not displaying anything and the fan is stuck at 100%. Is there anything apart from failing hardware that could cause such a problem? This happens immediately when I power the PC on.

Lemur · 09 Sep 2010

I would test this out on another pc.
You could also borrow another video card to put in your computer, as a process of elimination.

anaxerxes · 09 Sep 2010

Okay, I'll try this out on a friend's PC tomorrow. Thanks for the help!

anaxerxes · 10 Sep 2010

Well, I've tried this in a friend's PC and it booted up normally, but the same problem (i.e. the screen went black, the fan jumped to 100% and it wouldn't boot up after resetting the PC) occured after about 45 minutes of use, so it's almost certainly a hardware problem. I was able to play TF2 without artifacts etc. until this point.

However, what I'm wondering is if it might be an issue with power. The reason I ask this is because this card is a 9800GT "green" edition - it doesn't have require an extra power connector; it derives all the necessary juice from the PCI-E slot. I did a bit of Googlin' earlier and some people suggest that this might be a problem with insufficient power going to the card. Am I clutching at straws here?

Also, am I better off asking this in the graphics card forum? Please feel free to close the thread if I should.

richc46 · 10 Sep 2010

richc46 said:

I checked about 25% of your numerous BSODs. They show code 124

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_nvlddmkmbsod[1].zip\072110-16738-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50
Debug session time: Wed Jul 21 15:22:53.942 2010 (GMT-4)
System Uptime: 0 days 3:19:27.862
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80063ec028, b2000040, 800}
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: fffffa80063ec028, 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:  svchost.exe
CURRENT_IRQL:  f
STACK_TEXT:  
fffff880`02fdca58 fffff800`03203903 : 00000000`00000124 00000000`00000000 fffffa80`063ec028 00000000`b2000040 : nt!KeBugCheckEx
fffff880`02fdca60 fffff800`02d9b4d3 : 00000000`00000001 fffffa80`063edce0 00000000`00000000 fffffa80`063edd30 : hal!HalBugCheckSystem+0x1e3
fffff880`02fdcaa0 fffff800`032035c8 : 00000000`00000728 fffffa80`063edce0 fffff880`02fdce30 fffff880`02fdce00 : nt!WheaReportHwError+0x263
fffff880`02fdcb00 fffff800`03202f1a : fffffa80`063edce0 fffff880`02fdce30 fffffa80`063edce0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fdcc50 fffff800`03202dd5 : 00000000`00000004 00000000`00000001 fffff880`02fdceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fdcc90 fffff800`031f6e88 : fffff880`02fd4180 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02fdccc0 fffff800`02c83eac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02fdccf0 fffff800`02c83d13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdce30 fffff800`02c44999 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`067857d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x65
 
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
---------

Stop 0x124 - what it means and what to try

Read this excellent analysis. I would start with memory if the video card does not solve the problem

I would suggest that you do not just totally ignore my post. That is the reason you have BSOD