Windows might be damaged, but your hardware could be the issue.
Windows might be damaged, but your hardware could be the issue.
I've experienced problems for several months after updating Windows. Browser windows would crash, my entire browser would stop working, games would freeze, Windows Defender wouldn't open, and Explorer would hang or become unresponsive. When I went back to an earlier version, the issues disappeared. However, once a new update was forced, they returned. Today the update completed without any rollback option, claiming it had been over 10 days since the change. I decided to perform a system restore, but it failed repeatedly. After some research, I ran sfc /scannow which reported multiple unresolved errors. Various fixes were tried—repairing from a USB drive, formatting the drive in BIOS, and attempting a clean install—but none resolved the issue. The Windows installation kept failing, showing missing files on the USB disc. When using another USB device, the error disappeared for the fourth time. Despite these efforts, my system remained unstable, with persistent problems even after a full reset. I suspect a hardware fault—possibly CPU, motherboard, or RAM—but I'm hesitant to purchase parts without further advice. Appreciate any suggestions or assistance.
Yes, I operate after connecting to the live service. DISM.exe /Online /Cleanup-image /Restorehealth SFC /scannow
Thank you for the response, Fasauceome. I've completed the task. It previously sent a confirmation that it resolved problems, though it no longer does. I hope the logs were saved; the reinstall deleted them.
I don't know the exact solution since many factors could be involved, but it's unlikely it's hardware-related. Try watching some installation guides for a clean setup on a known working system—disconnect your internet and install drivers manually if needed. If your connection was throttled, Windows may prevent updates until you adjust settings.
Usually these problems after an update stem from the update itself rather than hardware faults. Even though a Windows Vista update once, by accident, damaged my motherboard, I’m not sure what caused it. Still, DISM is the most reliable solution, or you could reinstall Windows using the USB installer. You can also remove the update entry in the update history—though success isn’t guaranteed, it worked for me.
I don't think this will actually assist because I reorganized my storage after reinstalling... I've executed "DISM /Online /Cleanup-Image /RestoreHealth" several times. Running "DISM /Online /Cleanup-Image /ScanHealth" now shows everything is fine. Maybe I should attempt a fresh installation, though it's odd that a clean install would still face the same problems later.
Results: User benchmarks show impressive performance metrics. Game performance hit 127%, Desk tasks at 99%, and Work processes reached 117% CPU utilization. Hardware specs include an Intel Core i7-9700K processor, a Nvidia RTX 2080 GPU, and a 500GB Samsung 960 Evo NVMe PCIe M.2 SSD. Storage options feature a Crucial MX500 1TB SSD at 99.8% efficiency, a Samsung 970 Evo NVMe PCIe M.2 500GB at 290%, and an Seagate Barracuda 7200.14 2TB HDD at 80.1%. RAM capacity stands at 2x8GB Corsair Vengeance RGB PRO DDR4 at 3200MHz, achieving 69% utilization. The MBD is MSI MPG Z390 GAMING EDGE AC (MS-7B17). A helpful note: XMP settings need re-enabling. No major surprises found.
Sounds more like the OS is broken or data is corrupt. If you have a blank disk I'd try a fresh install and test drive it for a couple hours and see if you need to do a clean install. EDIT: Skimmed too quick. This smells like it could be RAM if persistent over OS reinstalls. Unslot one of the sticks and check for issues, and see if one is more stable than the other.
... heh... yeah, doesn't look like anything is wrong, except the XMP, but that shouldn't really cause these issues (actually the opposite, unstable XMP could cause these issues) But... i agree with the above post, dont think we have really excluded RAM yet, try with a single stick / in different slots, also running memtest86 couldn't hurt. PS: Also did you check event viewer? It might give some clues... i mean you already tried a lot and we arent really much wiser and theres always a chance event viewer picks something up.