Microsoft Windows Error Code 0x000000E2: How to Fix It

Easy 10-20 minutes Low Severity Verified June 2026
Error Code
0x000000E2
Brand
Microsoft Windows
Product Type
operating_system
Severity
Low
DIY Difficulty
Easy
Estimated Fix Time
10-20 minutes
Windows error code 0x000000E2, also known as MANUALLY_INITIATED_CRASH, occurs when a crash dump is manually triggered through keyboard shortcuts or debugging tools. This is typically not a system failure but rather a deliberate action to generate diagnostic information for troubleshooting purposes.
Ad

Tools You'll Need

How to Fix Error Code 0x000000E2

  1. Identify the trigger source

  2. Disable crash dump on keyboard shortcut

    Back up your registry before making changes. Incorrect registry modifications can cause system instability.
  3. Check for debugging software

  4. Review system event logs

  5. Configure crash dump settings

  6. Update system and drivers

Parts You May Need

Replacement keyboard
Check Price on Amazon
Replacement keyboard
Check Price on Amazon
Replacement keyboard
Check Price on Amazon
Replacement keyboard
Check Price on Amazon
Replacement keyboard
Check Price on Amazon
Replacement keyboard
Check Price on Amazon
Ad

When to Call a Professional

Contact a professional if crashes continue occurring without manual initiation, if you suspect malware involvement, or if you're uncomfortable editing the Windows registry. Also seek help if the system becomes unstable after making registry changes.

Frequently Asked Questions

What does error code 0x000000E2 mean?
Error code 0x000000E2 (MANUALLY_INITIATED_CRASH) means someone or some software deliberately triggered a crash dump, usually for diagnostic purposes. It's not typically a sign of hardware or software failure.
How do I prevent accidental manual crashes from keyboard shortcuts?
Disable the feature by setting the CrashOnCtrlScroll registry value to 0 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters, or ensure you don't accidentally press Ctrl+Scroll Lock+Scroll Lock.
Is the 0x000000E2 error dangerous for my computer?
No, this error is not dangerous. It's simply a controlled crash dump generation and doesn't indicate hardware failure or system corruption. However, frequent unexpected occurrences should be investigated.
Can debugging software cause this error automatically?
Yes, debugging and development software can trigger crash dumps programmatically. Check your installed development tools and disable automatic crash generation features if you don't need them.
Should I be concerned if this error happens repeatedly?
If the error occurs repeatedly without your intention, investigate potential causes like faulty keyboards, unwanted debugging software, or malware that might be triggering crash dumps maliciously.