ip35 pro Q6600

NoIdea

NoIdea

NoIdea

Associate
Joined
3 Dec 2007
Posts
264
Location
Essex
HI All,

I hope you can all help with my most recent O/C endeavours.

I dusted off my old machine a month ago, and it wouldnt work, so tatally rebuilt it and reset the BIOS.

I used to have it at 3.2, but now trying to push to 3.6. I've had it up and "stable" at 3.6. When i say stable, it doesnt crash or anything, however after an hour or so I get a couple of the cores failing in Prime.

Im very rusty on o/cing as I wasnt the greatest when I last had the rig out about a year ago.

Currently I'm at 3.5, using the below settings:

FSB 390 x9 =3.5
Dram Speed 1:1.0 (780)
Vcore 1.4225
DDR2 1.82
VTT 1.20
MCH 1.25
ICH1.05
ICHIO 1.5
PCI-E 100mhz

I had one core fail after around 3 hours last night, and as I say i'm very rusty, so i'm gonna assume thee is a glaring error in my setting above.

CPU-Z shows the vcore as 1.263 not 1.4225 under 100%load.

Temps dont rise above 63degrees after 3 hours.

Curent Spec:

ntel Core 2 Quad Pro Q6600 "Energy Efficient SLACR 95W Edition" 2.40GHz (1066FSB)
Microsoft Windows 7 Ultra 64bit
Seagate Barracuda 7200.11 500GB SATA-II 32MB Cache - OEM (ST3500320AS)
Antec P182 Special Edition Super Midi Tower Case - No PSU (Mirror Finish)
OcUK GeForce 8800 GT 512MB GDDR3 HDTV/Dual DVI (PCI-Express)
Abit IP35 Pro (Socket 775) PCI-Express DDR2 Motherboard
OCZ 2GB (2x1GB) PC2-6400 800MHz Reaper HPC Enhanced Bandwidth Edition Dual Channel DDR2 (OCZ2RPR800EB2GK)
OCZ StealthXStream 600w Silent SLI Ready ATX2 Power Supply
Tuniq tower

Any assistance would be great to try and get this more stable.


Thanks
 
i have to raise mch to 1.29 when running at 3.6 on the same board,
also had the v core a tad higher than yours

also my ddr2 ram require's 2.1v
 
Thanks Guys, taken your advice, now my settings look like this:

FSB 390 x 9 =3.5
DDR2 1:1 780
PCI E 100mhz
Vcore 1.4325
DDR2 2.00
VTT 1.23
MCH 1.29
ICH 1.05
ICHIO 1.50

I've run Prime for 30mins and no issues, I'll give it a longer test over night. I ran Everest for 20 mins and seems stable.

Temps on all cores ran no higher than 63 degrees.

So I guess I'll see what happens when I run it over night.

Hows the settings look now? Any further tinkering I guess will happen tomo if i encounter any probs with prime.

Thanks for the advice so far guys.
 
I've posted this before and it helped out...

My settings for 3.6 (my chip is a 1.3 VID)...

External Clock - 400
Multiplier - 9x
DRAM Speed - 1:1:25 (DDR2-1000)
PCI-E - 100

CPU - 1.52v (1.42 or so under load)
DDR2 - 2.0v
CPU VTT - 1.23v
MCH - 1.29v
ICH - 1.05v
ICHIO - 1.5v
DDR2 REF - 0%
CPU GTL 0+2 - 67%
CPU GTL 1+3 - 67%

Limit CPUID MaxVal - Disabled
C1E - Auto
Execute Disable Bit - Enabled
Virtualisation - Disabled
EIST - Auto

RAM - By SPD

...you will need to watch the PWM temps. My board is bolt modded and I have a 60mm fan hovering above the PWM area keeping them cool. You may well need the bolt mod if it's not already done... http://www.xtremesystems.org/forums/...&postcount=751

I also have 2x 40mm fans on the Northbridge, as it can get pretty toasty too.

Bear in mind that the above setting was when I was running 4gb RAM. I am still at 3.6 with 8gb, but have to run the memory on a different divider so that it runs at 800mhz. Any more was too much for the board to cope with.

EDIT - for what it's worth I found that anything above 1.3 for the MCH would cause instabilities. For some reason my board prefered the MCH to be kept fairly low.
Click to expand...
 
Thanks for that diggsy, after running prime for 9 hours I didn't experience any problems, temps didn't go above 71. However I did check hourly though the night and never caught it higher than 68.

Those temps seem ok?

I'm running everest now.
 
loadidle.png


Here is Cpu-z screenys with idle and load, curilously the core vid remans at 1.263
 
hum. when i had Abit ip35 pro, i was running at something like 1.4v MCH, and 1.45v Vcore for 3.6GHz.

but i did have 4 sticks of RAM, putting more strain on MCH. how many sticks of RAM have you got?

anything below 71c is fine. i think Q6600 G0 have max temperature of 71c
 
I have two sticks off RAM, 1 GB each.

In another thread, I mentioned I was going to upgrade the RAM to perhaps 4GB and get a new graphics card.

Is there any reason why Vcore in BIOS and Vcore in CPU-z is different? Or is Vcore in BIOS the MAX it will use, however CPU-z is only showing what its using.

What sort of idle temps can I expect. Currently mine is 32 33 31 32......
 
Vcore in BIOS is the Vcore being used by your hardware, well, attempted to be used.

Vcore reading during operation is what is being applied. there is a Vdrop due to power circuitary being put under load.

depends on your fan speed, idle temperature isn't important. i let my fan spin down during idle, giving over 40c idle temperature.
 
NoIdea said:
loadidle.png


Here is Cpu-z screenys with idle and load, curilously the core vid remans at 1.263
Click to expand...

Wait there is something really dodgy with the cpu-z voltage reading:confused:. Normally cpu-z displays 'core voltage' and not 'core VID'. The core VID is the voltage intel has specified for the cpu to run at stock speed and in this case it is 2.4GHz. So VID can also be thought of as stock voltage.

The reason it is not changing under idle or load is because it is not the correct voltage the cpu is running at. You have specified 1.4325v in bios and cpu-z is 'showing' 1.263v. If we are to take these values as they are then you are experiencing a collective vdrop/vdroop of 1.4325-1.263 = 0.1695v:eek: and this value is very high. This would suggest the mobo is a very poor overclocker and not good for stability.

My Q6600 G0 has 1.2625v VID. Although I haven't experimented throughly with my cpu at 3.4GHz but this is what I have on my gigabyte p45 ud3lr mobo:

Bios Vcore 1.4250v

Idle core voltage 1.376v

Load core voltage 1.312v (prime 95 small ffts)

Even though I am experiencing large vdrop/vdroop aswell of around 0.11v it is nowhere close to your's. I would suggest downloading the latest version of cpu-z and running it again:).

Edit at 3.5Ghz your core voltages at idle and load should be in 1.3xxv range.
 
Last edited:
Try running HWMonitor and see what the voltage is idle and load. CPU-Z is notorious for being more than a little iffy at reading voltages, certainly in my experience anyway.
 
Just downloaded previous version on CPU-z, core voltage shows at idle as 1.320. Under load, i was getting:
1.360
1.370
1.380
1.390

That looks more reasonable. No idea why the latest version isnt working.
 
I presume your first HWmonitor screen is showing idle cpu core voltage of 1.36v and 2nd screen is displaying load cpu core voltage of 1.33v. In these cases they seem to be correct values as mentioned in my previous post that for 3.5GHz the cpu core idle and load voltages should be in 1.3xxv range if you bios vcore is 1.432v:).
 
NoIdea said:
Just downloaded previous version on CPU-z, core voltage shows at idle as 1.320. Under load, i was getting:
1.360
1.370
1.380
1.390

That looks more reasonable. No idea why the latest version isnt working.
Click to expand...

Are you sure about that? The core voltage at load should always be lower than core voltage at idle because of Vdroop unless you have load line calibration LLC enabled in bios (if you have this feature) which is used to reduce vdroop and may affect the normal intel specification.

I think it is most probably the other way round.

Idle
1.360v-1.390v

Load
1.320v
 
Hmm OP it is very strange indeed:confused:. Your voltages are 100% correct but they should be the other way round. My Q6600 has exactly the same VID of 1.2625v. I think we need the input of fellow overclockers to shed light on this issue especially

Marine-RX179
redshadows
Rroff

These guys helped me in the past with my E6600 and Q6600 queries and their input proved very valuable. If you guys are on this thread please shed your light on the issue of lower idle core voltage and higher load core voltage OP is having:).
 
Last edited:
Thanks for that WingZero, hopwfully someone can shed some light.

Hopefully I wont destroy my rig whilst we are trying to resolve this. ha :)
 
You must log in or register to reply here.
Back
Top Bottom