Is This Game Down
This one's theirsReported

AION 2 "UE-AION2 Game has crashed and will close" (fix)

A crash dialog reading "The UE-AION2 Game has crashed and will close" pops up mid-session — reported both during character creation and during normal play — sometimes followed by the screen freezing entirely.

Also appears as: fatal error, UE-AION2 has crashed, crash on character creation, screen freezes after fatal error, game has crashed and will close, LowLevelFatalError, aion 2 crash to desktop

This is a generic Unreal Engine crash-reporter dialog, not a specific error code, so it can fire for more than one reason. No NCSOFT article on it was found as of 2026-10-08, and post-release Steam threads describe crashes without any fix from NCSOFT.

A NCSoft community manager collected one affected player's SteamID and confirmed the report reached the dev team. Player workarounds exist (repairing Visual C++, closing RTSS or the Discord overlay, and unplugging the keyboard and mouse at launch), but none works for everyone, and the unplug fix comes from players who describe crashes to desktop rather than quoting this dialog.

Crashes have been reported around 30 seconds in and after an hour of play, so more than one cause is likely.

Operational

No problems reported in the last 15 minutes.

Is AION 2 down right now? Live reports →

What to try

  1. 01

    Repair or reinstall the Visual C++ runtimes and reboot

    Repair or reinstall the Microsoft Visual C++ runtimes, then reboot. Three players reported this clearing the crash independently, and a fourth endorsed it. Be aware it is not universal — at least one player said updating the runtimes made no difference to their case.

    Reported
  2. 02

    Fully close RivaTuner Statistics Server and MSI Afterburner

    Close RivaTuner Statistics Server and MSI Afterburner completely, not just their overlays, and relaunch. Two players reported this working. RTSS hooks the renderer whether or not its on-screen display is showing, which is why closing the overlay alone is not the same test.

    Reported
  3. 03

    Turn off the Discord overlay (one report, LowLevelFatalError)

    In Discord, turn the in-game overlay off, then relaunch AION 2. In an r/Aion2 thread (October 11) about "LowLevelFatalError" crashes where the game froze, GPU use dropped to 0% and the client closed, the original poster said turning off the Discord overlay stopped "99%" of the crashes. One report, and it was the LowLevelFatalError variant rather than the UE-AION2 dialog.

    Reported
  4. 04

    Unplug keyboard and mouse after pressing Play, replug at the start screen

    Press Play, unplug the USB keyboard and mouse (or switch a wireless mouse off), and plug them back in once the start screen shows. In a Steam thread, "Steam Crash Possible Fix" (about 20 comments, 1 to 5 October), several players said this stopped their crashes (one with a Corsair K65, others with Razer mice). These players describe the game crashing to desktop, mostly with no error shown; none of them quotes the UE-AION2 dialog, so it may not be your case. It did not work for everyone: one player kept crashing every 1 to 3 hours after turning overlays off and removing Razer Chroma.

    Reported
  5. 05

    Set a Corsair K70 keyboard to BIOS mode before launching (one report)

    One player in the same Steam thread has a Corsair K70 LUX RGB keyboard with a BIOS-mode switch. With it set to BIOS mode the game launched without crashing, and switching it back once the game was open was fine. This is a single report, and it was a crash to desktop rather than the UE-AION2 dialog.

    Unconfirmed
  6. 06

    Try a clean boot to find a conflicting app (one report)

    One player in the same Steam thread said the game ran after a clean startup (msconfig), and suspects their Turtle Beach headset app. That is a suspicion, not a confirmed cause, and the player describes a crash to desktop with no error.

    Unconfirmed
  7. 07

    Note what you were doing before the crash and report it

    If neither helps, note what you were doing immediately before the crash — character creation, a specific zone, a specific action. A NCSoft community manager has collected SteamIDs for this one, so specific reports go somewhere. Crashes at around the 30-second mark and crashes after an hour have both been reported, which suggests more than one underlying cause is still in play.

    Unconfirmed

Did this fix it for you?

Your answer helps the next player know whether these steps are worth trying first.

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.