Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Etoile Chercheur
|
Posted - 2004.05.30 04:51:00 -
[1]
i'm getting this BSOD error when running EVE now, but i haven't added any new hardware and there are not IRQ conflicts that i can see. EVE runs fine for about two minutes, then blam, BSOD.
i'm running Windows XP Pro, and using a 512 and 64. leaving the 512 in by itself caused the same error, so that might be the problem. bad memory. if that is it, it's a damned shame that it wasn't the 64 stick that was bad...
of course, i'm unable to test the 64 by itself to rule out a memory issue.
the graphics card is in the AGP slot, and there is no PCI card in the adjacent slot.
RIGHT CLICK - SAVE AS
i'm really low on funds atm, so i'm rather desperate to find an alternative cause to this problem. plz let me know if any of you have run into the same issue and have found a solution.
Midshipman Etoile Chercheur - Logistics Division (M&T) | Hadean Drive Yards
|
Etoile Chercheur
|
Posted - 2004.05.30 05:52:00 -
[2]
i ran memtest86, and got loads of errors, even borking the program testing the memory. so there it is. well, crap. i'm out of EVE until i can replace the 512 it would seem. |
Snellgrove
|
Posted - 2004.05.30 06:37:00 -
[3]
Ouch, thats nasty
what type of ram (brand) do you have currently, and how old is it?
if you do find replacing the ram = you still get the errors, its not so bad. You just put it back in and you've got yourself 1024, and an excuse to totally get rid of the Pagefile (unless you really do use loads of ram, and still need a pagefile for some reason. -cant think of anything that uses over that level, though)
|
Etoile Chercheur
|
Posted - 2004.05.30 12:21:00 -
[4]
unfortunately, 1024 doesn't work in my box, even though it's supposedly rated for that much ram. apparently, when designing the motherboard's limits, they didn't take into account the small amount of ram on the motherboard itself, and putting 1024 on it causes it not to load windows...
how effed is that, huh? :(
here's to hoping i'll be able to scrape up enough cash to by new ram, at least 256 to get me by. then i can add 512 to that later...
i'm unsure about the RAM or the brand. i'm even unsure about the effing speed of the RAM, which worries me. frustratingly little detail can be discerned from looking at it.
|
Etoile Chercheur
|
Posted - 2004.05.31 16:42:00 -
[5]
okay... new RAM. new heatsink with fan. also new box fan that i never bother to buy before. the spot's been empty. big thanks to Circuit City. Best Buy, you can suck me, as your ppl were about as much help as a bic lighter out of fluid in a blizzard! argh! jerks.
Circuit City has my money from now on. i swear. customer service these days...
anyway, been running EVE successfully for several minutes by now, so a big WOOHOO! \o/
it seems that when i upgraded my RAM from 64MB to a whopping 576MB (added a 512 stick), i really should have added the box fan, as fan running air through the power supply simply isn't enough for all that, and my RAM fried slowly.
of course, that's just the more likely explanation. i'm happy, cuz now i can play EVE again!
another WOOHOO! \o/
|
Snellgrove
|
Posted - 2004.05.31 16:45:00 -
[6]
HOORAY! you can once again feed your addiction
good to hear its all working again though, thats cool!
|
Qwakrz
|
Posted - 2004.06.04 11:11:00 -
[7]
Its amazing how even a single bit error in ram can cause so many problems. It MUST be perfect or it WILL mess up.
|
Katsumoto
|
Posted - 2004.06.04 13:38:00 -
[8]
ive had that error on my last 3 computers i have and by replacing the mainboard it solved it, i am sure it is the motherboard because on the last three occasions i have had it, replacing the board works!
how i found out it was the board was by stripping the damn thing to its basics and seeing if i still had the error, then i replaced everything one by one and found out it was the motherboard!
might cost ya but it solved the problem for me!
Force Of Evil [email protected]
"If i was in world war two they'd call me spitfire." |
Syphelle
|
Posted - 2004.06.08 12:30:00 -
[9]
Just in case anyone else with this problem is reading this...
I got this BSOD error (amongst others). I had run memtest also, assuming that memory was the problem, but it came back with no errors. After taking all the usual drastic measures - format and clean install of xp, driver checks etc. - the problem turned out to be caused by my cpu overheating and has been fixed by replacing the heatsink and fan.
Whilst this won't be the case for everyone getting this error, it might save someone from needlessly replacing memory.
|
Commander Stringer
|
Posted - 2004.06.08 12:48:00 -
[10]
Yep, heat caused a major Eve lockup the whole system crash, new cpu/heatsink fixed it as above.
Nother thing you can try doin is updating your mainboard bios to the latest available. can fix timing problems on the AGP bus/memory.
|
|
Imhotep Khem
|
Posted - 2004.06.08 19:24:00 -
[11]
I believe this bug is typically tied to AGP bus. Probably the bad memory was being used by AGP and it did not like it. No matter, glad it is fixed. ____ If your not dyin' your not tryin'. |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |