ProblemThis guide covers a PC that loses power and stays off. If it returns to the boot logo by itself, use the gaming restart guide; for a blue screen, retain its code; if only the game closes while Windows remains active, investigate that game. Do not provoke another shutdown to classify it.

PC shuts down while gaming

The PC stops during a game and does not restart on its own. Distinguish loss of power from a display that merely goes black. Power and cooling need investigation, but a shutdown alone does not prove a bad PSU.

Try this first

1 quick checks · ~2 min

  1. Clear external airflowDo not keep gaming to try to confirm overheating.

Find your situation

See all the clues. Choose the one that matches what you observe.

Diagnostic signals

ObservationThe PC stays off
If the game and audio continue and only video disappears, investigate the display path. Returning to the boot logo on its own is a restart.
ObservationFailure follows a period of use
A relationship with load or ventilation is a reason to check cooling, not a substitute for measurement or proof of a failed part.
ObservationOne game versus several workloads
Use existing observations: one game first points toward its workload/software pattern; several demanding programs broaden suspicion to the system, without proving the PSU.

Step-by-step solutions

01

Clear external airflow

Do not keep gaming to try to confirm overheating.

  1. Stop the demanding workload and keep case air intakes and exhausts clear. Do not run the PC covered or enclosed.

  2. With the PC off and unplugged, look for blocked vents from outside. Follow its manual for cleaning; do not insert objects or open the PSU.

Sources:
02

Check external power

Rule out a damaged external cable or connection.

  1. Turn the PC off and unplug it before checking the external power cord. Do not use a damaged cord or loose connector.

  2. If there are no signs of damage, check with a known-working outlet or known-compatible external power cord. Ask a professional if the electrical installation is in doubt.

Sources:
Advanced

Advanced checks

Continue if the earlier steps did not help. Read each procedure’s precautions first.

03

Compare the correct metric without forcing load

  1. If the PC remains stable at idle, use an already available official tool without adding load. Retain CPU, GPU, sensor name and whether the reading was at idle or in-game. A reading after restarting does not represent the temperature before shutdown.

  2. Compare CPU readings with the exact processor specification and GPU readings with that card manufacturer’s specification. Core temperature, junction/hotspot and another model’s limit are not interchangeable. Reaching a limit can trigger throttling; it does not by itself prove it caused shutdown.

  3. With already recorded abnormal readings, blocked ventilation or suspect cooling, prioritize thermal review. Without comparable data, keep the hypothesis open and request review instead of starting a stress test. If it shuts down at idle or coolant leaks, stop using it.

04

Review the prior change with recovery prepared

  1. Record whether it began after changing GPU, RAM or CPU, or enabling XMP/EXPO, overclock or undervolt. Those profiles are not standard settings. If related, ask the manufacturer or technician to revert only the changed setting following the manual; do not load global BIOS defaults or try voltages.

  2. If restoring the previous configuration leaves it stable during normal use, configuration/compatibility becomes more suspect; it does not necessarily identify faulty RAM or PSU. If it shuts down again, stop the workload and request assessment. Do not repeat games or stress tests to confirm.

05

Prepare a power review with useful data

  1. From documentation, gather PSU model and age, CPU/GPU and recent upgrades. Shutdown across several workloads or after a new GPU justifies a technician reviewing capacity, connections and condition; printed wattage does not establish quality or condition.

  2. In Event Viewer > Windows Logs > System, retain events near the already known time. Kernel-Power 41 confirms unclean shutdown, not a defective PSU. If WHEA-Logger appears, retain its details for support; an isolated corrected event does not automatically identify the part that caused shutdown.

  3. Absence of WHEA does not exclude hardware: abrupt power loss may leave no useful record. If only one game fails, include its version and workload timing; if several fail, say so without running more. Avoid buying a PSU based only on that pattern.

Next step

Still not working?

If shutdowns recur, stop gaming and request review with the prior pattern, configuration, available readings and events. A next step must distinguish a specific hypothesis; repeating shutdown only exposes data and hardware.

Sources

Documentation behind this guide. Editorial recommendations are identified separately.

Source review: . A documentation review, not a physical hardware test.

Related problems