BSOD on fresh install, NVLDDMKM.sys

[MondoPain]

Hi

I was getting frequent display driver crashes and audio clicking on Win 8 so I went back to Win 7. Things were fine for the first 24 hrs or so, but now Im getting BSOD's all the time. I have also tried going back to previous nvidia drivers from a few months ago but this hasnt helped.

Any help would be much appreciated.

 

[marsmimar]

Hello Mondo and welcome to Seven Forums.

In going though your latest dump file, it appears that a few drivers have been flagged and show up several times throughout the analysis. They are nvlddmkm.sys (nVidia Video drivers); dxgkrnl.sys (DirectX Graphics Kernel); and dxgmms1.sys (DirectX Graphics MMS.)

In the interest of full disclosure I condensed the dump file to a more manageable size and only show a single reference to the flagged drivers.

Driver Reference Table - nvlddmkm.sys

Driver Reference Table - dxgkrnl.sys

Driver Reference Table - dxgmms1.sys

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="Red"]VIDEO_TDR_FAILURE[/COLOR] (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80069c22d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004a0c378, 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+135378
fffff880`04a0c378 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  2

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`022d19c8 fffff880`03d13000 : 00000000`00000116 fffffa80`069c22d0 fffff880`04a0c378 00000000`00000000 : nt!KeBugCheckEx
fffff880`022d19d0 fffff880`03d12d0a : fffff880`04a0c378 fffffa80`069c22d0 fffffa80`064f5310 fffffa80`06402010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`022d1a10 fffff880`03db9f07 : fffffa80`069c22d0 00000000`00000000 fffffa80`064f5310 fffffa80`06402010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`022d1a40 fffff880`03de3b75 : 00000000`ffffffff 00000000`00000243 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`022d1b20 fffff880`03de22bb : 00000000`00000102 00000000`00000000 00000000`00000243 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`022d1b50 fffff880`03db52c6 : ffffffff`ff676980 fffffa80`06402010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`022d1bf0 fffff880`03de1e7a : 00000000`00000000 fffffa80`064f5310 00000000`00000080 fffffa80`06402010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`022d1d00 fffff800`0311aede : 00000000`014af19b fffffa80`06422610 fffffa80`04e84890 fffffa80`06422610 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`022d1d40 fffff800`02e6d906 : fffff800`02ff7e80 fffffa80`06422610 fffff800`03005cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`022d1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+135378
fffff880`04a0c378 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+135378

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

[COLOR="red"]IMAGE_NAME:  nvlddmkm.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  50f94c87

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

fffff880`022d19c8  fffff880`03d13000 [COLOR="red"]dxgkrnl[/COLOR]!TdrBugcheckOnTimeout+0xec

fffff880`022d19e0  fffff880`04a0c378 [COLOR="red"]nvlddmkm[/COLOR]+0x135378

fffff880`022d1a38  fffff880`03db9f07 [COLOR="red"]dxgmms1[/COLOR]!VidSchiReportHwHang+0x40b

Suggest going to the driver websites and make sure you have the latest drivers. If you do, sometimes a previous version works better than the latest version. I'd also check for damaged or corrupt system files by running a system file checker scan from an elevated command prompt (option two.) If problems are found, run the scan 3 times and immediately reboot the computer after each scan.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[MondoPain]

Mars, thank you for your help. I have managed to have some success by unplugging my microsoft usb webcam - so far I havnt had a display driver crash yet. I am going to go ahead and follow your advice anyway. If my system remains stable I will update this thread.

Kindly

Mondo

 

[marsmimar]

That sounds promising, Mondo. I hope disconnecting the webcam solves the problems permanently. Thanks for the update.

 

[MondoPain]

Disconnecting the webcam has not stopped the crashes entirely. I am still getting frequent crashes on this display driver. I am frequently getting notified that "my display driver has stopped responding and has recovered" .

The system is stable when I am playing a game, but unstable when browsing online. I have stress tested the graphics card and it was stable and the temps were fine. I have tried a few versions of previous drivers, with having used driver sweeper in safe mode to remove the old drivers.

 

[leebojammin]

Hi,

I think what you are dealing with may well be this:

Nvidia struggles to fix TDR bug | ITProPortal.com

I discovered it today,so I hope it helps you. If it really is a IE 9 issue for you, you might try using chrome instead, as chrome isn't listed there as causing this issue. YOu could choose opera as well , or some other browser, just not one on the list.

Good luck
LeeboJ.