Can't get past 400x8 and Vista reports 2.13Ghz?!

My voltages are all on Auto... I'm totally new to overclocking, so I didn't want to mess with them...

Everest reports my vcore as 1.325v. Would changing this in the BIOS let increase my overclock? If so, should I be increasing or decreasing it?

I'm on 3.2Ghz stable (After a 5.30 hour PRIME95 torture test anyway!) and Everest is reporting an Idle CPU Temp of between 27 and 29, I believe it reaches about 38 under load... so my temps are fine at that OC. (Im guessing thats down to my Arctic Freezer 7 Pro)

Edit: Not a top priority, but Vista still reports it as running at 2.13GHz under Computer -> Properties. Is this just a bug in Vista, because Everest and CPU-Z both report 3200MHz
 
I have managed to boot windows at 438x8 (3.5GHz) using a vcore of 1.58750.

I have a bad feeling that this isn't very safe, since it goes red at 1.60? Am I playing with fire? And if so, is there anyway I can drop it and maybe tinker with another settings to give me my stability?

I am not sure this is a stable OC, I will torture test it in a second, thought I would post this first though just incase!

Edit: Going to drop down to a lower OC until I get the OK (or not!) about this vcore... Read elsewhere its dangerously high
 
That is kinda pushing it but keep an eye on temps, if it is stable slowly work the Vcore down till it Bsods,Dont post or isnt stable then go to the last setting that worked

Hope it goes well :D
 
Hey silent.

Im back down to 3.2GHz now with auto voltages again. Its stable for me, and I don't really know where to start incrementing from to get a stable OC.

I got a 3.4GHz OC using 425x8, but it was not stable and the vcore was already pretty high (in the high 1.5xs) just to get it there... Not sure why my chip needs so much vcore to hit the high speeds, but its not looking feasible to go any higher than 3.2GHz atm...

I wish I knew what I was doing wrong! lol
 
it could be vdroop :s causing your system to muck up

Set you Vcore to a sensible reading, then using cpu-z check your vcore and post the difference here when it is idle and load

Give us your temps?

but will anyone else like to shine some light on this thread please, all you overclocking genius's out their :p
 
I can't remember if I managed to boot at 356x9, but I knew 400x8 was stable.

Silent, should I manually set my vcore to whatever CPU-Z reports as load (1.448), keep my fsb and multiplier the same (400x8) and then post my vcore idle/load and temps?

It might be worth noting that at 400x8 and auto vcore, I am extracting a 8GB iso at the moment and my CPU temp is reporting 28 degrees. So it looks like my temps are fine and can easily handle more OC.
 
Still looking for help on this, hopefully someone can shed some light.

Been reading other threads with the same problem. People are suggesting turning on Load Line Callibration, and upping the FSB, PLL and NB voltages etc.

Also, it seems i may be suffering from large vdroop (Though im not 100% sure how to check my vdroop) which may be the reason I need such high vcore voltages to get a stable Overclock even at 3.2 (Im on 1.4875 vcore, just to get 3.2 stable now...)

I have messed around with overclocking A LOT since i first posted this, so I have tried alot, messed it up a lot and bluescreened a hell of a lot. So I don't have my original OC from the first post anymore, lol.

I've posted quite a few threads regarding overclocking problems, but thought I would revive this one, since it details what I have tried and what I started with etc!

Edit: I believe my VID is 1.325. So i may be crippled right off the bat according to alot of people :(
 
Hey

Sorry i must of missed this thread you are pumping a hell of alot of voltage through your cpu :s

Ok to check Vdroop basically you note down what you have set it to in the Bios

then boot in to windows see what the Voltage is idle then put it on load and see what the Voltage is with it on load

then post them here and ill see what to do from their, if it is bad we may need to do a Vdroop Mod which usually just means drawing over a resistor with a graphite pencil lol

Let us know
 
name='Silentsnake' said:
then post them here and ill see what to do from their, if it is bad we may need to do a Vdroop Mod which usually just means drawing over a resistor with a granite pencil lol
Click to expand...

I really hope you mean graphite.... :eek:

;)
 
I think i would rather run stock speeds than do any physical mobo modding to be honest lol.

Unfortunately I am away for the weekend now, so wont be able to do anymore OC tweaks til monday.

But i will post back on how i get on when Ive had the chance.
 
Or you could just enable LLC, which is asus' attempt to eliminate vdroop. On my P5Q-E it actually does a pretty good job.

And 1.48ish isn't that much for a 65nm chip.

One thing you could check is that the RAM is set to 2t. I spect it is as 1t is rarely the stock any more but its worth a shot. 1t, while faster, can be a lot more unstable.
 
I will definitely try enabling LLC when I get a chance. 1.48 still seems alot to me though for 3.2 (But what do i know? lol). I believe my RAM Command Rate is set to Auto, I will make sure its set to 2T (Which I believe is listed as 2N on my mobo?)
 
Ok, Ive gone to 266x9 (2.4Ghz - standard), set vcore to Auto and Load Line Calibration to Performance.

VID is 1.325

CPU-Z reports my IDLE vcore as 1.296 and my LOAD vcore as 1.304
 
name='tomglenn' said:
Ok, Ive gone to 266x9 (2.4Ghz - standard), set vcore to Auto and Load Line Calibration to Performance.

VID is 1.325

CPU-Z reports my IDLE vcore as 1.296 and my LOAD vcore as 1.304
Click to expand...

That is quiet a large droop i would try the LLC as ham says then post them here see if it makes a difference, if not i will google vdroop mod for you it isnt complicated and i did it on my Asus p5n32-e and it helped alot, all you have to do is use a pencil if it doesnt help then just erase it away very easy

:)
 
name='Silentsnake' said:
That is quiet a large droop i would try the LLC as ham says then post them here see if it makes a difference, if not i will google vdroop mod for you it isnt complicated and i did it on my Asus p5n32-e and it helped alot, all you have to do is use a pencil if it doesnt help then just erase it away very easy

:)
Click to expand...

That was with LLC on... You sure it's large? It's only a difference of 0.004v
 
name='Silentsnake' said:
That is quiet a large droop
Click to expand...

Duuuuude. Read.

His LOAD vcore is HIGHER than his IDLE. that means that LCC is doing it job. That is NOT droop.

(wooo caps)
 
You must log in or register to reply here.

Similar threads

P
Do some people never learn from the past?
Replies
2
Views
860
Pugsport
P
AlienALX
The Fairchild Ghost subwoofer project
2
Replies
35
Views
681
AlienALX
AlienALX
syfer1987
XFX 6800 XT AND RTX 2080 TI both faulty cards trying to fix
Replies
0
Views
192
syfer1987
syfer1987
AlienALX
Building my dream N64. More in depth than you would think (and me !)
Replies
11
Views
1K
AlienALX
AlienALX
Excalabur50
Bad, Bad, Good, Good, Bad
2
Replies
30
Views
6K
Excalabur50
Excalabur50
Back
Top