Win 10/ Updates/ BSOD's

Hi all.

I've had the Win 10 OS since it came out a couple of years ago. Now, I've had more than one desktop system since Win 10's release, but, I think I've noticed some kind of pattern.

At home, no matter which desktop system I've had Windows 10 on (and it's been three different desktop systems), after a Windows Update, restart, login, sometimes I'll get a BSOD.

I don't mean for this to sound like I receive blue screens ALL the time after every Windows Update, but, that does seem to be when it happens.

And it doesn't have to be a "major" Update. For instance, about a month ago or so, I updated to the Fall Creators Update; no problems. But then the other night, this happened:

Before I go to bed, I usually shut down my computer completely. Well, you know how Windows 10 has that feature where if you don't manually do a restart yourself after an Update, it will wait for your "Inactive Hours" and do an auto reboot. Well, I go to shut down my computer, and I see that it's at the splash screen (the screen where you tap any key, the screen slides up, revealing your Username and the blank field to enter your password). So, it must have done an auto reboot after some updates.

I tap my spacebar, enter my password, it goes to my desktop, and, (I'm a little bleary-eyed, late at night, ready for bed) I see a little tiny template in the middle of my screen and I can see the word "driver" in there, and an "OK" button to click. I click the "OK" button, and, *poof*, BSOD.

My machine rebooted, and everything's fine now.

But anybody else notice this with Win 10? This pattern? That after some kind of Windows Update, you get a BSOD?

And remember: I've had three different desktop systems with Windows 10, and I seem to notice these BSOD's after a Windows Update; not while gaming, or, doing something that demands a lot of system resources, graphically-intense, etc. Just after a Windows Update and logging into the desktop.

Thanks for any help or insight,
Pez

I never experienced the "driver" template that you are encountering; however, after major Cumulative updates, I get the "Oops, your PC ran into a problem and we are collecting diagnostic data and will reboot." It happens ever single time that Windows Update requires a restart. If the updates do not require a restart, the system performs normally.

I honestly believe the "Oops, your PC ran into a problem" is mislabeled and should read "Oops, our OS ran into a problem and your PC is fine."

I have ran diagnostics (built-in PC Doctor/F9 key on boot with my system) after receiving messages like that from Windows that state my PC has ran into a problem only to find that my hunch was correct in assuming that it is more likely an OS problem or glitch.

In all honesty, I believe the super-user administrator account that is automatically generated during a clean install of any build number of a Windows 10 OS, is one of the possible causes of some of these off the wall behavioral patterns of the OS in general.

I just replied to the thread, I didn't start one about BSOD.

OK, I followed the BSOD Posting Instructions; included with my post is the Zip file.
Pez

Can you provide us with the kernel memory dump please? Its located in C:\Windows\MEMORY.DMP.
You can upload it to an cloud service like dropbox or onedrive.

BSODHunter: I navigated to the location you stated: C:\Windows\, and looked for "MEMORY.DMP"; there is neither a file nor a folder by this name.

And just in case you were going to ask, yes, I have Show Hidden Files, Folders, & Drives turned on.

While I was in C:\Windows, I noticed a folder there called "Minidump", but when I opened it, it was empty.

However, were you able to do anything with the info from the program that I ran, the "dm_log_collector"; I posted the Zip file as requested from the article here of "BSOD - Posting Instructions".
Pez

Thanks for the info, axe0; I did as you instructed and ran the SystemInfo tool. I then filled in the info that was not automatically uploaded like you mentioned.

I hope I did all this correct so you can access it, check it out, and then maybe move forward on why I get these occasional BSOD's, especially after some Win 10 Updates.
Pez