Memory Parity Crash
I am getting a memory parity crash when I try to use the ship designer. I had this problem with the 1.9 beta and now it persists in 2.0. Is this a known problem?
Any ideas on how to fix it
I am getting a memory parity crash when I try to use the ship designer. I had this problem with the 1.9 beta and now it persists in 2.0. Is this a known problem?
Any ideas on how to fix it
No, that's not a known error. Memory parity crashes are bad. Try running memtest.
How do I go about using the utility? It seems there is a pay version and a free version. I dl the freeware and ran it but got no display or results from running it
memtest is a program to test if your memory is alright or not
they come in a few different kind of packages
-either an executable that will make a bootable floppy or bootable USB key
-or a CD Image (ISO) which has to be burnt on CD (after being unzipped of course) and will make a bootable CD
in any case you'll end up with a bootable media which you should boot on
windows will be bypassed and the specific software of memtest will be launched and it will then proceed to testing your memory and telling you whether or not it found any problem in your hardware
I advise you to read the website (I know it can be a bother) as it contains a lot of information on how to do this & that and what kind of results to expect and such ...
Lastly, this should test out your RAM but in some cases you can get other errors ... and sometimes it can also be because your computer BIOS is not properly configured...
Thanks, I have since figured out the bootable floppy thing. I will run the test to see if there are any memory problems.
The thing that gets me is that until the final beta I have never had a crash problem with GCII and the memory parity crash has never happened with any other program. It would seem that if it is a memory problem it would be random and not relative to a single program
yeah you are right
don't get me wrong, maybe there's no problem with your memory sub-system. But in fact it really depends on how much the memory sub-system is stressed by applications and also what type of usage ...
so memory errors can be very very hard to track down since they may happen very infrequently depending on usage (and type of defect if present)
very few applications push the memory sub-system to its limits
that's why I try to buy expensive branded, with lifetime support memory modules, even though it's not a 100% guaranty of not having problems either ![]()
Well, well
I have not gotten around to the memory test but when I saw that the latest release addressed some crashes I decided to give it a try and it appears that it is fixed.
I played for over an hour with no crash where previously the crash came in less than 15 minutes.
I will still do the memory test at some point since it is probably an issue to some extent.
Welcome Guest! Please take the time to register with us.