Stop Code: Critical Process died

Gavin Ross 101 Reputation points
2023-08-03T15:19:55.95+00:00

Hope someone can help or has been able to fix this error. We have had 4 domain controllers in the last week get this error after the latest software update. The problem is the vm is in a constant reboot. I cannot boot into safe mode, or command prompt to try and uninstall the updates. Screenshot 2023-08-03 080347

Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Wesley Li-MSFT 4,576 Reputation points Microsoft External Staff
    2023-08-04T07:39:30.1533333+00:00

    Hello

    The “Stop Code: Critical Process Died” error can be caused by a variety of issues, including hardware malfunctions, device driver issues, or corrupted system files. One potential cause of this error is a rogue update, which is a term that describes a recent Windows update that causes unwanted side effects on some PCs. If you can identify the update involved, there will usually be helpful notes in the update release notes from Microsoft. You can check the update’s Knowledge Base number and read what you can find from Microsoft about that string.

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

    If you’re unable to boot into safe mode or command prompt, it may be more difficult to troubleshoot the issue. One option is to try booting into the Windows Recovery Environment (WinRE) by using the power button on your PC to enter a special diagnostic mode. From there, you may be able to access a command prompt for troubleshooting.

    https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef--critical-process-died

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.