BSOD Error 116

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64 bit
- the original installed OS on the system? Started with vista ages ago
- an OEM or full retail version? OEM
- OEM = came pre-installed on system nope bought off newegg
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 3 years
- What is the age of OS installation (have you re-installed the OS?) yes about 5 weeks, been having problems since the v270.61 drivers were released.

I previously was using a EVGA 9800 GTS RMA card that worked for over a year now. I noticed there was a new nvidia graphics driver out so i installed it. One of timed i noticed there was a problem was when i tried to load up the control panel from my task bar, it said something about inappropriate version or something. I didnt pay any mind to it so I let it run for awhile.

I got my first crash, i had no idea what it was i thought i accidently restarted my computer. Than it kept happening and happening. I opened one of the minidump files with bluescreen view and i noticed the culprit was always dxgkrnl.sys. After trying to troubleshoot everything from my ram to stress testing my cpu. I came to the conclusion that it was my graphics card. So I purchased a new one.

Now I have the EVGA GTX 560 Superclocked, i thought everything was Alright and OK, but today I woke up to see my computer has crashed again from the same error. And yes i removed all nvidia stuff from my computer through control panel, and a safe mode driver sweeper.

I'm up for formatting my computer to see if it fixes the issues but i want that to be my last resort, before anything else.

Any assistance will be greatly appreciated i am truly tired of having these issues.

NyteMarE757 said:

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64 bit
- the original installed OS on the system? Started with vista ages ago
- an OEM or full retail version? OEM
- OEM = came pre-installed on system nope bought off newegg
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 3 years
- What is the age of OS installation (have you re-installed the OS?) yes about 5 weeks, been having problems since the v270.61 drivers were released.

I previously was using a EVGA 9800 GTS RMA card that worked for over a year now. I noticed there was a new nvidia graphics driver out so i installed it. One of timed i noticed there was a problem was when i tried to load up the control panel from my task bar, it said something about inappropriate version or something. I didnt pay any mind to it so I let it run for awhile.

I got my first crash, i had no idea what it was i thought i accidently restarted my computer. Than it kept happening and happening. I opened one of the minidump files with bluescreen view and i noticed the culprit was always dxgkrnl.sys. After trying to troubleshoot everything from my ram to stress testing my cpu. I came to the conclusion that it was my graphics card. So I purchased a new one.

Now I have the EVGA GTX 560 Superclocked, i thought everything was Alright and OK, but today I woke up to see my computer has crashed again from the same error. And yes i removed all nvidia stuff from my computer through control panel, and a safe mode driver sweeper.

I'm up for formatting my computer to see if it fixes the issues but i want that to be my last resort, before anything else.

Any assistance will be greatly appreciated i am truly tired of having these issues.

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

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.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Forums

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\060811-25796-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`030a0650
Debug session time: Wed Jun  8 15:23:21.361 2011 (GMT-4)
System Uptime: 0 days 5:00:22.720
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800637e4e0, fffff8800f1876e8, 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+1796e8 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800637e4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f1876e8, 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+1796e8
fffff880`0f1876e8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0587e9c8 fffff880`0fd1e000 : 00000000`00000116 fffffa80`0637e4e0 fffff880`0f1876e8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0587e9d0 fffff880`0fd1dd0a : fffff880`0f1876e8 fffffa80`0637e4e0 fffffa80`064d3c00 fffffa80`064a9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0587ea10 fffff880`0fdc4f07 : fffffa80`0637e4e0 00000000`00000000 fffffa80`064d3c00 fffffa80`064a9010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0587ea40 fffff880`0fdeeb75 : 00000000`ffffffff 00000000`001198dd 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0587eb20 fffff880`0fded2bb : 00000000`00000102 00000000`00000000 00000000`001198dd 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0587eb50 fffff880`0fdc02c6 : ffffffff`ff676980 fffffa80`064a9010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0587ebf0 fffff880`0fdece7a : 00000000`00000000 fffffa80`050ead50 00000000`00000080 fffffa80`064a9010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0587ed00 fffff800`0317732e : 00000000`fffffc32 fffffa80`064da060 fffffa80`03b7d040 fffffa80`064da060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0587ed40 fffff800`02ecc666 : fffff800`0304de80 fffffa80`064da060 fffff800`0305bcc0 fffff880`0121e384 : nt!PspSystemThreadStartup+0x5a
fffff880`0587ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+1796e8
fffff880`0f1876e8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+1796e8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800637e4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f1876e8, 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+1796e8
fffff880`0f1876e8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0587e9c8 fffff880`0fd1e000 : 00000000`00000116 fffffa80`0637e4e0 fffff880`0f1876e8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0587e9d0 fffff880`0fd1dd0a : fffff880`0f1876e8 fffffa80`0637e4e0 fffffa80`064d3c00 fffffa80`064a9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0587ea10 fffff880`0fdc4f07 : fffffa80`0637e4e0 00000000`00000000 fffffa80`064d3c00 fffffa80`064a9010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0587ea40 fffff880`0fdeeb75 : 00000000`ffffffff 00000000`001198dd 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0587eb20 fffff880`0fded2bb : 00000000`00000102 00000000`00000000 00000000`001198dd 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0587eb50 fffff880`0fdc02c6 : ffffffff`ff676980 fffffa80`064a9010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0587ebf0 fffff880`0fdece7a : 00000000`00000000 fffffa80`050ead50 00000000`00000080 fffffa80`064a9010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0587ed00 fffff800`0317732e : 00000000`fffffc32 fffffa80`064da060 fffffa80`03b7d040 fffffa80`064da060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0587ed40 fffff800`02ecc666 : fffff800`0304de80 fffffa80`064da060 fffff800`0305bcc0 fffff880`0121e384 : nt!PspSystemThreadStartup+0x5a
fffff880`0587ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+1796e8
fffff880`0f1876e8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+1796e8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

would it make a difference that i just got a new video card yesterday?

NyteMarE757 said:

would it make a difference that i just got a new video card yesterday?

Were you having the crashes before? I suspect so. And now?

could be heat, power, the mobo, vram, etc.

ya crashing was happening before the new video card, i think i might try reformatting because all of this happend after a driver was installed. Im not having any heating issues all the temps are looking fine throughout the entire thing.

Also when i reformat should i do it with 1 ram stick in or 2. OCZ DDR2 PC2-8500 Reaper HPC 4GB Edition *EOL - OCZ Currently the sticks i am using.

Hey zigzag, heres an update. I formatted my computer yesterday in the hopes that it could possibly be a glitch in the OS. It crashed again later. So i bit the bullet and took my entire computer apart, all the way down to taking the mobo out of the case. I lifted up my heat sink off my cpu and it was spread out everywhere like it was sloppily put on. I dont know if that could have caused issues, but once i completely dusted out my case and placed everything back in, it seem slike its running fine. Going to leave it running for awhile and if it crashes again, im going to be very sad.

I have a fan hooked big fan hooked up on the side of my case blowing air in, still crashes, can i add that everytime this crash does happen it sounds like my hard drive is doing some crazy loads.

NyteMarE757 said:

I have a fan hooked big fan hooked up on the side of my case blowing air in, still crashes, can i add that everytime this crash does happen it sounds like my hard drive is doing some crazy loads.

I would then download the mfr HD diagnostic and run chkdsk

A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

See "CHKDSK LogFile" below in order to check the results of the test.


B- Elevated Command Prompt:

Go to Start and type in "cmd.exe" (without the quotes)

At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"


C-CHKDSK LogFile:

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).

Copy/paste the results into your next post.

Log Name: Application
Source: Chkdsk
Date: 6/14/2011 12:19:12 AM
Event ID: 26212
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Branden-PC
Description:
Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
168704 file records processed.

File verification completed.
738 large file records processed.

0 bad file records processed.

0 EA records processed.

60 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
232222 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
168704 file SDs/SIDs processed.

Cleaning up 320 unused index entries from index $SII of file 0x9.
Cleaning up 320 unused index entries from index $SDH of file 0x9.
Cleaning up 320 unused security descriptors.
Security descriptor verification completed.
31760 data files processed.

CHKDSK is verifying Usn Journal...
34642920 USN bytes processed.

Usn Journal verification completed.
Windows has checked the file system and found no problems.

625027071 KB total disk space.
79936752 KB in 131305 files.
92260 KB in 31761 indexes.
0 KB in bad sectors.
288419 KB in use by the system.
65536 KB occupied by the log file.
544709640 KB available on disk.

4096 bytes in each allocation unit.
156256767 total allocation units on disk.
136177410 allocation units available on disk.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Chkdsk" />
<EventID Qualifiers="0">26212</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-06-14T04:19:12.000000000Z" />
<EventRecordID>1061</EventRecordID>
<Channel>Application</Channel>
<Computer>Branden-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
168704 file records processed.

File verification completed.
738 large file records processed.

0 bad file records processed.

0 EA records processed.

60 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
232222 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
168704 file SDs/SIDs processed.

Cleaning up 320 unused index entries from index $SII of file 0x9.
Cleaning up 320 unused index entries from index $SDH of file 0x9.
Cleaning up 320 unused security descriptors.
Security descriptor verification completed.
31760 data files processed.

CHKDSK is verifying Usn Journal...
34642920 USN bytes processed.

Usn Journal verification completed.
Windows has checked the file system and found no problems.

625027071 KB total disk space.
79936752 KB in 131305 files.
92260 KB in 31761 indexes.
0 KB in bad sectors.
288419 KB in use by the system.
65536 KB occupied by the log file.
544709640 KB available on disk.

4096 bytes in each allocation unit.
156256767 total allocation units on disk.
136177410 allocation units available on disk.
</Data>
<Binary>00930200067D020028CB040000000000CC0100003C0000000000000000000000</Binary>
</EventData>
</Event>

that doesnt seem right, thats the only chkdsk file in there and im sure it ran a chkdsk in windows with that same error than it ran another one after i restarted.