AION 2 crash 0xE0000011 (launching via Steam)
AION2.exe closes right after launching through Steam, with no dialog beyond the exit code 0xE0000011. The same install launched through PURPLE or the .exe directly instead throws 0xE0000013 for at least one affected player.
Also appears as: 0xE0000011, exit 0xE0000011, aion2.exe 0xE0000011, aion 2 won't launch from steam, aion 2 crashes immediately on launch
0xE0000011 is in the same family of NCGuard exit codes as 0xE0000012 and 0xE0000013: AION 2's anti-cheat closing the game during startup. NCSoft hasn't published what this one means. Four players hit it in one Steam Discussions thread during the September playtest, and reinstalling, redownloading through PURPLE and filing a support ticket with logs didn't get any of them past it.
The thread's original poster got 0xE0000011 launching through Steam and 0xE0000013 launching the .exe directly, so the two are likely the same startup check failing. About eight players fixed 0xE0000013 by unplugging USB peripherals until the NC logo passed. Nobody has reported trying that for 0xE0000011 yet, but it's the best-supported thing to try first.
Fix it, step by step
Unplug USB mouse, keyboard and headset until the NC logo passes
This is the fix about eight players confirmed for the sibling code [0xE0000013](/aion-2/errors/0xe0000013/), which the same player got when launching the .exe instead of Steam. Unplug or switch off MMO mice, gaming keyboards and USB headsets, launch, and plug them back in once the NC logo and music have passed. Untested for 0xE0000011 specifically.
Close Wireshark and DPS meters that use Npcap
One reply in the thread pointed at Wireshark and the FFXIV Advanced Combat Tracker, both of which capture network traffic through Npcap, as things anti-cheat can block. The original poster had neither running, so this is a lead, not a fix. If you use a packet-capture tool or a DPS meter, close it before launching.
Check for RGB control software and TPM 2.0 status
Close any RGB/lighting control software (Corsair iCUE, Razer Synapse and similar) before launching, and check that TPM 2.0 is enabled in your BIOS. One commenter proposed both as possible NCGuard triggers; the original poster had no RGB software and TPM 2.0 already on, and still crashed.
- NoteUnconfirmed
No confirmed fix yet; this page will be updated. Reinstalling, redownloading through PURPLE and contacting NCSoft support didn't resolve it for the players who tried. If it keeps happening, open a ticket at [help.plaync.com](https://help.plaync.com/) with the code and your logs.
Sorted. Glad that worked.
Nothing worked. Here's what to do next.
You've ruled out every step on this page, which is useful. Send this to support or drop it in the community Discord so nobody makes you repeat yourself.
Hit this error? Leave a comment
Say where you are, what you see on screen, and whether any fix worked for you.
No links. Anonymous, no account. Keep it about the game.
What people are saying
Notes from players who've hit this one — no time limit, an answer from months ago is still an answer.
- Nothing reported here yet.
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""