These mean GameGuard is already running or has collided with another instance or program, so a fresh copy cannot start. Clearing the running instance fixes it. Jump to your situation below or work through the methods in order.
GameGuard Error 115 means the game was launched more than once, or GameGuard is already running, so a second copy cannot start. The closely related Error 110 is a collision with another running instance or program (and Error 112 is a failure to load GameGuard's checking modules, often low memory or a virus). All three come down to a GameGuard or game process that is already in memory or a program clashing with it. The fix is to close the game fully, then open Task Manager (Ctrl+Shift+Esc) and end the GameMon.des process plus any lingering game process, and relaunch a single copy. If that does not clear it, reboot to flush the stuck instance, disable or whitelist security software that may be holding GameGuard open, and for 112 run a virus scan and confirm your PC meets the game's minimum requirements. Because these are duplicate-instance and collision errors rather than a ban, removing the running copy lets a clean GameGuard start.
Only one GameGuard instance can run at a time. Error 115 means one is already running or the game was launched twice, and Error 110 means another instance or program collided with it. Error 112 means GameGuard could not load its checking modules, often due to low memory or a virus.
Removing the running copy fixes 115 and 110: close the game and end the GameMon.des process, then launch once. A reboot flushes a stuck instance, disabling or whitelisting security software stops it holding GameGuard open, and a virus scan plus a requirements check addresses 112.
“115 and 110 are the duplicate and collision errors, and the fix is almost always in Task Manager. Close the game, then end GameMon.des and any leftover game process, and launch one copy. People trigger 115 by double-clicking the launcher twice, so just start it once. If it will not clear, reboot to flush the stuck instance. The 112 cousin is different, that is GameGuard failing to load its modules, usually low memory or something the antivirus should catch, so scan and check the game's requirements.”
GameMon.des process and any lingering game process.GameGuard Error 115 means it is already running or the game was launched twice; Error 110 is a collision; Error 112 is a module-load failure. Close the game and end the GameMon.des process in Task Manager, launch one copy, and reboot to clear a stuck instance. Disable or whitelist security software, and for 112 run a virus scan and check the game's requirements.
If 115 or 110 returns immediately after ending the process, a background launcher may be auto-starting the game twice, or a corrupted GameGuard is stuck; disable auto-launch and delete the game's GameGuard folder to force a clean redownload. You can also submit your error to us for a tailored fix.