You're working away, and then bam — your app vanishes. A dialog pops up: "STATUS_UNHANDLED_EXCEPTION (0xC0000144) — The exception %s (0x%08lx) occurred in the application at location 0x%08lx." I've seen this mostly with older software, custom business apps, or games that were patched badly. One client had it every time they tried opening their inventory software after a Windows update. Another time, a video editing tool threw it after a driver rollback.
What Actually Causes This?
Plain English: your program hit something it couldn't handle — a memory block it wasn't supposed to touch, a file that got corrupted, or a driver that gave it bad data. The exception code 0xC0000144 means "access violation" under the hood. The system says, "Hey, you can't do that," and the app didn't have a safety net.
Three usual suspects:
- Corrupted program files — often after an incomplete install or update
- Driver mismatches — especially graphics or USB drivers
- Memory bugs — bad RAM or heap corruption in the app itself
The Fix: Step by Step
I'm skipping the rabbit holes. Here's what works in most cases.
Step 1: Check Event Viewer for Details
Open Event Viewer (press Win+R, type eventvwr.msc, hit Enter). Go to Windows Logs > Application. Look for an Error entry with source "Application Error" around the time it crashed. The "Faulting module path" or "Exception code" will confirm it's 0xC0000144. The module name (like MyApp.exe) or a DLL tells you where the problem lives.
Step 2: Run System File Checker
Corrupted system files can trigger this in any app. Open Command Prompt as Admin and run:
sfc /scannowLet it finish. If it finds issues, reboot and try the app again. Had a client where this alone fixed a recurring crash in their accounting software.
Step 3: Reinstall the Crashing Application
Don't just repair — uninstall completely. Go to Settings > Apps > Apps & features, find the app, click Uninstall. Then download a fresh copy from the official site and install. If it's a custom business app, grab the installer from your IT admin or the vendor.
Step 4: Update or Roll Back Problematic Drivers
If the Event Viewer mentions a graphics or USB driver, update those first. Go to Device Manager, right-click the device, choose "Update driver." If the crash started after a driver update, roll it back: Device Manager > right click > Properties > Driver > Roll Back Driver. I've seen this with Nvidia drivers on older games.
Step 5: Check for Memory Corruption
Bad RAM can cause random crashes with this error. Run Windows Memory Diagnostic (press Win+R, type mdsched.exe). Choose "Restart now and check for problems." Let it run — takes 10–20 minutes. If it finds errors, you'll need to replace the faulty stick.
Still Failing?
If the fix above didn't work, here's what to check before giving up:
- Application compatibility mode: Right-click the app's .exe, go to Properties > Compatibility, run it as Windows 7 or 8.
- DEP settings: Data Execution Prevention can block legit apps. Go to System Properties > Advanced > Performance > Data Execution Prevention, and add an exception for the crashing app.
- Third-party antivirus: Temporarily disable it. I've seen Avast and McAfee block memory operations on custom software.
- Windows update: Install all pending updates. A missing security patch can cause access violations.
One more thing: if this is a .NET application, check that you have the correct .NET Framework version installed. Many business apps need .NET 4.8 or 3.5. Had a point-of-sale system crash with 0xC0000144 until I installed .NET 3.5.
If nothing works, contact the app vendor with the Event Viewer log. They may need to patch their code — that's their job, not yours.