• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Windows TDR error is back!

M

mellojoe

Gawd
Joined
Mar 19, 2007
Messages
703
:(

Please help! I've tried everything. This is an ongoing, randomly recurring error I've been fighting for years.

  • Now on my second copy of Windows.
  • I'm on my second graphics card. Switched from nVidia to AMD.
  • My second motherboard, switched from DFI to MSI.
  • My second power supply.
  • Second processor.
  • Second harddrive.
  • I have underclocked my graphics card.
  • I have increased cooling. GPU never gets over 50*C.
  • I have updated to newest drivers. I have used beta drivers. I have downgraded to old drivers.
  • I have edited the registry to increase the delay from 2s to 10s.
  • I have edited the registry to turn it off completely.
WHAT DO I DO?

Playing a game, at a random time, the game will just pause. Just everything freezes. Then a moment goes by, then I get an error. "Windows has recovered. AMD driver stopped working and has recovered."

Its called the Windows TDR error. I've searched everywhere, and I'm at my wits end. I honestly thought it was just something that plagued Windows 7. It never happened when I was on XP, and I was a long time XP holdout. Upgraded to 7, and started getting this random error. I really though that Windows 10 would solve it. Here I am on Windows 10, and it immediately started happening again.

For the last several months, I had no problems with it. I had underclocked my GPU and that seemed to help. Upgraded to Windows 10, and within a day, the error came back in the exact same games where it wasn't happening anymore.

Does anybody have any solutions? I'll try anything.
 
You didn't mention CPU Thermals, so case or HSF for overheating on that.
Memory wasn't mentioned either. Have you tried different sticks of memory, or reducing your memory for a while and see how it may affect the system.
 
Disable hardware acceleration in all your browsers might help. I know on 7970/280x series it just has to be done do to whatever. Also what gpu are you using? that may be important. Now since you're having issues...go ahead and try the newest amd driver 15.7.1. uninstall all amd software and use the current ddu to clean out left overs before installing the newest set.

Just for the record i WAS getting them for a short while until i disabled hardware acceleration in chrome and then i got one again when testing for highest usable gpu clocks but havent had one since.
 
I had similar problem with AMD 7950 GPU - issue was caused by too low (default) 2D clocks, but that happened only on desktop (usually when using browser)....

Did you try a clean install of Windows?
 
primetime said:
Disable hardware acceleration in all your browsers might help. I know on 7970/280x series it just has to be done do to whatever.
Click to expand...

That's not true, I have 7970's (Got the first one right when they came out) and have always had all hw accel on, no issues with that.

Honestly OP it sounds like you have a hardware issue. I know you have swapped through a bunch of HW but maybe more than one thing is bad, or it is related to something that hasn't been changed.
 
mellojoe said:
:(

Please help! I've tried everything. This is an ongoing, randomly recurring error I've been fighting for years.

  • Now on my second copy of Windows.
  • I'm on my second graphics card. Switched from nVidia to AMD.
  • My second motherboard, switched from DFI to MSI.
  • My second power supply.
  • Second processor.
  • Second harddrive.
  • I have underclocked my graphics card.
  • I have increased cooling. GPU never gets over 50*C.
  • I have updated to newest drivers. I have used beta drivers. I have downgraded to old drivers.
  • I have edited the registry to increase the delay from 2s to 10s.
  • I have edited the registry to turn it off completely.
WHAT DO I DO?

Playing a game, at a random time, the game will just pause. Just everything freezes. Then a moment goes by, then I get an error. "Windows has recovered. AMD driver stopped working and has recovered."

Its called the Windows TDR error. I've searched everywhere, and I'm at my wits end. I honestly thought it was just something that plagued Windows 7. It never happened when I was on XP, and I was a long time XP holdout. Upgraded to 7, and started getting this random error. I really though that Windows 10 would solve it. Here I am on Windows 10, and it immediately started happening again.

For the last several months, I had no problems with it. I had underclocked my GPU and that seemed to help. Upgraded to Windows 10, and within a day, the error came back in the exact same games where it wasn't happening anymore.

Does anybody have any solutions? I'll try anything.
Click to expand...

What game? Are you using a gaming client? I have never heard of or experienced an issue like this.
 
If you have completely replaced your hardware and reinstalled Windows and it still happens then it's either some type of software you are installing, a setting you change thinking that it's unrelated, or an ambient factor.
 
I did three things tonight:

#1) Increased the virtual pagefile
#2) Deleted and reinstalled soundcard drivers
#3) Deleted and reinstalled MSI Afterburner to ensure my down-clock of the GPU

One of those seemed to work. Haven't had the error.

PS: If you google "TDR error" you'll find a ton of similar experiences, none of them completely solved. Just a bunch of anecdotal evidence.
 
extide said:
That's not true, I have 7970's (Got the first one right when they came out) and have always had all hw accel on, no issues with that.

Honestly OP it sounds like you have a hardware issue. I know you have swapped through a bunch of HW but maybe more than one thing is bad, or it is related to something that hasn't been changed.
Click to expand...

Are you using windows 10 as well? Happened on mine a few drivers back....of course the latest may not have the issue. Regardless a lot people disable it do to the flickers with with what i thought was all of them...but i guess not all of them if you never had to;)
 
mellojoe said:
I did three things tonight:

#1) Increased the virtual pagefile
#2) Deleted and reinstalled soundcard drivers
#3) Deleted and reinstalled MSI Afterburner to ensure my down-clock of the GPU

One of those seemed to work. Haven't had the error.

PS: If you google "TDR error" you'll find a ton of similar experiences, none of them completely solved. Just a bunch of anecdotal evidence.
Click to expand...

I would think afterburner could be causing issues as well since last i checked unwinder hadn't released a win 10 version yet. Personally, I will wait to use it it till he does just to be on the safe side.
 
You could try turning off Timeout Detection and Recovery, but be warned that may cause a hard crash or bluescreen:

Use regedit to set HKLM\HARDWARE\DEVICEMAP\VIDEO\MaxObjectNumber to 0.

Alternatively, you can adjust the timeouts: https://msdn.microsoft.com/en-us/library/windows/hardware/ff569918(v=vs.85).aspx

TDRs happen when a graphics card takes too long to respond to a command. The above are workarounds, not solutions, for your problem.
 
On AMD cards i found turning down the gpu memory speed stopped this from occurring. So if your HD7770 is running at 1125MHz try turning it down 1000MHz using afterburner and if that works then bios mod it. On NVIDIA cards i could never find a solution.
 
Since most things except ram and mass storage was swapped, the cause is probably either software related or related to the two main components remaining from the old system.

It can even be a faulty peripheral that's causing the issues. Not so long ago someone had a USB dock that would crash windows randomly or make it not boot. Too bad the OP didn't perform change one at a time to isolate the cause. Changing pagefile size may have helped due to less aggressive ram use or hard drive fault which cleared when pagefile was resized (and probably rewritten to a new sector). Or it was one of the two other reasons... Now just waiting to see if the problem comes back or not.
 
You must log in or register to reply here.
Back
Top