Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Do you recall the exact error message? If it displays one at all?
Check to see if your Antivirus, or indeed, any other programs, are scheduled for a background scan at or within that time frame you leave the game in AFK and it crashes.
Run the Task Scheduler program, then click on 'Task Sceduler Library' on the left, to get a view on the possible culprits running at the scheduled time when the game is set to AFK but crashes. Disable the possible culprits and then reboot your system, and see if the error crops up again when you AFK.
(Type Task Schduler into search or Cortana function if you can't find it in Control Panel.)
It seems to be a notice from xingcode itself, when I click on "Log" button it will open the xingcode folder.
Thanks, I will check out this scheduler.
XMAG.XEM is one of the major culprits getting flagged, so add that to your antivirus' allowed list. it's located at the following directory:
Program Files (x86) > Steam > steamapps > common > Black Desert Online > bin64 > xc > na > 2
Is your game running fine or still getting errors? You haven't stated, so I'm wondering.
On a completely different note, but in the same line of thinking where XINGCODE3 is concerned, I've put myself in a position where I'll be receiving the "Fail To Init Security" error. ln hopes of tackling it on the current Windows 10 Insider Preview Builds, where a fix is no longer possible. Hopefully I'll get the stubborn error on my Insider Preview Build, but more importantly, I hope to come up with a possible fix to it, as it's one of the more stubborn errors to get around.