Windows 10: BSOD Upon Automatic Windows Update

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:

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 attached:

• CBS Log on 2018-03-10.zip - Logfile from my SFC Scanner run
• Computer Dump Info on 2018-03-10.zip - The bunch of stuff requested by each poster to this channel

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.

:)

 

Very high CPU Usage for no apparent reason

When the BSOD came, I did change the configuration from automatic memory dump to minidumps, upon initial analysis and searching online it came down to graphic driver, after updating the graphics driver using drivereasy, the BSOD issue was gone but this
constant CPU usage started.

 

after ms updates, booklet not shutting down completely

Recently, I was getting occassional BSODs upon shutting down Windows. Did a restore, and no more BSODs. Have disabled MS updates for the moment.

 

It's happening again. I can't stop Windows Update from going through this madness. It doesn't matter what instructions I follow.

Any help would be appreciated. This is effectively crippling my system.

 

I think I've stopped it. Previously, I disabled Windows Update via services.msc. Some Windows-shaped thing must have triggered it to resume. I might have done it without realizing. Who knows.

But the problem still remains. Any idea how I might be able to stop this?

 

I am still having this problem. I don't know how Windows Update keeps getting re-prompted but it's becoming crazy.

 

I have an active Microsoft Support thread here. Still investigating.

 

Please update us with how you get on. There are no crash dumps to analyse since the dump initialisation fails every time.

On the SFC please note that it can take three runs of this utility before it fixes all the problems.

Memory management errors do not always point to the memory itself being a problem it just means that something has not been managing the memory address space properly and it can be drivers. If you wanted to test your RAM more thoroughly we recommend memtest86+. Details below:





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.

We also have a beta log collector tool (at the end of the BSOD posting instructions) that digs a bit deeper into the system. You could try running that and posting the results.