• 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.

AMD® Phenom™ II Overclocking Thread

well so far 3.9ghz is still going strong with 1.5v. at 10.30pm i will stop it (because i wanna do some HT tests) then i'll do a 8 hour prime tomorrow.

at 1.5v i get a 0.001v ripple.
 
Last edited:
liamcrane: as gareth has mentioned this strange phenomena where the vCore you set in BIOS is different from the vCore you get in BIOS-Health Menu/CPU-z is well known, it's called vDrop and is pretty much normal. The reading you really need to pay attention to is the figure you see in CPU-z/BIOS-Health Menu, there isn't an official name for this "real-world" vCore figure so I just call it vCore Actual . . . It does help others who are reading about your work if they are informed of both figures (i.e what you set and what you get, idle/load) . . . The other variation of weird voltage that is quite common is called vDroop (Droop not drop as above), this is when the vCore sags/droops when the processor is under load . . . . both vDrop and vDroop can be offset to some degree if your motherboard has a BIOS feature called something like "Loadline Callibration" . . . I've only just started playing with this setting myself but found it works pretty good! :) . . . . props to eddyc for the info . . . . the last variation of voltage and is something I'm dealing with now is called McRipple, that's not the official name but I think it rolls off the tongue lol, anyway McRipple is where the vCore graphs look like they are actually seismic earthquake print outs! :p . . . . I'm still working out why this happens? . . .doesn't appear to be causing any problems but I think the less variation the better . . . both Gareth and Martin's vCore graphs are 100% smooth line with 0% ripple!

If you have time read post #622 where you can see my OCCT vCore graph and also a link to the software . . . also read post #624 where eddyc has linked up some useful info on Loadline Callibration . . . sorted! :cool:

[edit]

Oops one last thing for anyone just joining the thread, please read post #576 where it's explained how to configure the forum software to show "maximum" posts-per-page . . . having 80 posts each page really helps reading through & navigating large threads! ;)
 
Last edited:
Ive just been fiddling with the vcore and some basic benchmarks, from the looks of it i should have a fair bit of voltage to play around with when i come to blend testing.

 
Last edited:
well after 3hours n 45min mines failed at 3.9ghz but i really think it was the cpu-nb that made it fail because it didn't do a BSOD.... 1 thing that got me worryed is i thought i could smell a burning smell but i don't think it was... cpu temp was 54c, core temp (which is software madeup) was 57c
 
Last edited:
Hey phill0i, nice result and nice screenie, I want that font dude! :) also I was hoping you could select your own Star-Wars graphic hehe! . . . I sent you an email to your trust account for more details . . .
 
Last edited:
gareth170 : you say you think your fail; wasn't cpu-nb because it wasn't a BSOD... Is that a decent rule to work to, that a bluescreen is a vcore/frequency thing, and a graceful prime fail is a cpu-nb?

I ask because after 5 hours at 3.6 and stock volts mine BSOD'd out. Gutted, tbh... never had a prime run for so long before dying on me, felt soooo sure it was solid (that may be the dutch courage, it's pub night, after all...) :(
 
Last edited:
Ok guys i was going to leave the system priming over night but im getting a bit worried about damage to my motherboard as i have no cooling on the mosfets. Do you think their is a real risk of heat damage or am i just being over protective of my new toys?
 
I have no cooling on the mosfets, doesn't seem to be causing a problem here (2-3 months) . . . I put my fingers on the phases & VRMs and they are running hot but not burning! :D . . . I've been meaning to rig up some ghetto-loving cooling to help but in the meantime it's all good in the hood! :)
 
At last - this is what I've settled for (12hours prime blend stable) as temps are good with all fans low keeping PC nice and quiet :)

zoomee2.jpg


BIOS Settings as follows:
AI overclock tuner: Disabled
CPU Ratio - Auto
CPU Bus Freq: 224
DRAM Freq: 1493Mhz
CPU/NB Freq: 2464Mhz
HT Link Speed: 2464Mhz
CPU Volts: 1.45v
All other volts kept at Auto
CPU and CPU/NB Load-line calibration: Auto

Temps on CPU averaging 46Degrees C - only hit a high of 50+ last night due to raised room temperature (bit of testing ready for summer time :) )
Will need to tighten up RAM timings and job is a good un!
:)

thanks for your advice guys mucho appreciated.
 
Last edited:
Afternoon everyone, thought i would take the next step into my OC and try and get the 3.6ghz that i wish to stick with but it failed on me :(. I upped the multiplyer to 18x and set the voltage to 1.375 and left it on prime95 while i went out only to come back an hour and a half later to the message your computer has recovered from an unexpected shutdown :(. I checked the log file but could not find anything to why this happened. Anyway i have now upped the voltage to 1.385 and am running prime again now, but if i try and go 1 notch higher the voltage number turns yellow so i didnt wanna go any higher without checking with you guys first.
 
You must log in or register to reply here.
Back
Top Bottom