1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

AMD Radeon Adrenalin / Windows Update resetting GFX driver nightmare!

Discussion in 'Tech Support' started by 3lusive, 2 Oct 2026 at 12:02.

  1. 3lusive

    3lusive Minimodder

    Joined:
    5 Feb 2011
    Posts:
    1,127
    Likes Received:
    45
    Hi

    AMD Radeon RX 7900 XT with a Ryzen PC below. Current GFX driver is 32.0.31041.1004, and Windows 10 Pro 64bit 22H2, 19045.6466 OS Build.

    Absolute nightmare, my Windows machine below has been updated or something has happened around 7-10 days ago, and now every few hours or even shorter, Windows tries to reset the GFX driver to an incorrect or generic one, which makes the machine literally go blank and I have to restart everything and then switch the GFX driver back to correct in Windows Device Manager.

    Yesterday, I used AMD Cleanup Utility, booted in safe mode, deleted current drivers (but not chipset) and then fresh install, and then today it's doing the EXACT same issue. Soo annoying as I use my comp for work.

    I have tried AMD Cleanup Utility, regedit, deleting current drivers and installing new but something is overriding all and trying this stupid GFX driver swap/reset thing.

    Is this likely coming from AMD software or Windows update? Where do you think the fault lies and what can I do? It's never done this before to my knowledge.
     
  2. 3lusive

    3lusive Minimodder

    Joined:
    5 Feb 2011
    Posts:
    1,127
    Likes Received:
    45
    I used DDU to remove the AMD Radeon drivers, and installed fresh. I thought this had corrected it as it worked fine for nearly 48 hrs, but sadly just now its reset again (switched the driver to another), and when I restarted the PC, it displayed a Radeon error saying: [​IMG]

    AMD software detected that the display driver has failed to load on your system. An issue report has been created that can be set to AMD to help us improve our software. Would you like to report this issue?

    I'm now starting to think it's their faulty drivers causing this and not Windows. Does anyone have any comments?
     
    Last edited: 5 Oct 2026 at 18:39

Share This Page