Here's a post from the ATI forum that sums up the problem nicely:
Quote
and I watched "Virtual Size" for Aion.bin.
I went to Eltnen Fortress, and saw that the application reserved itself a bigger chunk of Virtual Size, kept running around like crazy watching as many people as possible, and the "Virtual Size" kept going up to almost 2GB.
Then poof, the CrySystem.dll error
Aion.bin reserved itself up to 2 038 952K
The second it tries to increase that size to over 2GB the application closes with the dreaded CrySystem.dll error... That's why it tries to write to adress 00000000 as it's trying to write outside the 2GB boundary, and it's either not allowed by Windows, or it can't handle it itself.
Numerous users have contacted NCSoft and even their video card makers about this issue already, and have been either shrugged off and pointed elsewhere or told completely useless things like "try a different video card." We need everyone to pester NCSoft until they at least acknowledge the problem.
Reducing the memory usage by turning down details will mitigate the crashes but is not an acceptable fix. It'll also be interesting to know if K-Aion has the same issue, as I can't imagine how that got out of beta testing (well, obviously a lot of things did...)
Please only vote if you have taken part in a castle siege.
Just trying to collect some data to see if there's a trend. Based on anecdotes the crashes don't seem to be tied to machine performance, though reducing graphic settings may reduce their frequency. Most of the time they occur with no predictability, as if the client simply gave up. Many people say they don' t recall crashing as frequently in such a situation on C-Aion or K-Aion.
This post has been edited by tpg0007: 08 October 2009 - 10:30 AM

Sign In
Register
Help




MultiQuote

