I am using Windows Server 2003 SP1, and it might be a problem... whatever, let me say my worst bug.
Today was the first time I 'was going to play' spring.
I got a chat with some users and got some infos from them.
And I started game.
When game screen got up, for a few second it was alright, but after a few seconds after that, my monitor blacked out and my COMPUTER ITSELF was totally FREEZED-And monitor was not getting any signs from computer.
Worse, this worst bug repeated.
What is the problem and how can I fix it?
The worst bug-Spring shuts down computer
Moderator: Moderators
Yeah, I was getting a lot of that too on 2003... I just said to hell with it and dumbed myself down to XP since the drivers didn't puke all over the OS (as much). The good news is that if you downgrade and if you have your docs and settings folder for 2k3 on a different drive/partition, XP will read that data just fine 
But yeah, try upgrading video drivers first and see if that fixes it. Also consider testing your RAM (Spring was bluescreening me a lot when I had a bad stick in).
But yeah, try upgrading video drivers first and see if that fixes it. Also consider testing your RAM (Spring was bluescreening me a lot when I had a bad stick in).
uneffortunally my grahic card did kill my computer, my motherboard has lost the abillity to remember BIOS and CMOS, and cant recogonize all the drives at some bootups. however i can communicate with ya because i had a lucky bootup, no jokeBut your graphic card driver CAN kill your computer, and spring may just use it in a way it doesnt like.
i dont think it was spring, but just remember computers are not perfect. afterall i got my motherboard for less than 30 dollars from a friend, and its giving out
-
CaptainMaim
- Posts: 265
- Joined: 04 Sep 2005, 01:25
A few versions back I started getting a bug where everytime Spring crashed, if I tried to send the error, or exit... My PC would BSD.. For a while it'd exit fine if I saved the error but at some point that stopped too. Now I just try tab out and have the process terminated before it blue screens my computer.
Gnome, you said that the computer was giving you the blue screen because you had a bad RAM stick in there? I'm wondering what signs did the computer give you? Because I've gotten like 2 bad RAM tests on startup over the last few months. It almost always works, but I'm not sure that it's perfectly good or not. Also, I've got 2 sticks of 512, and if one is bad, how can I tell which one it is? (If anything I'd think it's the one that's second, so I might only have problems if the RAM fills up.)
Gnome, you said that the computer was giving you the blue screen because you had a bad RAM stick in there? I'm wondering what signs did the computer give you? Because I've gotten like 2 bad RAM tests on startup over the last few months. It almost always works, but I'm not sure that it's perfectly good or not. Also, I've got 2 sticks of 512, and if one is bad, how can I tell which one it is? (If anything I'd think it's the one that's second, so I might only have problems if the RAM fills up.)
Bad Memory is a wicked way to get your computer fucked up, because due to different memory partitions everytime (you computer will never be in the same state when you start it, because of other programs, disc cache, ect) it will appear absolutely random.
Just generally decreased stability, random bluescreens when doing stuff, that thing.
If your computer runs less than stable, try running memcheck or something like that (for example on every newer knoppix version its a bootoption) for a night.
And if your computer even gave bad memory results at startup, than the memory is most likely bad (and the memtest will help you to find which one is). Remember, the startup test is VERY shallow, it run runs quickly over the memory, and an error even there shows that something is REALLY wrong (with the memory, or the timings, ect)
Just generally decreased stability, random bluescreens when doing stuff, that thing.
If your computer runs less than stable, try running memcheck or something like that (for example on every newer knoppix version its a bootoption) for a night.
And if your computer even gave bad memory results at startup, than the memory is most likely bad (and the memtest will help you to find which one is). Remember, the startup test is VERY shallow, it run runs quickly over the memory, and an error even there shows that something is REALLY wrong (with the memory, or the timings, ect)
It blue screened whenever I played any game, especially those using D3D or OGL (which is nearly every game these days). I started looking up the BSOD messages in the Event Log (somewhere under administrative tools) and noticed a pattern to the error messages... when I googled that message, it came up with the microsoft site saying that message means bad RAM, no ifs ands or buts. I swapped out the RAM, the BSODs stopped, then I RMAed that stick and now I have a new new one that's good.CaptainMaim wrote:Gnome, you said that the computer was giving you the blue screen because you had a bad RAM stick in there? I'm wondering what signs did the computer give you? Because I've gotten like 2 bad RAM tests on startup over the last few months. It almost always works, but I'm not sure that it's perfectly good or not. Also, I've got 2 sticks of 512, and if one is bad, how can I tell which one it is? (If anything I'd think it's the one that's second, so I might only have problems if the RAM fills up.)