F5F Stay Refreshed Hardware Desktop PC restarted during download and the Mobo LED displayed a red light.

PC restarted during download and the Mobo LED displayed a red light.

PC restarted during download and the Mobo LED displayed a red light.

I
Im_Eni
Junior Member
18
12-27-2022, 09:36 PM
#1
My specs are:
Motherboard: MSI B650 Tomahawk WIFI (latest Bios)
RAM: G.Skill X Flare 6000 CL30
CPU: Ryzen 5 7600x
PSU: Corsair RM 850x Shift
GPU: GTX 1050 (my old gpu, waiting till i have the money for new one)
So I built this PC a few days ago and everything worked flawlessly so far. But a few minutes ago I was downloading something on steam and then both my screens went black, the PC rebooted (without windows reboot screen) and the red CPU LED turned on, and was still on while my pc was running again. My WIFI also crashed. (maybe that is somehow connected to the pc crashing?). Now i turned the PC off myself and booted it again and the CPU LED is off now, but I'm still worried about this. Is there any way to find out where this came from and if anything is wrong with my CPU?
I
Im_Eni
12-27-2022, 09:36 PM #1

My specs are:
Motherboard: MSI B650 Tomahawk WIFI (latest Bios)
RAM: G.Skill X Flare 6000 CL30
CPU: Ryzen 5 7600x
PSU: Corsair RM 850x Shift
GPU: GTX 1050 (my old gpu, waiting till i have the money for new one)
So I built this PC a few days ago and everything worked flawlessly so far. But a few minutes ago I was downloading something on steam and then both my screens went black, the PC rebooted (without windows reboot screen) and the red CPU LED turned on, and was still on while my pc was running again. My WIFI also crashed. (maybe that is somehow connected to the pc crashing?). Now i turned the PC off myself and booted it again and the CPU LED is off now, but I'm still worried about this. Is there any way to find out where this came from and if anything is wrong with my CPU?

B
BreakfastLover
Junior Member
3
12-28-2022, 04:08 AM
#2
Check Reliability History/Monitor and Event Viewer.
Both tools might have recorded error codes, warnings, or event data prior to or during the downloads.
Also review Update History for any issues with Windows updates.
View log entries for additional information when needed.
B
BreakfastLover
12-28-2022, 04:08 AM #2

Check Reliability History/Monitor and Event Viewer.
Both tools might have recorded error codes, warnings, or event data prior to or during the downloads.
Also review Update History for any issues with Windows updates.
View log entries for additional information when needed.

M
MrZombie854
Member
58
01-19-2023, 03:04 AM
#3
In Event Viewer there are several critical errors recorded at the time of the crash and shortly afterward. One occurred when I manually rebooted the computer, another happened 4 minutes later, and a normal error from the same period mentions a Windows issue with fastboot and error code 0xC00000D4. It’s possible these relate to fastboot. There are also entries from a few days ago, likely missed because the PC entered sleep mode while I was away, possibly causing the crash during that time. The most puzzling part is that the red CPU LED stayed on continuously after the crash until I restarted the system, even though everything functioned normally afterward.
M
MrZombie854
01-19-2023, 03:04 AM #3

In Event Viewer there are several critical errors recorded at the time of the crash and shortly afterward. One occurred when I manually rebooted the computer, another happened 4 minutes later, and a normal error from the same period mentions a Windows issue with fastboot and error code 0xC00000D4. It’s possible these relate to fastboot. There are also entries from a few days ago, likely missed because the PC entered sleep mode while I was away, possibly causing the crash during that time. The most puzzling part is that the red CPU LED stayed on continuously after the crash until I restarted the system, even though everything functioned normally afterward.

C
coolgirl1566
Member
170
01-20-2023, 05:09 AM
#4
Please note the following:
If everything functions properly, leave it alone.
However, perform these actions:
1) Make sure all critical data is saved in backups at least twice on different locations apart from the current system or affected PC. Confirm the backups can be recovered and read. Build a routine for regular backups.
2) Monitor error codes frequently. Track any shifts in specific errors or total counts. Search for these codes online and record your findings. Minor issues like BSODs, crashes, or device problems require deeper analysis and resolution.
C
coolgirl1566
01-20-2023, 05:09 AM #4

Please note the following:
If everything functions properly, leave it alone.
However, perform these actions:
1) Make sure all critical data is saved in backups at least twice on different locations apart from the current system or affected PC. Confirm the backups can be recovered and read. Build a routine for regular backups.
2) Monitor error codes frequently. Track any shifts in specific errors or total counts. Search for these codes online and record your findings. Minor issues like BSODs, crashes, or device problems require deeper analysis and resolution.