CrySystem.DLL FIX 64 Bit OS

[Rawn]

Hello

I have been following this thread since I am having similar problems. I am running Windows 7 x64 with 6GB RAM and GT280 graphic card.

When looking through the eventlog I can also see that I'm getting the Crysystem.dll error. In my case it completely crashes my system and just shows major graphic faults on the screen and I have to hard boot the PC to use it again.

What I havnt seen in this thread is the other eventlog entry that I get just before I see the Crysystem.dll related event. Below is the event message

Activation context generation failed for "E:\Games\AionEU\bin32\MFC80.DLL". Dependent Assembly Microsoft.VC80.MFCLOC,processorArchitecture="x86", publicKeyToken="1fc8b3b9a1e18e3b",type="win32",ver sion="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis.

Searching through Google I found that this is also caused by other applications and the solution appears to be installing
Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) which I have installed now.

There is also a 2008 version, which I havnt installed in x86 version. Instead I installed the 2008 x64 version...
Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)

I have set my ingame graphic options back to maximum and I havnt crashed (I used to crash in random intervals). I have no clue if this fixes anything, but I figured it couldnt hurt trying

Also I have been monitoring the memory usage of Aion.bin and it doesnt seem to rise above 1.4GB. Been running around to different populated areas, while monitoring it.

Regards

Rawn

[Daireishi]

Originally Posted by Arazel

Just download the newest from M$ August 2009 Direct Link to M$ download below.

DirectX End-User Runtime Web Installer August 2009

To me, DX runtime seems like the most likely suspect. Have people that have this crashing problem tried using the above version of the DirectX runtime?

Has anyone had the crash while using the above Aug 2009 DX runtime?

[Arazel]

@ Azubah Your Welcome

@ Rawn Glad you solved your problem.

@ Daireishi The main problem lies with the crysystem.dll itself. Can't answer if the Dx installer has fixed it for anyone.

I was going to post the other CrySystem.DLL but since it's a completely unpacked version i don't want anyone to get in trouble with using it. They use Themida to encrypt the DLL.

[Charmille]

Took the second DLL and so far it is promising. With max settings I still crash but on slightly tuned down settings I'm running fine and the game is loading much faster when porting from one place to another. Gonna do some more tweaking but the DLL alone seems to atleast prolong the time between crashes for me which is worthy of two thumbs up Arazel!

Next gonna install the DX Aug version and see how that works out. Keep up the good work ^^

Update: The Aug 2009 DX runtime did not stop crashing. Went with max settings and crashed faster than before ^^; Time for more tweaking before I'll start pasting program lists etc. for you Arazel.

[Arazel]

@ Charmille Try page 1 tweaks i have listed as well. Nothing to do with the actual DLL but every little bit helps.

[Daireishi]

Originally Posted by Arazel

@ Daireishi The main problem lies with the crysystem.dll itself

The fault may manifest itself in CrySystem.dll, but that doesn't mean that's where the error that triggers the fault is located. It sounds like it has to do with how CrySystem.dll is handling memory pointers, or specifically, whether it checks for memory allocation problems. DX could be handing back null pointers that CrySystem.dll doesn't then handle properly...or maybe the crash message is how it handles it. Either way, DX is getting mapped into Aion's process space, its allocations would affect overall memory usage of the Aion process. If the DX version shipped with Aion had some memory management problems it could certainly manifest with a null pointer being handed back to CrySystem.dll which would then read the pointer and throw an exception.

That version of the DX runtime (Aug '09) is definitely worth testing for anyone that's having a crashing problem IMO. I would like to hear if it helps anyone that can easily reproduce this crash.

[Arazel]

@ Daireishi Although it does not hurt anything installing the Dx people still crash. So don't think the Dx play's as big of a role in the Crysystem as you may believe. See Charmille last statement above.

@ Charmille Check your PM.

[drakenbarion]

What is weird is that I got through a large scale seige without crashing, but not long after, I went to a small village and crashed. I had only 3 crashed in the past week tho. This DLL is much better so far.

A fix has to come. I think its foolish that a company would take so long, but you have to remember that they don't own the license for the cryengine either. They can get tweaks but I doubt they can change major things directly. Hopefully, the cryengine team will assist NCSoft quickly.

[Papander]

Placebo effect anyone?

[Arazel]

Originally Posted by drakenbarion

What is weird is that I got through a large scale seige without crashing, but not long after, I went to a small village and crashed. I had only 3 crashed in the past week tho. This DLL is much better so far.

A fix has to come. I think its foolish that a company would take so long, but you have to remember that they don't own the license for the cryengine either. They can get tweaks but I doubt they can change major things directly. Hopefully, the cryengine team will assist NCSoft quickly.

They don't own the engine your right. But they do have the license to modify the game engine.

@ Papander Sorry it won't work for you. You could always find a fix on your own. Or just wait on NcSoft. Personally i could care less but at least some people appreciate the fact that they can at least play.

[Unisolblade]

Thanks for this will try it the next siedge

[drakenbarion]

Originally Posted by Arazel

They don't own the engine your right. But they do have the license to modify the game engine.

I worded it badly. What I mean is that there may be aspects to the engine that NCSoft have no control of directly. We wont see the agreement that they have with the cryengine team, but those agreements might say what can and cannot be tweaked. So if memory management does not fall on the NCSoft side, then we all have to wait until cryengine team fix it.

But hopefully a fix is being worked into the next patch. Honestly, the description for the patch does not seem to have enough content to take as long as it has to since it just seems to be modifying variables such as the amount of exp received from gathering etc. That delay could mean that there are some other changes being made to the engine.

We all know how much QC these changes will have to go through. If they are trying to fix the crashing in the next patch, it is vital that they test it on as many setups as possible, so when they state that the crashing is fixed, it is true for as many users as possible. So for now we can only really bear with them.

Still, I am grateful for your temp Fix Arazel. I understand that you are limited to what you can do without the source, so lets hope things are fixed soon

[Nocturna]

I only tried 1 siege with this dll and i "only" crashed once right after we finished killing the boss.. usually i'd crash at the gate, dunno if i can say it worked for me Thanks for trying tho.

[Daireishi]

WTB 64-bit Aion client. Bet that'll fix OOM problems. Finally a consumer-level reason to have all that memory space.

I know Crysis had a 64-bit executable, bur CryEngine 1.0... not sure. Wasn't that FarCry 1 era?

[Ifalna]

Hmm not sure if anyone already said it, but about the L2 cache settings, I found this:

This is a myth.

The default value for this setting is 0, which tells Windows to auto-detect the correct value. Many settings in the registry work this way. The setting is only needed for ery old CPU’s, prior to the Pentium II. In no event will Windows set the detected value in the registry, it will remain at 0.

Windows only uses this value to optimize some low level memory allocations. The performance penalty for getting it wrong is very low, usually less than 2%. Windows does not use the cache, it is used only by the processor which will always use the full size.

Bottom line: Unless you are using a CPU more than 10 years old this setting will do nothing.

Larry Miller
Microsoft MCSA

Source: How to Set Vista for your CPU L2 Cache memory | Windows Reference

So I guess you can delete them from your initial post