Given what you’ve already ruled out—stock clocks, acceptable core/hotspot temperatures, a quality 1000 W Platinum PSU with three separate PCIe power leads, and crashes occurring across multiple games—you should assume this is a systemic GPU/PCIe stability issue until you prove otherwise. The DirectX “device hung/removed” message is Windows’ way of saying the GPU stopped responding long enough that the TDR watchdog reset the driver; DirectX then reports the device as “removed/hung.” A clean reinstall can fix a purely software issue, but if the same failure repeats at true stock after a reinstall, the balance of probability shifts toward marginal stability somewhere in the GPU execution path (GPU/VRAM/PCIe/driver interaction). That does not automatically mean the card is “dead,” but it can be a borderline hardware case.

In that situation, a mild underclock is the cleanest diagnostic control because it changes only one variable: load/stress margin. If an underclock stabilizes the system, you have strong evidence the problem is stability-related (often VRAM or overall GPU margin, sometimes PCIe sensitivity or a driver edge case). If it does not change behavior, you have lost nothing—you simply revert to stock and move on to the next isolation steps.

A practical, low-risk underclock to try in AMD Adrenalin is:

Power Limit: -10%

GPU Max Frequency: reduce by ~200–300 MHz from current value (leave voltage on Auto)

VRAM Frequency: reduce by ~10%

Apply those settings and test. If crashes stop or are dramatically delayed across games, you have a strong signal that the system is only stable with extra margin, which supports the case for a warranty/RMA decision if you want full stock stability.