The Phenom II List of Overclocks

holy :banana::banana::banana::banana:ing batman ^^^^^^:shocked:

please tell me you got this on water or air? and yes what are Vcore and temps please :up:

He's on phase.

well i cant really get anything stable on my board. cpu will boot 4 and was stable at 3825 but i just have random issues. the board just has so many issues i dont know where to begin stay away from the dfi 790gx jr if you want to overclock a pii the bios are a joke right now...

Run with Biostar TA790GX A2+
HT V @1.456, NB V @1.47
I like the bios, boot up at 3.8Ghz and easy 2.9Ghz NB freq.

On air, all cores...

http://img407.imageshack.us/img407/1...shot002zv4.jpg

model#=PII 940 BE
cpu_steps=CACVC AC 0849APMW
cpu_freq=3711
cpu_core="1.456 in the blue screen"
nb_freq=2385.1
htt_freq=2120.1
mem_freq=530
mem=2x2gb/Unganged
mobo=asus m3a79-t dlx
cooling=tec..
os=x86_xp_sp2



http://valid.canardpc.com/show_oc.php?id=487779

http://img.techpowerup.org/090118/Capture062.png http://img.techpowerup.org/090120/Capture097.png

**question about the occt. is the high priority default..if not, i will run it again w/ it.****
http://img.techpowerup.org/090119/Capture089.png

Hi, i've been reading this thread to gain some info how to OC my rig, so i give it a try.

I'm from the Netherlands so sorry for my sometimes poor English.

I'm very proud of my rig 'cause i worked my ass of to pay the damn thing:p:

But i want to reach those (magical) figures of 4.0 ghz but hey who doesn't.

I've been able to run it at 3.8 stable on a dozen or so Vantage runs, but when i run OCCT it crashes after half an hour due to high temps.

Maybe i can run it with lower Vcore but my RAID% collapsed and had to rebuild it so couldn't test anymore.
I will give it a go next weekend.

3.8 is not to bad for what i've been reading overhere but i'm on water so maybe higher is possible.

3.8 running specs:

CPU: 3.8
CPU multiplier: 19
FSB: 200
Vcore: 1.5750v
Ram @1066 5 5 5 15
Ram: 2.1v
HT: 800 or so, it's sets itself back 'cause it's on AUTO
NB FreQ: 2800
NB Multiplier:14
All other settings are stock or AUTO.

Here a screenie of the highest run out of 12 Vantage.

http://img164.imageshack.us/img164/348/phenom38bt7.jpg

My rig:
Asus Crosshair II Formula
AMD Phenom II 940
Thermaltake Thougpower 1200w
4x2g Corsair Dominator 1066mhz
Asus GTX280 @ SLI
Windows Vista H.P. 64bit


If somebody got a good idea or any upgrading critisism i'm listning.

Thanks in advance for the replies.

And guys, keep up the good work of torturing these lovely CPU's:up:

Grts from Holland


Chris

Quote:

---

Originally Posted by HondaGuy

CACVC AC 0848FPAW

---

I got the same one :)
batch 0077

Quote:

---

Originally Posted by Rammsteiner

Ugh, forget it:shakes: Everytimer I think I solved it somehow it happens again anyway.

First I had random 0x00000124 issues. This seems to ber solved now. However I still get the pop-up notifying that ati driver has stopped working and is recovered. This can happen 5 times in a row and BSOD into 0x00000116. And just yesterday it got worse and just BSOD'd into 0x00000ea.

I tried :banana::banana::banana::banana:loads of things, I reinstalled the driver a few times, I chose not to install CCC a few times, when it was installed I chose to close it before gaming and I even tried to install ATT instead of CCC...:shakes: Im done and Ill re-install XP x64. It's a shame since I wanted Vista for DX10 but this way I cant use it anyway.

Great job M$, luckily they're already testing Windows 7 while it seems that this particular issue (which happens to nVidia too btw) has been there since the Vista beta!:down:

Then to think a few years ago everyone was like avoiding XP as much as possible, well, I embrace it right now:cool::yepp:

---

Yank your other two cards for now and completely get rid of Catalyst.
1) Uninstall via control panel
2) Remove video cards (and choose to delete driver software) out of device manager
3) Scan for hardware changes
4) If it comes back as an ATI whatever instead of a generic video card, go to #2 and repeat until it doesn't. You may have to do this once for each version of Catalyst you've installed since you installed Windows.
5) Run Driver Sweeper (at guru3d, free)
6) Reboot
7) Run Driver Sweeper again, twice, to confirm everything is gone
8) Reboot
9) Ok, now you should be using Generic still and have no driver crap left over. Delete the ATI folder out of Program Files.
10) Install an OLD version of Catalyst prior to 8.11. Preferably you go further back to like 8.6 or 8.8. 8.11 and all versions of 8.12 are seriously buggy on at least 3k and 4k series cards and I had the same issues as you until I wiped out everything and installed older drivers. Fortunately, 8.12 is only about 1-3% faster than 8.6, so you aren't missing out on much.

Anyway, if you don't BSOD and get driver responding errors anymore, you'll know it was the dreadful 8.11/8.12 fiasco to blame. Install your other cards again.

Quote:

---

Originally Posted by Particle

Yank your other two cards for now and completely get rid of Catalyst.
1) Uninstall via control panel
2) Remove video cards (and choose to delete driver software) out of device manager
3) Scan for hardware changes
4) If it comes back as an ATI whatever instead of a generic video card, go to #2 and repeat until it doesn't. You may have to do this once for each version of Catalyst you've installed since you installed Windows.
5) Run Driver Sweeper (at guru3d, free)
6) Reboot
7) Run Driver Sweeper again, twice, to confirm everything is gone
8) Reboot
9) Ok, now you should be using Generic still and have no driver crap left over. Delete the ATI folder out of Program Files.
10) Install an OLD version of Catalyst prior to 8.11. Preferably you go further back to like 8.6 or 8.8. 8.11 and all versions of 8.12 are seriously buggy on at least 3k and 4k series cards and I had the same issues as you until I wiped out everything and installed older drivers. Fortunately, 8.12 is only about 1-3% faster than 8.6, so you aren't missing out on much.

Anyway, if you don't BSOD and get driver responding errors anymore, you'll know it was the dreadful 8.11/8.12 fiasco to blame. Install your other cards again.

---

sure glad I saved 8.10 .8.11 was ok but, 8.12 keeps putting a load on My GPU when I full screen my TV. and now it totally :banana::banana::banana::banana:ed it up and won't play TV right at all.I hit play the images is still and the sound is there I pause it it shows the frame it didn't play >_>. Full screen TV I get a prictureover laps in between frames and it never go's away. now lasty playing anything in 3d nowisgiving some weird frame sync(sync vertical refresh is OFF)

:up: thanks for the driver sweeper info

3D air, Biostar....

http://img134.imageshack.us/img134/8...shot004cu0.jpg

Quote:

---

Originally Posted by Particle

Yank your other two cards for now and completely get rid of Catalyst.
1) Uninstall via control panel
2) Remove video cards (and choose to delete driver software) out of device manager
3) Scan for hardware changes
4) If it comes back as an ATI whatever instead of a generic video card, go to #2 and repeat until it doesn't. You may have to do this once for each version of Catalyst you've installed since you installed Windows.
5) Run Driver Sweeper (at guru3d, free)
6) Reboot
7) Run Driver Sweeper again, twice, to confirm everything is gone
8) Reboot
9) Ok, now you should be using Generic still and have no driver crap left over. Delete the ATI folder out of Program Files.
10) Install an OLD version of Catalyst prior to 8.11. Preferably you go further back to like 8.6 or 8.8. 8.11 and all versions of 8.12 are seriously buggy on at least 3k and 4k series cards and I had the same issues as you until I wiped out everything and installed older drivers. Fortunately, 8.12 is only about 1-3% faster than 8.6, so you aren't missing out on much.

Anyway, if you don't BSOD and get driver responding errors anymore, you'll know it was the dreadful 8.11/8.12 fiasco to blame. Install your other cards again.

---

Thanks for the info, but already re-installed XP x64. I was completely done with Vista:shakes: Ill wait for SP2 or so before Ill try it again.

Anyway, what's considered to be a safe Voltage for Vnb? Im on air, but also with MOSFETs in mind. Im now at 9x285 for NB, but I'd like to get it to 10x285. I need about setting 15~16 for Vnb on this speed (say 1.275~1.3V), where should this end if I wanted to get higher with the Vnb?

Also, did anyone try Prime95 64-bit (blend)? Somehow it makes my system BSOD/error while I can run Memtest for 250%+ without issues:confused: First time I used Prime95 64, but also nothing seemed to help to fix errors, so Ill just use normal Prime95/OCCDT/Memtest then:confused:

Well guys... I have bad news. My laptop which had everything on it, is now just dead. I'll have to find something to get all my stuff off the hd, but its completely like dead now. So for you guys that means I don't have a way to update the list because that laptop was the only system I had with a copy of word on it. My copy of office is at home, so its a good thing I'm going home this weekend. I was hoping to make it through this semester with it, but I guess not.

On the fun side of things I have it completely taken apart and the only thing they used real thermal paste on was the cpu, northbridge and graphics had these weird pad things. Now I really get to go and price out a new laptop, so no launch day AM3 system for me:(.

So could someone take over the task for me? All I'd need to do is make it so someone else can edit my first post.

Quote:

---

Originally Posted by Rammsteiner

Thanks for the info, but already re-installed XP x64. I was completely done with Vista:shakes: Ill wait for SP2 or so before Ill try it again.

Anyway, what's considered to be a safe Voltage for Vnb? Im on air, but also with MOSFETs in mind. Im now at 9x285 for NB, but I'd like to get it to 10x285. I need about setting 15~16 for Vnb on this speed (say 1.275~1.3V), where should this end if I wanted to get higher with the Vnb?

Also, did anyone try Prime95 64-bit (blend)? Somehow it makes my system BSOD/error while I can run Memtest for 250%+ without issues:confused: First time I used Prime95 64, but also nothing seemed to help to fix errors, so Ill just use normal Prime95/OCCDT/Memtest then:confused:

---

Hey Ramm,how's the XP64 serving you? You got rid of those BSODs with the XP64 OS?

Sure, I'll do it.

Now do I just need to pm a mod to give you access to it or how does this work?

4.758GHz @ 1.608v under Windows XP 32-bit

CPU Stepping: CACVC AC 0850BPDW

http://valid.canardpc.com/show_oc.php?id=489008

I don't know that it can be setup in such a way as to allow me to edit your post. Fortunately, that won't be necessary. We can just setup the image and I can maintain that image file.

Quote:

---

Originally Posted by Particle

I don't know that it can be setup in such a way as to allow me to edit your post. Fortunately, that won't be necessary. We can just setup the image and I can maintain that image file.

---

yea that would be nice i liked how it was on the last phenom I list which i believe you did.

Quote:

---

Originally Posted by Brother Esau

Problems Right Now with Current Bios for ALL D.F.I AMD Boards with New Phenom II. Taiwan is working on this and I am Testing a Alpha Candidate right Now For D.F.I that will bring universal Code and layout for all D.F.I AMD Boards ...................Be Patient its being addressed as we speak:up:

Take my advice DO NOT Push to Hard with Current Bios. Voltage Tables in Bios Need serious attention much more so on 790FXB Models

---

Thanks brother. :D

As we "speek" I am running OCCT 2.0 on my "old" Gigabyte GA-MA690G-S3H with the X4 920 @ 260x12 :D
Unfortunately VCore is "no-no" in the F7 bios (which is the latest and only that support Deneb/PHII). So I cannot go any further on CPU-clock (regardless of HTT/MP combos).
I am running 260x12 just to verify that my DFI board was (for now)"crap" as it only allowed HTT < 240 (also verified with an X2 6000+) :(
The "old cheapo" Gigabyte board easily do over HTT300. :up:
So until I get a "working" Bios in my somewhat "pricey" DFI Jr-board I will have to be satisfied.
This "session" is a very good example of how cheap you can get away with purchasing a PHII for an existing rig.
(Max load was a tad over 45 degrees).

Quote:

---

Originally Posted by NCspecV81

4.758GHz @ 1.608v under Windows XP 32-bit

CPU Stepping: CACVC AC 0850BPDW

http://valid.canardpc.com/show_oc.php?id=489008

---

COOLING??????? nice Oc :)

Quote:

---

Originally Posted by SkullCracka

COOLING??????? nice Oc :)

---

SS phase. Actually just a stock vapo LS w/ fan mod and duniek mount.

Oldguy, here, use this in an img tag in your original post. I'll start with the Prime95-passable list. Please make a note that people should PM me to alert me of changes to their scores and indicate if the result is to be a new entry or a modification for something already in the table.

I will update the image at this URL with entries as they are submitted to me. The OP will always be up to date without editing it that way.

http://www.pcrpg.org/pics/computer/octprime.png
http://www.pcrpg.org/pics/computer/octsuicide.png

Stable
http://www.pcrpg.org/pics/computer/octprime.png

Suicide
http://www.pcrpg.org/pics/computer/octsuicide.png

Quote:

---

Originally Posted by Particle

Oldguy, here, use this in an img tag in your original post. I'll start with the Prime95-passable list. Please make a note that people should PM me to alert me of changes to their scores and indicate if the result is to be a new entry or a modification for something already in the table.

I will update the image at this URL with entries as they are submitted to me. The OP will always be up to date without editing it that way.

---

hi particle. im running xp32 sp3. occt stable ~7.25 hours

@ informal, yeah, got rid of all the crap:up: There's one little problem regarding my X-Fi though, driver keeps wanking I didnt reboot after install and now I cant re-install:rolleyes: Prolly have to use Driver Sweeper in save mode then.

Just finished a 3h run of OCCT, highest priority and a mix of RAM/CPU. All was fine. Although Im still wondering wtf is with the 64-bit Prime95:confused: It probably stresses the 64-bit registry that hard it doesnt allow a single OC:confused: But after a ~100% memtest session and this 3h OCCT run without issues Im pretty much convinced that this 64-bit Prime is either buggy or seriously picking on eventual almost non-excisting failures, so Ill leave it for what it is unless I get real problem running stuff.

@ BE, what's the voltage table issue? Does it set voltages too high, too low or is for example 1.3V equal to 1.275V while setting 1.275V equals 1.4V? Like seriously messed up?

According to the OC list I seem to have a damn nice OC here:rolleyes: 3.705Ghz @ '+0.150V' and 2.565Ghz NB @ ~'14' (IIRC, somewhere between 14 and 16). Ram running DDR1140 as well. I got to try and get the NB at 2.85Ghz and the RAM timings a tad tighter:cool:

Quote:

---

Originally Posted by Rammsteiner

@ informal, yeah, got rid of all the crap:up: There's one little problem regarding my X-Fi though, driver keeps wanking I didnt reboot after install and now I cant re-install:rolleyes: Prolly have to use Driver Sweeper in save mode then.

Just finished a 3h run of OCCT, highest priority and a mix of RAM/CPU. All was fine. Although Im still wondering wtf is with the 64-bit Prime95:confused: It probably stresses the 64-bit registry that hard it doesnt allow a single OC:confused: But after a ~100% memtest session and this 3h OCCT run without issues Im pretty much convinced that this 64-bit Prime is either buggy or seriously picking on eventual almost non-excisting failures, so Ill leave it for what it is unless I get real problem running stuff.

@ BE, what's the voltage table issue? Does it set voltages too high, too low or is for example 1.3V equal to 1.275V while setting 1.275V equals 1.4V? Like seriously messed up?

According to the OC list I seem to have a damn nice OC here:rolleyes: 3.705Ghz @ '+0.150V' and 2.565Ghz NB @ ~'14' (IIRC, somewhere between 14 and 16). Ram running DDR1140 as well. I got to try and get the NB at 2.85Ghz and the RAM timings a tad tighter:cool:

---

nice going so far:) run occt 6.5 hours+ to inspect your NB. i've had it fail at that mark and needed to up NB v's some to get it to complete. i used to run for 5.5 hours, but then left it running and forgot, and saw it fail at 6.5. now i run usually for 8 - 8.5 in the end.