- Mar 3, 2001
- 8,859
- 4
- 0
I had 384 megs of ram in my computer, and i got 2 more sticks of 256 megs of ram (same manufacturer as the current memory) in the mail yesterday. i was going to take out my stick of 128 and throw in the other 2 of 256. when i did that, windows 2000 started up w/ a BSOD about some .sys file (i can't remember what it was) and how if this is the first time i've seen it just to reboot and if not to change some BIOS settings. well i rebooted, got it again, reset the BIOS to defaults, and still got the error. so i took out all the ram, and just put in one of the new sticks. now i get an ASPI.sys error. so i took that out, and put in JUST my old stick of 256, and it boots up fine. what the hell is going on? it's all the same manufacturer (Zeus components) and they've worked in my system just fine until now... help!
Update: i put in my old stick of 256, and a new one, and now i get the BSOD's that auto reboot, and it's a different file each time... wtf is up?? i know this ram works w/ my motherboard, friend of mine has same ram and same mobo w/ win98se and it works fine... should i nuke win2k and start over? if everything is fine until the OS, shouldn't that make it the culprit? thing is i don't understand HOW win2k could screw up cuz of new/more memory.
Update: i put in my old stick of 256, and a new one, and now i get the BSOD's that auto reboot, and it's a different file each time... wtf is up?? i know this ram works w/ my motherboard, friend of mine has same ram and same mobo w/ win98se and it works fine... should i nuke win2k and start over? if everything is fine until the OS, shouldn't that make it the culprit? thing is i don't understand HOW win2k could screw up cuz of new/more memory.
