Tree of Savior Forum

Random Client Crash inside dungeon - Can't enter again

Please fill in as much as you can :

Date and Time: 21/02/2016 - pm 8h43

Game Control Mode (Keyboard/Joypad/Mouse): Joypad

Bug Description :
I entered the dungeon and was playing normally. Then the game crashed randomly with a crash message then I needed to click Ok. After this I needed to open my game again and couldn’t enter the new Lv.240 instance dungeon (2 runs per day).

It is intermittent and usually happens on maps: 2nd Demon Prison, Workshop and Instances Dungeons: Lv.190, Lv.217, Lv.240 and the new Lv.240 (2 runs per day).

After the crash you can’t enter some dungeons if it was your last run, like Mercenary Post raids or Lv.240 (2 runs per day).

Steps to reproduce the issue :

  1. Intermittent error, can’t reproduce.

Screenshots / Video:
Event log:
"Application pop-up: Tree Of Savior: Client_tos.exe - Application Error : The instruction at 0x0000000000BC090A referenced memory at 0x00000000849D2000. The memory could not be written.

Click on OK to terminate the program"

~15h50 am:

16h am:

This happens a lot of times and the memory address changes from crash to crash.

System

  • CPU : Intel® Core™ i5-2450M CPU @ 2.50GHz 2.50 GHz
  • RAM : 6.00 GB
  • Graphics Card : NVIDIA GeForce GT 540M
  • Mainboard :
  • Storage : 1 TB (+1 TB external HDD)
  • OS : Windows 10
  • Internet Connection : Optical Fiber 10 MB/s download and upload.
  • Country, Region : Korean locale, English system language.

@STAFF_J @STAFF_John:
Is there a way this could be applied as a quickfix or at least sent to the devs to be fixed on international version? I’m sure that I’m not the only with these problems. Not even reinstalling the client helped to fix these crashes.

Possible ways to reduce damage/penalties for crashes:

  1. Allow entering these raids/instance dungeons again after crashes.

  2. Detect crashes and does not consume the instance count if the crash happened before the half of the time the parties usually takes to finish the raid.

And it would also help if this happens you got spawned near the dungeon NPC because when you crash you usually take 1-3 minutes to get near the instance dungeon entrance again.

Does the launcher have a Verify Integrity function? If yes try to use it and see if there are any corrupted file, other thing is, try to remove the english language pack from the game, it could be some inconsistency on the files that cause that too.

It does not have.

  1. I’ve already reinstalled the game.
  2. Already tried to use korean-only language.
  3. Already cleared friendlist and friendlist groups.
  4. Tired to defrag all my game files and then the entire system.
  5. Tried to play without Joypad.

Hmmm, I take you already updated all your drivers (VGA, sound, network, chipset, etc.).

Do the issue only happen on the map you reported or other area?

I would say depending on the area, it could be lack of RAM due to the load but i can’t say for sure.
Even so in the end the problem can be on the client files or lack of optimization on that map.

All updated and even tested older versions of NVIDIA drivers.

It can happen anywhere but these are more common, maybe because of the number of monsters but it already happened in other places like Lv.220 grinding map or so but these happened a lot less.

Well, I’m guessing the that if it was RAM it would be crashing for everyone if it’s running on x86 mode. And I’d say that 6 GB is enough to run the game considering iCBT 2 and how the game crashes even when there’s not even a lot of monsters in the screen.

If it was just lack of optimization everyone would crash but not everyone is crashing a lot, I’d say only a few people but I know people that were crashing most of the times on dungeon Lv.190 for an example.

I’m now trying to reinstall the game for a second time because this is already getting tiring. More than a month of game crashing almost every day x.x

I guess it’s something like thread concurrency issues along with some random lag spikes that makes code run into unexpected sections that aren’t using mutexes or semaphores when they should or something like this.

Yeah, the thing is, different setups cause different behaviors, but yeah, even tho 4 GB of Ram is the minimal, if the system can’t provide enough to the game run crashes are bound to happen, what OS are you using? Is it 64 bits? You can check how much memory you have free on the Task Manager, try open the game and leave it there (if you aren’t stuck on the map problem) right click on the Task Bar and click Task Manager (note that Windows 7 Task Manager window is really different from the Windows 8/10) i don’t remember if, on Win8/10, is called Show More or Show Details the small button on the bottom left of Task Manager


Mine is in portuguese so it may confuse you, but the first column is the CPU Max load and the use from each process the second is the Memory consumed and the use by each process.

One trick i can suggest you is to add the game executable on the DEP list, it says Windows 7 but it is basically the same for other versions, after finishing it will ask you to restart the system, do it and try to play again and see if it crashes.

Yes. Oh I am Brazilian :wink:

Yes. Windows 10 64 bit.

While playing ToS with everything running (TS, Chrome with tabs and so) on Process Explorer:

About DEP wasn’t it only about handling external processes from accessing other’s processes memory?

Yeah, that is why, sometimes windows have problems on managing memory addresses, DEP help on that, i had some games when i was using Win7 that crashed and even caused blue screen, so when i used DEP it ran smoothly, on Win10 i didn’t need to use it tho. Well its just a test anyway if it works nice if not then it is something on the client, other thing that i could ask you to try is to run the system with a clean boot, it is a bit of a pain but help to see if it fix, if it fix it can be some software that is causing conflict.

Speaking of which, you can try add the game folder on your AV exception list and see if you can play, i did on mine during iCBT because of that IPF error problem, it lessened the problem for me tbh.

Already tried clean boot and I installed my Windows in November only to play ToS, there’s almost nothing here aside from Skype, Chrome and so. Also AV and Firewall are disabled when playing after it started crashing but it didn’t change anything.

I’ll try disabling DEP or adding the game to the list but I doubt it would do anything.

Yeah if it really don’t solve then it could be something in one of the latest patches that could cause it, but try the DEP and check, never know if it work.

It’s crashing since January.

Yeah, probably some patch did it, but tbh, posting here something from the KR version will take a while to reach IMC i think, because they are focused there, ours here are probably on a queue. Well all we can do is wait and see. Let’s just hope it work with DEP.

I just hope this gets at least fixed on International version and they can forward reports to the devs if there are enough details, I think :c

They surely will, i heard they fixed a bunch of stuff on the KR version that we had here on the Int version.

By looking at the instruction address I guess it’s the same code crashing over and over.

The said instruction is from one of the components (Visual C) that is trying to access an address of memory being used or reserved.
Note that each time the error occur the memory address is different.

Just to make sure, other games work fine? The reason i am asking is, if it happen at random times even on other games, it is more likely to be a faulty memory module (hardware).

What you could try and do is repair the Visual C components (VC2005, VC2008, VC2010), and see if it helps

I have rhe same problem and it only crashed when i entered dungeon

1 Like

Hmm. It’s perfectly normal to throw exceptions in external modules if you called them with invalid parameters such as an already freed address or something like this.

The game also crashes without any messages or hangs from nothing sometimes. I’ll try to update VC runtime.

Yeah, other games works fine on Windows and Linux, even emulators. Any other program works fine.

And there’s a new thing, just now the client hanged and there’s a thread started at address 0x0:

Oh, the start address 0x0 is normal, when it’s running fine it’s like this:

Guessing about the two States (Running and Wait:UserRequest) I guess the client entered an infinite loop.

EDIT: Funny, now my entire party crashed, just the Linker survived :smiley:

Haha, yeah well the only thing you can try is update/repair the runtimes and see if it work, if not something on the latest patch messed up.

Wasn’t on latest patch since these are happening since January.

EDIT: Reinstalled all VC redist from 2005 to 2013, let’s see how it works now.