theagentd
New member
- Dec 18, 2023
- 1
Hello.
Windows Update ran Friday evening last week, after which I shut it down for the update. I booted it up this Monday again, and it started up with a Bluescreen.
It ran startup repair unsuccessfully, and PC remained unbootable. The thing is, I've had this issue a few times before, but startup repair has always succeeded at repairing the PC afterwards. I'm starting to think that this has happened after each Windows Update update I've performed now.
I ran chkdsk, sfc and dism offline through the startup repair cmd window.
- chkdsk ran without any issues over ~45 minutes, with no corrupted files or bad sectors.
- sfc always finds some corruption, but warns that it could not fix everything.
- dism fails at 54.9% every time, with a bit of log diving showing a ERROR_BAD_COMPRESSION_BUFFER as the error.
After running these three, the PC now boots again, but it's very broken. The Start menu does not work, and neither does a bunch of built-in Windows tools, like the Security view, Windows Update, etc, but there doesn't seem to be any problems with any other programs.
I've tried both online and offline versions chkdsk, sfc and dism, offline booted from a Windows 11 installation USB, with the USB used as source for DISM, but no matter what I do I get the same issues. Running dism in read-only/verify-only mode makes it fail somewhere around 90% instead.
I also tried running SFCFix, but it crashes after around 1 second of running (after saying 'y' to everything), with very little in the log. ComponentsScanner reports no corruption.
I have two disks with separate Windows installations (the other is Windows 10) in this computer, and I have had zero issues when using the Windows 10 disk over the weekend, so I believe it's unlikely to be a hardware issue with RAM or other hardware. I have also run the Windows offline memtest on RAM as well.
One (IMO far-fetched) theory is that the original cause of this issue came from moving the PC, which somehow made the problematic NVMe.2 SSD get a bad connection to the slot it's sitting in. This seems unlikely as everything was working fine until it was rebooted, and I believe I've seen the bluescreens before this move. Regardless, I have reseated the SSD just in case this was the issue.
I've attached the logs I can think of here. Any idea of what's going wrong would be greatly appreciated!
Thank you for reading, and best regards
D
PS: I have noted that a bunch of programs report my Windows version as Windows 10...? Opening up cmd shows "Microsoft Windows [Version 10.0.22631.2861]" and the SDCFix log file shows "Microsoft Windows 10 Build 22631 - amd64", yet it's definitely Windows 11.
Windows Update ran Friday evening last week, after which I shut it down for the update. I booted it up this Monday again, and it started up with a Bluescreen.
It ran startup repair unsuccessfully, and PC remained unbootable. The thing is, I've had this issue a few times before, but startup repair has always succeeded at repairing the PC afterwards. I'm starting to think that this has happened after each Windows Update update I've performed now.I ran chkdsk, sfc and dism offline through the startup repair cmd window.
- chkdsk ran without any issues over ~45 minutes, with no corrupted files or bad sectors.
- sfc always finds some corruption, but warns that it could not fix everything.
- dism fails at 54.9% every time, with a bit of log diving showing a ERROR_BAD_COMPRESSION_BUFFER as the error.
After running these three, the PC now boots again, but it's very broken. The Start menu does not work, and neither does a bunch of built-in Windows tools, like the Security view, Windows Update, etc, but there doesn't seem to be any problems with any other programs.
I've tried both online and offline versions chkdsk, sfc and dism, offline booted from a Windows 11 installation USB, with the USB used as source for DISM, but no matter what I do I get the same issues. Running dism in read-only/verify-only mode makes it fail somewhere around 90% instead.
I also tried running SFCFix, but it crashes after around 1 second of running (after saying 'y' to everything), with very little in the log. ComponentsScanner reports no corruption.
I have two disks with separate Windows installations (the other is Windows 10) in this computer, and I have had zero issues when using the Windows 10 disk over the weekend, so I believe it's unlikely to be a hardware issue with RAM or other hardware. I have also run the Windows offline memtest on RAM as well.
One (IMO far-fetched) theory is that the original cause of this issue came from moving the PC, which somehow made the problematic NVMe.2 SSD get a bad connection to the slot it's sitting in. This seems unlikely as everything was working fine until it was rebooted, and I believe I've seen the bluescreens before this move. Regardless, I have reseated the SSD just in case this was the issue.
I've attached the logs I can think of here. Any idea of what's going wrong would be greatly appreciated!
Thank you for reading, and best regards
D
PS: I have noted that a bunch of programs report my Windows version as Windows 10...? Opening up cmd shows "Microsoft Windows [Version 10.0.22631.2861]" and the SDCFix log file shows "Microsoft Windows 10 Build 22631 - amd64", yet it's definitely Windows 11.