Bridge Commander Central
BC Forums => BC Technical Support => Topic started by: JamesTiberiusKirk on January 08, 2010, 05:55:05 PM
-
I have some strange BC-Crashes. Everytime I try to load (for example DJ's Ships) two or more high-quality ships, the game just returns to the desktop. It even happens when I try to fill in more ships.
I somehow think that its my new ram stick. got 2 2gigs, same specifications, but they dont seem to like each other (some bluescreens from time to time). Could it be a bc-problem or is it my memory?
-
lower the color depth
-
lower the color depth
that could never be the reason of any crash. atleast not with my computer specs
-
Then you won't have anything to loose by trying.
Sometimes it is not just the hardware you know.
-
It could indeed be those huge memory leaks BC has. When I use highly detailed and big ships, or ships that have pulse weapons etc, this game goes from 40% memory usage to 80% within 10-15 minutes, which is annoying. Then it usually crashes to desktop with "STBC.exe didn't shut down normally" and tries to find out the reason which it can't find, and then i just have to restart the game.. and the bigger the install, the sooner it happens.. :'(
-
Lionus is right (sadly). I also made the experience that BC doesn't like to load a Ship at the same time it is created (like AdShip does), (at least it doesn't like it if you create several ships at once). And Anything working with timers is a huge problem in my installs (but as that are mostly my mods, it could be because I still didn't figure out how to disable and remove them properly)
-
Could you take a photo of the bluescreen and attach it here the next time it happens?
If it is indeed a memory problem reducing the ram frequency or increasing the timings (CAS Latency, RAS to CAS delay, etc.) might help.
-
this thread is going too far offtopic at this point... perhaps it be best to go back to the original point pls?
thx :)
edit - thread cleaned...
-
Of cause :)
James... Did you try lowering the settings.
-
problem is, I never had these problems before i put my new ram in. atleast i think i did not
-
problem is, I never had these problems before i put my new ram in. atleast i think i did not
Come to think of it, I've encountered a similar problem before:
In that case the RAM was a part-1 of a two part set put into the wrong DIMM. Basically it was build for dual ram, but was placed as a single individual module.
You may want to try taking it out, or making sure that it is placed in the corresponding DIMM.
-
do you use km?
-
do you use km?
of course and i did before the crashes occured
-
km is very unstable, there is your anwser, it dosn't have a fix
-
KM is not the problem and it isn't as unstable as many Non KM modded installs can be.
-
km is very unstable, there is your anwser, it dosn't have a fix
If you would have read he said he uses KM [[ and did BEFORE the crash ]]
So as nebula said KM is Not the problem
JTK.. : if your mem- sticks dont like each other that can cause quite a problem.
-
km is very unstable, there is your anwser, it dosn't have a fix
Thats not true. :roll
Crashes stopped when i put out the new memory stick. So I guess ill leave it out.