AMD Radeon RX 5600 XT driver keeps crashing and when i try to fix it I keep getting 0x0 errors

neatlyfoldedwind 0 Reputation points
2026-09-09T21:48:54.6466667+00:00

(SORRY IF THIS FEELS REALLY VAUGE AND SUPERFICIAL I HAVE BEEN DEALING WITH THIS FOR MONTHS AND HAVE BEEN TRYING TO FIX IT FOR SO LONG. ASK ME FOR INFO IN THE FORUM AND ILL TRY TO GET IT MY PROBLEM IS I CANT CREATE THIS CRASH CONISISTENTLY NO MATTER WHAT I DO IT OCCURS ALMOST RANDOMLY WHICH MAKES IT EVEN HARDER TO FIND ANYTHING OUT ABOUT IT AND UNDERSTAND IT AND WHY ITS CRASHING/BUGGING.) (GO TO END FOR MORE IMPORTANT INFORMATION)

This problem too horrible but It's not something I want to deal with because i will have actual important things on the side and then: Oh! It's all gone! this problem mainly occurs when I'm on any video game at all.

I will be playing and 1/3 things happen:

1 screen goes black and starts bugging but then Oh! all the sudden it comes back on my game is crashed and everything is slow running literally anything that's not like a wikipedia tab takes like half the cpu and anything beyond that takes it all

or number 2 same bug will occur and screen will go black ill have to unplug my monitor and then plug it back in to get the screen back on (think this happens cause whatever occurs bugs out my monitor)

but again once the screen goes on my game is crashed and everything is slow

or 3 in which screen will go black and it just wont come back on and i have to turn the computer off entirely

(which its pretty obvious why this would be a problem because it gives me a big setback or complete halt from every task I was working on which is real annoying especially when i have something important and didn't save it yet)

but no matter what occurs if i get the computer on doesn't matter just lets me finish my tasks because i get the same few issues:

my AMD Radeon RX 5600 XT in device manager is disabled with a big danger sign near it I look at it and see that my driver isn't working because something along the lines of:

"this driver could not be started because windows could not load the proper drivers"

so i disable and enable the driver and i get error:

Windows has stopped this device because it has reported problems. (Code 43)

It takes like almost all my cpu almost any game you could imagine

(as i said anything that isn't a wikipedia tab takes almost all of it)

i tried a myriad of ways check or fix or see whatever is wrong

id say I've tried like 9 ways to check/fix it (maybe more) of increasing severity so i cant really remember them all sorry

1 deleting and redownloading driver

2 trying to reason with windows updates

3 running a troubleshooter (yeah these first few are pretty stupid)

4 fixing problems with windows update

5 sfc/dism I've scanned now and checked my pc health a billion times now and its not something they could fix also used a few other dism/sfc commands used to clean up all the sorts

6 when the error occurs trying to disable and enable it did not work

7 checking for literally anything in event viewer since currently i am having this glitch i noticed 6 errors occurring right before the crash most being timeouts and somethin about a thing called VendorId (no idea what that is if or if its important but i don't thinkkk??)

these last 3 ones will be the main important ones

8 i tried to go into advanced startup and fix it from there it said it could not do it due to like "a unknown error" it would not tell me what so i checked the logs in command prompt error 0x0 as the reason it couldn't work

9 last time this occurred I made a custom log for it in event viewer just to see what would happen its is something along the lines of

device "device name" had a problem starting driver name oem10.inf problem 0x0 problem status 0xC00000E5 service amduw

(sorry its vague i don't know how to post the logs here being mostly new and don't want to expose any information that i) (shouldn't i can give you any info needed as long as you fix this thank you)

(sorry if most of this post feels like a nothing burger i don't know what the issue is and i'm just dumping like a few months of information hoping for some form of coherence to come out) #windows

Windows for home | Windows 11 | Performance and system failures
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ivan B 123.1K Reputation points Independent Advisor
    2026-09-09T22:27:14.5066667+00:00

    Hii,

    According to what you describe, it is very possible to be a hardware failure with your GPU.

    Search for msinfo32.exe in the search bar, take a screenshot, and post it here so we can see the correct laptop model or desktop configuration.

    Access the c:\windows\minidump folder, copy the files to your desktop, then upload them to OneDrive or Google Drive and post the link here for analysis.

    Thanks

    Was this answer helpful?

  2. AI answer

    2026-09-09T21:49:28.3233333+00:00

    The symptoms match a graphics driver or GPU timeout problem that is leaving the display adapter in Code 43 state after recovery fails. In Windows, this is commonly tied to Timeout Detection and Recovery (TDR), where the GPU stops responding during graphics-heavy work such as gaming, Windows tries to reset it, and the driver may then fail to restart correctly.

    A practical troubleshooting path is:

    1. Update the display driver from Device Manager
      • Open Device Manager.
      • Find the graphics device with the warning icon.
      • Right-click it and select Properties.
      • Open the Driver tab and select Update Driver.
      • Select Search automatically for updated driver software.
      • If Windows finds a newer driver, let it install and then restart.
      • If Windows does not find one, install the latest driver provided by the device manufacturer.
    2. Check whether the crash is a TDR-style graphics timeout
      • The pattern described—black screen during games, recovery attempts, game crash, then degraded performance—matches the documented TDR behavior where Windows reports that the display driver stopped responding and recovered, or bug checks if recovery does not complete.
      • This is especially relevant because the issue happens mainly during gaming.
    3. Use Safe Mode to isolate the graphics driver
      • Go to Settings > Update and Security > Recovery > Advanced startup.
      • Select Restart now.
      • Then choose Troubleshoot > Advanced Options > Startup Settings > Restart.
      • After restart, choose option 4, 5, or 6 for Safe Mode.
      • Safe Mode loads only the minimum required drivers and services, which helps determine whether the normal graphics driver stack is the trigger.
    4. Check for recently added hardware or driver changes
      • If any hardware, driver, or system service was added or changed before this started, remove or update it.
      • Windows bug check guidance specifically calls out recently added drivers, services, and hardware as common causes.
    5. Check Device Manager and Event Viewer after the next failure
      • In Device Manager, review the graphics adapter properties and look for the faulting driver.
      • In Event Viewer, check the System log for critical or error events at the same time as the black screen or crash.
      • This can help confirm whether the display driver is the component failing.
    6. Run Windows Memory Diagnostics
      • In Control Panel, search for Memory.
      • Select Diagnose your computer's memory problems.
      • After the test finishes, open Event Viewer and check the System log for MemoryDiagnostics-Results.
      • Graphics-related crashes can also be triggered by memory instability.
    7. Run the hardware diagnostics from the PC manufacturer
      • This helps rule out a hardware fault in the GPU or related components.
    8. Verify graphics-related software is current
      • Make sure graphics-related software such as DirectX and OpenGL is up to date.
      • Make sure any graphics-intensive applications or games are fully patched.
    9. If Code 43 remains after driver update attempts
      • Code 43 means the driver reported to Windows that the device is not working properly.
      • Microsoft’s guidance is that this can indicate either a hardware problem or a driver/driver software failure.

    About the problem 0x0 entry: the provided context does not define that event value, so the supported conclusion is the more important one: Code 43 on the graphics adapter plus black-screen crashes during gaming points first to graphics driver failure, GPU timeout behavior, or hardware instability.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.