I forgot to mention that I did perform a Windows Memory Diagnostic and it showed up with 0 issues found.
sfc /scannow keeps finding corrupt files and "successfully repairs them" only to find more corrupt files and "repair them" again the next time I run a /scannow
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
So a good amount of the information here I give could be a huge TMI, but here I go anyways.
So the other day I updated my Nvidia driver (GeForce GTX 1070 64-bit) to the latest version, (526.98) and tried to play a game (Doom Eternal) and ended up with a BSOD. However, the BSOD kept appearing over and over again when I restarted my computer, not letting me do anything. So I went back to my old driver, (461.92 NVIDIA Studio Driver). In doing so, I did do a clean install, if that info helps at all. Today, I tried to play a new game (Warzone 2) and it required me to get a newer driver (requirement: 526.86). This driver came with the Nvidia Geforce Experience application. I wanted to optimize my experience with the game to prevent an incident similar to what happened with Doom Eternal. However, when opening Nvidia Geforce Experience, I'm greeted with an error code 0x0001. I've checked my NVIDIA Display container LS, LocalSystem Container, and FrameView SDK services in the services application. They were all working fine. My C and D drives were fine too. So instead I checked if I had any corrupt files using sfc /scannnow (as shown in the screenshot below.) For some more added context, the other day after I reinstalled the older driver, I checked for any corrupt files, and it did show that it repaired the found corrupt files. So you could expect my surprise when I was greeted with another scan result saying the exact same thing. Just in case I checked once more. Same message. Here are the CBS logs for both scans:
https://docs.google.com/document/d/1ePc8nXdKDMAsWQ_k5O3b0z9UMGnRBeU-rnTu6bAKZaI/edit (was too long, don't know why the second CBS logs are so much shorter than this one)
2022-11-24 15:04:40, Info CBS TI: --- Initializing Trusted Installer ---
2022-11-24 15:04:40, Info CBS TI: Last boot time: 2022-11-24 14:39:52.500
2022-11-24 15:04:40, Info CBS Starting TrustedInstaller initialization.
2022-11-24 15:04:40, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:4
2022-11-24 15:04:40, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:5
2022-11-24 15:04:40, Info CBS Lock: New lock added: WinlogonNotifyLock, level: 8, total lock:6
2022-11-24 15:04:40, Info CBS Ending TrustedInstaller initialization.
2022-11-24 15:04:40, Info CBS Starting the TrustedInstaller main loop.
2022-11-24 15:04:40, Info CBS TrustedInstaller service starts successfully.
2022-11-24 15:04:40, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2022-11-24 15:04:40, Info CBS Startup processing thread terminated normally
2022-11-24 15:04:40, Info CBS TI: Startup Processing completes, release startup processing lock.
2022-11-24 15:04:40, Info CBS WU creates the package, AppID:<<PROCESS>>: taskhostw.exe, UpdateID:{F398026B-5FFE-4881-8F09-7C2562D4EF39}, revision: 203
2022-11-24 15:04:40, Info CBS Read out cached applicability from TiLight for package: Package_for_KB5020683~31bf3856ad364e35~amd64~~19041.2304.1.3, ApplicableState: 112, CurrentState:0
2022-11-24 15:06:41, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2022-11-24 15:06:41, Info CBS Ending the TrustedInstaller main loop.
2022-11-24 15:06:41, Info CBS Starting TrustedInstaller finalization.
2022-11-24 15:06:41, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2022-11-24 15:06:41, Info CBS Ending TrustedInstaller finalization.
I will provide some more information as it might be related, or could be a whole separate jar of pickles of its own. My computer struggles to perform a factory reset or a system restore. Both instances of a factory reset or a system restore will result in something going wrong or maybe something preventing these actions from happening and end up changing no files in the end. Could this be related to the constant "repaired" corrupt files? Could it be a virus? Please help me out!
(Microsoft Windows [Version 10.0.19045.2251])
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
4 answers
Sort by: Most helpful
-
Anonymous
2022-11-24T21:20:15+00:00 -
Anonymous
2022-11-24T21:15:39+00:00 I'd say backup your stuff, one of these is required: full (long) format the hard drive (might work) or buy another (best possible outcome), also required following that: then clean install Windows :)
Its very likely that it would be fixed after that. Anything else may be under cooked and only have greater chance for it being not fixed.
Its possible something else could be causing it to happen by a side issue but you may never find it unless you have also done the long format or new drive with the clean Windows install.
I should add that the BSOD could be causing the drive to become corrupted. That would be a side issue. But, you kind of need to rule out the drive itself.
-
Anonymous
2022-11-24T21:28:36+00:00 What are some consequences to full formatting the hard drive? Will all my files be deleted (hence the backup)? Are there any risks?
-
Anonymous
2022-11-24T21:13:01+00:00 Maybe time to use the HD makers free bootable disk checking utility
There's also memtest86 the free bootable memory test utility