[Knite]

NC West is still trying to lock down exactly what is causing the Crysystem.dll error and they have asked us fansites to ask you for some feedback on the error so that our data can be forwarded off to the Korean developers.

Ayase has put together a form for those experiencing errors to fill out so that we can better understand what is causing this issue. Please head over to this link to fill out the form.

The best way to get this figured out is for all the feedback we can to be submitted, so if you find yourself crashing often under different circumstances, please fill out the form as many times as you can.

Here is what Ayase had to say about it:

Ayase said:

Just wanted to reply here to say that we haven't forgotten about this issue. It's a problem we're fully aware of, it exists, it's real, it's happening to many of you. I sent out an e-mail earlier today to fansites in order to help gather more information. We asked the fansite administrations to ask you guys for IPs and time of debug log report. Aionsource might post a request on the front page soon as well.

Basically, the best us non-techies can do right now is to gather all the information we can and pass it on. We're talking to the Korean developers to sort it out and want to make sure that all information possible is available when tracking this down.

1. If you are experiencing Crysystem.dll-crashese, contact our Customer Support (Support | NCsoft) with the crash debug log.

2. Fill out a little form I put up over at Google (as detailed as you can):

https://spreadsheets...FRi1EQjFmYlE6MA

Having this information will make it easier for us to find patterns and to filter out these reports from other matters when forwarding the necessary data.

Thanks in advance everyone. :)

Thanks for the help, everyone. Lets get this bug worked out!

[Loth]

This makes no sense, they must have hundred of thousands of error reports sent in via the Report thingie we get when we crash (multiple times a day).

All they need to do is look at the report spread sheet, I sure hope they have one, and not just dump our logs, and they have all the information they need.

I am sending a report every time I crash (which can be many times a day), and I am sure many others are doing the same, as this is potentially a game breaking issue, and we all want it to be fixed sooner rather than later.

So why exactly is it, that we need to send the report via mail now? I would really like to know this.

This post has been edited by Loth: 16 October 2009 - 07:52 PM

[shangriLOL]

Loth, it's not that you need 2 send the devs your crash report by email. They already have the report. They are asking you to let them know which crash report it is that you sent in. The form only asks for IP address (to identify the crash report as YOUR crash report), and when your Aion crash occured (so they can see which reports from your IP are pertinent).

This is awesome, please help out by sending in when your crash happened. This is standard operating procedure for software developers tracking crashes/bugs.

[scritchy]

shangriLOL said:

This is awesome, please help out by sending in when your crash happened. This is standard operating procedure for software developers tracking crashes/bugs.

Standard procedure would be including all the relevant information, including timestamps, in the log file itself or the report it generates when you hit the 'send' button.

[shangriLOL]

^yeah you're right. They should have created the system like that in the first place. But that's not how it is and ayase has set up the best way for their devs 2 tackel the issue, and there is no reason for us to complain about this little step. I'm sure they can search thru the errors for anything that has 2 do w/ crysystem.dll, but this will help just teh same by getting some more specific occurances and logs 2 work with...

I love this game and there is very little wrong with it that I can find (not talking about game mechanics - if you don't like how a game plays, its probably not for you). Since I lowered the texture quality, I haven't had many crashes. I also do shift+F12 whenever I'm in any citadel/fortress type area w/ lots of peeps.

Haha, funny I mentioned I haven't had many crashes, cause as I was typing that my Aion crashed. Off 2 send an error report lol...

[chobbo]

They only need look at our "technical support" forum to find a **** load of data about this very problem...

and wow...that spreadsheet asked no relevant questions >.> Thought the least they would ask is system specs.

This post has been edited by chobbo: 16 October 2009 - 11:29 PM

[Shriker]

I'm one of the lucky ones that only occasionally gets the error and crash. Every time it crashes, it sends an error report to someone. Next time it crashes I'll have to see whether it's Microsoft or NcSoft.

Honestly I never even thought to check. Maybe NcSoft could give Microsoft a call...

It's obviously NcSoft's problem as it occurs on all supported operating systems.

Everyone is getting the EXACT same message, crapping out trying to address some non-existent memory location. Basically the cryengine is trying to access memory location 0.0.0.0

I have some programming experience and the worst situations are always those intermittent errors that seem to have nothing in common so you have to dig and dig and play Sherlock Holmes and eventually figure out what the bug is.

There is only one cryengine error and it is always the exact same error unless I'm reading something in the forums that I am misinterpreting. If it happens on all versions of Windows (mine is VistaX64 with 6 gigs memory, FYI) then how hard can it be to figure out what is going on?

Like I said, I'm just a layman that has written some code, but it really seems like the problem is pretty pinned down and ready to be fixed.

Just out of curiosity, are there any systems that have NEVER had this crash? That would be where I would start in the analysis.

[shangriLOL]

chobbo said:

They only need look at our "technical support" forum to find a **** load of data about this very problem...

and wow...that spreadsheet asked no relevant questions >.> Thought the least they would ask is system specs.

They ask for the date and IP so that they can find the error report you sent in. That error report contains all the relevant data, specs, mem usage, files involved, etc. This is just to help them locate error reports for crashes that fit the criteria of the CrySystem.dll crash.

[The XiL]

ten


Yes because simply using crysystem.dll as a filter when the error is specifically called crysystem.dll is impossible. I spent 2 hours on the phone with the tech support retards. It took him two seconds to find a report. I told him "look for errors submitted while any fortress in the lower abyss has been vulnerable since release day." He says "oh wow I see what you mean."

These people are retarded. The left hand doesn't know what the right hand is doing but they both have a thumb buried deep in the same a$s.

They have been ignoring this problem since beta. Now that people are starting to participate in large scale PvP on a regular basis it's time they picked this game breaking bug up and dusted it off. This bug has been around for a long time. And I find it funny that one of the files GameGuard modifies in the client just happens to be causing the problem.


char

[Qetesh]

I get this a lot... at random, but especially during mass pvp.

[Loth]

shangriLOL said:

^yeah you're right. They should have created the system like that in the first place. But that's not how it is and ayase has set up the best way for their devs 2 tackel the issue, and there is no reason for us to complain about this little step. I'm sure they can search thru the errors for anything that has 2 do w/ crysystem.dll, but this will help just teh same by getting some more specific occurances and logs 2 work with...

I love this game and there is very little wrong with it that I can find (not talking about game mechanics - if you don't like how a game plays, its probably not for you). Since I lowered the texture quality, I haven't had many crashes. I also do shift+F12 whenever I'm in any citadel/fortress type area w/ lots of peeps.

Haha, funny I mentioned I haven't had many crashes, cause as I was typing that my Aion crashed. Off 2 send an error report lol...

I also really like this game, and for the time being, I can work through this issue, however, when I get to max level and, hopefully, mass PvP and some group vs. group PvP is what I will spend the majority of my time doing, this just will not do.

And to get some more specific occurances, umm, they do know that we crash in populated areas, they even know what the cause of the problem is, as it has been pinned in threads on this very messageboard with Ayase posting replys, so they well know what and when this issue pops up, and even a solution has been posted.

Also, I do believe the shift + F12 does nothing but lessen the burden on your video card by not having to display other players, the textures are still loaded to memory.

I might have been half asleep when I made my original post, and misunderstood the first step as sending support an email, they probably mean to just keep sending the error report generated by the game itself via the popup when we experience a crash, but the second step I will still maintain does nothing to fix this problem, as they have all the relevant data in their log db, or at least they should have.

[zekans]

So crashing is the only issue? the whole 5 FPS during mass PvP is just perfectly fine?

:s

[Arazel]

Anyone that has Windows 7 can use the PSR function. Just go to the start button, type in PSR stands for Problem Steps Recorder. It will record everything your program does and tells you what dll's are accessed in the process, and when it crashed. You can save those as a Txt document and send those in as well.

Most of the crashing is related to the 2 GB Virtual Memory Wall, so if you know what your doing and you have 64 bit windows you can patch the Aion.Bin file so it can read over the 2 Gb Virtual Memory Wall - most is 4 GB on a 64 bit system. This won't be a fix for everyone but for some it will help out or even stop the issue.

[Gallael]

I would find it hard to believe that they can't reproduce this problem themselves. Surely they have a QA department with many different types/brands/configurations of PCs. Heck, just go build a brand new top of the line computer like I did and you should be able to reproduce it pretty easy. Quad core, 6 gig ram, ATI 4980, Win7 64-bit. Just run around Morheim for a while with graphics on high.

[ILUV]

Wow I started getting this error last week in Elten and in the Abyss during a fortress battle last night and thought it was just me !!!!

This post has been edited by ILUV: 17 October 2009 - 09:33 AM
Reason for edit: *edit: Elten not Morheim lol*

[GundamHealer]

Good work, keep crashing and reporting guys lol.

I've crashed and sent logs like 30+ times now, if only i could remember the times of everyone they;d have a nice chunk of info to work with

[Chob]

Just set your OS to Korean if you don't want to crash.
100% confirmed

[Elendiel]

Damn do you people ever run out of things to complain about? Just send them any info you can so we can all see this fixed ASAP. who really cares if it's a little extra work as far as I'm concerned it's well worth it.
Thanks to everyone trying to fix this issue much appreciated:skip:

[Ekkio]

Elendiel said:

Damn do you people ever run out of things to complain about? Just send them any info you can so we can all see this fixed ASAP. who really cares if it's a little extra work as far as I'm concerned it's well worth it.
Thanks to everyone trying to fix this issue much appreciated:skip:

The confusion comes from being asked to fill out a basic form with basic information that's already in the crash log a user will typically send after the client folds (minus perhaps our IP address); I don't understand how this form helps, they already have a truckload of crash logs from players.

Call me cynical, but this sounds a lot more like a PR thing so that players will feel like NCsoft is tackling the issue.

[Arazel]

No crashing here, at least not yet. But then again i patched my Aion.Bin file.