STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Page 1 of 2 12 LastLast

  1. Posts : 5,705
    Win7 x64 + x86

    STOP 0x116: VIDEO_TDR_ERROR troubleshooting(also for STOP 0x117 errors

    NOTE: If overclocking, please reset the system to default values while troubleshooting it.

    Info on the STOP 0x116 error: BSOD Index
    More info on this particular error (applies to all video cards, not just AMD): AMD Game Forums - ATIKMDAG.sys problems and TDR FAQ Link broken
    New Link - Thanks to Captain Jack: How to troubleshoot
    New link (25 Apr 2012): AMD Game Forums - ATIKMDAG.sys problems and TDR FAQ
    31May2011 - More info (Thanks to VirGnarus): NVIDIA Statement on TDR Errors - NVIDIA Forums

    Best advice that I've seen about this error (from here: 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." - H2SO4
    If all that doesn't work, then I'd have to suggest trying a new video card.

    A Microsoft article about fixing Video TDR timeout (STOP 0x117) here: "Display driver stopped responding and has recovered" error in Windows 7 or Windows Vista
    Last edited by usasma; 13 Aug 2012 at 06:40.
      My Computer

  2. Posts : 5,705
    Win7 x64 + x86
    Thread Starter

    Additional tests to try (can help to prove that there's physical problems with the video card or other components):

    Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
    FurMark Setup:
    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature" (BurnIn test in newer versions).
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
    - Click "Quit" to exit
    Try this free stress test: Free Software - GIMPS
    Prime95 Setup:
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
    The Test selection box and the stress.txt file describes what components that the program stresses.
    Last edited by usasma; 14 May 2012 at 18:11.
      My Computer

  3. Posts : 5,705
    Win7 x64 + x86
    Thread Starter

    More info from the AMD link above - the suggestions in red are mine. This was extracted from this post - ( )

    From this link ( ):
    The following hardware issues are examples that can cause a TDR event:
    - Failing overclock on CPU or GPU (stop overclocking)
    - Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: |MG| Video Memory Stress Test 1.7.116 Download )
    - Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( HD Diagnostic ), reset your pagefile
    Use this technique to "reset" your pagefile:
    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.
    and run the 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.
    - Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!)
    - GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)
    The following software issues are examples that can cause a TDR event:
    -Incompatible drivers of any sort (either GPU, sound, etc) ( )
    -Messy registry (I doubt this and don't approve of registry cleaners)
    -Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for this OS)
    -Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for this OS)
    -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 and that it's compatible with Win7)
      My Computer

  4. Posts : 1
    Windows 7 Ultimate x64

    Test Results

    I did the sfc.exe /scannow and got the results that some files are corrupted and cannot be repaired.... i checked the log for the files and found their names to be as follows: -


    Please help...

    My Graphic card is XFX GTS 250 with updated drivers.
      My Computer

  5. Posts : 5,705
    Win7 x64 + x86
    Thread Starter

    Please start your own topic in the Crashes and Debugging forum - not in this HOW-TO section.
    Last edited by usasma; 30 Apr 2011 at 16:29.
      My Computer

  6. Posts : 2
    Windows 7 Home Premium 32bit

    Not a video card issue. Same error with two different video cards. Anyone have a solution for this yet?
      My Computer

  7. Posts : 5,705
    Win7 x64 + x86
    Thread Starter

    Please start your own topic in the Crashes and Debugging forum - not in this HOW-TO section.
      My Computer

  8. Posts : 294
    Windows 7 Ultimate x64 SP1

    I encountered this error for the first time. I hope this will answer one of the many causes of this error.

    When I select DXVA feature in CoreAVC and DXVA in Media Player Classic Home Cinema and play a video that can utilize DXVA the screen goes black and I am unable to recover to desktop, a few seconds later I get a BSOD.

    It seems like the error is caused by 2 different programs, CoreAVC and MPC Home Cinema, fighting for hardware acceleration.

    This problem does not occur if I run multiple instances of the same video or different videos that utilize DXVA in MPC - HC. Only when I enable DXVA in CoreAVC is when both codecs clash and cause a BSOD.
      My Computer

  9. MLK
    Posts : 5
    Widows 7 Professional x64

    I have also encountered this error.

    On a multimonitor setup with a single Radeon HD 7970 there is a driver issue that causes the BSOD with cause atikmpag.sys.

    Two possible solutions removed the BSOD entirely:
    1) disconnect all but one monitor and you can use the driver you want.
    2) install the rc11 driver found here

    When using the rc11 driver you can use multiple monitors on the 7970.

    Hope this helps others encountering the same problem.

      My Computer

  10. Posts : 1,314
    Windows 7 64-bit

    Thanks for the update, MLK. Given that this is a Release Candidate version of the driver, I hope they happen to officially release a fully revised version of the driver sometime soon that'll resolve this issue.
      My Computer

Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:32.
Find Us