CRASH Xigncode / Nexon anti cheat?

(Killgar) #1

About one minute into play (Whitechapel, US West obj server, 10:45 pm EST) the game crashed and got a popup window with some goofy “Where in the world is Carmen Sandiego” clipart and this message:

0xE019100B

Error:Suspicious program detected. Please close any other programs you have running and restart the game.

Hit the log button and it opened G:\Nexon Launcher\extraction\appdata\Binaries\XIGNCODE\client but I’m not sure if any of the XEM files would be useful

The only apps open were Xt, nexon launcher, firefox x2, and steam. Spybot-SD, AVG, steelseries engine, razer synapse, msi afterburner, and chrom app launcher in systray. I’ll close out/disable as much as possible and reply back later if I get the same result.

[Edit] closed everything then brought up task manager, had 6x CoherentUI_Host.exe32 (killed them, each got a "not responding dialog box) 3x ShooterGame-Win32-Shipping.exe32 (eating a ton of memory 3GB, couldn’t end process)

started nexon launcher and Xt again and the game froze at the server list, now I have 3x new coherentUI, 4x shootergame (5GB mem usage), 2x xxd.xem*32 and xm.exe…same suspicious program detected popup.

(Glottis-3D) #2

how about… turning off your cheats then???:D:D:D
stupid joke, i know…:slight_smile:

(shirosae) #3

I’ve been getting the same as the above for about a month. Play for a couple of minutes, then CTD with a goofy XIGNCODE error box.

I have a 765 KB xigncode.log binary file which gets updated every crash (it’s too big to upload here even when zipped), can’t see anything readable inside.

Stuff I’ve tried which didn’t work: Turning off AV.Turning off firewall. Turning off all background stuff I can. Trying to run DB immediately after a reboot having turned off all the background stuff I can. Updated drivers. Trying to play again after new updates.

Stuff I’ve tried which did work: Completely uninstalled all DB/Nexon stuff I could find, then reinstalled from a freshly downloaded installer (so whatever version was new two weeks ago). Got one session in just fine for a few hours, then the same crashes after restarting the client/game the next day.

Tried playing again yesterday after the new update, same crash, though the game ran fine through the training thing and frontend GUI. Crash happened a minute or so after joining a server.

(Nail) #4

full reboot ?

(Humate) #5

shirosae & OP… I think theres a couple of legitimate programs that are deemed suspicious - netlimiter I think is one, sandboxie could be another. Also from my understanding, with the exception of sandboxie - they dont need to be running to be flagged. I’m sure someone with a lot more knowledge on the subject could elaborate. Hope this helped.

(shirosae) #6

Both warm and cold boots.

In the time between the last working DB and the crashing, I’ve installed Wing Commander III and a new bibliography MiKTeX package. If either of those are being caught then welbia/xigncode/nexon/db can gtfo.

(Toomic) #7

Can you upload a log file for the game when this happens, log files are located here by default - C:\Users%username%\Documents\My Games\UnrealEngine3\ShooterGame\Logs

Could you also delete your xigncode.log and generate a new one that will hopefully be small enough to upload to the forums.

(shirosae) #8

[QUOTE=Toomic;511265]Can you upload a log file for the game when this happens, log files are located here by default - C:\Users%username%\Documents\My Games\UnrealEngine3\ShooterGame\Logs

Could you also delete your xigncode.log and generate a new one that will hopefully be small enough to upload to the forums.[/QUOTE]

I have a new “Launch.log” that is 400 KB in size, and a “xigncode.log” which is 210 KB in size. Zipped they’re respectively 85 KB and 26 KB. All of these are bigger than the 19 KB .txt / 16 KB .zip limit the forum is complaining about.

(BomBaKlaK) #9

Game crash over here also …

(Anti) #10

Folks if you’re having this issue please try going to C:\Nexon\Library\extraction\appdata\Binaries\XIGNCODE\client and delete the file xmag.xem, then try again. That might help. If it doesn’t please let us know in this thread.