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.
Virus or malware?
It’s not possible to rule it out completely except for certain negative scans through Windows Defender/Security or other anti-AV applications.
There’s a possibility of a zero-day infection, which is unlikely but not impossible.
In the meantime, make sure to back up all important data at least twice in locations separate from the affected system.
Check that the backups are free of viruses, recoverable, and readable.
PSU voltages all checked perfectly without load. At least the setup was completely re-plugged and cleaned. The virus/malware situation is really beyond my experience, especially when it comes to deciding what to do or trusting anything I read online. Someone mentioned using Microsoft autoruns on YouTube—any advice there? Also, making a backup and ensuring it’s recoverable and readable sounds important. I’ll need to research more and watch some tutorials because I’m not sure what I’m dealing with. My system mostly has games, so there isn’t much critical data left. A bios and chipset update might be the best option. The system would normally restart without issues, but now it keeps restarting with a yellow error message and a hard restart being necessary. This only happens during a restart. If it’s not related to the BIOS or chipset, maybe I should reset everything and start fresh at 100%. Honestly, I’m really unsure if it’s software or hardware that’s causing this.
Run Microsoft's built-in Windows Defender/Security. This is generally the sole antivirus/malware solution required. Still, many users, including myself, occasionally rely on free Malwarebytes when issues arise. Make sure you visit Malwarebytes' official website directly, not any third-party site that appears in search results.
= = = =
After reviewing this again, I’m considering a "modern deployment diagnostics provider." It might be faulty or damaged. I recommend executing "dism" and "sfc /scannow" to locate and resolve any corrupted files.
For reference:
https://www.windowscentral.com/how-use-d...s-10-image
https://www.lifewire.com/how-to-use-sfc-...es-2626161
The main goal is to further pinpoint potential causes behind the restart problem.
The logs following the dism and subsequent sfc execution show the process after resolving the corrupted files. After restarting, it displayed the usual error messages and 0d code. Stuck in that condition, I performed a hard restart, which finally stopped the recurring issue with the other 40 codes. I tried another restart afterward and everything functioned normally. Although uncertain if everything is fully resolved, I am deeply grateful for your assistance. This represents a significant improvement, and I wouldn’t have solved it without you.
I will continue monitoring Event Viewer and the restart status moving forward to identify any remaining issues. Thank you once more for your support. My technical skills are limited to hobbyist level, developed through self-study on the internet and YouTube, and I’ve gained a lot from this experience. It was somewhat stressful but also quite rewarding.
Microsoft Windows [Version 10.0.19045.5737]
© Microsoft Corporation. All rights reserved.