A program on my PC started closing the instant I double-clicked it, with a small popup reading "The application was unable to start correctly (0xc0000005)." No error log, no crash window — just gone. This post walks through how I figured out which of the four usual causes was mine, and the exact fix for each.


🖥️ What Happened to Me

It happened right after a routine Windows update — a design tool I use daily wouldn't open anymore. I'd click the icon, see the cursor spin for half a second, and then nothing. Task Manager showed the process flash in and out of the list. Eventually I got a small dialog naming the culprit: 0xc0000005. If you're seeing the same thing on a completely different app, that's normal — this code isn't tied to one program. It's a low-level Windows error meaning a process tried to read or write memory it wasn't allowed to touch, so Windows kills it before anything worse happens.



⚠️ Symptoms & the Exact Message

The pattern is fairly consistent across machines: the app opens for a split second (sometimes you see a splash screen, sometimes nothing at all) and then closes on its own. The message is usually one of these two:

  • "[Program name].exe – Application Error: The instruction at 0x... referenced memory at 0x.... The memory could not be read."
  • "The application was unable to start correctly (0xc0000005). Click OK to close the application."

You might also find a matching entry in Event Viewer under Windows Logs → Application, listed as an "Application Error" with Exception code 0xc0000005 — worth checking before you start fixing anything, since it confirms the process name that's actually failing.



🔍 Four Likely Causes (and How to Tell Which Is Yours)

I stopped guessing once I realized this error almost always traces back to one of four things. Here's how to tell them apart before you touch a single setting:

  • Corrupted or mismatched app files — started right after a partial install, a failed update, or copying the program from another PC.
  • A misbehaving DLL or missing runtime — Event Viewer's "Faulting module" line points to a .dll instead of the .exe itself.
  • Security software over-blocking — started immediately after installing or updating antivirus/EDR software.
  • DEP (Data Execution Prevention) flagging the app — older or unusual software that Windows' memory-protection feature doesn't trust.

In my case, the faulting module in Event Viewer was a .dll bundled with the app, not the .exe — that pointed straight at cause #2.



🛠️ The Fix for Each Cause

1) Corrupted app files — Uninstall the program from Settings → Apps → Installed apps, restart, then reinstall it fresh from the developer's site. Don't just repair; a clean reinstall clears out half-written files a repair can miss.

2) Missing or broken runtime/DLL — This is what fixed it for me. Many apps quietly depend on the Microsoft Visual C++ Redistributable, and if that runtime is missing or an older version, you'll get exactly this error. Reinstalling the current redistributable resolved it in under five minutes.

🔗 Official Page — Microsoft Learn: Latest Supported VC++ Redistributable learn.microsoft.com · Free · Pick the x86/x64 package under "Visual Studio 2015, 2017, 2019, and 2022"

3) Security software over-blocking — Temporarily disable real-time protection, try opening the app once, then re-enable protection right away. If it opens fine, add the app's install folder to your antivirus exclusions instead of leaving protection off.

4) DEP flagging the app — Open Control Panel → System → Advanced system settings → Performance Settings → Data Execution Prevention tab, choose "Turn on DEP for all programs except those I select," add the app, and restart it. Use this only for software you trust.



🧩 Still Crashing? A Few More Angles

If none of the four above worked, check RAM next — bad memory sticks produce exactly this kind of "invalid memory read" error, often in more than one unrelated app. Run mdsched.exe (Windows Memory Diagnostic) and let it run a full pass overnight. Also verify system files aren't damaged:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Run both from an elevated Command Prompt (right-click Command Prompt → Run as administrator), restart afterward, and try the app again.



❓ FAQ

Q. Is 0xc0000005 always caused by a virus?
Rarely, but malware that corrupts system DLLs can trigger it. A quick scan doesn't hurt, but it's usually not the real cause.

Q. Why does it only happen with one specific app?
Because the broken piece — a missing DLL, a corrupted install — is specific to that program's files, not to Windows itself.

Q. Does a full Windows reset fix it for good?
Usually yes, since it reinstalls the runtime environment from scratch, but that's a last resort — try the four causes above first.

Q. Can outdated GPU or chipset drivers cause this too?
Occasionally, especially for apps that touch graphics memory directly. Updating drivers via Device Manager is worth a quick try if the fixes above don't help.



✅ Wrap-Up

Error 0xc0000005 always comes down to Windows blocking a program from touching memory it shouldn't. Check Event Viewer first to see whether the .exe or a .dll is at fault, then work through corrupted files, a missing VC++ runtime, security software, and DEP settings in that order. For me, reinstalling the Visual C++ Redistributable was the entire fix — start there if you're not sure where to begin.

#0xc0000005 #WindowsError #ApplicationCrash #AccessViolation #WindowsTroubleshooting