Question Issue with restart every time I update?

[BML415]

Every time I run an update for Windows 10 my computer throws a yellow led on the mb and I have to hard restart. After the reset it will finish update and run normally. Does anyone have any insight?

My only idea is maybe I need to update the MB bios but I am not very experienced with software and I am too scared to brick or corrupt my PC.

 

[rgd1101]

full system spec? include brand and model of the psu

 

[BML415]

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

 

[Ralston18]

Look in the motherboard's User Guide/Manual to determine the meaning of that yellow LED.

Look in Reliability History/Monitor and Event Viewer to determine if Windows is capturing any error codes, warnings, or even informational events just before or at the times when you were forced to restart.

 

[BML415]

Look in the motherboard's User Guide/Manual to determine the meaning of that yellow LED.

Look in Reliability History/Monitor and Event Viewer to determine if Windows is capturing any error codes, warnings, or even informational events just before or at the times when you were forced to restart.

The manual only says "reserved for future ami sec error codes". Google was a little more specific, "Indicates an undetected CPU or potential issues with memory, VGA, or other devices. Clear CMOS, re-install memory and VGA, and remove other devices".

The yellow led is the DRAM indicator. I had expo enabled and had to use cmos once when I couldn't get the computer to reboot even after a forced restart. With expo disabled the computer boots but still has the issue when self restarting after updates. I tried booting with each stick individually but had no issues there. Also didn't have any issues with a stress test. The system was completely fine for awhile before this issue started to occur.

I will dig into the History/Monitor and Event Viewer. Thanks for the help its greatly appreciated.

 

[BML415]

Look in the motherboard's User Guide/Manual to determine the meaning of that yellow LED.

Look in Reliability History/Monitor and Event Viewer to determine if Windows is capturing any error codes, warnings, or even informational events just before or at the times when you were forced to restart.

My event viewer has been showing a LOT codes in the error and warning section and a couple in the critical just happened a few days ago.
Crit
- 41 Kernel power (1 times last 7 days)
- 142 Kernel power (1 time last 7 days)
Error (these are the most frequently experienced)
- 2 kernel event tracing (17 times last 7 days)
- 3 kernel event tracing (11 times last 7 days)
- 131 device setup manager (55 times last 7 days)
- 1010 modern deployment diagnostics provider (119 times last 7 days)
- 1796 tpm-wmi (13 times last 7 days)
- 10010 distributedCOM (33 times last 7 days)

There are more codes but these are the most frequently reoccurring

Today on startup the mb code 40 popped up which indicates waking from hibernation/sleep state but the pc was off. System is running normally but shows that code.

Unless there's a issue with the hardware itself I'm thinking a MB bios and chipset driver update might be the next step? Thoughts? Would I update the bios or chipset first if that seems like a good move?

 

[Ralston18]

Varying errors and increasing numbers of errors suggest a PSU problem. Perhaps starting to falter and fail due to age, history of heavy use. Simply nearing its' designed in EOL (End of Life).

Or perhaps some defect bring the PSU to a premature end.

Two suggestions: 1) Some "house keeping" and 2) Swap in a known working PSU for test purposes.

Before doing either ensure that all important data is backed up at least 2 x to locations away from the PC in question,. Verify that the backups are recoverable and readable.

Suggestion 1:

Power down, unplug, open the case.

Clean out dust and debris.

Verify by sight and feel that all connections, cards, RAM, jumpers, and case connections are fully and firmly in place.

Use a bright flashlight to inspect for signs of damage: bare conductor showing, pinched/kinked wires, melting, corrosion, browned or blackened areas, moisture, cracks, loose or missing screws, scratches....

Suggestion 2:

Swap in another known working PSU - verify that the PSU has sufficient wattage to support the build but does not necessarily need to be 1200 W.

Be sure to use only the cables that come with the swapped in PSU.

The objective simply being to narrow down the list of potential culprits.

Continue watching Event Viewer and Reliability History for any changes: error codes and frequencies.

Warning and informational events are meaningful as well.

 

[BML415]

Varying errors and increasing numbers of errors suggest a PSU problem. Perhaps starting to falter and fail due to age, history of heavy use. Simply nearing its' designed in EOL (End of Life).

Or perhaps some defect bring the PSU to a premature end.

Two suggestions: 1) Some "house keeping" and 2) Swap in a known working PSU for test purposes.

Before doing either ensure that all important data is backed up at least 2 x to locations away from the PC in question,. Verify that the backups are recoverable and readable.

Suggestion 1:

Power down, unplug, open the case.

Clean out dust and debris.

Verify by sight and feel that all connections, cards, RAM, jumpers, and case connections are fully and firmly in place.

Use a bright flashlight to inspect for signs of damage: bare conductor showing, pinched/kinked wires, melting, corrosion, browned or blackened areas, moisture, cracks, loose or missing screws, scratches....

Suggestion 2:

Swap in another known working PSU - verify that the PSU has sufficient wattage to support the build but does not necessarily need to be 1200 W.

Be sure to use only the cables that come with the swapped in PSU.

The objective simply being to narrow down the list of potential culprits.

Continue watching Event Viewer and Reliability History for any changes: error codes and frequencies.

Warning and informational events are meaningful as well.

I went through the system and checked connections already when I was trouble shooting to eliminate that it might be a ram module issue. I will go through it again and I'll reach out to bequiet to see if I have a warranty of any kind still for the PSU. Finances are really tight for me right as work is super slow so I don't have the spare money to buy a PSU to swap in. I am an electrician however so maybe I can test it. First boot was 5-13-2024 so nothing should be close to EOL at this point unless faulty or premature. Computer is only used after work for gaming and watching videos so it doesn't have a lot of use compared to a work from home type rig.

The warning and info sections on event viewer are even worse than the others. 422 warnings in last 7 and 2808 info in the last 7 days. The most frequent ones:
ID 112 DeviceSetupManager (222 in the last seven days)
400 PowerShell (69 last 7 days)
403 PowerShell (69 last 7 days)
600 PowerShell (414 last 7 days)

When I click on the 600 it says:
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 says a lot more but its strange because it keeps referencing Intel, Intel graphics and Tiger Lake hardware ids which has me super confused as nothing in the build is Intel.

 

[Ralston18]

As an electrician you have and know how to use a multi-meter.

FYI:

https://www.lifewire.com/how-to-manually-test-a-power-supply-with-a-multimeter-2626158

Not a full test because the PSU is not under load.

However, any voltages out of tolerance make the PSU suspect.

If any given device or component is not getting/receiving the required power (either not at all or intermittently) then when the system attempts to use that device or component errors will occur.

As for the strange references: could be the wrong drivers, corrupted or buggy drivers, counterfeit/fake products.

Key is to narrow down potential culprits directly or by elimination.

 

[BML415]

As an electrician you have and know how to use a multi-meter.

FYI:

https://www.lifewire.com/how-to-manually-test-a-power-supply-with-a-multimeter-2626158

Not a full test because the PSU is not under load.

However, any voltages out of tolerance make the PSU suspect.

If any given device or component is not getting/receiving the required power (either not at all or intermittently) then when the system attempts to use that device or component errors will occur.

As for the strange references: could be the wrong drivers, corrupted or buggy drivers, counterfeit/fake products.

Key is to narrow down potential culprits directly or by elimination.

Right on good looking out. I greatly appreciate you taking the time to assist me thus far. I'll dive into the PSU later this evening. Is it possible it might be some sort of virus etc.

 

[Ralston18]

Virus/malware?

Cannot exclude that barring some specific negative scans via Windows Defender/Security or other Anti-AV app.

Caveat being some "zero-day" infection. Unlikely but cannot be excluded however unlikely.

In the meantime be sure to back up all important data at least 2x to locations away from the system in question.

Verify that the backups are virus free, recoverable, and readable.

 

[BML415]

Virus/malware?

Cannot exclude that barring some specific negative scans via Windows Defender/Security or other Anti-AV app.

Caveat being some "zero-day" infection. Unlikely but cannot be excluded however unlikely.

In the meantime be sure to back up all important data at least 2x to locations away from the system in question.

Verify that the backups are virus free, recoverable, and readable.

PSU voltages all tested perfect while not under load. At least the system got a full re-plug and cleaning.

The virus/malware stuff really out of my league when it comes to what to do or trust it was just something I read on a forum. Dude was talking about using Microsoft autoruns on youtube. Do you have any advice in that realm?

Same with making a backup and checking if its recoverable and readable. I'll have to do some reading and watch some videos because I have no clue there. There's not much on my system except games so nothing really important data wise. A bios and chipset update might be the move, The system used to restart no issue but now never does, just throws the yellow dram led and 0d code requiring a hard restart. This only happens when restarting. If its not bios or chipset maybe I nuke the system and start over 100% fresh everything? I can't lie, not knowing if its software or hardware is pretty overwhelming atm.

Checked my bios version and I'm currently on 2613 and the current is 3222. I can only assume the chipset is just as out.

 

[Ralston18]

Run Microsoft's built in Windows Defender/Security. Overall that is very much the only AV/malware software that is needed. However many people, myself included, also use free Malwarebytes from time to time when something seems amiss. Just be sure that you go directly to Malwarebytes' website. Not some website that pops up via a search.

= = = =

After reading back, I am wondering about "modern deployment diagnostics provider".

Could be buggy and/or corrupted.

I suggest that you run "dism" and "sfc /scannow" to find and fix buggy or corrupted files.

FYI:

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

The immediate objective simply to continue narrowing down possible reasons for the restart problem.

 

[BML415]

Below are the logs after running dism and then sfc. After it fixed the corrupted files I attempted restart and it did the typical dram light and 0d code. Being stuck in that state I did hard restart after that and noticed it finally didn't restart with the other 40 code I was also getting. Seeing this I attempted another restart and everything booted as normal. I don't know if everything is fixed at this point but I cannot express enough my gratitude and appreciation for you to take all this time out to help me get to this point. I feel like this is a big step and I would have never figured this much out without you.

I will be keeping an eye on Event Viewer and restart status going forward to see what else might still need to be addressed. Thank you, again for helping me. My pc knowledge is only hobbyist level at best and all self taught through the internet and youtube and trying to figure this out I have learned a lot. Somewhat stressful but also a bit enjoyable.

Microsoft Windows [Version 10.0.19045.5737]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>dism /online /cleanup-image /restorehealth /source:e:\sources\install.esd

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.5737

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

 

[Ralston18]

@BLM415

Glad it seems to be working out.

There is always more to learn - me included.

Just keep "working" at it all - but at an enjoyable level.