How to Fix Error 0xc0000005: The Application Was Unable to Start Correctly
What 0xc0000005 means
Every program Windows runs gets its own slice of memory, and the operating system polices those boundaries strictly. Error 0xc0000005, also called an access violation or exception code 0xc0000005, fires when a program tries to read from or write to a memory address outside its own slice, or to an address that is reserved, damaged, or already freed. Windows does not guess what the program meant to do — it kills the process immediately and shows the familiar message: The application was unable to start correctly (0xc0000005). That is why the error feels so abrupt: there is no slow failure, just a program that refuses to open at all.
The same code can appear in very different situations, which is why a single fix does not work for everyone. Sometimes the trigger is a corrupted Windows system file that every program depends on. Sometimes it is a single damaged executable or library inside one app. Other times the culprit is outside the app entirely: a graphics driver that hands back bad memory addresses, a security tool that blocks legitimate memory access, a RAM stick that flips bits under load, or a drive that returns corrupted data. The steps below narrow it down from the cheapest checks to the hardware tests, so you do not reinstall Windows for a problem that a single DEP exception would have solved.
Common causes
- Corrupted Windows system files: a failed update, a sudden shutdown, or old malware damage can break the shared files programs need at startup, so the first app that touches them crashes with an access violation.
- A damaged program installation: a broken executable, a missing or mismatched library file, or a bad app update can make one program reach for memory that is no longer valid, while everything else runs fine.
- Faulty or outdated drivers: graphics and chipset drivers manage memory directly, and a buggy driver can hand a program an invalid address or clash with a Windows update.
- Security software or Data Execution Prevention blocking the app: antivirus tools and DEP both stop programs from using memory in ways they consider unsafe, and a false positive looks exactly like a crash.
- Faulty RAM, a failing drive, or leftover malware damage: bad memory returns wrong data, a dying drive serves corrupted files, and a cleaned-up infection can leave broken registry entries and permissions behind.
How to fix error 0xc0000005 — step by step
Work through these fixes in order. The first two rule out temporary faults and system damage, steps 3 and 4 fix the app itself, and the last two find conflicts and hardware faults.
- Restart the PC and run the app as administrator. Close the error, restart your PC, then right-click the program shortcut and choose Run as administrator. A restart clears a one-off memory fault, and administrator rights rule out a simple permissions problem. If the app opens now, the fault was temporary or permission-related, and you can stop here.
- Repair system files with SFC and DISM. Open Command Prompt as administrator: right-click Start, choose Terminal (Admin) or Command Prompt (Admin), and run
sfc /scannow. Wait for the scan to finish, then runDISM /Online /Cleanup-Image /RestoreHealthand runsfc /scannowonce more. These tools replace damaged Windows files that can trigger an access violation every time an app starts. - Reinstall the failing application cleanly. Open Settings, go to Apps, then Installed apps, find the failing program, and choose Uninstall. Restart the PC, then download a fresh copy from the official developer site and install it again. A clean reinstall replaces damaged program files and broken libraries that a repair install often leaves behind.
- Exclude only the failing program from Data Execution Prevention. Press Win + R, type
sysdm.cpl, and press Enter. On the Advanced tab, under Performance, click Settings, open the Data Execution Prevention tab, and choose Turn on DEP for all programs and services except those I select. Click Add, pick the executable file of the failing program, click OK, and restart. Only exclude the one program that fails, and never turn DEP off system-wide. - Do a clean boot to find the conflicting software. Press Win + R, type
msconfig, and press Enter. On the Services tab, check Hide all Microsoft services, click Disable all, then open the Startup tab, click Open Task Manager, and disable every startup item. Restart the PC and try the app again. If it works, re-enable services and startup items a few at a time until the error returns, and you have found the conflict. - Test your memory, disk, and drivers. Press Win + R, type
mdsched, and press Enter to run Windows Memory Diagnostic, then restart when prompted and check the result in Event Viewer. In an administrator Command Prompt, runchkdsk C: /f /rto check the drive, and update your graphics and chipset drivers from Device Manager or the manufacturer site. Faulty RAM, a failing drive, or a bad graphics driver can all produce the same access violation.
Did this fix it? Quick checklist
- PC restarted, app tried as administrator
- SFC and DISM completed, app reinstalled cleanly
- DEP exception added for only the failing program
- Clean boot tried, memory and disk tested
If the error survives all six steps, the problem is likely deeper than one app: run a full scan with Windows Security or your antivirus, then check the Windows Event Viewer under Windows Logs, then Application, for the crash entry tied to the program name — the faulting module listed there often names the exact driver or library at fault. A repair install of Windows, done as an in-place upgrade from the official Microsoft media, keeps your files and apps while replacing system files; a clean install is the last resort, and only after a backup.
Frequently asked questions
What does error 0xc0000005 mean?
It is a Windows access violation error. It means a program tried to read from or write to a memory address it did not have permission to use, so Windows stopped the program before it could run. The message usually reads The application was unable to start correctly (0xc0000005). The usual triggers are corrupted system files, a damaged program installation, a conflicting driver or security program, faulty RAM, or malware damage left behind after an infection.
Why does 0xc0000005 affect only one program?
Because the fault often lives inside that program, not in Windows itself. A damaged executable, a broken library file, or a bad update to that one app can trigger an access violation while every other program runs normally. If the error follows one app after a clean reinstall, look wider: test your RAM, update your graphics driver, and run SFC and DISM, because a system-wide fault can still show up in the most demanding program first.
Can antivirus software cause 0xc0000005?
Yes. Security software can block a program from accessing memory it needs, and Data Execution Prevention can do the same when it flags a legitimate program. Temporarily disable your third-party antivirus and try the app again. If the error disappears, add the program to the antivirus exclusion list and to the DEP exception list in step 4, then turn protection back on. Never leave antivirus disabled as a permanent fix.
Will fixing 0xc0000005 delete my files?
No. Restarting, running SFC and DISM, reinstalling one program, adjusting DEP for one program, doing a clean boot, and testing memory and disk all leave your personal files alone. The only step that removes anything is uninstalling the failing program, and even then your documents stay put unless they live inside that program folder. Back up important files before you run chkdsk with the repair option, because a failing drive can lose data on its own.