Random BSOD/reboot on ASUS laptop - nvlddmkm.sys error

[Chinesinho]

I've been dealing with this problem for a week now. Everything works fine in safe mode, but when I boot into normal mode, it's like a 50/50 chance that it will even let me boot into the OS. It would either just reboot, or if/when it does get into the OS, the system would be very slow & unresponsive, then the BSOD pops up with the nvlddmkm.sys error. Sometimes I'm able to use the computer for a while before this happens; sometimes not.

From my hours of googling, it seems like it's a driver issue w/ the graphics gard (GeForce 9300M G). I've done the following troubleshooting, but to no avail:

1. Re-formatted my hdd & did a clean install of the OS
2. Tried various NVIDIA drivers (even loaded the latest beta driver from NVIDIA's site)
3. Ran memtest86 and dimms came back clean

Here's some basic system info:

Windows 7 Ultimate x64
Not the original OS installed, my Win 7 is the MSDN copy
Age of system: A little over 2 years ago. Purchased back in June of 2008.
Age of OS installation: 1 day old, just re-installed yesterday.

I wasn't able to get a System Health Report but attached is my dump files. When I ran perfmon /report, all I saw was a blank screen. I would really appreciate it if someone could shed some light on this...hopefully I won't have to line-up during Black Friday for a new laptop :/

Thanks in advance!

 

[Capt.Jack Sparrow]

Hello and Welcome !

Seems like it might has to do something with the GPU card itself. Follow this guide and run all the Test http://www.sevenforums.com/748030-post2.html .

Info on your Bugcheck:

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling." - H2SO4

http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

Bugcheck:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006c6e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880048672b0, 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+132b0
fffff880`048672b0 48895c2420      mov     qword ptr [rsp+20h],rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`05bfd9c8 fffff880`03cf6cbc : 00000000`00000116 fffffa80`06c6e010 fffff880`048672b0 00000000`00000000 : nt!KeBugCheckEx
fffff880`05bfd9d0 fffff880`03cf69c6 : fffff880`048672b0 fffffa80`06c6e010 fffffa80`046b0d50 fffffa80`06a72010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05bfda10 fffff880`03d9df07 : fffffa80`06c6e010 00000000`00000000 fffffa80`046b0d50 fffffa80`06a72010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05bfda40 fffff880`03dc7b75 : 00000000`ffffffff 00000000`000012f4 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05bfdb20 fffff880`03dc62bb : 00000000`00000102 00000000`00000000 00000000`000012f4 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05bfdb50 fffff880`03d992c6 : ffffffff`ff676980 fffffa80`06a72010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05bfdbf0 fffff880`03dc5e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`04e0f768 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05bfdd00 fffff800`02928166 : 00000000`0243e2ba fffffa80`06b75060 fffffa80`03cd0040 fffffa80`06b75060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05bfdd40 fffff800`02663486 : fffff800`027fde80 fffffa80`06b75060 fffff800`0280bc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`05bfdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+132b0
fffff880`048672b0 48895c2420      mov     qword ptr [rsp+20h],rbx

SYMBOL_NAME:  nvlddmkm+132b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a4c6469

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner

Hope this helps,
Captain

 

[Chinesinho]

Thanks Capt. Sparrow! I wasn't able to run the "FurMark" test (something about the program not being able to initialize...I wonder if it's because I'm running x64?). However, I am currently running the Prime95 stress test. Will let you know my results after it is done.