Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


BSOD - Graphic Card error

  • Please log in to reply
2 replies to this topic

#1 jinxiang


  • Members
  • 97 posts
  • Local time:07:31 PM

Posted 08 October 2014 - 06:11 AM

Please Advice ...


Microsoft ® Windows Debugger Version 6.3.9600.17029 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [G:\100814-19390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03415000 PsLoadedModuleList = 0xfffff800`0365a670
Debug session time: Wed Oct  8 19:01:47.799 2014 (UTC + 8:00)
System Uptime: 0 days 1:56:43.345
Loading Kernel Symbols
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8005d51010, fffff88004b5ad84, 0, 2}
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 : nvlddmkm.sys ( nvlddmkm+153d84 )
Followup: MachineOwner
0: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Attempt to reset the display driver and recover from timeout failed.
Arg1: fffffa8005d51010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004b5ad84, 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:
fffff880`04b5ad84 803d7e50710000  cmp     byte ptr [nvlddmkm+0x868e09 (fffff880`0526fe09)],0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
fffff880`042739c8 fffff880`02e7a000 : 00000000`00000116 fffffa80`05d51010 fffff880`04b5ad84 00000000`00000000 : nt!KeBugCheckEx
fffff880`042739d0 fffff880`02e79d0a : fffff880`04b5ad84 fffffa80`05d51010 fffffa80`05928010 fffffa80`05997410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04273a10 fffff880`02f20f07 : fffffa80`05d51010 00000000`00000000 fffffa80`05928010 fffffa80`05997410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`04273a40 fffff880`02f4ab75 : 00000000`ffffffff 00000000`0006d8da 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`04273b20 fffff880`02f492bb : 00000000`00000102 00000000`00000000 00000000`0006d8da 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`04273b50 fffff880`02f1c2c6 : ffffffff`ff676980 fffffa80`05997410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`04273bf0 fffff880`02f48e7a : 00000000`00000000 fffffa80`054ef570 00000000`00000080 fffffa80`05997410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`04273d00 fffff800`0372cfee : 00000000`fffffc32 fffffa80`0598d620 fffffa80`0188e9e0 fffffa80`0598d620 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`04273d40 fffff800`034835e6 : fffff880`031d3180 fffffa80`0598d620 fffff880`031ddfc0 00000000`00000e38 : nt!PspSystemThreadStartup+0x5a
fffff880`04273d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND:  .bugcheck ; kb
fffff880`04b5ad84 803d7e50710000  cmp     byte ptr [nvlddmkm+0x868e09 (fffff880`0526fe09)],0
SYMBOL_NAME:  nvlddmkm+153d84
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys
FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}
Followup: MachineOwner

BC AdBot (Login to Remove)


#2 jinxiang

  • Topic Starter

  • Members
  • 97 posts
  • Local time:07:31 PM

Posted 09 October 2014 - 06:14 AM


#3 hamluis



  • Moderator
  • 56,113 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:31 AM

Posted 09 October 2014 - 10:50 AM

Worth reading, IMO:  http://www.sevenforums.com/crash-lockup-debug-how/63320-stop-0x116-video_tdr_error-troubleshooting.html


What I would try:  Uninstall current graphics drivers completely...then install drivers which came with system/motherboard.  Others seem to prefer to newest drivers, but I don't see any sense in abandoning a driver version which worked well until it became damaged/corrupted.  The uninstall is essential because it is presumed to be damaged and incapable of functioning properly.



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users