BSOD errors reported on Windows 10 April Update

Madalina Dinita
by Madalina Dinita
Managing Editor
3 Comments
Download PDF
Affiliate Disclosure

BSOD windows 10 april update

Just a few days before Microsoft launched the long-awaited Windows 10 April Update, we gave you a word of warning about the potential BSOD errors that you may encounter after installing this update.

As a quick reminder, frequent BSOD errors delayed the initial Windows 10 version 1803 release, so the chances that the problem transferred to the final OS version were pretty high.

Well, we hate to be right in such cases, but recent user reports confirm that BSOD errors may sometimes affect the Windows 10 April Update.

I have been having frequent BSOD errors after installing the recent update. There have been a few different stop codes, which I unfortunately didn’t catch, but the most common is CRITICAL_PROCESS_DIED. Strangely, Windows is not generating dumps of any kind. The percentage counter on the BSOD screen never increments beyond 0% before the PC shuts down. I checked the debugging info, and it is indeed set to create minidumps, but the directory doesn’t even exist.

Simply clicking and opening various built-in apps may trigger this error. The CRITICAL_PROCESS_DIED error may also appear out of the blue, even if users are not actively using their computers.

Oh great. I just had that happen for the first time a few minutes ago. All I was doing at the time was reading on Reddit. I got the “CRITICAL PROCESS DIED” and a bunch of other stuff I don’t remember.

These errors determined many users to roll back to the Windows 10 Fall Creators Update. If you’re planning to do the same, here’s a quick guide on how to roll back after installing the update.

The guide was compiled after the Fall Creators Update was released, but the steps to follow are the same.


Blue Screen of Death errors are extremely troublesome. Make them a thing of the past with these great tools!


Now, if you prefer to stick to the Windows 10 April Update, we also have two dedicated troubleshooting guides to help you fix the CRITICAL_PROCESS_DIED error:

Over to you know: Did you encounter any BSOD error s after installing the Windows 10 April Update? Did you go back to the previous OS version? Let us know in the comments below.

RELATED STORIES TO CHECK OUT:

  • I installed the update yesterday. The install was smooth but soon after loading into windows, I got a bsod with some sort of page_fault error. It attempted to restart but failed numerous times before I was given the choice to “Restore my previous version of Windows”. After restoring, windows continued to prompt me to install the April update. I continued to say no until I eventually passed out and woke up to my computer unable to boot again. It ends up that it installed while I was asleep. So I reverted again and left for work. Now I’m sitting here looking at my bios screen, unable to boot or restore windows. I really don’t want to do a clean install but it looks like I don’t have a choice. Thanks Microsoft.

  • I have exactly the same thing on my pretty new HP ProBook 470 G5 (i7 8th Gen, 16Gb RAM, NVMe SSD 256 + 1Tb HDD). I went back to previous version of windows and it went well. But I was hoping that BSODs were due to some error in upgrade process so I’ve performed a clean install of the Windows 10 (downloaded from Microsoft). Of course, I made an image of my disk first. And the BSODs are still happening. I’ve contacted Microsoft and the guy just started reinstallation of windows (to repair corrupted files – but I’ve just performed clean install!?), but the same thing. On the other hand, on my standalone PC (Pentium G3220, 12 Gb RAM, sata 3 SSD, 1x2Tb hdd, 1x750Gb hdd) in my office everything went well and the windows is working awesome.

  • I have tried installing this update 3 times now. BSOD each time. Each time it crashed, it automatically rolled the system back.

    It is very frustrating not being able to install, as the reminder keeps popping up peridoically.

    Is there a way to simply cancel the update so it does not nag me every few hours?