So after I took the cover off my tower, I gave it a thorough cleaning, got rid of all the dust that collected in the fans and heat sinks. I did not take off any components, and everything stayed plugged in. Note, that I did unplug and flip the switch and pressed the power button to clear the remaining power from the mobo. After I plugged everything back in, it wont POST, fans spinning, lights blinking, ect, but no monitor action.
I thought I had bumped a wire, so I rechecked them all, nothing. I decided to reset the CMOS by removing the battery. Success! It loads, saying that settings were changed, date/time, ect. So I simply loaded defaults, thinking that I could manually set them after I made sure it was working. I got to the login screen and it crashed, like a mem failure. And from then on, I hasn't POSTed.
I reset the CMOS again, checked wires, everything. My PSU works, fans work, light on video card turns on, ect. What can this be?
Since you reset the CMOS, you will need to manually set the RAM speed/timings/voltage to their rated specs in the BIOS. This is especially important with DDR2 OCZ RAM since it typically required a ton of voltage to run at its rated specs. Can you get to the BIOS when you do another CMOS reset?
Right, it does require alot of voltage, 2.1v minimum. I am currently unable to get to the BIOS. I realize that I should have set the settings again. But it should reset after I reset the CMOS again right? It worked only once, and from then on, it wont even load the BIOS. I tried to reset the CMOS several times after that.
Yes, unless a stick of RAM fried in your latest attempt to boot with incorrect RAM settings. That's why I posted a link to the troubleshooting sticky. It most certainly applies to you. Have you tried getting the system to start with each stick of RAM installed by itself? The first thing I would do is reset the CMOS again and then try booting with each stick of RAM by itself. If it starts again, manually set the RAM values and you should be good to go.
I know you think your problem is special in some way, but a no-boot problem is a no-boot problem. That's what the checklist was created to troubleshoot.