crashdummy35

Okay, go into your bios and set the RAM at these settings manually:
Use the 400MHz multi for this. It's 2.0D on my board, not sure about that one.
400 Mhz
5-5-5-15
1.80 volts

Set the cpu like this:
multi: 8
fsb: 400 (Speed will be 8 x 400 = 3.2GHz)
Cpu vcore (voltage): 1.265v about here for now. <--Look in CPUZ and write what it shows, it will be a bit lower after booting Windows.
vtt (I believe it's called on that board): 1.22

North Bridge: 1.22 about here for now.

Remember, keep the RAM at 800MHz for now. It shows as 400MHz in CPU-Z because it's 400MHz x 2 = DDR2 readings.

See if you boot with those settings.

Munchener

Done! Can't boot; not even to BIOS

Returned to defaults and all auto.

Previously, I set it like this and worked:
FSB: 299
Multi: 10
Memory: 749MHz (auto option to choose from)
Memory V: 1,95v
vCore: 1,2625v
Memory Timings: auto (4-5-5-15 said CPU-Z)
NB: auto


Any of this helps to ring any bell?

Thanks!

Munchener

One very wierd thing that happens is that everytime I change to manual vCore, the next time I enter BIOS, the only option for vCore is auto. I have to choose auto again, save and exit, and enter BIOS again to regain access to manual vCore voltages... very strange...

I disabled Speedstep and C1E options. Why does the mobo have them both? Aren't both options the same thing?

crashdummy35

Same settings. Raise vcore to 1.28v. NB to 1.24.

Did you disable all of those throttling features like ericeod said?
"I can see from the CPU-Z screenshot you have SpeedStep enabled. Notice the x6 CPU multi. That means the CPU multi and vcore is dropping when at idle. Try disabling SpeedStep (called EIST or C1E in bios), bump your vcore to 1.275v, and see how much you can push."

And what do you mean it wouldn't even post to the bios screen? Nothing happened? Nothing at all?

I wish I new more about that boards bios.

Let me go get my girl from work and I'll check back in.

Just be patient...as you are seeing, overclocking can be work when it's new to you.

Just hang in there.

Munchener

OK, I changed some things to slowly approach the target (what target? dunno ). Attached are the screen captures.

Another wierd thing: I set manual vcore in 1.275, but CPU-Z shows 1.248, like it was in auto mode (the mobo doesn't have a manual option of 1.248 either).

I attached Coretemp and Super Pi also, just in case they show something useful.

Attached Thumbnails

 

crashdummy35

That's normal. The voltage drops after entering Windows, it will drop a bit more when the cpu is under a full load. Don't worry about it.

Go in and set your vcore to 1.275v or near there and start raising the fsb. If you get into Windows, write down the voltages like this 1.275v bios/1.??v cpu-z so you can keep track of the voltages and vdrop/vdroop.


With the voltage at 1.275v or 1.28v raise the fsb until you can no longer boot into Windows. Write everything down. Keep an eye on your RAM too, keep at or just below/above stock, don't let it get away from you. You can go back in and oc that later as best as you can. For now focus on the cpu and getting that fsb up as high as it'll go.

You have plenty of room voltage wise...don't worry.

*A note: If the multi for that cpu isn't locked, lower it to 8 or 9. 10 is too high for what you are doing now. 8 would be best.

crashdummy35

Go any higher..?

Munchener

This are my new seemingly stable specs. However, the vCore keeps turning auto right after I set it manual @1,2875, and CPU-Z shows it climbing to 1,360.

Also, I set the multi fixed to 10, and it appears to be 10.5.

This mobo has quite a character... doesn't accept all manual changes that I made...

Attached Thumbnails

 

ericeod

SpeedStep lowers the CPU multi thus lowering the CPU speed while C1E lowers the voltage as well.

__________________
eVGA 680i Overclocking guide .......... ASUS P5E/Maximus Thread.......... 4.4GHz CPU-Z

crashdummy35

You have to disable all of the throttling features while you overclock. Keep the voltages and multi + speeds from dropping.

Those are built to relieve stress on the cpu when it isn't under load, you can re-enable them later if you want but for now you want steady stability. That's what you are looking for at this point.