• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

***The Official Wolfdale 8200/8400/8500 Overclocking Thread ***

inam22 said:
With 1.3 vcore in bois and 1.296 in windows you should be able to hit 4 ghz easy and if you want to run your cpu at 3.7ghz then you really don't need that much vcore,i am running my e8400 at 3.8 with 1.240 vcore.
Click to expand...

I'm finding I am having to push the vcore (at least in the bios) otherwise it simply fails 10 or so mins into orthos.

I'm currently at 1.37 which gives me a stable 3.84ghz with orthos running without incident for several hours.

I did reseat the chip with some artic 5 and I'm now seeing load temps hit 61/62c. (thats if you can trust coretemp).

Nice to hit 4ghz but in real terms I won't see any difference from 3.8.

Cheers, Paul.
 
darkgen said:
I'm finding I am having to push the vcore (at least in the bios) otherwise it simply fails 10 or so mins into orthos.

I'm currently at 1.37 which gives me a stable 3.84ghz with orthos running without incident for several hours.

I did reseat the chip with some artic 5 and I'm now seeing load temps hit 61/62c. (thats if you can trust coretemp).

Nice to hit 4ghz but in real terms I won't see any difference from 3.8.

Cheers, Paul.
Click to expand...
3.8's what I've settled on for now... I get that with 1.35v.

For 4GHz I needed at least 1.3875v, and things started to get a little bit hot then under Othos :(

It was pretty stable tho.

SW.
 
Guys,

Over the last couple of days I’ve had a couple of strange occurrences which have left me a bit concerned to say the least :(

First off, last night I had a minor crash of my programs – I had a couple of instances of Firefox running, Word and Acrobat Reader. Basically everything stopped responding and had to be closed down manually and I was presented with the usual Windows Critical Error etc… Not a major problem, Windows was fine afterwards and I was able to resume what I was doing immediately.

Now today was slightly different: I had just FF and Media Player running and I had a whole system crash, bsod, the lot! My system froze, I saw the bsod briefly, my music still playing normally in the background and then the system rebooted :mad:

Do you think I’m suffering from the legendary Wolfdale degradation phenomena? I’ve only got 1.325v running through it atm, but the volts have been as high as 1.3875v in the past. I think tonight I’ll Orthos it again, although it was good the other week for 10hr+ at 3.8? I’ve since tested it with OCCT (Stable) and 3DMark06 (Stable).

1largeny4.png
2largedd2.png


In the meantime, has any one got any ideas?

Cheers,

SW.
 
CPU/NB GTL Voltage Reference: CPU: Auto, 0.63x, 0.61x, 0.59x, and 0.57x. NB: Auto, 0.67x, and 0.61x. CPU Gunning Transceiver Logic (GTL) voltages are nothing more than reference levels that the CPU uses when determining if a data or address signal is either high (1) or low (0). Precision voltage dividers generate these voltages and are usually specified as a percentage of VTT. In the case of 0.67, this would be 67% of VTT. For example, if VTT is 1.20v then a CPU GTL Voltage Reference of 0.67x would result in a GTLREF value of 0.67 x 1.20V = ~0.80V.
Click to expand...

Basically, a quad core benefits from a higher voltage reference, wolfdales due to their 45nm architecture would "in theory" benefit from a lower voltage reference. Personally I've noticed a lot more stability with the reference voltage at 63% instead of 67%.
 
Right, I’m starting to get a bit annoyed now…

I left Orthos running over night, as per pic, and I thought all was good? I tweaked the vcore up a tiny amount, 1.35v I think, and it was all looking good from the Orthos results ;)

orthosdg4.jpg


Having it stopped it running; I cracked on with a bit of gaming, and then spent a bit of time on the web. Now, all I did next was hit Send/Receive on Outlook Express and my system froze, and I got the usual bsod and prompt reboot…

What’s going on? I’m getting a bit cheesed off now – until I sort it out I’ve gone back to stock settings :(

I all out of ideas – starting to think it might be Windows/software related?

Any ideas?

SW.
 
Might be wrong but it sounds to me like its more memory related than anything, also have you upped the voltage on your NB?

EDIT: those CPU-Z frames show that you still have speed step on! Turn that off!

EDIT2: lol soz.... try your ram @ 5-5-5-15 2T
 
Last edited:
sam.wheale said:
Right, I’m starting to get a bit annoyed now…

I left Orthos running over night, as per pic, and I thought all was good? I tweaked the vcore up a tiny amount, 1.35v I think, and it was all looking good from the Orthos results ;)

orthosdg4.jpg


Having it stopped it running; I cracked on with a bit of gaming, and then spent a bit of time on the web. Now, all I did next was hit Send/Receive on Outlook Express and my system froze, and I got the usual bsod and prompt reboot…

What’s going on? I’m getting a bit cheesed off now – until I sort it out I’ve gone back to stock settings :(

I all out of ideas – starting to think it might be Windows/software related?

Any ideas?

SW.
Click to expand...

Mine did the same thing at 500FSB, memtest, prime/Orthos stable yet it would freeze at odd times in games or just opening up an app. Pretty sure its my mb, just doesnt like these wolfdale chips, can run higher fsb's on conroe cores but not these chips :(
 
Foehammer2003 said:
Might be wrong but it sounds to me like its more memory related than anything, also have you upped the voltage on your NB?

EDIT: those CPU-Z frames show that you still have speed step on! Turn that off!

EDIT2: lol soz.... try your ram @ 5-5-5-15 2T
Click to expand...
Yeah - could be memory I suppose? I've run memtest86 quite recently though, and it was fine :(

Plus, wouldn't Orthos have kicked off if there was a memory issue? I'll try those suggested mem settings, but I think they're almost the stock settings?

Regarding speedstep - what would turning that off achieve?

Cheers,

SW.
 
As above, basically you never use software overclocking do you? Thats because its an unstable mare of an idea.

Speedstep is so run at stock speed the system can underclock when its not being used heavily to do nothing other than conserve power, but if you want to OC then you cant have that. Because one minute its telling your processor to underclock at low Vcore then in a instant its saying "Oi more power... speed.... i want zeee world" processor says "canne do it capin, i aineee goota the powa" end result:BSOD :)

Basically its like on AMD 939 (and on), and since then any power saving functions a processor has, have to be disabled, its the VERY first thing i do whenever I go to the BIOS to OC.

So you have the choice... save on power consumption or save on speed, its more likely that than any memory settings
 
Foehammer2003 said:
As above, basically you never use software overclocking do you? Thats because its an unstable mare of an idea.

Speedstep is so run at stock speed the system can underclock when its not being used heavily to do nothing other than conserve power, but if you want to OC then you cant have that. Because one minute its telling your processor to underclock at low Vcore then in a instant its saying "Oi more power... speed.... i want zeee world" processor says "canne do it capin, i aineee goota the powa" end result:BSOD :)
Click to expand...
Ha - good answer ;)

I get why speedstep is used but I don't understand why it becomes a problem when overclocking?

Speedstep works fine at stock right, but then you up the fsb/volts to get your Oc and it becomes unstable? It's not like the processor is going from the Oc speed back down to the original stock speed with speedstep - surely its all relative to the new Oc speed?

I'll give it a go anyways, thanks :)

SW.
 
Bit of a sweeping statement there jokester, I know of quite a few motherboards, AMD and Intel that will overclock better without it enabled. DFI would explicitly state you should disable it when doing extreme overclocking, I had a Biostar SFF system that stated the same in its manual.

I'd say a “mild” overclock should be fine, but you may find when you are reaching the "total absolute max" overclock for a given cpu it can become flaky where as it wouldn’t with SS disabled, if your clock back a few megahertz your fine in most cases :)
Maybe thats all you need to do to gain stability Sam
 
Jokester said:
sam.wheale:- Can you tell us what your Vcore drops to when Speedstep kicks in and what it's value is when the CPU is running at full speed?
Click to expand...
Hi guys - thanks for the replies!

According to the latest version of cpu-z my vcore is 1.296v when at 3.8GHz and that can drop down to 1.280v when idle and with speedstep on. That’s with 1.33v something in the bios.

In the meantime I've upped the ram vcore to 2.2v, which is what my Ballistix should be running at anyway, and I've also upped the mch and fsb overvolt by 0.1v each. Hopefully I might have a bit more luck now? I've kept the mem settings the same: 4, 4, 4, 12.

It seems pointless stressing my system again so soon, because I know its stable - 15hrs+ Orthos.

Could it be my memory? I might just take a gamble and go for some new stuff if it’s going to solve my problems?

SW.
 
You must log in or register to reply here.
Back
Top Bottom