All of the attached DMP files are of the VIDEO_TDR_FAILURE (116)
The following drivers need to be updated ASAP:
ASACPI fffff880`06357000 fffff880`0635f000 Mon Oct 30 22:09:12 2006 (4546b048) 000089fb ASACPI.sys
^^ Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities - http://support.asus.com/download/download.aspx
timntr fffff880`01a9a000 fffff880`01b42000 Thu Dec 28 11:30:38 2006 (4593f12e) 000b27e8 timntr.sys
^^ Acronis True Image Backup Archive Explorer also included in Seagate DiscWizard:
If no update available, I recommend removing this software.
RTKVHD64 fffff880`06ac0000 fffff880`06bc1f80 Mon Mar 26 07:18:49 2007 (4607ac19) 001088cb RTKVHD64.sys
^^ Realtek High Definition Audio Function Driver - http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=8&PFid=14&Level=3&Conn=2
mv61xx fffff880`00fb3000 fffff880`00feb000 Fri Jun 15 03:43:26 2007 (4672431e) 0002b257 mv61xx.sys
^^ Marvell 64xx/63xx SAS Controller - http://www.marvell.com/support.htmlIf the above do not help, move on to *116 troubleshooting:
The basic definition of a 0x116 bugcheck is:There may be a bug in the video driver or video hardware.
So, let me now explain what VIDEO_TDR_ERROR means. First off, TDR is an acronym for Timeout Detection and Recovery. Timeout Detection and Recovery was introduced in Vista and carried over to Windows 7. Rather than putting exactly what Timeout Detection and Recovery does exactly, I'll just directly quote the MSDN article!Timeout detection:
Preparation for recovery:
The GPU scheduler, which is part of the DirectX graphics kernel subsystem (Dxgkrnl.sys), detects that the GPU is taking more than the permitted amount of time to execute a particular task. The GPU scheduler then tries to preempt this particular task. The preempt operation has a "wait" timeout, which is the actual TDR timeout. This step is thus the timeout detection phase of the process. The default timeout period in Windows Vista and later operating systems is 2 seconds. If the GPU cannot complete or preempt the current task within the TDR timeout period, the operating system diagnoses that the GPU is frozen.
To prevent timeout detection from occurring, hardware vendors should ensure that graphics operations (that is, DMA buffer completion) take no more than 2 seconds in end-user scenarios such as productivity and game play.
The operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to inform the driver that the operating system detected a timeout. The driver must then reinitialize itself and reset the GPU. In addition, the driver must stop accessing memory and should not access hardware. The operating system and the driver collect hardware and other state information that could be useful for post-mortem diagnosis.
The operating system resets the appropriate state of the graphics stack. The video memory manager, which is also part of Dxgkrnl.sys, purges all allocations from video memory. The display miniport driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As previously mentioned, some legacy DirectX applications might render just black at the end of this recovery, which requires the end user to restart these applications. Well-written DirectX 9Ex and DirectX 10 and later applications that handle Device Remove technology continue to work correctly. An application must release and then recreate its Direct3D device and all of the device's objects. For more information about how DirectX applications recover, see the Windows SDK.
With this being said, if Timeout Detection and Recovery fails to recover the display driver, it will then shoot the 0x116 bugcheck. There are many different things that can cause a 0x116, which I will explain below:Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.
The following hardware issues can cause a TDR event:
1. Unstable overclock (CPU, GPU, etc). Revert all and any overclocks to stock settings.
2. Bad sector in memory resulting in corrupt data being communicated between the GPU and the system (video memory otherwise known as VRAM or physical memory otherwise known as RAM).
GPU testing: Furmark
RAM testing: Memtest86+
3. Corrupt hard drive or Windows install / OS install resulting in corruption to the registry or page file.
HDD diagnostics: http://www.carrona.org/hddiag.html
To reset your page file, follow the instructions below:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step
b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.
Run System File Checker:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.
- Overheating of the CPU or GPU and or other components can cause 0x116 bugchecks. Monitor your temperatures and ensure the system is cooled adequately.
- GPU failure. Whether it's heat, power issue (PSU issue), failing VRAM, etc.
The following software issues can cause a TDR event:
-Incompatible drivers of any sort (either GPU, sound, etc)
-Messy / corrupt registry
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version).