The application was unable to start correctly (0xc0000005) / Exception code 0xc0000005 access violation
A program tried to read or write memory it doesn’t own and Windows stopped it — buggy software, bad drivers/plugins, security software injection or faulty RAM.
Seen on:
Windows
Meaning
STATUS_ACCESS_VIOLATION. When it happens at startup, antivirus/DEP or corrupt program files are common; when many programs crash, suspect RAM or system files. The Event Viewer “Application Error” entry names the faulting module.
Common causes
- Bug in the program or a plugin/add-in
- Security software or overlay injecting into the process
- Corrupt program files or runtime
- Faulty RAM or overclock
⚡ Quick fix
- Check Event Viewer → Windows Logs → Application for the faulting module
- Reinstall/update the program and its runtimes
- Test without overlays/antivirus; run Memory Diagnostic
Detailed fix by platform
Windows
- powershell
Get-WinEvent -FilterHashtable @{LogName='Application'; Id=1000} -MaxEvents 5 | Format-List TimeCreated, Message sfc /scannow
How to diagnose
- Module — Faulting module name in Event 1000
- Scope — One app or many?
- Hardware — RAM test
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Windows
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026