Yeah the ATI 9.9 drivers are crap, really really crap...anyways if your daring enough you could try some tweaked out drivers and see if they help you out. www.tweakforce.com/ These guys are pretty good and tweaking out drivers.
Check the previous page mate, someone has found a memory leak on the client... like we already knew, its not a driver problem, the client has a memory leak
$OE lies list http://www.rlmmo.com/viewtopic.php?t=424&start=0 " And I don't want to hear anything about "I don't believe in vampires" because *I* don't believe in vampires, but I believe in my own two eyes, and what *I* saw is ******* vampires! "
I crash a lot, particularly in crowded areas. There was another similiar thread a few days ago over @ ;AionSource, and it seemed to be mainly affecting ATI card owners (particulalrly high-end cards). I7 920 ATI 4890 Plus (1gig) 6 GB Corsair XMS3 (triple channel) WIN Vista 64bit
Note - the crashes aren't due to hardware failiure, though I haven't ruled out the possibility of a driver conflict somewhere.
I crashed on this game, my son does not. The only difference in our two machines are mine is a quad and i run an ati vid card. other than software, they are alike down to the power supplies and cases.
Yeah the ATI 9.9 drivers are crap, really really crap...anyways if your daring enough you could try some tweaked out drivers and see if they help you out. www.tweakforce.com/ These guys are pretty good and tweaking out drivers.
Check the previous page mate, someone has found a memory leak on the client... like we already knew, its not a driver problem, the client has a memory leak
Dang missed that lol, was reading reading and reading and i guess i just missed it lol, anyways, hope they fix it for ya all.
"The great thing about human language is that it prevents us from sticking to the matter at hand." - Lewis Thomas
To export the .dll and look at the code to see if it has any .dll dependancies. If it does, locate the source of the dependency and track down the problem from the source.
If the crysys.dll file isn't using any dependancies and is just a stand alone .dll module then the problem lies somewhere in the code of the .dll and needs to be handled by NCsoft.
If the .dll shows dependancies though, track them down, keep a log of where each trail is taking you, and you can probably pinpoint the issue there.
The problem lies in that file, and since you have stated this only started happening after a recent patch, I would venture to say, they changed some of the code in this particular .dll that is screwed up now causing crashes. If that is the case, It wouldn't matter what your system specs were or how clean your boot is, the .dll will crash the system.
A lot of people are bashing the OP for no reason what so ever. Clean Boot is for dummies who do not know enough about PC's to actually fix anything. Now typically a clean boot MIGHT solve your issue. This being a .dll issue though, isn't the case.
This problem lies on the game code, and possibly some part on the user.
Navigate to the game folder and find the crysys.dll or whatever you said was causing the issue. Then use something like this http://www.nirsoft.net/utils/dllexp.zip To export the .dll and look at the code to see if it has any .dll dependancies. If it does, locate the source of the dependency and track down the problem from the source. If the crysys.dll file isn't using any dependancies and is just a stand alone .dll module then the problem lies somewhere in the code of the .dll and needs to be handled by NCsoft. If the .dll shows dependancies though, track them down, keep a log of where each trail is taking you, and you can probably pinpoint the issue there. The problem lies in that file, and since you have stated this only started happening after a recent patch, I would venture to say, they changed some of the code in this particular .dll that is screwed up now causing crashes. If that is the case, It wouldn't matter what your system specs were or how clean your boot is, the .dll will crash the system. Hope this helps.
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
A lot of people are bashing the OP for no reason what so ever. Clean Boot is for dummies who do not know enough about PC's to actually fix anything. Now typically a clean boot MIGHT solve your issue. This being a .dll issue though, isn't the case.
This problem lies on the game code, and possibly some part on the user.
Navigate to the game folder and find the crysys.dll or whatever you said was causing the issue. Then use something like this http://www.nirsoft.net/utils/dllexp.zip To export the .dll and look at the code to see if it has any .dll dependancies. If it does, locate the source of the dependency and track down the problem from the source. If the crysys.dll file isn't using any dependancies and is just a stand alone .dll module then the problem lies somewhere in the code of the .dll and needs to be handled by NCsoft. If the .dll shows dependancies though, track them down, keep a log of where each trail is taking you, and you can probably pinpoint the issue there. The problem lies in that file, and since you have stated this only started happening after a recent patch, I would venture to say, they changed some of the code in this particular .dll that is screwed up now causing crashes. If that is the case, It wouldn't matter what your system specs were or how clean your boot is, the .dll will crash the system. Hope this helps.
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
You actually know what a memory leak is? Feel free to explain your view of a memory leak
A lot of people are bashing the OP for no reason what so ever. Clean Boot is for dummies who do not know enough about PC's to actually fix anything. Now typically a clean boot MIGHT solve your issue. This being a .dll issue though, isn't the case.
This problem lies on the game code, and possibly some part on the user.
Navigate to the game folder and find the crysys.dll or whatever you said was causing the issue. Then use something like this http://www.nirsoft.net/utils/dllexp.zip To export the .dll and look at the code to see if it has any .dll dependancies. If it does, locate the source of the dependency and track down the problem from the source. If the crysys.dll file isn't using any dependancies and is just a stand alone .dll module then the problem lies somewhere in the code of the .dll and needs to be handled by NCsoft. If the .dll shows dependancies though, track them down, keep a log of where each trail is taking you, and you can probably pinpoint the issue there. The problem lies in that file, and since you have stated this only started happening after a recent patch, I would venture to say, they changed some of the code in this particular .dll that is screwed up now causing crashes. If that is the case, It wouldn't matter what your system specs were or how clean your boot is, the .dll will crash the system. Hope this helps.
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
Because of the part I labeled in red. I do not own AION or I would gladly investigate for everyone. Sometimes .dll files point specifically to other processes of the PC to make them work.
For example, though this is very far fetched and more than likely would never happen.
This .dll could say look for ATI driver aticore9_1.dll - aticore9_4.dll if file not present FALSE (false would equal crash).
Meaning if an ATI user were using anything later than driver 9.1-9.4 the system can't read it and would crash.
This would be a user problem.
The above is a very generic and crude example of an instance a .dll could be dependant on.
My point was, it MIGHT be solely on the .dll code, or it could be pointing to something on the users system, that they either do not have, isn't up to date, or is corrupt in itself, and would cause the client to stop responding and crash.
You are right though, since it doesn't happen to everyone, it very well could be some strange dependancy that all these unfortunate users share that are causing them to crash.
I was trying to point out that clean booting something helps, but won't fix a code problem or missing dependancy in a .dll file.
Track this problem down at the source root cause of it. Anytime I game and I get a file system error. First thing I do before I try anything else, even clean boot, is research the file, locate it, and trace the problem of the file first. If I can't solve the problem at it's root, then I start looking into other means of help.
A lot of people are bashing the OP for no reason what so ever. Clean Boot is for dummies who do not know enough about PC's to actually fix anything. Now typically a clean boot MIGHT solve your issue. This being a .dll issue though, isn't the case.
This problem lies on the game code, and possibly some part on the user.
Navigate to the game folder and find the crysys.dll or whatever you said was causing the issue. Then use something like this http://www.nirsoft.net/utils/dllexp.zip To export the .dll and look at the code to see if it has any .dll dependancies. If it does, locate the source of the dependency and track down the problem from the source. If the crysys.dll file isn't using any dependancies and is just a stand alone .dll module then the problem lies somewhere in the code of the .dll and needs to be handled by NCsoft. If the .dll shows dependancies though, track them down, keep a log of where each trail is taking you, and you can probably pinpoint the issue there. The problem lies in that file, and since you have stated this only started happening after a recent patch, I would venture to say, they changed some of the code in this particular .dll that is screwed up now causing crashes. If that is the case, It wouldn't matter what your system specs were or how clean your boot is, the .dll will crash the system. Hope this helps.
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
You actually know what a memory leak is? Feel free to explain your view of a memory leak
A memory leak is a routine/program that takes up more and more memory the longer it runs. Not able to release memory it has used so to speak...
...and since I have run this program for long periods of time, I would think I would have noticed...and I haven't. Hence the question. You ok with me asking a question???
A lot of people are bashing the OP for no reason what so ever. Clean Boot is for dummies who do not know enough about PC's to actually fix anything. Now typically a clean boot MIGHT solve your issue. This being a .dll issue though, isn't the case.
This problem lies on the game code, and possibly some part on the user.
Navigate to the game folder and find the crysys.dll or whatever you said was causing the issue. Then use something like this http://www.nirsoft.net/utils/dllexp.zip To export the .dll and look at the code to see if it has any .dll dependancies. If it does, locate the source of the dependency and track down the problem from the source. If the crysys.dll file isn't using any dependancies and is just a stand alone .dll module then the problem lies somewhere in the code of the .dll and needs to be handled by NCsoft. If the .dll shows dependancies though, track them down, keep a log of where each trail is taking you, and you can probably pinpoint the issue there. The problem lies in that file, and since you have stated this only started happening after a recent patch, I would venture to say, they changed some of the code in this particular .dll that is screwed up now causing crashes. If that is the case, It wouldn't matter what your system specs were or how clean your boot is, the .dll will crash the system. Hope this helps.
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
Because of the part I labeled in red. I do not own AION or I would gladly investigate for everyone. Sometimes .dll files point specifically to other processes of the PC to make them work.
For example, though this is very far fetched and more than likely would never happen.
This .dll could say look for ATI driver aticore9_1.dll - aticore9_4.dll if file not present FALSE (false would equal crash).
Meaning if an ATI user were using anything later than driver 9.1-9.4 the system can't read it and would crash.
This would be a user problem.
The above is a very generic and crude example of an instance a .dll could be dependant on.
My point was, it MIGHT be solely on the .dll code, or it could be pointing to something on the users system, that they either do not have, isn't up to date, or is corrupt in itself, and would cause the client to stop responding and crash.
You are right though, since it doesn't happen to everyone, it very well could be some strange dependancy that all these unfortunate users share that are causing them to crash.
I was trying to point out that clean booting something helps, but won't fix a code problem or missing dependancy in a .dll file.
Track this problem down at the source root cause of it. Anytime I game and I get a file system error. First thing I do before I try anything else, even clean boot, is research the file, locate it, and trace the problem of the file first. If I can't solve the problem at it's root, then I start looking into other means of help.
why do people with crap pc's or dont know how to tweak thier game rigs always blame the game they are trying to play .... nubs
if you are reading this u have at least the basic knowledge to use the internet learn to tweak your system , search is a wonderfull thing
i have a crappy pc only thing that bothers me is i cant play it on max settings apart from that it runs fine, not all faults are with the game most of the time its your pc or the muppet user who "thinks" he is a computer genius and knows it all and the game devs and all the other gamers in the world are talking crap
Im wondering the same thing as some of the other posters, if the problem is with the client why arent more people having the issue? I ask only to alleviate my own ignorance on the subject, not to exacerbate the conflict.
i dont mind player posting stuff that dont work yes it did happen before ,but i got to say on my amd x2 4600+,with 4 gig of ram and nvidia8800gt game run smooth most of the time (when no gold seller are around (grin)
the only thing i would love ncsoft to do more often is restart their server more often
that being said ,some stuff still arent supported
exemple sli got support from nvidia only this week
so give it time they ll find what the deal is with those that have problem,it could be a memory leak
A lot of people are bashing the OP for no reason what so ever. Clean Boot is for dummies who do not know enough about PC's to actually fix anything. Now typically a clean boot MIGHT solve your issue. This being a .dll issue though, isn't the case.
This problem lies on the game code, and possibly some part on the user.
Navigate to the game folder and find the crysys.dll or whatever you said was causing the issue. Then use something like this http://www.nirsoft.net/utils/dllexp.zip To export the .dll and look at the code to see if it has any .dll dependancies. If it does, locate the source of the dependency and track down the problem from the source. If the crysys.dll file isn't using any dependancies and is just a stand alone .dll module then the problem lies somewhere in the code of the .dll and needs to be handled by NCsoft. If the .dll shows dependancies though, track them down, keep a log of where each trail is taking you, and you can probably pinpoint the issue there. The problem lies in that file, and since you have stated this only started happening after a recent patch, I would venture to say, they changed some of the code in this particular .dll that is screwed up now causing crashes. If that is the case, It wouldn't matter what your system specs were or how clean your boot is, the .dll will crash the system. Hope this helps.
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
Because of the part I labeled in red. I do not own AION or I would gladly investigate for everyone. Sometimes .dll files point specifically to other processes of the PC to make them work.
For example, though this is very far fetched and more than likely would never happen.
This .dll could say look for ATI driver aticore9_1.dll - aticore9_4.dll if file not present FALSE (false would equal crash).
Meaning if an ATI user were using anything later than driver 9.1-9.4 the system can't read it and would crash.
This would be a user problem.
The above is a very generic and crude example of an instance a .dll could be dependant on.
My point was, it MIGHT be solely on the .dll code, or it could be pointing to something on the users system, that they either do not have, isn't up to date, or is corrupt in itself, and would cause the client to stop responding and crash.
You are right though, since it doesn't happen to everyone, it very well could be some strange dependancy that all these unfortunate users share that are causing them to crash.
I was trying to point out that clean booting something helps, but won't fix a code problem or missing dependancy in a .dll file.
Track this problem down at the source root cause of it. Anytime I game and I get a file system error. First thing I do before I try anything else, even clean boot, is research the file, locate it, and trace the problem of the file first. If I can't solve the problem at it's root, then I start looking into other means of help.
your right ,the first thing everybody should do is write down the error or if they can take a screen shot of it
and then google it .hell i actually never done this ,i ll try to remember it ,lol often im so ticked of by getting issue i see red and forget these things
drbaltazar, just go to the previous page of the thread and actually read it, there are links for many things and images. stop making stupid posts that dont help in any way.... and please, take care of that english
Thousands of people have this problem because their computers are not up to system standards. Lots of people are playing on laptops or under-performing computers, not because the game is flawed. I personally have not experienced this at all.
This.
Last week it hit me too. I used to laugh at people who run dated rigs, but now I have entered the club too. Must be an age thing or something.
This is a new development for those saying thats our problem and not client problem. This is a post from another user, i hope theres no problem in posting it here, its on the last page of the first link i provided inc ase anyone want to check it out. Read it from the bottom up since its a reply e-mail with 2 or 3 replys
"well heres my talk with ncsoft so far about the issue through customer support. Just replied to the latest message seems the response rate is 24 hours or just slightly more, ill reply back here with the response.
Subject
Client Crashes - Memory Leak Discussion Thread
Response (Mike L.) 10/07/2009 07:29 PM
Hello -----, When you noticed the Ram usage going over 2GB what were you doing in game exactly? Also does it do this all the time or is it just when you go to specific areas? Can you also provide us with a screenshot of the task manager showing the high memory usage? Regards,
Mike
NCsoft Technical Support
Response (Robert) 10/06/2009 05:51 AM
Hi -----, Thank you for contacting NCsoft Technical Support. I am escalating your ticket for further assistance. Once your ticket has been reviewed someone will be in contact with you as soon as possible. Regards,
Robert
NCsoft Technical Support Billing and Technical Support can be reached via phone,
Monday - Friday, 12pm - 5pm Central at (512) 225-6359.
Customer (-------) 10/05/2009 02:15 AM
Hi this is becoming now a very serious problem. 100s of people are suffering from client crashes but are blaming graphics cards and drivers but I have managed to locate the real problem. The problem is a memory leak in the game engine where textures are the main cause of it. Aion is a 32 bit app but is trying to take more ram than is allowed. A 32 bit application is not allowed by windows to use more than 2GB of ram, if you have exactly 2GB of Ram you might not crash but most people like me have alot more. Aion detects that we have more ram and as soon as it reaches 2GB it tries to take more then crashes and it ALWAYS crashes when it reaches using 2GB of ram.
I have 6GB of ram and I wouldn't mind it taking more but it can't as its a 32bit application. However aion shouldn't need more than 2GB of ram it keeps eating ram because theres a leak somewhere and I believe it is linked with the textures. My computer specs
Windows 7 64 Bit
Intel Core i7 920 @ 3.6ghz
6GB Tri-Channel Ram
Nvidia Geforce GTX 260 latest drivers
Directx 9 is fully updated using the march 2009 SDK
directx10 and 11 updated as well Please can you forward this to the technical department and also can you please arrange for someone to address the problem so people know a fix will be on its way. Question Reference #091005-000802
Category Level 1: Technical Support
Date Created: 10/05/2009 02:15 AM
Last Updated: 10/07/2009 07:29 PM
Status: In Progress
Department: Tech Support
NCsoft Account: Unknown
Game Account: Unknown
Operating System: Unknown
Character Name:"
There you go folks, someone has found the memory leak...
you do know this is a 32 bit game right,lol
64 bit isnt officially supported yet so any issue is prob related to that in your case
This is a new development for those saying thats our problem and not client problem. This is a post from another user, i hope theres no problem in posting it here, its on the last page of the first link i provided inc ase anyone want to check it out. Read it from the bottom up since its a reply e-mail with 2 or 3 replys
"well heres my talk with ncsoft so far about the issue through customer support. Just replied to the latest message seems the response rate is 24 hours or just slightly more, ill reply back here with the response.
Subject
Client Crashes - Memory Leak Discussion Thread
Response (Mike L.) 10/07/2009 07:29 PM
Hello -----, When you noticed the Ram usage going over 2GB what were you doing in game exactly? Also does it do this all the time or is it just when you go to specific areas? Can you also provide us with a screenshot of the task manager showing the high memory usage? Regards,
Mike
NCsoft Technical Support
Response (Robert) 10/06/2009 05:51 AM
Hi -----, Thank you for contacting NCsoft Technical Support. I am escalating your ticket for further assistance. Once your ticket has been reviewed someone will be in contact with you as soon as possible. Regards,
Robert
NCsoft Technical Support Billing and Technical Support can be reached via phone,
Monday - Friday, 12pm - 5pm Central at (512) 225-6359.
Customer (-------) 10/05/2009 02:15 AM
Hi this is becoming now a very serious problem. 100s of people are suffering from client crashes but are blaming graphics cards and drivers but I have managed to locate the real problem. The problem is a memory leak in the game engine where textures are the main cause of it. Aion is a 32 bit app but is trying to take more ram than is allowed. A 32 bit application is not allowed by windows to use more than 2GB of ram, if you have exactly 2GB of Ram you might not crash but most people like me have alot more. Aion detects that we have more ram and as soon as it reaches 2GB it tries to take more then crashes and it ALWAYS crashes when it reaches using 2GB of ram.
I have 6GB of ram and I wouldn't mind it taking more but it can't as its a 32bit application. However aion shouldn't need more than 2GB of ram it keeps eating ram because theres a leak somewhere and I believe it is linked with the textures. My computer specs
Windows 7 64 Bit
Intel Core i7 920 @ 3.6ghz
6GB Tri-Channel Ram
Nvidia Geforce GTX 260 latest drivers
Directx 9 is fully updated using the march 2009 SDK
directx10 and 11 updated as well Please can you forward this to the technical department and also can you please arrange for someone to address the problem so people know a fix will be on its way. Question Reference #091005-000802
Category Level 1: Technical Support
Date Created: 10/05/2009 02:15 AM
Last Updated: 10/07/2009 07:29 PM
Status: In Progress
Department: Tech Support
NCsoft Account: Unknown
Game Account: Unknown
Operating System: Unknown
Character Name:"
There you go folks, someone has found the memory leak...
you do know this is a 32 bit game right,lol
64 bit isnt officially supported yet so any issue is prob related to that in your case
A few other things to note:
- The guy is complaining about crashes on a currently unofficially released OS that is probably not advertised as being supported by Aion. Sure it launches this month, but it is not out officially yet.
- He states his system is running on the Intel i7 920 3.66ghz... the 920 is a 2.66ghz processor. This makes me wonder if he even knows what is running under his hood. Can the 920 be OC'd to 3.66? I doubt it.
My system is almost identical to his, if not identical. Same CPU, 6 gigs tri-ram, GTX 260, the works... accept I am running Vista Ultimae 64bit. I have yet to experience any crashes. Granted I have not yet reached the Abyss, but I have four level 20 characters and never experienced a crash in a city or over crowded area. Worse I have had is rubber banding which tends to fix itself after fifteen minutes of play or so.
Note saying there isn't a problem out there, but this guy saying he has found a memory leak doesn't mean it is true. I can right support and say I am God and they should bow down before me, but that doesn't make it so.
Anyway, hope the people having issues with the crashes are able to get that fixed. Have a good day, people!
why do people with crap pc's or dont know how to tweak thier game rigs always blame the game they are trying to play .... nubs
if you are reading this u have at least the basic knowledge to use the internet learn to tweak your system , search is a wonderfull thing
i have a crappy pc only thing that bothers me is i cant play it on max settings apart from that it runs fine, not all faults are with the game most of the time its your pc or the muppet user who "thinks" he is a computer genius and knows it all and the game devs and all the other gamers in the world are talking crap
The thing you don't realize is that I ran the same system through cb (ver. 1.1) with no crashes and no issues. The crashes have only happened recently. There are NUMEROUS posts on AIONsource and the official forums of client crashes. Even people in our own legion are suffering through this mess.
Comments
Check the previous page mate, someone has found a memory leak on the client... like we already knew, its not a driver problem, the client has a memory leak
totally unplayable? nah. not THAT bad.
I've seen worse
$OE lies list
http://www.rlmmo.com/viewtopic.php?t=424&start=0
"
And I don't want to hear anything about "I don't believe in vampires" because *I* don't believe in vampires, but I believe in my own two eyes, and what *I* saw is ******* vampires! "
I crashed on this game, my son does not. The only difference in our two machines are mine is a quad and i run an ati vid card. other than software, they are alike down to the power supplies and cases.
Check the previous page mate, someone has found a memory leak on the client... like we already knew, its not a driver problem, the client has a memory leak
Dang missed that lol, was reading reading and reading and i guess i just missed it lol, anyways, hope they fix it for ya all.
"The great thing about human language is that it prevents us from sticking to the matter at hand."
- Lewis Thomas
A lot of people are bashing the OP for no reason what so ever.
Clean Boot is for dummies who do not know enough about PC's to actually fix anything.
Now typically a clean boot MIGHT solve your issue. This being a .dll issue though, isn't the case.
This problem lies on the game code, and possibly some part on the user.
Navigate to the game folder and find the crysys.dll or whatever you said was causing the issue.
Then use something like this
http://www.nirsoft.net/utils/dllexp.zip
To export the .dll and look at the code to see if it has any .dll dependancies. If it does, locate the source of the dependency and track down the problem from the source.
If the crysys.dll file isn't using any dependancies and is just a stand alone .dll module then the problem lies somewhere in the code of the .dll and needs to be handled by NCsoft.
If the .dll shows dependancies though, track them down, keep a log of where each trail is taking you, and you can probably pinpoint the issue there.
The problem lies in that file, and since you have stated this only started happening after a recent patch, I would venture to say, they changed some of the code in this particular .dll that is screwed up now causing crashes. If that is the case, It wouldn't matter what your system specs were or how clean your boot is, the .dll will crash the system.
Hope this helps.
Hmm haven't had a problem yet... but it's only early days for me.
Anyone remember AoC? Wow now that was FUBAR when it came to crashes!
O_o o_O
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
Waiting for a game that never comes...
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
You actually know what a memory leak is? Feel free to explain your view of a memory leak
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
Because of the part I labeled in red. I do not own AION or I would gladly investigate for everyone. Sometimes .dll files point specifically to other processes of the PC to make them work.
For example, though this is very far fetched and more than likely would never happen.
This .dll could say look for ATI driver aticore9_1.dll - aticore9_4.dll if file not present FALSE (false would equal crash).
Meaning if an ATI user were using anything later than driver 9.1-9.4 the system can't read it and would crash.
This would be a user problem.
The above is a very generic and crude example of an instance a .dll could be dependant on.
My point was, it MIGHT be solely on the .dll code, or it could be pointing to something on the users system, that they either do not have, isn't up to date, or is corrupt in itself, and would cause the client to stop responding and crash.
You are right though, since it doesn't happen to everyone, it very well could be some strange dependancy that all these unfortunate users share that are causing them to crash.
I was trying to point out that clean booting something helps, but won't fix a code problem or missing dependancy in a .dll file.
Track this problem down at the source root cause of it. Anytime I game and I get a file system error. First thing I do before I try anything else, even clean boot, is research the file, locate it, and trace the problem of the file first. If I can't solve the problem at it's root, then I start looking into other means of help.
My game has not crashed at all since i've gotten it. I have never had a graphics error or anything =/
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
You actually know what a memory leak is? Feel free to explain your view of a memory leak
A memory leak is a routine/program that takes up more and more memory the longer it runs. Not able to release memory it has used so to speak...
...and since I have run this program for long periods of time, I would think I would have noticed...and I haven't. Hence the question. You ok with me asking a question???
Edit: Spelling terrors
Waiting for a game that never comes...
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
Because of the part I labeled in red. I do not own AION or I would gladly investigate for everyone. Sometimes .dll files point specifically to other processes of the PC to make them work.
For example, though this is very far fetched and more than likely would never happen.
This .dll could say look for ATI driver aticore9_1.dll - aticore9_4.dll if file not present FALSE (false would equal crash).
Meaning if an ATI user were using anything later than driver 9.1-9.4 the system can't read it and would crash.
This would be a user problem.
The above is a very generic and crude example of an instance a .dll could be dependant on.
My point was, it MIGHT be solely on the .dll code, or it could be pointing to something on the users system, that they either do not have, isn't up to date, or is corrupt in itself, and would cause the client to stop responding and crash.
You are right though, since it doesn't happen to everyone, it very well could be some strange dependancy that all these unfortunate users share that are causing them to crash.
I was trying to point out that clean booting something helps, but won't fix a code problem or missing dependancy in a .dll file.
Track this problem down at the source root cause of it. Anytime I game and I get a file system error. First thing I do before I try anything else, even clean boot, is research the file, locate it, and trace the problem of the file first. If I can't solve the problem at it's root, then I start looking into other means of help.
Thanks for an enlightening answer...
Waiting for a game that never comes...
why do people with crap pc's or dont know how to tweak thier game rigs always blame the game they are trying to play .... nubs
if you are reading this u have at least the basic knowledge to use the internet learn to tweak your system , search is a wonderfull thing
i have a crappy pc only thing that bothers me is i cant play it on max settings apart from that it runs fine, not all faults are with the game most of the time its your pc or the muppet user who "thinks" he is a computer genius and knows it all and the game devs and all the other gamers in the world are talking crap
Im wondering the same thing as some of the other posters, if the problem is with the client why arent more people having the issue? I ask only to alleviate my own ignorance on the subject, not to exacerbate the conflict.
mm link the leak ,the exact leak not a story about possible leak lol.
i dont mind player posting stuff that dont work yes it did happen before ,but i got to say on my amd x2 4600+,with 4 gig of ram and nvidia8800gt game run smooth most of the time (when no gold seller are around (grin)
the only thing i would love ncsoft to do more often is restart their server more often
that being said ,some stuff still arent supported
exemple sli got support from nvidia only this week
so give it time they ll find what the deal is with those that have problem,it could be a memory leak
just show what the exact leak is
Since you explained that rather well, I have a question for you. I have no worries with this game...has the same dll as anyone else, and plays on the same patch...
I have been in big battles...and in cities with so many people that I couldn't find any NPCs...I have NEVER had any crashes.
So...if it is that DLLs fault some guys keep on crashing...or a memory leak...why aren't everyone experiencing it???
Because of the part I labeled in red. I do not own AION or I would gladly investigate for everyone. Sometimes .dll files point specifically to other processes of the PC to make them work.
For example, though this is very far fetched and more than likely would never happen.
This .dll could say look for ATI driver aticore9_1.dll - aticore9_4.dll if file not present FALSE (false would equal crash).
Meaning if an ATI user were using anything later than driver 9.1-9.4 the system can't read it and would crash.
This would be a user problem.
The above is a very generic and crude example of an instance a .dll could be dependant on.
My point was, it MIGHT be solely on the .dll code, or it could be pointing to something on the users system, that they either do not have, isn't up to date, or is corrupt in itself, and would cause the client to stop responding and crash.
You are right though, since it doesn't happen to everyone, it very well could be some strange dependancy that all these unfortunate users share that are causing them to crash.
I was trying to point out that clean booting something helps, but won't fix a code problem or missing dependancy in a .dll file.
Track this problem down at the source root cause of it. Anytime I game and I get a file system error. First thing I do before I try anything else, even clean boot, is research the file, locate it, and trace the problem of the file first. If I can't solve the problem at it's root, then I start looking into other means of help.
your right ,the first thing everybody should do is write down the error or if they can take a screen shot of it
and then google it .hell i actually never done this ,i ll try to remember it ,lol often im so ticked of by getting issue i see red and forget these things
drbaltazar, just go to the previous page of the thread and actually read it, there are links for many things and images. stop making stupid posts that dont help in any way.... and please, take care of that english
This.
Last week it hit me too. I used to laugh at people who run dated rigs, but now I have entered the club too. Must be an age thing or something.
Specs: Q6600, P35 MOBO, 4GB crappy DDR2, NVGTX260OC.
And yes, I really thought I could run games with that one. I'm purchasing i7-920, 4GB DDR3 2000MHz, Asus P6T Deluxe MOBO and second GTX260 to SLI.
It's just inevitable that games develop and need better gear.
Everything is OK.
www.fz.se/wtf/item.fz
arent these guys the same that do togear lol
good link lol
you do know this is a 32 bit game right,lol
64 bit isnt officially supported yet so any issue is prob related to that in your case
you do know this is a 32 bit game right,lol
64 bit isnt officially supported yet so any issue is prob related to that in your case
A few other things to note:
- The guy is complaining about crashes on a currently unofficially released OS that is probably not advertised as being supported by Aion. Sure it launches this month, but it is not out officially yet.
- He states his system is running on the Intel i7 920 3.66ghz... the 920 is a 2.66ghz processor. This makes me wonder if he even knows what is running under his hood. Can the 920 be OC'd to 3.66? I doubt it.
My system is almost identical to his, if not identical. Same CPU, 6 gigs tri-ram, GTX 260, the works... accept I am running Vista Ultimae 64bit. I have yet to experience any crashes. Granted I have not yet reached the Abyss, but I have four level 20 characters and never experienced a crash in a city or over crowded area. Worse I have had is rubber banding which tends to fix itself after fifteen minutes of play or so.
Note saying there isn't a problem out there, but this guy saying he has found a memory leak doesn't mean it is true. I can right support and say I am God and they should bow down before me, but that doesn't make it so.
Anyway, hope the people having issues with the crashes are able to get that fixed. Have a good day, people!
The thing you don't realize is that I ran the same system through cb (ver. 1.1) with no crashes and no issues. The crashes have only happened recently. There are NUMEROUS posts on AIONsource and the official forums of client crashes. Even people in our own legion are suffering through this mess.
I have experienced exactly 0 crashes on Windows 7, 64-bit. And that statement isnt limited to Aion.
As with every OS, its the hardware specs that cause the crashes. The OS isnt to blame in most cases.