- Apr 22, 2008
- 71
- 0
- 18,630
The Problem
A few months ago, my (Dell Pre-built) Win 10 PC was prompted to automatically install a Windows update. At this time, I had updates set to manually install.
However, after that update, my PC began to update, got to about 25% and then segued straight into one of those newfangled Win 10 BSOD error. The stop code: MEMORY_MANAGEMENT. I rebooted. Then again with the error. On the third attempt, Windows had the good sense to revert.
I've been building and/or using PC's most of my life and this was actually new. I'd never had a standard Windows Update on a pre-built machine immediately tank.
I wish I'd kept notes on that original error. I looked online, found a handful of people who had the same issue, and then learned that I could just temporarily tell Windows to not update the particular package. I used the Windows 10 Update Assistant.
Problem solved. Until this morning. I woke to find that Windows was just about ready to reboot and install the update. Without thinking (and because it'd been so long), I just allowed the update to happen. But then our pal BSOD returned. Again, on the third attempt it reverted.
I ended up going through that yet again when I wasn't able to disable the Windows Update process (stop it from Autostarting and Disable if possible). But then, after that I now have an out-of-date-but-actually-usable machine.
Data I've Collected So Far
I searched the web for the least obviously spyware looking advice I could find and avoided any dumb site that told me I need to download some custom tool. I found a link to this page and followed some of the advice.
First, I ran SFC Scanner (sfc/scannow at command prompt) and it got the whole way through the scan. In the end, I received the only solid bit of data that alludes to a direct problem:
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example: C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.
This log-file is included with this post. At least there's something to point at, right? I don't know how to read those things, but I'm pretty sure the phrase "Primitive installers committed for repair" shouldn't appear like a million times in that logfile.
I continued by running the Windows Memory Diagnostic and, after a reboot and running the thing and then returning me to Windows, it told me there were no problems.
Next I started Windows Defender and ran a full scan. After a marathon three hours of that, I got the all clear. No problems found.
After that, I skipped other things on that URL above. Defragging the registry is not the problem. That said, I sure don't know what the problem is outside the barest outlines.
Here's what I linked to:
• CBS Log on 2018-03-10.log - Logfile from my SFC Scanner run
• Computer Dump Info on 2018-03-10.zip - A bunch of other standard msconfig logs.
Any help would be much appreciated. For now, I'm just remaining vigilant and keeping Windows Update disabled. But that is clearly not a long-term strategy. Especially since, every day since, it keeps happening, no matter how much I manually stop it. Eventually, a day later, it'll just pop right back on and the cycle begins again.
This bites.
A few months ago, my (Dell Pre-built) Win 10 PC was prompted to automatically install a Windows update. At this time, I had updates set to manually install.
However, after that update, my PC began to update, got to about 25% and then segued straight into one of those newfangled Win 10 BSOD error. The stop code: MEMORY_MANAGEMENT. I rebooted. Then again with the error. On the third attempt, Windows had the good sense to revert.
I've been building and/or using PC's most of my life and this was actually new. I'd never had a standard Windows Update on a pre-built machine immediately tank.
I wish I'd kept notes on that original error. I looked online, found a handful of people who had the same issue, and then learned that I could just temporarily tell Windows to not update the particular package. I used the Windows 10 Update Assistant.
Problem solved. Until this morning. I woke to find that Windows was just about ready to reboot and install the update. Without thinking (and because it'd been so long), I just allowed the update to happen. But then our pal BSOD returned. Again, on the third attempt it reverted.
I ended up going through that yet again when I wasn't able to disable the Windows Update process (stop it from Autostarting and Disable if possible). But then, after that I now have an out-of-date-but-actually-usable machine.
Data I've Collected So Far
I searched the web for the least obviously spyware looking advice I could find and avoided any dumb site that told me I need to download some custom tool. I found a link to this page and followed some of the advice.
First, I ran SFC Scanner (sfc/scannow at command prompt) and it got the whole way through the scan. In the end, I received the only solid bit of data that alludes to a direct problem:
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example: C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.
This log-file is included with this post. At least there's something to point at, right? I don't know how to read those things, but I'm pretty sure the phrase "Primitive installers committed for repair" shouldn't appear like a million times in that logfile.
I continued by running the Windows Memory Diagnostic and, after a reboot and running the thing and then returning me to Windows, it told me there were no problems.
Next I started Windows Defender and ran a full scan. After a marathon three hours of that, I got the all clear. No problems found.
After that, I skipped other things on that URL above. Defragging the registry is not the problem. That said, I sure don't know what the problem is outside the barest outlines.
Here's what I linked to:
• CBS Log on 2018-03-10.log - Logfile from my SFC Scanner run
• Computer Dump Info on 2018-03-10.zip - A bunch of other standard msconfig logs.
Any help would be much appreciated. For now, I'm just remaining vigilant and keeping Windows Update disabled. But that is clearly not a long-term strategy. Especially since, every day since, it keeps happening, no matter how much I manually stop it. Eventually, a day later, it'll just pop right back on and the cycle begins again.
This bites.
Facebook
Twitter
Instagram