Solved BSOD TEST thread

[Gandalf]

This thread is only for test purposes...


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


Loading Dump File [C:\Users\Gandalf\Desktop\030814-11013-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0325e000 PsLoadedModuleList = 0xfffff800`034a16d0
Debug session time: Sat Mar 8 18:08:01.401 2014 (UTC - 7:00)
System Uptime: 0 days 0:26:49.213
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80071e92d0, fffff88007385694, ffffffffc000009a, 4}

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+97e694 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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


FAULTING_IP:
nvlddmkm+97e694
fffff880`07385694 803d6ea7eeff00 cmp byte ptr [nvlddmkm+0x868e09 (fffff880`0726fe09)],0

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02bc7a48 fffff880`04a77140 : 00000000`00000116 fffffa80`071e92d0 fffff880`07385694 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02bc7a50 fffff880`04a4a867 : fffff880`07385694 fffffa80`145ff000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02bc7a90 fffff880`04a76f4f : fffffa80`ffffd84d 00000000`00000000 fffffa80`071e92d0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02bc7b40 fffff880`04b4603d : fffffa80`12c72c70 00000000`00000080 00000000`00000000 fffffa80`145c3410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02bc7bc0 fffff800`035702ea : 00000000`01ba259b fffffa80`146204c0 fffffa80`06aaf6f0 fffffa80`146204c0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02bc7c00 fffff800`032c48e6 : fffff880`03572180 fffffa80`146204c0 fffff880`0357cfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02bc7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+97e694
fffff880`07385694 803d6ea7eeff00 cmp byte ptr [nvlddmkm+0x868e09 (fffff880`0726fe09)],0

SYMBOL_NAME: nvlddmkm+97e694

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 52f651cf

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

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

 

[Gandalf]

My Whocrashed program gave me this ...

[FONT=Segoe UI, Arial]Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Sun 3/9/2014 1:08:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030814-11013-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (nvlddmkm+0x97E694)
Bugcheck code: 0x116 (0xFFFFFA80071E92D0, 0xFFFFF88007385694, 0xFFFFFFFFC000009A, 0x4)
Error: [FONT=Segoe UI, Arial]VIDEO_TDR_ERROR[/FONT]
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: [FONT=Segoe UI, Arial]NVIDIA Windows Kernel Mode Driver, Version 334.89 [/FONT]
company: [FONT=Segoe UI, Arial]NVIDIA Corporation[/FONT]
description: NVIDIA Windows Kernel Mode Driver, Version 334.89
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 334.89 , NVIDIA Corporation).
Google query: [FONT=Segoe UI, Arial]NVIDIA Corporation VIDEO_TDR_ERROR[/FONT]


[/FONT]
[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]One crash dump has been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

[FONT=Segoe UI, Arial]nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 334.89 , NVIDIA Corporation)[/FONT]

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


[/FONT]

 

[carwiz]

I would ask for the msinfo file and the log files. It looks like a read error on disk may have caused the timeout. If the Nvidia driver is current for the hardware, run a disk check and/or a SFC scan to see if any system files are corrupt.

Added: By the way, a test for whom?

 

[Golden]

Both report 116 errors.....2nd most feared next to 124's.

Check for over clocking and overheating card first

 

[carwiz]

Both report 116 errors.....2nd most feared next to 124's.

Ain't that the truth.

 

[Capt.Jack Sparrow]

You can go through this Tutorial : http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html