Jump to content

Hi, i built my PC at the start of the year and it was going fine but a couple of months ago I started having my games crashing and the screen would go black for a couple seconds but the sound would still be activethe entire time, after the screen comes back I have the AMD crash toll saying I had the drivers timeout.

 

The issue happens on some games with basically 100% consistency where for exemple on black ops 6 I cant do a single game of nuketown start to finish without crashing meanwhile other games I dont have this problem at all for exemple on dark souls I left it running for hours on end and no crashes.

 

My pc has a 7800x3d, 7800xt and a 750W psu.

 

I've tried everything from using both AMD utility tool and DDU to do a clean install of thr latest drivers aswell as trying older drivers, windows is fully updated, I tried undervolting, deactivating freesync and instant replay, tried going to regestry editor and seting TdrDelay to 10 value, my temperatures are normal...

 

Tomorrow I will try updating my BIOS and completely wiping my SSD and re-installing windows which after that I don't know anything else to try.

 

Anyone here had this problem and fixed it/is it just a bad GPU and should I try to get it replaced or does anyone have other possible solutions that I should try?

 

This was my first PC that I built myself so I'm not that experienced with this specially software stuff, Thanks.

Link to comment
https://linustechtips.com/topic/1614746-amd-driver-timeout-issues/
Share on other sites

Link to post
Share on other sites

Just to note:

 

 

When AMD SW says that there was a driver timeout, it does not mean the card is the issue. It means there was some kind of instability and the driver timed out "just in case" to revert things to default. 

 

Issue can still be unstable RAM or CPU for example. Check those as well. 

Link to post
Share on other sites

8 hours ago, WereCat said:

Just to note:

 

 

When AMD SW says that there was a driver timeout, it does not mean the card is the issue. It means there was some kind of instability and the driver timed out "just in case" to revert things to default. 

 

Issue can still be unstable RAM or CPU for example. Check those as well. 

And how would I go about testing and determining which of the three is causing the problem? 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×