- Joined
- May 2, 2007
My system is moderately overclocked (2.8GHz) and has been running along for months now. I usually just put my machine in standby when I leave it, but Friday night I (for whatever reason) decided to actually turn it off. Oops. Later, Friday night, I tried to use the machine and now it won't POST. I reseated everything, blah,blah, blah.
Here is what I know:
So, here's my thoughts. I can't believe that TWO sticks of crucial memory went bad at once. I suspect that something went out in the MB and it can no longer negotiate/talk to the faster RAM (or it can talk to it, but once it applies the RAM's suggested settings it dies). I'm planning on RMA the MB, but want to make sure they actually fix the thing....I think they want me to RMA my RAM first! Anyway, thoughts?
(*)Something a little strange about this: When I first got life back in the system with the Kingston RAM, it game me two choices (F1) to run setup and (F2) to load DEFAULTS and continue....EVERY SINGLE time I pressed F1 to run setup (or tried [DEL], it just showed gobbly-gook garbage on the screen and was dead....finally, out of desperation, I hit F2 and it tried to boot into Windows! So, then I Reset the machine and THEN [DEL] into setup finally worked! But, I'm suspecting something is screwed with the CMOS too.
Here is what I know:
- System before death was P5K-vanilla (400FSB) with 2 sticks of Crucial Ballistix PC-8000 (2GB total, 1GB each) RAM running at 1066MHz @ 2.25V (this is what the memory is RATED at)
- During the system build I did TONS of memtest to feel confident in this setup, speed and voltage....machine has been ROCK stable for months
- Even with Clear CMOS, machine will no longer POST with my 2 sticks of Ballistix memory
- Even with Clear CMOS, machine will no longer POST with ANY ONE of my 2 sticks of Ballistix memory in ANY slot
- Machine DOES respond to NO RAM properly
- Machine POSTS fine with new stick of slower RAM that I borrowed (Kingston PC-5300), but immediately says "Wrong CMOS" and forces me into setup (*)
- Once, I've got it to POST with slower RAM without "wrong CMOS" error, I can put my Ballistix back in and run at the then current values
- Once I tell the machine to go to 'default' settings with Ballistix RAM, it's dead...no POST, nothing. And nothing other than the slower Kingston RAM can bring it back from the grave
So, here's my thoughts. I can't believe that TWO sticks of crucial memory went bad at once. I suspect that something went out in the MB and it can no longer negotiate/talk to the faster RAM (or it can talk to it, but once it applies the RAM's suggested settings it dies). I'm planning on RMA the MB, but want to make sure they actually fix the thing....I think they want me to RMA my RAM first! Anyway, thoughts?
(*)Something a little strange about this: When I first got life back in the system with the Kingston RAM, it game me two choices (F1) to run setup and (F2) to load DEFAULTS and continue....EVERY SINGLE time I pressed F1 to run setup (or tried [DEL], it just showed gobbly-gook garbage on the screen and was dead....finally, out of desperation, I hit F2 and it tried to boot into Windows! So, then I Reset the machine and THEN [DEL] into setup finally worked! But, I'm suspecting something is screwed with the CMOS too.