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.
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:
- ‘Critical Process Died’ in Windows 10: Fix this Error
- Fix: Critical_process_died csrss.exe on Windows 10
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: