PC Keeps Restarting While Gaming

Record whether the failure is an instant reboot, blue screen, freeze
then reboot, or only a game crash

SAFE

Record whether the failure is an instant reboot, blue screen, freeze
then reboot, or only a game crash.

An instant power cycle without an error points to a different path from a Windows blue screen, but does not prove a bad PSU. A blue screen warrants its stop code and Windows diagnostic context. A game closing to the desktop belongs in the Crashing guide; a machine that stays powered but locks up belongs in Freezing.

Temporarily return CPU, GPU and memory tuning to factory/default
settings

SAFE

Temporarily return CPU, GPU and memory tuning to factory/default
settings. AMD recommends establishing a stock baseline for stability
diagnosis.

If restarting stops at stock settings, a tuning or stability setting is implicated; reintroduce changes singly only after a stable baseline. If it continues at stock, keep that result and check temperatures, event timing and connections instead of assuming a particular component failed.

Monitor CPU/GPU temperatures and clock behaviour under the same gaming
load

CAREFUL

Monitor CPU/GPU temperatures and clock behaviour under the same
gaming load. Use exact manufacturer specifications rather than a
universal temperature number.

If a sharp temperature rise, thermal limit or falling clocks precedes the restart, cooling deserves attention using the exact CPU/GPU model guidance. If readings are normal or absent, heat is not established as the cause; continue with safe connection checks and the failure record.

With mains power disconnected, check motherboard, CPU and GPU power
connections

CAREFUL

With mains power disconnected, check motherboard, CPU and GPU power
connections. Never open the PSU.

If a loose approved external or internal power connection is found, reconnect it only with the PC unplugged and retest. If connectors are scorched, smell burnt or are damaged, stop using the system and seek qualified help. A secure connection does not rule out every power or hardware fault.

Remove avoidable variables such as risers, extension cables and newly
added peripherals while testing

CAREFUL

Remove avoidable variables such as risers, extension cables and newly
added peripherals while testing.

If removing a recent riser, extension or peripheral stops the restarts, reintroduce items one at a time to identify the trigger. If nothing changes, note that result and continue with software/update history or qualified substitute testing.

Install relevant Windows and official chipset/GPU updates

CAREFUL

Install relevant Windows and official chipset/GPU updates. Check
release notes if the problem began after a driver change.

If the problem began with an update, compare the maker’s known issues and supported rollback path before changing more settings. If official updates resolve it, record the version; if restarts persist, the timing alone does not establish a driver cause.

Use Microsoft’s clean-boot process when a background-software conflict
is plausible, then restore normal startup afterwards

CAREFUL

Use Microsoft’s clean-boot process when a background-software
conflict is plausible, then restore normal startup afterwards.

If a clean boot prevents the restart, restore startup items systematically to locate a conflict, then return Windows to normal startup. If it still restarts under the same load, a background service becomes less likely; do not treat that as a hardware diagnosis.

Treat the PSU
as one possibility, not a verdict

ADVANCED

Treat the PSU as one possibility, not a verdict. Known-good
substitute testing is stronger evidence than buying a replacement on
suspicion.

A repeatable power cycle after safe stock, temperature and connection checks warrants manufacturer or technician testing of the complete power path. A known-good compatible substitution provides stronger evidence than buying a PSU on suspicion. Never dismantle or probe a PSU.

Still not fixed?

If the symptom changes between a crash, freeze or restart, use the PC//FIX symptom checker to follow the right path.

Stop repeating the same fixes. Record the hardware configuration,
exact symptom, temperatures or debug codes where relevant, and every
test already completed. Use that evidence to move into the related
PC//FIX guide or contact the component/system manufacturer when
controlled substitute testing or warranty support is required.

How to reduce repeat
problems

Keep Windows and appropriate drivers maintained, keep the PC clean
with sensible airflow, leave storage headroom, use stable settings and
make one hardware or tuning change at a time. A known-good baseline
makes future faults much easier to diagnose.

Frequently asked questions

Should I buy
replacement parts to test the problem?

Not as an early step. Known-good substitute hardware is useful when
you already have it, but buying components at random is expensive
diagnosis.

Should I update the
BIOS as a general fix?

No. Firmware updates should have a specific compatibility, stability
or security reason and must follow the motherboard or system maker’s
instructions.

Can
XMP, EXPO, overclocking or undervolting cause problems?

Yes. Returning to stock is a useful diagnostic test, but it does not
prove the feature or component is permanently faulty.

Should I reinstall Windows?

Only when evidence points to an operating-system problem and less
disruptive checks have been exhausted. A reinstall cannot repair
hardware that fails before POST.

When should I stop
troubleshooting?

Stop for electrical hazards, physical damage, data-loss risk you do
not understand or work beyond your confidence level. Never open a
PSU.