MANUALLY_INITIATED_CRASH (0xE2): what it means and how to fix it
Updated Oct 27, 2026 · Checked against Microsoft documentation · How this page is made
Quick answer
This error occurs when you or a program deliberately force Windows to crash to capture diagnostic information. It is not a sign of a hardware failure but rather a tool used for troubleshooting system freezes. If you did not trigger this intentionally, it may indicate a software issue or a stuck keyboard key.
What it means
What this error means
When you see the MANUALLY_INITIATED_CRASH stop code, it means Windows has been commanded to stop immediately. This is not a standard crash caused by a broken driver or failing hardware. Instead, it is a specific instruction sent to the operating system to force a 'blue screen' so that the system can write a memory dump file to the disk. This file is a snapshot of what was happening in your computer's memory at that exact moment, which technicians use to diagnose complex, intermittent problems.
Why it happens
There are two primary ways this happens. First, it can be triggered by a specific keyboard shortcut. Windows has a built-in feature that allows users to force a crash by holding the rightmost CTRL key and pressing the SCROLL LOCK key twice. If you have a sticky key or if a piece of software is simulating these keystrokes, your computer might crash unexpectedly.
Second, this error is often triggered by developers or IT professionals using specialized debugging tools. If you are not a developer, you might have accidentally run a diagnostic script or a tool designed to force a crash dump for analysis. Because this is a manual command, Windows does not consider it a 'failure' in the traditional sense, but rather an execution of a requested task.
Common causes
- You accidentally pressed the keyboard shortcut sequence to force a crash.
- A keyboard key is stuck or malfunctioning, triggering the shortcut.
- Diagnostic software or a script was run that intentionally forced a crash dump.
- A kernel debugger was attached to the system and issued a command to stop.
How to fix it
Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.
Check your keyboard
Use this if you suspect a stuck key is triggering the crash.
- Inspect the rightmost CTRL key and the SCROLL LOCK key for physical debris.
- Ensure no objects are resting on the keyboard.
- Try using a different keyboard to see if the crashes stop.
Did this fix it?Disable keyboard-initiated crashes
Use this if you want to ensure the keyboard shortcut cannot trigger a crash.
- Open the Registry Editor by typing regedit in the taskbar search box.
- Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbdhid\Parameters.
- Look for a value named CrashOnCtrlScroll.
- If it exists, right-click it and select Delete, or set its value to 0.
Did this fix it?Run the Windows Update troubleshooter
Use this to ensure your system files and drivers are up to date.
- Open Settings.
- Go to Update & Security or Windows Update.
- Select Troubleshoot and then Additional troubleshooters.
- Run the Windows Update troubleshooter.
Did this fix it?
Is it just you?
25+ Microsoft Q&A threads discuss this. Most recent activity:
- Laptop freezes when I plug in the SD cardNov 17, 2025
- Microsoft Solitaire Collection crashes and shows "Your device ran into a problem and needs to restart."Oct 6, 2025
- Windows 10 Hard Freezing often. I can't isolate the cause.Nov 18, 2020
- Y540 frequent crashes, no BSOD, no logsNov 4, 2023
- how can ı debug my minidump filesFeb 14, 2013
Checked Oct 27, 2026. Refreshed automatically every few days.
Sources
Frequently asked questions
Is my computer broken if I see this error?
No, this error is a deliberate command to stop the system. It is not a sign of failing hardware.
How do I stop this from happening again?
Ensure your keyboard is functioning correctly and avoid pressing the rightmost CTRL and SCROLL LOCK keys simultaneously.
What should I do if my computer keeps crashing with this code?
Check for any background diagnostic tools or scripts that might be running, and consider testing your computer with a different keyboard.