Sign in with
Sign up | Sign in
Your question

Can't get into BIOS after messing with RAM speeds

Last response: in Motherboards
Share
April 20, 2013 7:16:01 PM

I have an ECS a780gm-a with a Penom 9500 under a Cooler Master Hyper 212 EVO, 2 GB RAM sticks, a new 750W power supply, and a Palit 460 GTX (2GB edition).
It was running awesomely with my 3 old 233 GB HDD's on RAID0. I OC'ed the GPU with MSI Afterburner and the CPU about 15% through the BIOS. No problems at all with those settings.
THEN I decided to mess with the ram as well and manually gave it 2.2volts and set the speed to 533 (I think... not sure. I remember it was set to 200 when I enabled the manual setting and remember seeing 400 as another choice but being the idiot that I am, I decided to go full throttle immediately).
After I save and quit on the BIOS with those RAM settings, the computer wouldn't go back into BIOS. You can see everything getting power; lights come on, HDD's power up, fans start going. I move the CMOS jumper thinking that it's no biggie, wait 30 seconds, move it back and still no-go. I remove the CMOS battery for an hour, still no BIOS.
I also tried putting only one stick of RAM instead of 4, and even tried different RAM from another computer. I tried plugging in the MB to a different power supply. I even disconnected everything from the MB, took it out of the case, took the CMOS battery out, and left it out for a good 3 hours. Still no BIOS.
I tried all this booting with and without the GPU as well, and with the jumpers in different positions.

Did I just brick my MB?
Also worth mentioning: I have a full ATX case with fans up the wazoo, so I am certain that heat wasn't an issue.

Help me internets, you're my only hope.
a c 98 V Motherboard
April 20, 2013 7:30:15 PM

What is the RAM manufacturer and model? It might have that info and the timings, frequency, and voltage physically on it.

Overvolting probably fried it, depending on what voltage the RAM was rated to run at.
April 20, 2013 7:34:56 PM

ihog said:
What is the RAM?

Overvolting probably fried it, depending on what voltage the RAM was rated to run at.


This one @ 1.8v
I tried different RAM, though, after moving the CMOS jumper.
Are you saying that I fried the RAM slot?
Related resources
a b V Motherboard
April 20, 2013 7:40:49 PM

Will windows os post/boot or it does nothing?
April 20, 2013 7:47:27 PM

ur6beersaway said:
Will windows os post/boot or it does nothing?


Doesn't do anything. My monitor gets no input whatsoever.
Another thing that's worth mentioning (and scary) is that once I turn on my computer using the button on the case, I can't turn it back off using that same button. In order to stop the MB from getting power I have to flip the switch on the PSU.
a b V Motherboard
April 20, 2013 8:01:24 PM

To test the board, I would attach a speaker and pull out all of the RAM. IF the speaker starts going nuts as it should, that is a good indicator that the CPU is being initialized and hence the memory controller is talking to the RAM slots checking for population. The MB to me would be good at this point because it is doing its basic diagnostic functions.
April 20, 2013 9:42:54 PM

ur6beersaway said:
To test the board, I would attach a speaker and pull out all of the RAM. IF the speaker starts going nuts as it should, that is a good indicator that the CPU is being initialized and hence the memory controller is talking to the RAM slots checking for population. The MB to me would be good at this point because it is doing its basic diagnostic functions.


Tried putting the BIOS on a USB and flash it but, not surprisingly, the computer did not boot from the USB.

I just came back from the store with a speaker. I put it in, took off all the RAM and turned on the computer. No sound. I put a stick in, turned on the computer and no POST sound or anything. AAAAAGHH my baby is dead! DEAD!
a b V Motherboard
April 20, 2013 9:47:57 PM

Sorry for your loss, lesson learned.
April 20, 2013 9:57:22 PM

ur6beersaway said:
Sorry for your loss, lesson learned.


I guess now my question would be: how did I brick it? I can see how forcing that voltage would kill the RAM, maybe even the RAM slots, but obviously it did more damage than just that. Maybe the north bridge? But how?
Even if I killed both the RAM and the slots, I should be able to hear a sound when I turn on the computer (regardless of whether or not I have RAM in, since the MB wouldn't see it anyways) like you suggested, assuming that everything else is in order.
a b V Motherboard
April 20, 2013 10:12:34 PM

The CPU is always initialized before anything else.
IF when the RAM is pulled you are not getting any type of beeps, I would look more at CPU being either seated wrong and/or is bad.Also when the RAM is pulled no beeps, could also be a bad MB. I would start with bad MB.
April 20, 2013 10:25:28 PM

ur6beersaway said:
The CPU is always initialized before anything else.
IF when the RAM is pulled you are not getting any type of beeps, I would look more at CPU being either seated wrong and/or is bad.Also when the RAM is pulled no beeps, could also be a bad MB. I would start with bad MB.


I just put in this CPU last week myself. I really doubt that I seated it incorrectly, considering that the CPU is keyed to the slot, I locked in the CPU latch correctly, and that the computer was working fine for a week up until this issue with them RAM.
I'm sure it's the MB and not the CPU, I just don't understand why overvolting the RAM would affect anything other than the RAM/slots. Like I said, even if the RAM slots themselves were killed, I should still hear the sustained beep that happens when there's no RAM, regardless of whether the RAM is in there.
!