What is wrong??? E2180 + P5Q-E

Associate
Joined
23 May 2008
Posts
420
Hi,

I have:

- E2180 @ 295 x 10 @ 2.95GHz
- P5Q-E
- Corsair XMS2 TWIN2X4096-6400C5 G PC2-6400 4GB DDR2 800 Dual Channel Kit Desktop Memory
- Sapphire HD4850 @ 680/1090
- AC Freezer 7 Pro
- Antec 900

I cannot get FSB any greater than 295... i can't do 300 x 10 as it won't even post... Won't even do 333 x 9. Tried voltage settings at Auto, 1.3525, 1.45 even... All failed to post...

Is it the RAM? Maybe I cheaped out RAM?

Please help, and cheers!
 
Hi,

I have:

- E2180 @ 295 x 10 @ 2.95GHz
- P5Q-E
- Corsair XMS2 TWIN2X4096-6400C5 G PC2-6400 4GB DDR2 800 Dual Channel Kit Desktop Memory
- Sapphire HD4850 @ 680/1090
- AC Freezer 7 Pro
- Antec 900

I cannot get FSB any greater than 295... i can't do 300 x 10 as it won't even post... Won't even do 333 x 9. Tried voltage settings at Auto, 1.3525, 1.45 even... All failed to post...

Is it the RAM? Maybe I cheaped out RAM?

Please help, and cheers!


Try 8 x 400, enable loadline calibration, disable speedstep, see how you get on. Your ram should be fine.
 
8 x 400, enabled loadline calibration, forced voltage in BIOS to 1.356V,
right now it's idling at 38C,

running Orthos as of right now, shooting at 55C,
fails Superpi 1M (crashes right after I click go)
CPUZ reporting Core Voltage at 1.336 fluctuating

Maybe too much? I don't know why superpi refuses to run
 
oook... BSOD right after I clicked on post lol..

I changed voltage to Auto on BIOS, seems to be working, Superpi ran fine, but now CPU-Z reporting voltage of 1.432 idle and 1.440/1.448 under Orthos...

Hope this voltage is fine, temp is not at 39 idle and 61 right now under orthos

I can keep voltage on Auto on BIOS and be safe?
 
oook... BSOD right after I clicked on post lol..

I changed voltage to Auto on BIOS, seems to be working, Superpi ran fine, but now CPU-Z reporting voltage of 1.432 idle and 1.440/1.448 under Orthos...

Hope this voltage is fine, temp is not at 39 idle and 61 right now under orthos

I can keep voltage on Auto on BIOS and be safe?


Try upping the voltage a notch at a time until stable. My E2180 has a VID of 1.25V, I've noticed those with higher have to put a little more through to achieve 3.2Ghz. I'd be OK with temps up to 70C under Prime or Orthos load, because it would never get to those temps under normal use.

What voltage are you running your ram at?
 
This might be a silly question but you are changing the ram frequency/multiplier as you increase the fsb? You need to try to keep the ram as close to it's stock speed as possible.

It is not a good idea to leave voltages on auto as motherboards can supply much higher than needed voltages which can damage components. Best to manually increase vcore a notch at a time until you get stable. Keep an eye on your temps though. As you are running 4Gb of ram you may need to increase the NB voltage a notch or two to aid stability.

I had a E2180 that could do 3.6Ghz (8x450) with 1.4v vcore in a £45 Gigabyte P31 DS3L. I would hope that a mobo costing twice as much would be capable of a similar clock.
 
I see, cheers for the help.
As per RAM, I kept it at 800MHz to keep it 1:1 with the FSB on manual.

Yeah, I had it on Auto and CPU-Z showed 1.4480V at load, so I went to BIOS and did one notch down to 1.4V and although it did boot, SuperPi (again) wouldn't run... Showing 1.376V on CPUZ and 1.384V on load ( and why does the voltage go UP under load?!? )

I'm wondering why I need a voltage so high... maybe i'll try NB +0.2 or something.
 
Last edited:
Mine went up, as did quite a few others in the P5Q thread over at XS.

It's also the reason why quite a lot of the ASUS X38 boards were Prime95 stable for hours, but were unstable at idle.
 
Any particular reason how KelticDaz has E2180 running @ 3.2GHz with 1.356V??
Did he get a better processor out of the lot?

Also, the "effective" voltage is the one reported by CPU-Z, not the BIOS setting, correct?
For example, when I say I am running my CPU at 1.4V, the actual setting in BIOS should be higher?

Thanks in advance.
 
KelticDaz's chip has a low default voltage (1.25v) so his needs less voltage than most to get to 3.2ghz.

And yip the effective voltage is that read by CPU-Z, and is normally lower than that set in the BIOS. The difference is usually quite small if Loadline Calibration is enabled, and is a lot more if LLC is disabled.
 
Ah I see thanks....

Well I had the voltage to Auto at BIOS last night, Orthos ran for about 7 hours w/o warnings or errors, Realtemp reported a max temp of 66, and CPU-Z reported 1.448V under load. I thought the AC7 would be a better cooling than this, but I think i pasted the thermal grease too much... maybe i should try resetting it on the cpu.

I nudged it down to 1.4V on BIOS, forgot what CPU-Z was reporting but it was 1.39 or something, i got it running Orthos right now at home, gonna check back after work to see what's up.
 
Update:

ok it seems that SuperPi fails at ANY OC other than the stock.. It fails randomly from 16k to 16m at random spots. It's not SuperPi error per se, but Windows just force closes it. So I figured I couldn't gauge stability with SuperPi.

It's now at 1.4v bios, 1.396v CPU-Z under Orthos or Prime95-64, stable for at least 12 hours on both at 400x8. The only problem is with SuperPi, which I find very weird.

Popped Zalman vf1000 on my HD4850 and it now idles at 34 and 45 under gaming load, or 55 under Furdemo. Just gotta get some extra sinks for the VRM's.

Cheers for all help.
 
what BIOs version are u using?

got a p5q-e and the newer bios aint that good for me, using version 0704 gives me the best results so far.
 
I'd be grateful for your continued updates as I'm looking at getting the same E2180 and P5Q-E setup myself.
 
Update: Ok I think the stable voltage is at 1.4v for my CPU, showing 1.315v VID under Coretemp. I had a notch down from 1.4v and it did prime OK for 6+ hours, however it BSOD'd playing a 720p movie file (Band of Brothers) after about 3 hours so I bumped it back upto 1.4v. Temp's hitting max 63C both cores in Realtemp so far, giving a delta to Tjmax of 22C. SuperPi still crashes no matter what.
 
Back
Top Bottom