BSOD "Attempt to reset display driver and recover from time out failed

yupper · Feb 7, 2013

BSOD "Attempt to reset display driver and recover from time out failed

I bought a XFX HD 7850 2GB less than 2 weeks ago and has experienced numerous BSOD all with the same error message "Attempt to reset display driver and recover from time out failed" I've tried various versions of AMD's catalyst driver but it has not resolved my issue. I have not attempted to overclock the GPU, all factory default settings.

The BSOD's are not easily reproducible. So far, it's happened only when I play Skyrim, after maybe 40+ minutes of gaming (but not always, as I've gone longer than that without experiencing the BSOD). What happens is that I would see artifacting on the screen: long, thin, triangles pointing to the center of the screen, when the artifacting occurs there is a GPU temperature spike (it goes to around 66 degrees celcius), and then the BSOD. The first BSOD I experienced, there was no artifacting. I had exited Skyrim and launched FireFox, and was immediately hit with a BSOD with that error message.

Using MSI Afterburner to keep track of the GPU temp, it normally does not go above 60 - 62 degrees celcius during Skyrim (idles at 27 - 30 degrees celcius). I can't reproduce the BSOD using GPU stress testing utilities like Furmark and MSI Kombuster (highest temperature seen is 66 degress celcius).

Driver versions I've used:

1) installed new GPU, uninstalled old nvidia driver, cleaned orphan nividia driver files in safe mode using Driver Sweeper, installed catalyst driver version 13.1. Experienced first BSOD in Skyrim.

2) uninstalled catalyst 13.1, cleaned orphan files in safe mode using Driver Sweeper, installed catalyst driver 12.11 beta.

3) uninstalled 12.11 beta, cleaned orphan files in safe mod using Driver Sweeper, installed catalyst driver 13.2 beta 3.

4) uninstalled 13.2 beta 3, used the new AMD driver cleaner utility in safe mode. Installed catalyst driver 13.2 beta 5.

I experienced BSOD in Skyrim with all these driver versions based on the pattern described above, but never during stress testing using MSI Kombuster of Furmark. I've tried reseating the GPU. I guess at this point I just need to know if this is a driver issue or hardware issue requiring RMA with the manufacturer. Thanks for reading.

Code:

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-Y8B93-FW2HQ-RJW3J
Windows Product Key Hash: u1X0EvAiRkoLOF4NCJ+kRDXaNTI=
Windows Product ID: 00371-OEM-9044945-73248
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {69E4C086-F9FA-410D-9E40-72706C325919}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120830-0333
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{69E4C086-F9FA-410D-9E40-72706C325919}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-RJW3J</PKey><PID>00371-OEM-9044945-73248</PID><PIDType>3</PIDType><SID>S-1-5-21-2104148743-222844551-4121701896</SID><SYSTEM><Manufacturer>EVGA__</Manufacturer><Model>nForce 750i SLI</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>6.00 PG</Version><SMBIOSVersion major="2" minor="5"/><Date>20080707000000.000000+000</Date></BIOS><HWID>244F3907018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
Activation ID: e120e868-3df2-464a-95a0-b52fa5ada4bf
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00180-449-473248-02-1033-7601.0000-1542012
Installation ID: 013202485384526851972956315565007904891193376382269965
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: RJW3J
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 2/7/2013 10:38:03 AM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 12:4:2012 22:12
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: OAAAAAMABAABAAEAAQACAAAAAQABAAEA6GH2x1n08pd3FlocKH1K00gktOukh++SipvsqL6pRso=

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name    OEMID Value    OEMTableID Value
  APIC            EVGA          NVDAACPI
  FACP            EVGA          NVDAACPI
  HPET            EVGA          NVDAACPI
  MCFG            EVGA          NVDAACPI

Dsprague · Feb 7, 2013

First please could you post this: Windows Genuine and Activation Issue Posting Instructions

yupper · Feb 7, 2013

Edited post to add the diagnostic report.

Dsprague · Feb 7, 2013

Looks ok to me, so moving along first things first please check for an update to your BIOS it is very old, pre windows 7 old:

Code:

BIOS Version:              Phoenix Technologies, LTD 6.00 PG, 7/7/2008

Next please uninstall Daemon tools it is a known causer of BSODs, then download and run this tool:

DuplexSecure - Downloads

When the tool runs if the uninstall button is grayed out your done and you can close the window if it is not click uninstall and let it run. DO NOT click install it will install a driver known to cause BSODs.

run the system file checker corrupted system files can cause this type of BSOD aswell :

SFC.EXE /SCANNOW
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.

yupper · Feb 7, 2013

Thanks for your suggestions:

1) I uninstalled DT, downloaded DuplexSecure, clicked 'uninstall', rebooted, and checked in DuplexSecure again and the 'uninstall' button is greyed out. Hopefully that means I did it right

2) I ran the system file checker and it said that "Windows Resource Protection did not find any integrity violations."

3) Yeah, my motherboard is old. This is the latest version of the BIOS for the EVGA i750 series, I believe: EVGA 750i FTW (E175) - SZ1K BIOS Released (if you can confirm that I'd be appreciative).

I am sort of nervous about flashing the BIOS. Last timed I trie to flash a BIOS (a few years ago) I somehow screwed up and had to replace the entire motherboard. Uh....do you think this is a likely culprit? Any other suggestions that you'd recommend before trying to flash the BIOS?

[edit]
Ok, I flashed the BIOS. Looks ok so far. I also reverted to catalyst driver 13.1, since at least with the non-beta version I didn't BSOD during Skyrim (but after I exited...)

Dsprague · Feb 8, 2013

Well the likenly causews of a 0x116 stop are as follows:

Code:

[B]Usual causes:[/B]  Video driver, overheating, bad video card, BIOS, Power to card

so really there are only a few things I have left that I can think of to try before is becomes apparent that it is likely a hardware failure. First you can try resetting your page file:

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.

you can run hdd diagnostics by going to the following link and running through the steps provided:

Hard Drive Diagnostic Procedure

yupper · Feb 8, 2013

Thanks for the suggestions and links.

After flashing the BIOS and reverting back to catalyst 13.1, I also used MSI Afterburner to increase the auto fan speed to lower the temperature for my GPU during peak performance in Skyrim. I did manage to play for over an hour without issues.

Although my initially reasons for trying the other beta catalyst drivers was not just because I experienced a BSOD after quitting Skyrim when using catalys 13.1, but that I saw some occasional, split second artifacting in the game. That was the reason I tried the other drivers (based on recommendations by some Skyrim players). However, the occasional split second artifacting did not occur with the other beta drivers (but they produced the BSOD during Skyrim). Since reinstalling 13.1, the occasional split second artifacting is back. This must sound confusing...

But the point I am trying to make is that it compounds my own confusion as to whether the problem is the driver(s) or the GPU.

I have SeaTools for DOS burned on CD (SeaTools for Windows won't detect my Seagate sata drive, for some inexplicable reason), I'll run some tests. Meanwhile, given that lowering the GPU temperature seems to have helped mitigate the BSOD issue for now, I was wondering if you can recommend some utilities for real-time monitoring of CPU, mobo, and HDD temperature, so I can see if this might be a heating issue.

Dsprague · Feb 8, 2013

Hwinfo is a great tool also speed fan

yupper · Feb 10, 2013

I experienced another BSOD during Skyrim, and this time the error message was entirely different. Something about 'ndis.sys' (I didn't manage to catch all of it before the OS rebooted). Here's the minidump.

Code:

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


Loading Dump File [C:\Windows\Minidump\021013-33290-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e59000 PsLoadedModuleList = 0xfffff800`0309d670
Debug session time: Sun Feb 10 00:41:38.309 2013 (UTC - 5:00)
System Uptime: 0 days 2:23:25.995
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff88005a43570, 13738b121, fffff80004634910, a}

Unable to load image nvm62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvm62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvm62x64.sys
Probably caused by : nvm62x64.sys ( nvm62x64+55c9 )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff88005a43570, Virtual address for the attempted write.
Arg2: 000000013738b121, PTE contents.
Arg3: fffff80004634910, (reserved)
Arg4: 000000000000000a, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  System

CURRENT_IRQL:  2

TRAP_FRAME:  fffff80004634910 -- (.trap 0xfffff80004634910)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88005a43570 rbx=0000000000000000 rcx=fffff88001901ec0
rdx=fffffa800738e430 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800195ad92 rsp=fffff80004634aa0 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=fffffa8005d6a4b0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
ndis! ?? ::FJGMBFAB::`string'+0x4fa:
fffff880`0195ad92 4885ff          test    rdi,rdi
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7e447 to fffff80002ed7fc0

STACK_TEXT:  
fffff800`046347a8 fffff800`02e7e447 : 00000000`000000be fffff880`05a43570 00000001`3738b121 fffff800`04634910 : nt!KeBugCheckEx
fffff800`046347b0 fffff800`02ed60ee : 00000000`00000000 fffff880`050117a8 00000000`00000000 fffffa80`05dc21a0 : nt! ?? ::FNODOBFM::`string'+0x432fb
fffff800`04634910 fffff880`0195ad92 : fffffa80`0738e560 fffffa80`05efe000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff800`04634aa0 fffff880`05a435c9 : fffffa80`05efe000 fffff880`05a83340 00000000`00000000 00000000`00000000 : ndis! ?? ::FJGMBFAB::`string'+0x4fa
fffff800`04634ae0 fffffa80`05efe000 : fffff880`05a83340 00000000`00000000 00000000`00000000 fffffa80`06001e80 : nvm62x64+0x55c9
fffff800`04634ae8 fffff880`05a83340 : 00000000`00000000 00000000`00000000 fffffa80`06001e80 fffff880`05a5e433 : 0xfffffa80`05efe000
fffff800`04634af0 00000000`00000000 : 00000000`00000000 fffffa80`06001e80 fffff880`05a5e433 fffffa80`06001e80 : nvm62x64+0x45340


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvm62x64+55c9
fffff880`05a435c9 4883a3d807000000 and     qword ptr [rbx+7D8h],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvm62x64+55c9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvm62x64

IMAGE_NAME:  nvm62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48f8fd12

FAILURE_BUCKET_ID:  X64_0xBE_nvm62x64+55c9

BUCKET_ID:  X64_0xBE_nvm62x64+55c9

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

I did recently upgrade to the latest nforce driver for my motherboard (v15.57 for Win7 64bit). Can't be that driver is outdated. Any ideas? Overheating issue likely? Here's a screenshot of my SpeedFan temp readings. Is 'system' the motherboard? Faulty sensor reading? HWInfo also shows the same temperature range for the motherbaord. Is that temperature normal?

Dsprague · Feb 11, 2013

its not over heating its your network driver:

Driver Reference Table - nvm62x64.sys

the usual causes for a 0xBE stop: Device driver, Memory

If you would like to rule out memory problems you can run Memtest86+ for eight or more passes:

RAM - Test with Memtest86+

yupper · Feb 13, 2013

It took a bloody long time but I ran through 8 'passed in Memtest86+. Any other ideas? I've started a support ticket with XFX about my GPU, and their first reply is to basically tell me to perform some of the same test you've already suggested (plus telling me to reseat my CMOS battery....). This will be the first/last AMD GPU I ever buy....

Dsprague · Feb 13, 2013

Did you also update the network dirver that I pointed out? In your last BSOD it was the problem not your GPU.

yupper · Feb 13, 2013

Yeah, I updated the motherboard drivers for network and chipset (15.57). That last BSOD actually occurred after I updated the motherboard drivers.

TVeblen · Feb 15, 2013

It is most likely a bad video card, based upon the tests you have run so far.

But here is my list of diagnostics to try if you want to check and be sure:
(Note: I compiled theses diagnostics about 4 years ago, some things have changed on newer systems, but the process is pretty much the same)

"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected. The solution is in the: why?

There is no one-size-fits-all solution to TDR errors. But the problem is usually found in the local environment (your computer). Finding the cause is a matter of checking every possible cause and uncovering the culprit through a simple process of elimination. By methodically running down a checklist of diagnostic procedures you should be able to find the cause and can correct it.

There are numerous reports of hardware solutions to TDR's. The most common are:

Poor Cooling
Problems with the power supply
Overclocking Issues
Bad System memory or incorrect memory timings
Defective PC Components

The order you do the diagnostics is not all that important. My personal strategy is to do the cheap & easy stuff first, the cheap & harder stuff next, and then the stuff that costs last. But whatever order you do it in you need to check or confirm the following:

SOFTWARE
Poorly written software and games will cause TDRs. But if this were the case it would affect lots of people, not just a few. Check the game's website & forums for patches and tips.
See if other people in the forums are having the same problem and if they were able to solve it and how.
You could also be asking too much of your video card. Check to see if your video card is tested and recommended for the game/program. Test the game at reduced settings.

WHAT ACTIONS CAUSE THE PROBLEM
It helps if you can isolate the actions that trigger the TDR. Most often it will be an application using 3D graphics. But if the incidents occur constantly it would point more towards defective hardware. If it happens more specifically (just when running Game X) it points towards overheating, settings, software, or driver issues.

GENERAL SYSTEM PERFORMANCE
You need to eliminate the possibility that your computer has a global problem. You can use a program like Prime95 to stress test your system. Free Software - GIMPS
You can run the "Stress Test" for a few hours or overnight. This will not tell you what the problem is, but it is helpful to uncover any issues your system has with instability and cooling.

OVERHEATING
Running a video intensive game for hours can generate some serious heat and overheating will cause video errors. You can check your temps by looking at your BIOS readings or use a free program like Speedfan SpeedFan - Access temperature sensor in your computer .
A real easy test is to just pull the side panel(s) off your case (You can also blow a house fan directly into the open case) and see if the problem goes away or gets better. If it does then the issue is definitely overheating. If you are overheating you need to look at installing some cooling upgrades. You want to look at ventilating the case (more or bigger fans), Upgrade your case to a larger gaming case (lots of fans, water-cooling), etc.
There are free utilities like BurninTest PassMark BurnInTest software - PC Reliability and Load Testing that you can use to test your system's cooling capability. Caution is recommended using these types of programs.

VIDEO DRIVERS
Bad drivers happen and they can get corrupted. Before installing or reinstalling any video drivers first completely uninstall all old video software and the drivers. (Some people say to run a cleaner program from safe mode, some say this is unnecessary). Never rely on the driver package to overwrite the old drivers. Also: Delete the video driver folder (ex: C:\NVIDIA) in Windows Explorer (or windows may install the same drivers again!).
After uninstalling the old drivers and rebooting Windows 7 will install it's own WDDM 1.1 driver. Check for the video problem while using this generic Windows driver.
You can then install the latest drivers for your card (or try older drivers).
See This Tutorial: http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html#post414637

DEVICE MANAGER
Look in Device Manager and make sure there are no problem devices (yellow ! icon). Correct these by loading the correct drivers or disable the problem device and see if the video problem goes away.

POOR CONNECTIONS
Reseat video card and memory modules. Make sure the contacts are clean. Check all the electrical connections.

CHECK YOUR MOTHERBOARD VOLTAGES
In BIOS, check the listed voltages against the manufacturer recommended specs. Reset the voltages to factory defaults and see if the video problems disappear.

MEMORY
Memory errors can cause video problems. Run a program like Memtest86+ for at least 3 passes to see if there are any memory errors. Memtest86+ - Advanced Memory Diagnostic Tool .
You can also test for a bad memory module by installing one stick in Slot 1 and testing, and then switch it out for the next stick, etc.
When populating all of the RAM slots on a motherboard it is sometimes necessary to go into the BIOS and increase the voltage to the RAM slightly to obtain a stable system.

OVERCLOCKING
Overclocking can be a trial and error process. The clocks and/or multipliers you set or change for CPU, Memory, or GPU could be unstable. Eliminate this as a possibility by resetting these to their BIOS defaults to see if that clears the video problems. The simplest way to do this is to "Restore Bios Defaults", or “Clear CMOS”.

UNDERCLOCKING
Some people have reported that by going into the video cards control panel and "down-clocking" the cards performance settings they were able to clear up the TDRs. Since W7 does not seem to tolerate any hiccups in the GPU, this would allow you to run a poor performing card in the W7 environment.
So for instance, you could set the GPU clock from a 777 MHz factory setting to 750MHz, and the ram clock from a 1126MHz factory setting to 1050Mhz, or similar small change for your particular card.

BIOS
Check you motherboard manufacturer’s website for an updated BIOS. An updated BIOS may correct an unstable condition, particularly if it says the newer BIOS corrects memory errors or has bug fixes. You could also try loading the BIOS defaults.
Caution is recommended when updating (flashing) a BIOS. The safest way to do so is from the update utility within the BIOS. Follow instructions carefully.
While you are there, check the motherboard manufacturers forums to see if others are having issues with the same board.

WINDOWS POWER MANAGEMENT
Eliminate Power Management settings as a possible cause, especially if you are working with a laptop. These settings could be particularly important if the issue is in playing games.
Go to Control Panel > Hardware & Sound > Power Options. Under "Select a Power Plan" you will find that "Balanced" is the default setting.
At the bottom you will see a Down arrow next to "Show Additional Plans". Click that and select "High Performance". See if the TDR issue is affected.
Alternately, you can click "Change Plan Settings" next to the "Balanced" plan and change the setting to "Never" put the computer to sleep (This is the default on a desktop) and/or change when the display is turned off as a test.

POWER SUPPLY
You need to know that your power supply is delivering sufficient power. Power supply problems are the most common cause of video problems, especially using high end cards.
Check the power supply's amperage ratings. Be sure it has the ample amperage for your video card and the rest of the system.
You can test the supply with multimeter to measure for a steady 12v to the card's power connectors. (The only true way to test a power supply would be to use the very expensive diagnostic equipment used in labs). But for us regular folks: I tested my power supply by hooking up my multimeter to the PCI-E connectors that I was using to power my video card (I used a spare pair from the power supply to run the card while I was testing). I then observed the meter while I used the computer, first watching the voltage, then the amps, to see if there was any drop-off or erratic behavior while booting or using the computer. My readings were rock solid. So I declared my power supply good.
Otherwise you need to replace the supply to eliminate this possibility. Or borrow one from another computer.

VIDEO CARD
I suspect that a video card must perform flawlessly to operate in a Windows 7 environment and run the most recent games. If you tried all the above diagnostics and no problems were found then that leaves you with only one possibility: a defective video card. Some brands and models have the problem more consistently than others. You could check their forums for clues.
You could try your card in another computer running W7 to see if the problem goes along with the card.
You could try a different card in your computer. I bought an inexpensive card to use. My TDR's disappeared using a "lesser" card. Or borrow a card from another computer.
Otherwise RMA or replace the card.

**********
TDR complaints have come from PC owners running virtually every PC configuration. They occur regardless of which video engine, manufacturer, driver, or system used. They are too numerous to write off as a random problem, but at the same time if people are getting their systems to run correctly using the same hardware and software that you are then it follows that your problem must be solvable.

More Info Here:
Timeout Detection and Recovery of GPUs through WDDM
NVIDIA Statement on TDR Errors - NVIDIA Forums
How to troubleshoot

yupper · Feb 15, 2013

Are you sure it's the GPU? The thing is, I reverted back to catalyst driver v13.1, and didn't BSOD during my Skyrim play at all. Instead, if I quit after a long Skyrim session, and launch FireFox, I get the 'attempt to reset driver...' error, exactly like before (whereas the beta drivers I tried never did that, but gave me BSOD -during- Skyrim). I am thinking this is just the poopy catalyst driver acting up? Unfortunately I don't have another game to test. Well I do have other games, but they are old are probably not going to stress the GPU at all.

TVeblen · Feb 16, 2013

No, I'm not sure of anything on your computer. I can't even see it!

It is just a mater of test - test - test. You will discover the problem the usual way: by carefully eliminating every known cause to discover which one is responsible for your problem.

You should not get a TDR error message at all. Having no crash to blue screen is an improvement, but the problem - the video card is not responding as expected - is still there.

In my case (when I first experienced TDRs after installing W7 on a machine that was running XP without problems for months) after researching and testing everything on that list I finally gave in and looked at the video card itself. What I did was buy a $50 video card and tested that in my system. All my problems went away. I RMA'd the GTX260, got a new one, and have never seen a TDR on that computer since.

Perhaps you could borrow a card from a friend's machine to test with?

Dsprague · Feb 16, 2013

Just had a thought what iis the wattage on your PSU?

yupper · Feb 16, 2013

OCZ 600W. I think that's enough for my peripherals?

GPU: 7850 2GB
Mobo: EVGA 750i SLI FTW
Seagate 500 GB HDD x 1
DVD R/W

I was wrong about not getting BSOD during Skyrim while using 13.1 catalyst. I just got one. :/ Blue Screen flashed by so fast I didn't manage to catch the error message.

Mini dump:

Code:

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


Loading Dump File [C:\Windows\Minidump\021613-42447-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02e68000 PsLoadedModuleList = 0xfffff800`030ac670
Debug session time: Sat Feb 16 23:04:25.333 2013 (UTC - 5:00)
System Uptime: 0 days 1:25:28.018
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800472a4e0, fffff88004b04410, 0, 2}

Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+9410 )

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: fffffa800472a4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004b04410, 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: 
atikmpag+9410
fffff880`04b04410 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06dce858 fffff880`04e66000 : 00000000`00000116 fffffa80`0472a4e0 fffff880`04b04410 00000000`00000000 : nt!KeBugCheckEx
fffff880`06dce860 fffff880`04e65d0a : fffff880`04b04410 fffffa80`0472a4e0 fffffa80`06d5c010 fffffa80`06ac9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06dce8a0 fffff880`04f0cf07 : fffffa80`0472a4e0 00000000`00000000 fffffa80`06d5c010 fffffa80`06ac9010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06dce8d0 fffff880`04f3ad5a : 00000000`ffffffff 00000000`000500ea fffff880`06dcea30 fffffa80`06ac9010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06dce9b0 fffff880`04f366af : fffffa80`06ac9010 ffffffff`feced300 00000000`00000000 fffff8a0`00c88000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`06dce9f0 fffff880`04f35023 : fffffa80`06ac9010 00000000`00000002 fffff880`06dceb50 fffff880`06dceb40 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`06dceae0 fffff880`04f352fe : 00000000`00000000 00000000`00000002 00000002`000006a0 fffffa80`045baaf0 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`06dceb10 fffff880`04f082c6 : ffffffff`ff676980 fffffa80`06ac9010 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`06dcebb0 fffff880`04f34e7a : fffffa80`06d5c010 fffffa80`06d5c010 00000000`00000080 fffffa80`06ac9010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06dcecc0 fffff800`0317e34a : 00000000`fffffc32 fffffa80`06b4e760 fffffa80`03cd2890 fffffa80`06b4e760 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06dced00 fffff800`02ece946 : fffff880`009e6180 fffffa80`06b4e760 fffff880`009f0f40 fffff880`01789edd : nt!PspSystemThreadStartup+0x5a
fffff880`06dced40 00000000`00000000 : fffff880`06dcf000 fffff880`06dc9000 fffff880`07c2bd70 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+9410
fffff880`04b04410 4055            push    rbp

SYMBOL_NAME:  atikmpag+9410

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50d21667

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.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: fffffa800472a4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004b04410, 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: 
atikmpag+9410
fffff880`04b04410 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06dce858 fffff880`04e66000 : 00000000`00000116 fffffa80`0472a4e0 fffff880`04b04410 00000000`00000000 : nt!KeBugCheckEx
fffff880`06dce860 fffff880`04e65d0a : fffff880`04b04410 fffffa80`0472a4e0 fffffa80`06d5c010 fffffa80`06ac9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06dce8a0 fffff880`04f0cf07 : fffffa80`0472a4e0 00000000`00000000 fffffa80`06d5c010 fffffa80`06ac9010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06dce8d0 fffff880`04f3ad5a : 00000000`ffffffff 00000000`000500ea fffff880`06dcea30 fffffa80`06ac9010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06dce9b0 fffff880`04f366af : fffffa80`06ac9010 ffffffff`feced300 00000000`00000000 fffff8a0`00c88000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`06dce9f0 fffff880`04f35023 : fffffa80`06ac9010 00000000`00000002 fffff880`06dceb50 fffff880`06dceb40 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`06dceae0 fffff880`04f352fe : 00000000`00000000 00000000`00000002 00000002`000006a0 fffffa80`045baaf0 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`06dceb10 fffff880`04f082c6 : ffffffff`ff676980 fffffa80`06ac9010 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`06dcebb0 fffff880`04f34e7a : fffffa80`06d5c010 fffffa80`06d5c010 00000000`00000080 fffffa80`06ac9010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06dcecc0 fffff800`0317e34a : 00000000`fffffc32 fffffa80`06b4e760 fffffa80`03cd2890 fffffa80`06b4e760 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06dced00 fffff800`02ece946 : fffff880`009e6180 fffffa80`06b4e760 fffff880`009f0f40 fffff880`01789edd : nt!PspSystemThreadStartup+0x5a
fffff880`06dced40 00000000`00000000 : fffff880`06dcf000 fffff880`06dc9000 fffff880`07c2bd70 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+9410
fffff880`04b04410 4055            push    rbp

SYMBOL_NAME:  atikmpag+9410

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50d21667

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

I could try underclocking the GPU in Catalyst Overdrive, but not sure to what speed?

I do have a 'lesser card', but it's an ATI MS4408, so obviously it won't run Skyrim. I did install it to test and works fine on my system.

yupper · Feb 22, 2013

I am still trying to figure out what is causing my BSOD--which has become more frequent. I tried the new 13.2 beta 6 drivers and ever since then it's actually made things worse. Now I BSOD after 5 minutes of Skyrim. First I get artifacting on screen where everything is scrambled, but I can actually still do things like open up the game menu to save the game. Then a freeze lasting about 5 seconds, followed by the BSOD. Afterburner shows that the GPU is not overheating (still around 50 degrees celcius).

I had tried reseating the ram and the card, and that actually seemed to stabilize things for a few days (where I went without any BSOD at all). But then I experienced one today, so upgraded the catalyst driver to 13.2 beta 6, and the BSOD became more frequent. So even after reverting back to 13.2 beta 5, I am still experience BSOD after 5 minutes of playing Skyrim.

So far I've eliminated ram and harddrive, how do I eliminate motherboard as a potential cause of the BSOD? I am not sure if I can get what I need to test the power supply.....

TVeblen · Feb 22, 2013

The best way for a civilian to test a power supply is with a digital multimeter.

You find a spare (unused) power connector from the power supply and connect the red lead from the multimeter to one of the yellow wire pins (12v), and the black lead from the multimeter to one of the black wire pins (ground). Leaving those connections made, you run the computer as normal, watching the reading as you do. That includes shutting down and starting up. You watch to be sure the 12v reading on the multimeter remains relatively steady - it should not deviate from 12.0v more that a tenth of a volt if at all.

Any noticeable drops or spikes in voltage during use indicates the power supply is having troubles.

BSOD "Attempt to reset display driver and recover from time out failed

New member

My Computer

Whisperer in Darkness

My Computer

New member

My Computer

Whisperer in Darkness

My Computer

New member

My Computer

Whisperer in Darkness

My Computer

New member

My Computer

Whisperer in Darkness

My Computer

New member

My Computer

Whisperer in Darkness

My Computer

New member

My Computer

Whisperer in Darkness

My Computer

New member

My Computer

Building Stuff

My Computer

New member

My Computer

Building Stuff

My Computer

Whisperer in Darkness

My Computer

New member

My Computer

New member

My Computer

Building Stuff

My Computer