Hello there,
The last few weeks I experience crashes to desktop in space and on ground, that ALWAYS return the same two Cryptic Error IDs:
268 and 595427.
When this happens, it seams that no memory dump or report is sent to Cryptic. The Error application simply closes and that's about it.
After the crashes I let the client verify itself and all, but this crashes still happen. I have to admit, that I am kind of glad, that my client doesn't crash that often any more, but when it does (once or twice a day) the Error IDs are 595427 and 268.
So please Cryptic:
Could you explain what the IDs mean so that I could narrow down the problem?
Could you explain why it is always the same IDs?
Shouldn't there be a new ID with every crash so that you can track it with your system or is this a strange way to pacify the people that got upset when the Error Application returned a "unknown" for the ID? I just wonder because I have not seen "unknown" IDs lately...
If you want to read my DXdiag etc. please go to the thread
--> HERE <-- .
Status: I have updated the graphics drivers and sounddrivers as new as possible, I even tried a second partition with fresh WinXP installation just for the game and I did a full memory and CPU check with memtest86+ and Orthos - no errors there. Temperature is under 60 °C and I am starting to run out of Ideas.
Thanks in advance
Comments
Also when you updated the driver did you
remove the old driver
rebooted
used a driver clearner/remove program to remove any bits of the old driver
rebooted
installed the new driver.
Yes I did use Driver Cleaner NET as you described and I will post my dxdiag later when I am home...
By the way: how should I attach my file, when there seems to be no option for that in this forum? I guess I would have to use some webspace elsewhere?
And I still would like to know what's up with this Error IDs, what they mean and why they do not change?
Since you reinstalled on a clean OS, and you are still getting the same errors. I believe this is a hardware related issue. So with this being said one thing I would recommended trying is testing your memory. There could be a bad block that the game uses causing these crashes. Microsoft has a program called Memtest installed to the OS so give that a try. You may also try removing one stick at a time to see if the crash reappears. Even if you do not have any other issues with any other programs this could be the cause. Keep in mind that the Cryptic engine uses portions of your hardware that many other games do not, or in different ways. I would also suggest running a disc scanning utility on your hard drive to ensure there are no bad blocks or sectors. If the game keeps reinstalling on a bad sector or blocks then this could cause issues.
Give those a try and let us know what you get back.
Any word on why the same Error IDs (595427 and 268) keep comming? Are they related to memory faults? That could be interesting, since I've seen after a search that in this forums there are several people that had the same Error IDs. I thought that Error IDs are for your Database to find the dumps that people sent you... But when one Error ID is related to a specific kind of Error, then it would be great to have a list what ID stands for which problem...
I do get a popup with the message:
devassert: 0;Attempted to add static string "Textures:Art" after AUTO_RUNs, not allowed
Me too. I havemade no changes, but am getting the error.
I'm inclined to think it's a hardware compatibility issue - perhaps the game doesn't like 64 bit OS's. It's really beginning to become too much of a hassle though since away mission progress isn't saved - it's always a fresh restart. I can't deal with clearing each away mission 4 times a piece.
A majority of the time if you are getting consistent crashing it is due to either hardware/os conflict or a hardware failure. Run some high level diagnostic tools on your hardware to make sure it is functioning properly. Also make sure your video and audio drivers are up to date.
I did remove one ram memory at a time (I have two 2 gig memories in my machine). The error occured both times. Maybe the two units are defect, but every other stress test did not bring up any errors - I checked that with memtest86+ and with the windows 7 memory check multiple times. Maybe I try using the memory of a friend's machine - he has no problems whatsoever...
But anyway: My initial question remains... what's up with the same Error IDs comming up again and again? Shouldn't they change with every crash or do the numbers 595427 and 268 stand for a certain type of error? Would be nice, if you could give a statement on that...