Sudden PC reboots ?
Sudden PC reboots ?
Specs-
CPU: Ryzen 5 7600x
GPU: Zotac SFF Solid RTX 5070 ti
Motherboard: MSI B650M Gaming Plus (BIOS v: 7E24v1B)
RAM: XPG Lancer Blade 2x16gb 6000Mhz CL36
SSD: Kingston SNV3S 1TB; MSI Spatium 512gb
PSU: Cooler Master MWE 850w atx 3.1 (Rated "B" on PSU tier list)
Cooler: Cooler Master Masterliquid ML240L
Issue:
Recently assembled my own PC and have been using it for about three weeks. The only issue I’ve encountered is that the system will reboot completely on its own, without a full shutdown. It tends to happen roughly three times so far.
Additional details:
I’m confident this isn’t due to overheating, as stress tests show both CPU and GPU running under 65°C during full loads. The reboot also occurred while using Davinci, meaning the GPU wasn’t active then. I’ve been monitoring CPU and GPU temperatures constantly during games, and neither reached their maximum power draw when the restarts happened.
My hypothesis:
It might be related to the motherboard, especially the BIOS settings. I updated the BIOS once but opted for the latest stable version instead of the beta release, which was available on the manufacturer’s site. I’m seeking further opinions and would appreciate insights into the possible cause.
Thank you all for your assistance.
After the reboot, access the start menu and enter "event viewer." Launch it, move to system logs, then expand Windows Logs and choose System. Within the System log, search for events near the time of the abrupt restart. This could help identify the cause.
Hi mate, the reboot happened, here is the
System Log
ranging from 2:29pm to 3:00pm. The reboot happened around 2:58 but there are no recent logs right before the reboot. And after the reboot there are logs saying that system was shut down abruptly.
Hope you can have a look and let me, massively appreciate it. Thanks!
Hello,
The log excerpt you shared isn't a sequence of events explaining why the system restarted. It's actually an XML query from the Windows Event Viewer tool. This command instructs Event Viewer to examine the System log for entries with severity levels ranging from Error to Critical (Level 1 to 4) that happened between 3:29 AM and 4:00 AM UTC on November 12, 2025.
To determine the reason behind the reboot, you should review the specific events this query would return. Important points to consider are:
- How to Locate the Reboot Reason in Event Viewer
Here are the main events to check:
1. Identify Shutdown/Startup Times
First, locate the events that signal the start and end of an unexpected session.
- Search for the last clean shutdown (if any):
Look for Event ID 1074 (User-initiated shutdown).
If found, it suggests a normal shutdown, and the reboot was probably scheduled, not abrupt.
- Identify the unexpected shutdown/startup:
Look for Event ID 6008 (unexpected system shutdown). This is your strongest clue of a sudden crash, BSOD, or power failure.
- Check if the event log service started:
Event ID 6005 indicates a system startup.
2. Review Critical Errors Before Reboot
If Event ID 6008 appears, examine the events in the minutes right before the shutdown time.
- Focus on errors with Level 1 or 2 severity:
- Event ID 41 (Kernel-Power): Common after an unexpected shutdown. It often contains details like a BugCheck (BSOD) or power loss.
- Event ID 1001 or similar: May point to a Blue Screen of Death. The code in the description helps identify the crash type.
- Hardware Failures:
Events from devices such as Disk, nvlddmkm (NVIDIA driver), or Storage may signal hardware issues.
Possible Reasons for the Reboot Based on Log Timing
Within the narrow timeframe you mentioned, typical causes include:
- Windows Update: The system downloaded an update and restarted. (Event ID 1074 from "System" process)
- Power Interruption: A brief outage or surge detected. (Event ID 41 without BugCheck code)
- Driver or Software Crash: A failed driver triggered a BSOD. (Event ID 41 with BugCheck)
- System Maintenance: Scheduled tasks or virus scans completed, prompting a restart.