Help Needed!

Soldato
Joined
1 Aug 2006
Posts
5,724
Location
Cardiff
Posting this on behalf of a friend...longtime lurker.

Quoting.

Specs
Q6600 (B3)
ASUS P5N32-SLI PREMIUM WIFI
2GB OCZ PC2-6400 CROSSFIRE

OK, so i wanted to start overclocking the CPU, but am having some problems with it.

I can't seem to increase the FSB over 1126mhz (280mhz) before it starts to "lock up" on the BIOS Splash screen after reboot.
I have increased all the voltages...

VCORE - 1.34
VTT - 1.4
DRAM - 2.0
Northbridge - 1.4
HT - UNCHANGED
Southbridge - UNCHANGED

Now the VTT setting i was a bit wary about. I read a few things, and one forum seemed to insist that you can fry your CPU by changing this setting, while another one practically shouted at you with a megaphone to up it to the max (1.55) to assure stable overclocking. I comprimised and went for 1.4. I read it was something about capping the voltage as not to damage it or something?, so i figured putting it at 1.4 was slightly more than my VCORE and was a safe amount for the CPU to max out at. So i need some reassurance that this should be maxed out, or what this exactly does.

So the weirdest thing is that the VCORE voltage is reported different everywhere i look. As i stated, in the BIOS i set it at 1.34, and it shows up in the BIOS Power screen as exactly that after rebooting. However if i load up CPU-Z, it shows it being at the (stock?) 1.264v. If i look in EVEREST, it says this under "Sensor" information, but reports it at 1.300v under "CPU" information, neither of which i actually set it at. So what's going on and which value is correct? What's lieing? It seems my temps have risen by about 5C, but then again its slightly warmer today so I can't say if that's down to the voltage or not. (BTW, I'm using a Tuniq Tower 120, so the temps under full load maxes at 50C atm, it used to be 45C)

I'm using CPU clock mode - "Manual - Precision CPU/MEM Tweaker" which as i up the FSB, it automatically adjusts the MEM frequency so it stays around 400mhz. Can see the BIOS screen type thing here

My values on that screen are "New FSB Speed (QDR) - 1126" and "New MEM Speed (DDR) - 800" .. [might be 804]

All options in all the power management stuff like that Vanderhousen..something-or-other are DISABLED.

My Current RAM timings are on 4-4-4-12.

So sorry it's a long post, but i was hoping maybe someone else has this mobo, or someone has some decent suggestions.

My BIOS is dated 10/18/2006, so i wonder if an update will do it good? I've heard horror stories about updating the BIOS on this board so I'm pretty scared to do so. I'll only do it if absolutely neccesary.

Thanks for reading.
 
Ok, firstly the different CPU voltages. CPU-Z and the Everest Sensor readings are the actual real readings in Windows. They are lower than the value set in BIOS because of 'vdroop'. The value being given by Everests CPU menu is the default voltage (VID) for that particular CPU.

And I would really update the BIOS since the one he currently has was brought out long before the Q6600 first appeared back in April, tho the CPU support list here doesn't actually list any of the Quads.


Btw Vanderhousen is the virtualization option (it gives a boost to programs like VMWare and VirtualPC).
 
Right, as to the votages he says no matter what he sets his VCORE at it reports as 1.264, he also says that flashing BIOS is his utter last resort an he really doesnt want to do it unless totally needed.
 
Is he using the very latest version of CPU-Z?

And I see no other option than updating the BIOS.
 
He says...

The PCIE NB and PCIE SB spectrum is on DOWN SPREAD at the moment, should I put them both to disabled..all the other spectrum things are disabled I believe except for those 2

Also CPU-Z 1.36.
 
Download CPU-Z 1.41 for a start. It reads most vcores correctly.

I'm not really familiar with the n590i boards, so I'm not sure what the spectrum options are for (other than CPU Spread Spectrum which should be disabled).
 
I have the same problem too mate and my bios is the 0901 revision. I have overclocked before but never met this problem, let me know if you have any luck.

Just seen how old this thread is.........anyone had any luck with it?
 
Back
Top Bottom