How To Fix Windows Has Encountered A Critical Error

How to Set up CRITICAL_PROCESS_DIED Errors in Windows

(Prototype credit: Tom's Hardware)

CRITICAL_PROCESS_DIED is ane of the few Windows BSODs (Blue Screens of Death) that anyone can provoke at volition. If you impale the process named svchost.exe in Windows 10 (right-click in Job Manager, and pick "End process tree" from the pop-up menu), information technology will immediately cause the machine to crash with this very fault code. Among other things, that means Windows won't run unless the generic organization process that hooks Windows services up with dynamic link libraries (DLLs) is operating. Considering this is a fundamental part of how the Windows OS operates, the OS won't work unless i (usually more) instance of this service is running (at least ane for each DLL in use, in fact).

In essence CRITICAL_PROCESS_DIED signals that some procedure necessary to Windows proper performance has ended abruptly and unexpectedly (to the Bone, anyhow). I don't recommend that users endeavor killing svchost.exe unless they've saved their work, closed all open applications, and are fix for their PC to restart after the BSOD appears and the postal service-crash dump files are saved.

Virtually Mutual Causes for CRITICAL_PROCESS_DIED Fault

When this error occurs, numerous potential causes are worth investigating. As with about BSODs, your clearest guide to further such investigation is to consider what changed on your PC recently. Statistically, the nigh frequent cause of this item finish lawmaking is a rogue update, followed past system file corruption that causes the executable for some disquisitional system process (of which svchost.exe is a great instance) to dice. The listing of potential causes includes:

Rogue update: this is a term that describes a (usually recent) Windows update such as a Cumulative Update, a security update, or some other update, that causes unwanted side effects on some PCs. If you can place the update involved – there will usually exist helpful notes in the update release notes from Microsoft. To that stop, please bank check the update'south Cognition Base number and read what you can find from Microsoft well-nigh that string.
Thus, for example, yous could use Google to observe useful information for KB5003173 with the string: "site:Microsoft.com KB5003173" where this
Microsoft Support notation (opens in new tab) is your main focus for follow-upward. Information technology includes a section heading that reads "Known issues in this update" where y'all'll find data well-nigh known problems and potential or actual resolutions or workarounds. 3rd-party sources are also sometimes of involvement, because they may document fixes or workarounds that Microsoft has non yet vetted and published.
To see what updates you've installed recently, get to the old Windows control panel, launch Programs and Features and click "View installed updates," which shows yous a list of all updates in social club of install. If you lot need to uninstall 1, right click information technology and select "uninstall."

If that doesn't work, y'all can boot from the Windows Recovery environment and utilise the DISM command to uninstall an offline image at the command line. That's a fairly circuitous performance that's documented in Pick half dozen of Shawn Brink'due south excellent TenForums tutorial Uninstall Windows Update in Windows 10. It is also the best known method for removing a rogue Windows x update.

Uninstalling a Rogue Update — (Paradigm credit: Tom'southward Hardware)

Corrupt organisation files: These are best addressed using the DISM /Online /Cleanup-Epitome /CheckHealth command (run at an administrative command prompt or in an administrative PowerShell session). If this control finds annihilation to report, run DISM /Online /Cleanup-Image /RestoreHealth to clean things up. Next, run the system file checker until information technology reports nil establish or stock-still (this sometimes takes two or 3 iterations): SFC /SCANNOW. If it works, this volition often fix the IRQL error equally well.

Use DISM — (Epitome credit: Tom's Hardware)

Incompatible device drivers: If you've recently updated a driver, you should probably utilize the "Roll Back Driver" pick on that device's Commuter tab in Device Manager. If the tab is greyed out, you may have to uninstall the current commuter and install the previous version manually.

Roll back driver — (Paradigm credit: Tom'due south Hardware)

Try a Clean Boot to Resolve CRITICAL_PROCESS_DIED Errors

If y'all all the same can't figure out what is causing your CRITICAL_PROCESS_DIED errors, a Windows 10 clean kick should be your adjacent step. A make clean boot starts Windows 10 with the barest minimum prepare of drivers and startup programs. It seeks to eliminate possible causes of trouble that have been added to the startup environment over time. See our article on how to perform a make clean boot in Windows ten for instructions.

Make Use of Recent Reporting to Solve CRITICAL_PROCESS_DIED Errors

If yous visit TenForums.com, BleepingComputer.com, Answers.Microsoft.com (opens in new tab) or the Tom's Hardware Forums and search for the CRTICIAL_PROCESS_DIED error string you volition run into how often the error has been reported lately.

You will also get some fantabulous insight on how others have approached diagnosis of the underlying cause, and what fixes they've applied. Information technology's especially helpful to read through fixes that claim success because these might work for you lot, likewise. On the other manus, unsuccessful fixes tin can be informative, too, because they tell you which repairs to try afterwards rather than sooner (or not at all).

Ed Tittel is a long-time Information technology writer, researcher and consultant, and occasional contributor to Tom'southward Hardware. A Windows Insider MVP since 2018, he likes to cover Os-related driver, troubleshooting, and security topics.

Source: https://www.tomshardware.com/how-to/fix-critical-process-died-error-windows

Posted by: leeyeas2002.blogspot.com