Write down the pattern
Under load, at idle, after ten minutes, only in one game, only after a cold start. A shutdown under load points at power or cooling; a shutdown at idle points at firmware or a failing board.
A machine that dies without a blue screen is usually losing power, not crashing. The event log, the pattern and four swaps tell you which part is at fault.
Note **when** it dies, read the **Event Viewer** for a Kernel-Power 41 entry, turn off **automatic restart** to see the bug check, then test **power delivery, cooling and RAM** in that order.
Under load, at idle, after ten minutes, only in one game, only after a cold start. A shutdown under load points at power or cooling; a shutdown at idle points at firmware or a failing board.
Kernel-Power 41 means the machine lost power without a clean shutdown. It is a symptom, not a diagnosis, and the entry above it in the list often names the real cause.
eventvwr.msc > Windows Logs > System > Filter: Critical
With the restart disabled, a real crash stops on the blue screen and shows a bug check code. That code separates a driver problem from a hardware fault in one reboot.
System Properties > Advanced > Startup and Recovery > uncheck Automatically restart
Separate PCIe cables instead of one daisy chain, a different wall socket, and no cheap extension lead. A power supply that trips its protection cuts the machine with no log entry at all.
Ten minutes of CPU load, then ten of GPU load, then both together. Whichever run reproduces the shutdown narrows the fault to that part or to the power that feeds it.
One RAM stick, no discrete GPU if the CPU has integrated graphics, one drive. A machine that stays stable in that configuration is a parts problem, and adding them back finds it.
Power. Either the supply trips or the board loses standby voltage. Swap the unit before anything else.
A transient load spike, or a driver resetting the GPU. Check the graphics driver and lower the power limit as a test.
A firmware power state or a memory profile that is unstable at low load. Load the default firmware settings and retest.
Now you have a code. Look it up before you change hardware again; it may be a single driver.
No. It records that the previous shutdown was not clean. The cause sits above it or outside the log.
Yes, and a failing extension lead with a switch does it more often than the socket itself.
Re-enable **Automatically restart** once the machine is stable again and reinstall any part you removed. Nothing on the disk is modified by the diagnosis.
Free · no account needed · tracks your progress