A Deep Dive into maimai DX Error Code 0010 and How to Handle It

What is 0010#

ALLS system error 0010: unexpected game program failure — this is the error that pops up when SEGA’s ALLS boot process mxsegaboot detects that the main game program mai2.exe has terminated abnormally. The only fix SEGA offers is to shut down and restart the game’s main program. This article will go deep into this subject and explain it in detail

The error system#

Maimai cabinets have two error systems

Trigger mechanism#

In one sentence: the game process died without going through the normal Core.Kill channel

From decompilation we can see that ALLS designed three legitimate exit paths:

The boot layer’s two detection channels#

mxsegaboot identifies abnormal exits through two independent channels:

1. Abnormal exit code: when the game process exits, the boot layer reads its exit code. Only a few specific values count as a “normal exit” (the legitimate values corresponding to Core.Kill); everything else is judged abnormal

2. Process crash flag: the mxmaster framework records whether the game process has ever crashed (fault). The boot layer queries this flag at startup and judges an abnormal exit if it is non-zero

Both ultimately result in rendering the 0010 error page

How the game triggers it#

1
GameMain.Update() / LateUpdate()
2
  └─ try/catch → ExceptionHandler()
3
       ├─ 写崩溃日志（.log + .png，保留最近 4 份）
4
       ├─ 截图
5
       └─ 设 GameManager.IsException = true
6

7
GameMainObject.Update()
8
  └─ if (GameManager.IsException)
9
       ├─ isQuit = true
10
       └─ Application.Quit()   ## 没有 Core.Kill！→ 触发 0010

Resource IDs pointing to nonexistent resources#

The most common case, which is what we usually call illegal dirty data in the account

When the game’s resource manager (DataManager.cs) can’t find a matching ID, almost all of them return null; only the Chara-related getters return a defensive empty object:

Any GetXxx(illegalID).field accessed without a null check produces a NullReferenceException → triggers 0010

CheckDisableCollection in UserData.cs (which automatically resets illegal collection items at login) only covers some of the fields:

Known crash list#

The following scenarios have been tested in practice plus code analysis; when an account holds an illegal ID, they will definitely crash:

R8 is the most typical disaster zone

Trigger process#

1
账号存档中含有客户端不存在的资源 ID
2
（已下架 / 未更新的超前数据 / 脏数据）
3
  ↓
4
对应画面调用 GetXxx(id) 返回 null
5
  ↓
6
未判空直接访问字段 → NullReferenceException
7
  ↓
8
ExceptionHandler 记录崩溃日志
9
  ↓
10
GameManager.IsException = true
11
  ↓
12
GameMainObject.Update 检测到 → Application.Quit()
13
  ↓
14
引导层判定进程非正常退出 → 弹出 0010

How to fix it#