There seems to be a problem where the system restarts each time an update is applied.
There seems to be a problem where the system restarts each time an update is applied.
Regularly updating Windows 10 often causes a yellow LED on the MB display, requiring a hard restart. After resetting, the update completes successfully. Some users suggest checking the MB BIOS, though I'm not very familiar with software and worry about damaging my system.
MB - Asus Rog Strix B650e-e
CPU - AMD Ryzen 7 7800X3D
RAM - Corsair Vengeance 32gb DDR56000
GPU - Asus Rog Strix 4090 OC
AIO - Asus ROG Ryujin III 360
Memory - (2) Samsung 980 Pro 2TB M.2
PSU - be Quiet! straight power 12 1200W ATX 3.0
Fans - Lian Li UNI fan AL120 v2
Case - Corsair 5000D Airflow
The manual mentions these codes are reserved for future AMI security error messages. Google provided more details, saying it points to an undetected CPU problem or memory, VGA, or other device issues. It suggests clearing CMOS, reinstalling memory and VGA, and removing other devices.
The yellow LED shows the DRAM status. When I had Expo turned on, I needed to reset CMOS once before the computer would reboot even after a forced restart. Without Expo enabled, the boot process still failed when trying to restart manually after updates. I tested booting with each stick separately without problems. No issues arose during a stress test either; the system worked well for a while until this problem appeared.
I plan to check the History/Monitor and Event Viewer. Thank you very much for your assistance.
My event viewer has been displaying numerous error and warning codes recently, along with a few critical ones just a few days ago. The most common entries include various kernel power statistics and several device setup logs. Today during startup, the MB code 40 appeared, suggesting the system woke from hibernation while off. It appears the PC is operating normally despite this code. Unless hardware problems are suspected, updating the MB bios and chipset drivers seems like a reasonable next step. Would you consider updating the bios or chipset first?
Different types of errors and a rising frequency indicate a power supply issue. It may be starting to weaken, possibly because of age or previous heavy usage. It could be close to reaching its End of Life. Alternatively, a single defect might cause the PSU to fail early. Two recommendations: 1) Perform basic maintenance and 2) Replace with a verified working PSU for testing. Before doing either, make sure all critical information is saved at least twice on separate devices away from the PC. Check that these backups are accessible and readable.
Suggestion 1:
Turn off, unplug, and open the enclosure. Remove dust and debris. Confirm everything—connections, cards, RAM, jumpers, and case—is securely attached. Examine with a bright light for damage signs: exposed wires, bent pins, melting, corrosion, discoloration, moisture, cracks, loose screws, scratches.
Suggestion 2:
Replace the PSU with another known functional unit—ensure it provides enough wattage but doesn’t have to be 1200 W. Use only the original cables for the swap. The goal is to limit possible causes and focus on troubleshooting. Keep monitoring Event Viewer and Reliability History for any error codes or patterns. Pay attention to warning and informational events as well.
I examined the system and verified existing connections during troubleshooting to rule out a ram module problem. I plan to repeat the process and contact bequiet to confirm if any warranty remains for the PSU. My finances are very limited at the moment, and work progress is slow, so I don’t have the funds to purchase a replacement PSU. Despite this, as an electrician I might be able to test it myself. The first boot occurred on 5-13-2024; unless there’s a fault or premature shutdown, nothing should be near end-of-life. The computer is primarily used after work for gaming and video watching, so it receives less use than a home-based setup. The warning and info sections in the event viewer are particularly problematic, showing 422 warnings in the last week and 2808 info updates recently. The most common entries are:
- ID 112 DeviceSetupManager (222 in the past week)
- 400 PowerShell (69 in the past week)
- 403 PowerShell (69 in the past week)
- 600 PowerShell (414 in the past week)
Clicking on 600 reveals:
Engine State is changed from Available to Stopped
NewEngine State=Stopped
PreviousEngineState=Available
"HostApplication=Powershell.exe - execution policy - command function test- device running known bad driver { param ($intelDisplayAdapters) $driverVersionMatch = $false; $chipsetSeriesMatch = $false"
It provides more details but is confusing because it keeps referencing Intel, Intel graphics, and Tiger Lake hardware identifiers, which contradicts the fact that the build doesn’t include Intel components.
As an electrician familiar with using a multi-meter,
Please note:
This isn't a complete test since the PSU isn't under load.
But any voltages outside tolerance raise suspicion about the PSU.
If a device or component isn’t getting or receiving enough power—either not at all or sporadically—the system will likely fail when that part is used.
Regarding the strange references: they might indicate incorrect drivers, damaged or faulty drivers, or counterfeit products.
The main goal is to identify possible causes quickly through direct inspection or elimination.
Looking great overall. Thank you for your help so far; I'll check the PSU later tonight. Could it be a virus or something similar?