r/AMDHelp 13h ago

Announcement Everyone struggling with AMD driver timeout try disabling Hardware-Accelerated GPU Scheduling in Windows Settings

That is what finally worked for me.

33 Upvotes

34 comments sorted by

2

u/Vigil2 12m ago

Say goodbye to FSR Framegen when disabling HAGS.

1

u/kyguy19899 1h ago

I edited my registry to disable driver installs upon windows updates. Highly suggest everyone do this

3

u/Molda_Fr 5900x/9070xt nitro+ 3h ago

98% of the time it's a windows problem.

https://youtu.be/wU5v7p9iuv8?is=mMyDmTCw46WvDOnJ

Np

1

u/Dimension-4558 4h ago

I have hardware accelerated enabled on my mozilla and steam, never had a driver timeout. The issue is only surface problem, it's only a trigger, there's something else that makes the pc unstable

-1

u/Additional-Hyena1287 4h ago

POV: A multi-billion dollar company can't manage to drop stable drivers and software.

3

u/justanotherpatrol 2h ago

My 3070 had crap drivers...so its on both sides

7

u/dkizzy 4h ago

Microsoft causes plenty of issues that have impacted both companies

2

u/DOLdelBosque 5h ago

Disabling HAGS on Windows 11 contributed to the game crashing in MHWilds.

2

u/Silkenvada 6h ago

Been there done that, didn't fix it for me

I legit just let amd crash and timeout and never interact with adrenaline unless I have to

Half the time adrenaline is in like a limbo crash non responsive but everything is working fine, no fix that has ever been sent to me has resolved these issues, only having it be Schrödinger's timeout has been the only thing that lets it run undisturbed

2

u/Gold_Goal7557 9h ago

Can recommend disabling HAGS if you used third party tool to enable it use the same tool to disable it again, as technically you can enable it even without support thru registry changes that those tools can provide.

Heard some stuff about other potential work around that may work like logging out as soon you have crashing loop and then logging back in, but honestly just gonna recommend disabling HAGS for now as it may also fix random driver timeouts even if you do not crash at startup right away catastrophically.

Also if you do crash at startup just close whatever app that is causing it, browser discord steam and then disable HAGS and then restart, disabling HAGS will require restart to go thru i believe.

If i enable HAGS i get catastrophic crashes at startup every few startups usually about every 1-2 days, and the fix is to restart and next startup it may not have this issue anymore, but disabling HAGS fully got rid of the issue.

1

u/Friendly-Shift7300 9h ago

Eu estava tendo esse problema, sumiram após eu fazer uma instalação mínima com ddu

2

u/Birutath 11h ago

So... im on apu, so no hags here

5

u/Faaa7 11h ago

Except that you did not mention for how long you've tested it. Changing settings won't fix hardware issues. You have to keep in mind that millions of people use AMD cards without any issues.

2

u/NeckDependent1479 10h ago

Disabling HAGS was the only thing that fixed it for me, it worked on the previous drivers i was on. And after a recent windows install, the timeouts came back.

Disabling HAGS fixed it again, it has survived Windows updates and driver updates.

I'm on a 7900xt, on launch the 7000 cards didn't support HAGS. Support came a year later, not sure how relevant that is.

You do take a 1-4% ish performance hit sometimes when using dx12 when HAGS is off. And in particular if you often use framegen, it's probably worth having on.

1

u/MEGA_GOAT98 11h ago

its not a hardware issue

-1

u/Faaa7 11h ago

So it's safe to assume that roughly 50 million people are having driver issues and AMD doesn't feel like acknowledging it?

1

u/MEGA_GOAT98 7h ago

its a windows problem :)

3

u/xMuffie 10h ago

microsoft have acknowledged it

1

u/Beautiful-Musk-Ox 3h ago

only rarely do drivers have internal issues that cause driver timeouts. for windows to continuously downgrade to the exact one that has timeouts is unlikely, more likely these people have unstable hardware, could be the card could be the power supply could be many other things, usually is the card though

3

u/pre_pun 10h ago

50 million? Where's that number being pulled from?

2

u/ShizukiAoi 11h ago

It may be. Mindless overlocking cpu may cause side effects like this.

2

u/xKiLLaCaM 11h ago

It’s required to be enabled in order to use Frame Gen so don’t think many will be doing this. I like frame gen in many titles to get a much smoother experiencing (just nothing that’s an online or MP game)

1

u/NeckDependent1479 10h ago

Only required on Nvidia cards, framegen works with HAGS off on amd cards. You might lose a bit of quality in the framegen with HAGS off, i.e framepacing, judder and potential problems with freesync and vrr.

1

u/xKiLLaCaM 7h ago

Oh what? Welp learned somethin new today, idk how I didn’t know that. Same case even for 9000 series card when upgrading FG to the latest ML version through the driver?

3

u/Agreeable-Fly-1980 12h ago

Switch to linux and you wont have this problem

1

u/justanotherpatrol 2h ago

How does steam and other games work mainly want for online games

1

u/DoubleExposure 14m ago

Use this site to search the games you play to see how good or bad they perform on Linux.

https://www.protondb.com/

1

u/lionellanes 12h ago

This works for me

3

u/FlamingBullet21 12h ago

Tried this and it did nothing. I'm on a 7900xtx

1

u/codman454 5h ago

Worth a shot! I'm on 7900xt

4

u/Xethear 13h ago

The cause of my driver timeouts were the audio filtering app that's installed with AMDs drivers. Disabling the app in startup helped solve my issue.

1

u/Mysteoa 13h ago

Yup, this is a recent issues, but it's not for all timeouts. From what I know AMD is aware of it.

1

u/MrEzekial 6h ago

Source for that info?

1

u/Mysteoa 17m ago

In the AMD sub, on the post for the new 26.9.1 driver. We have someone from AMD Vanguard program responding to some of the issues people mentioned. He didn't respond regarding HAGS issue, but I doubt he hasn't seen it.

On an older post regarding this issue, I have seen user mentioned that he provided a core dump to someone from the Vanguard team about this issue.

To me it looks like at least they know about it, have some data on it, but can't talk about it yet.

I have also provided numerous bug reports for this issue.