Computer randomly shuts off, including while idle without BSOD

Kernel-Power Event ID 41 with BugcheckCode = 0, no BSOD, and no dump files usually means Windows did not get enough information to record a stop error. In this pattern, the documented starting point is usually power loss, a hard hang, or another hardware condition that prevents Windows from writing the error or dump to disk.

Since the PSU has already been replaced and memory testing passed, the most relevant next checks are:

1. Check for volmgr Event ID 46 in Event Viewer
   • Open Event Viewer and review the System log around the same timestamps as the shutdowns.
   • If there is a volmgr Event ID 46 (Crash dump initialization failed!), check the page file configuration.
   • The documented cause is that the system may have restarted without a configured dump file. The default dump file is the page file.
2. Treat repeated Event ID 41 with all zeros as a likely hardware path first Microsoft’s guidance for this exact scenario says the symptoms typically indicate a hardware problem, especially when Event ID 41 is missing details or all values are zero.
3. Disable any overclocking
   • If CPU, RAM, or GPU overclocking is enabled, disable it.
   • Verify whether the issue still occurs when the system runs at the correct speed.
4. Re-check memory configuration, not just memory health
   • Even if a memory test passed, verify that all memory modules run at the same speed and are configured correctly.
5. Check for overheating
   • Inspect internal temperatures and look for any overheating component.
   • This applies even if shutdowns also happen while idle.
6. Review the event history around the first failures
   • Filter the System log for 41, 1001, 6008, 1074, 7045 and related reboot history.
   • If 1001 appears, that points to a bugcheck that may have saved a dump.
   • If 1074 appears, that indicates an application or user initiated shutdown/restart.
   • 6008 confirms the previous shutdown was unexpected.
   • 7045 can help identify whether a driver or software installation started shortly before the problem began.
7. If the machine hard-freezes before power-off, treat it as a hang path
   • In this scenario, Windows may be blocked from writing to disk, so Event ID 41 can still show zeros and no dump is created.

What the current evidence suggests:

• Event ID 41 alone does not identify the root cause.
• BugcheckCode = 0 and no dump file means the shutdown is often outside normal Windows crash handling.
• Because the PSU and BIOS were already addressed, the remaining documented areas to isolate are page file / dump configuration, overclocking, memory configuration, overheating, and driver/update timing from the event history.

A practical next sequence is:

1. Check for volmgr 46.
2. Verify the page file is present/configured.
3. Reset any OC/XMP-style tuning to default values.
4. Review System log history for 41/1001/6008/1074/7045 around when this started.
5. Inspect for thermal or other hardware instability.

Avoid editing the Reliability registry values unless specifically needed for shutdown event tracker behavior; that does not fix the underlying restart problem.

References:

• Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"
• Troubleshoot unexpected reboots using system event logs