BSOD (Blue screen of death) after Windows updates

ReneM · 03 Apr 2020

On 3 different machines, all with Windows 10 Pro 64-bit installed, I get BSOD for Windows updates.
Blue screen of death usually occurs in connection with the restart.

One machine is brand new, with latest BIOS and drivers.
Everything is the latest, but still BSOD with every Windows update.

Unfortunately, I can't investigate the cause as Windows does not create dump files, nor does a Minidump.
The settings is checked and found to be correct.

Have read somewhere on the Web that it may be because I'm using SSD drive, but I can't see why that could be the reason.

I appreciate any help.

Thanks in advance.

zbook · 03 Apr 2020

Choose one computer per thread.

Open threads in the BSOD forum:
BSOD - Posting Instructions

Make sure the default language is English:

https://www.tenforums.com/tutorials/...dows-10-a.html
Change Display Language in Windows 10

Update the specs in the my computer section:

System Specs - Fill in at Ten Forums
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

.
New computers should not have BSOD > contact the computer manufacturer for Return Merchandise Authorization (RMA)

AddRAM · 03 Apr 2020

Windows Update is working fine so you can rule that out, at least it is over here.

And yes I`d rule out having a SSD installed, that should not matter at all.

Are you able to browse without any issue ?

BSOD on all 3 has to be a clue.

Are all 3 machines activated properly ?

As stated, I`d get on the phone with customer service of the new machine.

jdc1 · 03 Apr 2020

Pick a machine and post the BSOD reports (from the pinned topic) for it.
Test machines in Safe Mode and in Troubleshooting mode. Do they crash there also?

ReneM · 03 Apr 2020

Thanks for the good advice and guides

I have now updated my specifications and created PC number 2, which is my primary computer.

I downloaded the Log Collector V2 and generated a zip file which I attached.
I hope it helps clarify why I can't create either dump or mini dump files for BSOD.
My settings look like this and should be OK.

Attachment 273057

And setting in the registry HKLM \ System \ CurrentControlSet \ Control \ CrashControl registry:

Attachment 272930

I appreciate any help.

Thanks in advance.

zbook · 03 Apr 2020

See instructions post #2.

ReneM · 03 Apr 2020

zbook said:

See instructions post #2.

Hi Zbook

I'm sorry. Really sorry.I will look into it tomorrow.

jdc1 · 03 Apr 2020

FYI - troubleshooting the failure to generate/capture a memory dump is usually an exercise in futility.
Assuming that the settings are correct/default, then most missing dump files are due to:
- hardware failure, or
- crashing too early in the boot process (before the crash logging stuff has fully loaded)

Test with a clean boot ( https://support.microsoft.com/en-us/...oot-in-windows ) to troubleshoot the crashes. In short, if it doesn't crash with a clean boot, then it's one of things that was disabled when setting the clean boot up

If that's the case, then re-enable things a few at a time to see what causes it. It's a long, boring process, but it's the easiest way to isolate the problem.