STATUS_NONCONTINUABLE_EXCEPTION 0xC0000025 on Windows

What's Going On with 0xC0000025?

You're in the middle of something — maybe a game, a heavy engineering tool, or even just a browser — and BAM: the app crashes with “EXCEPTION (0XC0000025) - Cannot Continue Windows STATUS_NONCONTINUABLE_ cannot continue from this exception.” Feels like the OS just threw its hands up and said, “Nope, I’m out.”

I've seen this on a dozen different machines — from a dental office's accounting software to a gamer's custom rig. The error means a program tried to continue executing after it hit a fault that the kernel flagged as non-continuable. Usually, that’s a bug in the software or a bad driver feeding garbage into the system. Let's fix it.

One quick note: if this happens right after you install new RAM or a new GPU, skip straight to cause #2. Otherwise, start with #1.

Cause #1: Buggy Software (The Most Common Culprit)

Nine times out of ten, this error comes from a piece of software that has a logic bug or a memory corruption issue. The application tries to do something the OS says “no way” to, and that’s your 0xC0000025. I've seen it in custom database apps, old engineering tools (like SolidWorks 2015 on Windows 11), and even some games after a patch.

How to fix it

1. Note the exact app that crashed. Check Windows Event Viewer under Windows Logs > Application — look for a red Error with source “Application Error” or “.NET Runtime.” Copy the faulting module path.
2. Reinstall that application. Use a clean uninstaller like REVO to wipe leftovers. Then grab the latest version from the vendor’s site — not a third-party mirror.
3. Check for updates. Even a minor patch can fix this. I had a client whose shipping software crashed every 30 minutes; a one-year-old update fixed it.
4. If it’s a game, verify integrity of game files in Steam or the launcher. Corrupted assets can trigger this exception.

If reinstalling doesn't help, try running the app in Windows 8 compatibility mode. Right-click the .exe, go to Properties > Compatibility, check “Run this program in compatibility mode for:” and pick Windows 8. That’s solved it for a few stubborn old apps.

Cause #2: Overclocking Instability (RAM or CPU)

This one shows up a lot on custom-built desktops. You’ve got an overclocked CPU or RAM running beyond spec, and under a heavy load, the system throws a non-continuable exception. The OS can't recover because the memory state is corrupt. I’ve seen this most often with XMP profiles on DDR4-3600 sticks that the motherboard can't actually handle.

How to fix it

1. Disable all overclocks. Go into your BIOS/UEFI (usually F2 or Del at boot). Set CPU multiplier to auto, disable XMP, and set RAM speed to the default JEDEC speed (usually 2133 or 2400 MHz). Save and exit.
2. Run a memory test. Download MemTest86 (free version). Boot from a USB and let it run for at least one full pass. If you see red errors, you’ve got bad RAM or a bad memory controller.
3. Stress test the CPU. Use Prime95 with small FFTs for 15 minutes. If it throws an error (watch the worker windows), your CPU overclock is unstable — or the chip itself is failing.

If the error stops after you revert to stock speeds, you know the culprit. You can try a milder overclock later, but for now, stable is better than fast.

Cause #3: Corrupted or Outdated Drivers (Especially GPU and Storage)

Sometimes it’s not the app itself — it’s a driver that’s passing bad data. The most common offenders are graphics drivers (NVIDIA or AMD) and storage drivers (especially NVMe controllers). I fixed a machine last month that crashed with 0xC0000025 every time it opened a video editor; turns out the Intel RST driver was three years old and busted.

How to fix it

1. Update your GPU driver. Use DDU (Display Driver Uninstaller) in Safe Mode to fully remove your current driver. Then install the latest from NVIDIA or AMD — not from Windows Update.
2. Update chipset and storage drivers. Go to your motherboard manufacturer’s support page (not a generic driver updater tool). Download the latest chipset driver, SATA/AHCI driver, and NVMe driver for your exact board model.
3. Roll back a recent driver if the error started after a driver update. In Device Manager, right-click the device > Properties > Driver > Roll Back Driver.
4. Check for Windows updates. Some cumulative updates include driver fixes. I’ve seen a few KB patches from Microsoft resolve these exceptions on systems using Realtek audio drivers.

If you can't boot into Windows due to the crash, boot into Safe Mode (press F8 or Shift+F8 at boot, or use a recovery USB). Safe Mode loads minimal drivers — if the error doesn't happen there, a driver is the problem.

Quick-Reference Summary

Most people will solve this by reinstalling the crashing app or backing off their overclock. If you’re still stuck after trying all three, consider a clean Windows install — it’s nuclear, but it works. And if you’re on a laptop, check with the manufacturer for a BIOS update; I’ve seen that fix the exception on Dell XPS models with 12th-gen Intel chips.