Overclocking E6300 & Asus P5B-E

[Icepick]

I'm having a problem getting my e6300 stable at 2.8GHz on the Asus P5B-E. I think that my problem is that I can't get more voltage to the CPU. Whenever I increase the voltage in BIOS and then check with CPU-Z or Asus AI Suite it still shows the default voltage setting.

Right now I have VCore set to 1.4V in BIOS and CPU-Z shows 1.336V. :roll: Orthos is getting errors after only 1 min 13 secs. Does anyone know if there's something else I have to do in order to get the VCore settings to stick?

 

[The-Noid]

that is called vdroop. IT will drop off when your processor is under load. It is possible that your power supply can't handle the added voltage to maintain it. Otherwise your omtherboard just has a very high vdroop. Either do a vdroop mod to the motherboard, or keep increasing voltage.

 

[n7]

I'm pretty sure the P5B-E has the same 1066/1333 strap config as the P5B Deluxe does.

Try running @ 7x401+, nothing lower.

As for vcore, use Asus's PC Probe 2 (should come with your CD) to keep an eye on it, as CPU-Z can sometimes be off.

It does sounds like your mobo has excessively bad vdroop though, so just keep increasing it till you get it to where you want.

 

[imported_mikejf]

I've this board and CPU too. I'm running at 2.8Ghz with 1.3 Vcore. It droops to 1.26v, but runs stable.
Use the BIOS readings for vcore, some apps give false readings.
If you leave the Vcore on Auto, you'll get plenty of CPU voltage; too much really. Mine was like 1.48v and the Temps went through the roof.

 

[Icepick]

Thanks for the tips!

I think that my problem was not the Vdroop. I ran memtest86 on my RAM and got 3 errors within 27 minutes. I'm going to RMA this RAM and hopefully get some better sticks.

By the way, is it normal to get a few errors with memtest86? Or should my RAM test completely free of errors for hours?

 

[Paperdoc]

Everything I've seen in the forums says you should NEVER get errors in Memtest. If you do you have one of two situations: badly configured memory (for OC'ing) or faulty RAM if you are running it according to specs. Or, I suppose, a more obscure problem like a bad RAM socket.

 

[Red Storm]

I've got a 6300 and a P5B-E as well, and vdroop is a problem for me too. I set my vcore to 1.4 but cpu-z, core temp, and PC Probe are showing stock vcore numbers. I still haven't found my OC limit, but that's mostly because I'm hesitant to push my DDR2-675 Corsairs above 800MHz.

So is there nothing that can be done about vdrooping?

 

[James Bond]

I was going to get either E6300 or 6400 + P5B-E.. but this is making me wonder.

I want it soley for the reason of overclocking

 

[Red Storm]

Well the P5B-E is no slouch. It took my 6300 to 3GHz easily (vcore set to 1.35), but I backed down to 2.8GHz because of my RAM. I'd say the P5B-E is a great overclocker, although I've heard a new revision should be out sometime in the next few months, but I'm not sure on that one.

 

[tempoct]

I have similar observation on my E6300 and P5B Deluxe Wifi. Seems to be common with this combo.
But it runs stable. I was using Vcore = "AUTO" before, like Mikejf said, the board will supply too much and temp is 60+. Dropped out and manually set it then it run nicely.
I think it's a good idea to find how much your RAM can take. Set CPU multi to x6 and set the board "cpu freq" to stock (266) or lower and try to OC only your RAM. Run Orthos large FFT for an hour or so. This will verify your memory capability.