Awwww feck

[avsmithy]

Hi guys

Just a quick question, i was overclocking last night and i was at 3.1GHz on my E2200 at 1.33V (ok right?) the temp was 45 at load so i see no problem there.

However now my pc wont post (no beeps )

This happened before (twice actually) and it was the mobos fault. Im guessing this is the same problem now. Its an ASUS P5QL PRO, P45 chipset so im guessing its should handle this o/cing ok?

Anyway since the only thing that i can do is send it back to Asus (taking a month or two) after which it will probably break again, what should i do?

Thanks Alex

P.S. im poor (and 16) so should i send back the OCZ Nia i just bought, to spare some money in case this whole thing goes south?

 

[Jeddy]

Clear the cmos.

That should fix it. Failing that you may have killed something because asus mobo's are usually great at recovering from failed overclocks.

 

[Rastalovich]

I voted with the shudder.

However, my experience with mobos is that if u identify one failing the same way a previous one failed, then ur onto a bad thing and get it changed. Replacing it with the same only if ur not going to oc with it.

Reason I say that, even with mobos that have proven oc names, they are manufactured just like everything else - u get revisions, poor batches and even new lines of components as the age of the mobos moves on. Therefor a once found to be brilliant item becomes "ok". Not true in all cases, but certainly can be an explanation when u repeatedly see the same issue.

Now b4 all that, I would go down the total strip-down to bare components (psu, 1 stick memory, cpu, gfx), being sure they're all seated well, clear the cmos really well and see if it works.

 

[avsmithy]

cheers will try that now...

edit:

ok i have removed the CMOS battery

now we play the waiting game....

 

[llwyd]

Do as rast said. Then to clear the CMOS, set the jumper to clear, pop the batt out, leave it half an hour, pop it back in, try boot with the jumper on clear, power down, set it back to save and then try start up properly.

If that doesnt work, looks as if youve suffered the infamous asus bios disapearing act. Their boards have been doing it since C2D. I had 2 P5Bd's do it and 2 Commandos back in the day. Decided to go abit since.

 

[avsmithy]

WHOOO it works!!!

Thanks sooooo much guys!!

Now how hard do you think i could push this thing???

i got 3.1ghz @ 1.35V on 283fsb

RAM is at 2.1V 800MHz 4-4-4-12 (rated to that)

is does superpi but gets error on OCCT (error detected on core #...)

any suggestions?

p.s. first time ive done serious overclocking but dont mind burning out cpu in 10 months ----- as long as it lasts till august!

 

[Rastalovich]

I've debated the "w8ing for the battery" thing with people b4. What the attempt is there is that the theory is the battery maintains power to the cmos storage to hold settings whilst the pc is off. Thing being here that ur "w8" is for all the power to run down from whatever capacitors are on the mobo whilst the battery is removed.

However, same effect can be achieved by removing the battery, turning off ur psu (leaving it plugged in) and repeatedly pressing the "on" button. Everything should drain.

Debatable.

EDIT: Very good news to hear it's up and running. U may want to start another thread about attaining a great oc, but I'd first read all the great guides within the forum sections.

 

[lasher]

I've debated the "w8ing for the battery" thing with people b4. What the attempt is there is that the theory is the battery maintains power to the cmos storage to hold settings whilst the pc is off. Thing being here that ur "w8" is for all the power to run down from whatever capacitors are on the mobo whilst the battery is removed.

However, same effect can be achieved by removing the battery, turning off ur psu (leaving it plugged in) and repeatedly pressing the "on" button. Everything should drain.

Debatable.

EDIT: Very good news to hear it's up and running. U may want to start another thread about attaining a great oc, but I'd first read all the great guides within the forum sections.

Agreed will save having to merge posts etc and keep this thread clean

 

[Mul.]

To respond to your original post, in my opinion I don't think it's right to RMA a board because it didn't work well with an overclock. The motherboards are only rated to function at the default speeds of the CPU. Anything over that is a bonus. Further, it wouldn't be fair to consider it an Asus problem as an overclock will vary from model to model and even within a particualar model, especially when the P5QL Pro is one of Asus' entry level P45 boards. I'm not trying to lecture anyone. Just throwing my two cents into the mix

WHOOO it works!!!

Thanks sooooo much guys!!

Now how hard do you think i could push this thing???

i got 3.1ghz @ 1.35V on 283fsb

RAM is at 2.1V 800MHz 4-4-4-12 (rated to that)

is does superpi but gets error on OCCT (error detected on core #...)

any suggestions?

p.s. first time ive done serious overclocking but dont mind burning out cpu in 10 months ----- as long as it lasts till august!

You won't need to worry about burning out your CPU as you're not really anywhere near doing anything of the sort. I suspect you'll hit the limits of your CPU due to an FSB wall as a lot of E2000 CPU's just don't like high FSB's.

I'd start by removing any factors that could potentially get in the way of your overclock. For now, that's RAM frequency and FSB limits. Locate DRAM Frequency in BIOS and set it to the lowest possible. This should be the 1:1 setting that'll run your RAM at DDR2-566 at 283FSB.

Next is Northbridge to FSB Strap Frequency. When you increase the FSB of your CPU, it's an FSB increase over the default FSB. Let's say you're using an 800FSB CPU like your E2200. As you increase the FSB of your CPU, the strain on the Northbridge increases, such that it's strained more when overclocked to 1066FSB than a CPU that is 1066FSB by default. Changing the Northbridge to CPU Strap makes the motherboard think that the default FSB of the CPU is something else. This may not help if your board automatically changes it but seeing that the option's there, set FSB Strap To North Bridge - 266. For now, keep the same CPU FSB and Voltages and rerun OCCT and tell us what happens.

If that doesn't help, I'd start raising the CPU VCore.