Question New RX9070 Constant Crashes, Not sure how to diagnose.

Welcome to the forums, newcomer!

Gigabyte b850m Gaming X Motherboard
+
Update BIOS
For the sake of relevance, please state the BIOS version you're on for your motherboard.

Re-install windows
In offline mode, after recreating your bootable USB installer for your OS?

If you haven't disable the iGPU in BIOS. Following that, use DDU to remove all GPU drivers(intel, Nvidia and AMD) in Safe Mode, then manually install the latest GPU driver sourced from AMD's support site in an elevated command, i.e, Right click installer>Run as Administrator.

Try and uninstall any anticheat app's on your platform or reinstall your games, one game at a time until you encounter the issue.
 
Hi Lutfij!

To answer your questions,
  • BIOS Version: F4a (updated OP)
  • I have re-installed windows in offline mode
  • I have disabled iGPU.
  • I have used DDU to remove all drivers and ran the installer for the latest AMD drivers from the AMD website as Administrator.
  • I have no anticheat apps installed currently.
 
Last edited:
looks like windows error reporting was debugging your problem before you wiped the system.
C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20250531-1836.dmp

VIDEO_TDR_TIMEOUT_DETECTED

basically something was not responding, and it was being debugged.

if you still have the file we can take a look at it in the debugger.

most likely it was your gpu not responding but it could be some other device we can not tell without looking a the dump.

I would change the memory dump type to kernel and just wait for the next bugcheck. if you get one then copy memory.dmp file to a server and post a link.

you have already done the general fix attempt
(update bios, and drivers) hopefully that will take care of the problem.
 
looks like windows error reporting was debugging your problem before you wiped the system.
C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20250531-1836.dmp

VIDEO_TDR_TIMEOUT_DETECTED

basically something was not responding, and it was being debugged.

if you still have the file we can take a look at it in the debugger.

most likely it was your gpu not responding but it could be some other device we can not tell without looking a the dump.

I would change the memory dump type to kernel and just wait for the next bugcheck. if you get one then copy memory.dmp file to a server and post a link.

you have already done the general fix attempt
(update bios, and drivers) hopefully that will take care of the problem.
I can do this as soon as I get home.
 
I can do this as soon as I get home.
this file might also be interesting:
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.90692e6e-91a6-4973-83e7-0fe8658e00a5.tmp.txt

if you still have it. I think it will show the windows error reporting debugging session. if so then you can see what microsoft auto debugging bots thinks the problem is.

do set your memory type to kernel, and it will catch proper debug info for this type of error.
 
this file might also be interesting:
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.90692e6e-91a6-4973-83e7-0fe8658e00a5.tmp.txt

if you still have it. I think it will show the windows error reporting debugging session. if so then you can see what microsoft auto debugging bots thinks the problem is.

do set your memory type to kernel, and it will catch proper debug info for this type of error.
Not entirely sure how to set it to that, but I am going to try to figure it out. Will report back in a bit.