How to fix dead critical process BSOD in Windows 10 after upgrade

The blue screen of death is one of the scariest things that can happen to your PC. It can happen randomly without warning or at any time so you can save your work. If you see a blue screen with the error code that says CRITICAL_PROCESS_DIED After Windows Update (particularly Windows April Update v1803), we have listed some solutions that you can try to fix the problem.

It has been reported that simply clicking on any Windows built-in application will activate the Critical Process Dead BSOD. When you are on the blue screen, there is nothing you can do except restart your computer.

What Causes Critical Process BSOD to Occur in Windows 10?

The CRITICAL_PROCESS_DIED blue screen error will occur when a critical Windows component detects any unauthorized modification of its data. It is usually related to buggy outdated drivers. If you see the error immediately after Windows Update, it may indicate that one or more drivers are causing update conflicts.

This is a common case in all major Windows updates. There will always be a small portion of people who have a specific set of hardware that will cause the BSOD error. Finally, the error will be fixed in the next patches or in the new versions of drivers that are compatible with the new updates. So the first thing you should try after you get the Critical Process Dead BSOD error is update all your hardware drivers .

If it’s been a while since you’ve run Windows Update, you can run it again to allow it to find and install the latest drivers for your computer automatically. If the update was installed not too long ago, and then the BSOD started to happen, you will have to check your manufacturer’s website for the latest drivers. Otherwise, you will just have to wait until Microsoft fixes the problem or when there are new versions of drivers to solve the problem. In the meantime, you can downgrade or try the following solutions.

YOU CAN ALSO READ:   Windows 10 April 2018 update causing "Location is not available"

Clean boot your computer

A clean boot means starting your computer in a clean state with only the core system files that Windows trusts to start, removing all other startup programs and services. A clean boot will allow you to make any fixes that take time to complete before the blue screen kicks in.

To start on a clean boot, go to startup and search for msconfig . Go to the tab Services and then check the checkbox that says Hide all Microsoft services . Then click the button Disable all . This will disable all other services except Microsoft services. Go to the tab Beginning and click Open Task Manager . Sort the status and disable all enabled startup programs. Restart your computer. It should now boot clean. The blue screen should be temporary fixed.

Alternatively, you can try to re-enable these startup programs one by one until you find the problematic program causing the Critical Process Dead BSOD error.

Now that your PC stops giving you blue screen, you can proceed to try the following solutions.

YOU CAN ALSO READ:   WireGuard VPN is coming to Android 12: Why is it better than the current ones?

Roll back to a previous version of Windows 10

If you are in a rush and don’t have time to diagnose what is actually causing the CRITICAL_PROCESS_DIED BSOD, you can choose to revert to the previous state of your Windows before the update. Here we’ll explain to you how to do it.

  1. Hold down the Windows key + I to open the Settings app.
  2. Click on Update and security .
  3. From the left panel, click Recovery .
  4. On Go back to the previous version of Windows , Click the button Start .
  5. Just select a reason, then click Next .
  6. Click on No thanks when they offer to download the latest updates.
  7. Click a couple Next again, then select Go back to the previous build .

The rollback process can take anywhere from 30 minutes to a few hours to complete. Please do not interrupt it as it may break your Windows. It will reboot in the process and once it boots into Windows it will be on its previous build before the troublesome update.

Use the System File Checker tool to fix BSOD

The blue screen error, especially the CRITICAL_PROCESS_DIED error, is often caused by a corrupted system file that Windows relies on running. The System File Checker tool will scan, locate, and repair any corrupted Windows system files found. Here’s how to run it on Windows 10.

Go to Start and type cmd . Right-click on the command prompt and select Execute as an administrator . This is important as SFC will only work when you have administrator privileges. At the command prompt, enter sfc / scannow . SFC will start scanning now. It may take a while. Restart your computer when the process is done.

YOU CAN ALSO READ:   How to reset Windows 10 to factory settings on a laptop / desktop PC

What else can you try when nothing works?

Yes can’t even start windows To test some of the solutions, you can try starting in safe mode and making the fixes. If you can’t boot into safe mode, the last thing you can do is clear your CMOS. Note that this is an advanced solution that should only be done by those who know what they are doing, which involves physically touching your motherboard, such as changing the CMOS jumper and resetting the CMOS battery. Do a search to find a guide on how to do it.

Assuming you already have antivirus software installed, run a scan on your computer to see if there are any malware causing conflicts with your system files and drivers that ultimately lead to a blue screen error . It is always imperative that any computer user have antivirus software installed to protect their computer.

As we have already mentioned that the error is related to the driver problem, if you just updated your Windows not too long ago, it may take some time for your hardware manufacturers to find new drivers that are compatible with the current Windows Update.

Therefore, I would advise you to temporarily downgrade to a previous version and wait a week or two until these manufacturers release new compatible drivers and, more importantly, until Microsoft fixes what needs to be fixed.

Leave a Reply

Your email address will not be published. Required fields are marked *