Fix ERROR_UNHANDLED_EXCEPTION 0X0000023E Crash

What is ERROR_UNHANDLED_EXCEPTION (0X0000023E)?

You're working in an app—maybe a game, a design tool, or a custom business program—and suddenly it vanishes. No warning, no save. Just a popup saying ERROR_UNHANDLED_EXCEPTION (0X0000023E) with some hex addresses. That's Windows telling you the app hit a problem it couldn't recover from. The %s in the message is the exception name (like Access Violation), 0x%08lx is the exception code, and 0x%08lx is where in the code it happened. Most of the time, the fix is simpler than the error looks.

Don't panic. We'll start with the quickest fix—30 seconds—and work up. Stop when the crash stops.

Step 1: The 30-Second Fix — Reinstall the Crashing App

This sounds too easy, but I've watched it work hundreds of times. Corrupted installation files cause this exact error. Here's the drill:

Press Windows Key + R, type appwiz.cpl, and hit Enter.
Find the app that crashed. Right-click it and choose Uninstall.
Restart your PC. Don't skip this—Windows needs to clear locks and temp files.
Download a fresh copy from the official site. Not a third-party mirror.
Install it, run it, and try to trigger the error again.

After reinstalling, most users see the app start fine. If it still crashes, move to Step 2.

Step 2: The 5-Minute Fix — Run System File Checker and DISM

Corrupted Windows system files can trip up any app. The SFC and DISM tools fix that. You don't need to know what they do—just run them in order.

Run DISM first (it fixes the repair tool itself)

Right-click the Start button and pick Windows Terminal (Admin) or Command Prompt (Admin).

Copy-paste this command and press Enter:

DISM /Online /Cleanup-Image /RestoreHealth

Wait. It takes 5–10 minutes. You'll see a progress bar. Let it finish—don't close the window.
When it says "The restore operation completed successfully," you're good.

Then run SFC to fix system files

In the same admin terminal, type:
```
sfc /scannow
```
Let it run. It takes about 15 minutes. If it finds corrupt files, it replaces them automatically.
After it finishes, restart your PC.

After the restart, launch the app. If it still shows 0X0000023E, we need to go deeper.

Step 3: The 10-Minute Fix — Check Windows Event Viewer for Clues

The error message gives you hex codes, but Event Viewer shows the real story. Here's how to read it:

Press Windows Key + R, type eventvwr.msc, and press Enter.
On the left, expand Windows Logs and click Application.
Look for a red exclamation mark (Error) that happened right when your app crashed. The Source column will say something like Application Error or .NET Runtime.
Double-click that event. In the window that opens, look for these lines:
- Faulting module path — this tells you which .dll file caused the crash.
- Exception code — should be 0xc0000005 (Access Violation) or similar.
- Faulting process id — not useful to you, but skip it.
If the faulting module is something like nvlddmkm.dll (NVIDIA driver) or igfxem64.dll (Intel graphics), you need to update or roll back your graphics driver.
If it's KernelBase.dll or ntdll.dll, the issue is likely memory or a corrupt OS file—move to Step 4.
If it's clr.dll, that's the .NET runtime. Run the .NET Framework Repair Tool from Microsoft (free download).

After addressing whatever you found, restart and test the app. Still crashing? Keep going.

Step 4: The 15-Minute Fix — Clean Boot and Update Visual C++ Runtimes

Background services and outdated runtime libraries are classic culprits. Let's eliminate them.

Clean Boot to stop interference

Press Windows Key + R, type msconfig, and hit Enter.
Go to the Services tab. Check Hide all Microsoft services at the bottom, then click Disable all.
Go to the Startup tab and click Open Task Manager. Disable every startup item you see.
Close Task Manager, click OK in msconfig, and restart.
After restart, try the app. If it works, something you disabled was the problem. You can re-enable services one by one until the crash comes back—then uninstall or update that service's app.
When you're done, go back to msconfig, choose Normal startup, and restart.

Reinstall all Visual C++ Runtimes

Many apps rely on these, and a missing or broken one throws exactly this error.

Go to the official Microsoft site: search "Visual C++ Redistributable latest supported downloads".
Download the vc_redist.x64.exe and vc_redist.x86.exe (both).
Run each one and choose Repair if you see it, or Uninstall then reinstall.
Restart after reinstalling.

Test the app again. If it still crashes, we're down to hardware or deep corruption.

Step 5: The 20+ Minute Fix — Memory Test and Repair Install

Check your RAM for faults

Bad memory can produce random crashes with any error code. Windows has a built-in test.

Press Windows Key + R, type mdsched.exe, and press Enter.
Choose Restart now and check for problems.
Your PC will reboot into a blue screen with a progress bar. Let it run—takes 20–30 minutes.
When it finishes, Windows boots normally and shows the results in a notification. If it found errors, one of your RAM sticks is bad. Remove the suspect stick (check your motherboard manual) and test again.

Last resort: Repair install Windows

This keeps your files and apps but replaces all system files. It's not a full reset.

Download the Windows 11 Media Creation Tool (or Windows 10 if you're on that) from Microsoft's site.
Run it and choose Upgrade this PC now.
When it asks, select Keep personal files and apps.
Click Install. It takes about an hour. Your PC will restart a few times.
After it's done, update drivers and Windows, then test the app.

I've seen this fix the most stubborn 0X0000023E crashes. If the app still fails after a repair install, the problem is almost certainly the app itself—a bug the developer needs to patch. Contact their support with the Event Viewer details.

One more thing: If you're running Windows 10 version 1809 or older, update to the latest version. That ancient build had a known heap corruption bug that caused this exact error in many apps.