The Phenom II List of Overclocks

[faior]

Hondaguy, hehe I have seen the same difference.. which is just that the phenom2 overclocks better than phenom1s.
Altought my wprime result with 24/7 clocks is this: http://faior.miumau.net/wprime3.6.JPG

and 24/7 screen: http://faior.miumau.net/3.666.jpg edit url

[chew*]

Cybercat might I make one other suggestion, Your using 8 gigs with all 4 dimm slots populated, this tends to add stress to the mem0ry controller.( yes i know how to spell )

Try running only 4 gigs and see what you can acchieve, I know you probably have no plans to run 24/7 with 4 gigs but it would help determine what is limitng your OC.

[HondaGuy]

Hondaguy, hehe I have seen the same difference.. which is just that the phenom2 overclocks better than phenom1s.
Altought my wprime result with 24/7 clocks is this: http://faior.miumau.net/wprime3.6.JPG

and 24/7 screen: http://faior.miumau.net/3.666.jpg edit url

What board are you using, I guess the M3A79-T? Not alot of difference there in Wprime still have here the SB600 board also running PII on,, thinking of selling chip tho

[Rammsteiner]

Guys, I think Ive once again some retarded problem.

Like last night, I was testing 3.8Ghz CPU, NB 2Ghz (since 1.8Ghz would limit the CPU to 3.6Ghz) and HT at 1.8Ghz. RAM at DDR800, so pretty much only multiplier OCíng.

I set Intelburntest for 5 runs, 4 runs were all showing stability and then in between the 4th and 5th run I got a BSOD, 0x00000124. Ive gotten this one quite often, I googled it, only resulting in more questionmarks as it seems this BSOD could be for about anything.

A very few seemed to be related to the soundcard, most others were to certain series of nVidia cards, unstable OC's etc. But sometimes I ran a succesfull 8 run Intelburntest and then the very same settings BSOD'd the 2nd time after the 2nd run

Today I decided to get rid of my soundcard and uninstalled drivers. Then I tested my RAM, only for 40% coverage though, about 1.5hours, without a single error. I just run Prime95 for 1.5hours without issues. Although I dont know how Intelburntest relates to Prime95, this is quite weird nonetheless.

I also read a few single OC results from Intel users that adding FSB VTT and NB Volts (NB as in motherboard of course) helped them getting rid of this BSOD rage.

Thus far it seems to be all fine and happy but Ive this curse everytime Im convinced it's fixed it happens some way again. Does anyone have experience with this particular BSOD? Any tips or whatever?

Im even thinking that Intelburntest might not be such a good program after all. It's nice, but Prime95 managed to get my load temps higher and I cant believe that 15 minutes of Intelburntest defeats say a 8hr run of Prime95

Anyway, having no sound at this point, thinking Ill use my onboard sound after. Saves me from a load of crap anyway and onboard sound ain't all that bad nowadays

[chew*]

Hmmm ramm, vid card related in some cases, sounds like PCI or PCI traffic.

Curious if the PCI lock works, is it set to auto? sometimes at auto or default 100 it's not really locked, ruuning it manual at 101 can sometimes lock it.

I do get that exact code when really pushing this rig, more voltage does not fix it for me, bringing NB temps lower does....

Doesn't seem like SB, usually the easiest way to determing SB issues is your hard drive will "katunk" and BSOD.

[Rammsteiner]

Ain't getting BSOD's anymore now, my PC restarted this test I just started instead of BSODíng.

Ive PCI-e at 100, but Ill set it to 101 then just to be sure. GPU related, highly unlikely to be honest. There could have died a million things but GPU, no

Anyway, seems like I hit my max clocks for CPU then with +0.150V, 3.7Ghz (or slightly above that but it just restarted at 3.755).

[chew*]

[QUOTE=Rammsteiner;3582887]
Ive PCI-e at 100, but Ill set it to 101 then just to be sure. GPU related, highly unlikely to be honest. There could have died a million things but GPU, no

Can be gpu related if the GPU can not handle a high PCI frequency not all gpu related errors are due to actual ocing of the card.

[BertM]

Ain't getting BSOD's anymore now, my PC restarted this test I just started instead of BSODíng.

Ive PCI-e at 100, but Ill set it to 101 then just to be sure. GPU related, highly unlikely to be honest. There could have died a million things but GPU, no

Anyway, seems like I hit my max clocks for CPU then with +0.150V, 3.7Ghz (or slightly above that but it just restarted at 3.755).

i have constant restarts, it rarely just gives an error or something.
and the max temp for the cpu goes down with higher frequency.
insane cooling is required to give the cpu a working temp of 40 degree or something.
for me 3700 and has a crash temp of about 44 degrees but 3500 doesnt even crash at 51 degree.

i guess i still do something wrong, as lightman has 51 degree on 3750

[Cybercat]

your running too hot, and the chip could be failing stress at oc settings as a result, in my opinion. please try to get this temperature down and then try to re-oc.

take an average of your temp using ITE smartguardian and CoreTemp. It would also be a good idea to get a thermal probe on the heatsink/waterblock if you are able to, so you can add in to the calculated average.

Well often it fails before it even gets a chance to heat up. Like if I try 3.5 at stock vcore, I'm lucky if the OS boots. I've been using smartguardian to monitor temps. Core Temp would act funky (temp would get stuck it seems). Anyway, other than the floor fan I don't have many options to lower temps, but I'll post back here if I think of something. I don't own an external temp probe.

Cybercat might I make one other suggestion, Your using 8 gigs with all 4 dimm slots populated, this tends to add stress to the mem0ry controller.( yes i know how to spell )

Try running only 4 gigs and see what you can acchieve, I know you probably have no plans to run 24/7 with 4 gigs but it would help determine what is limitng your OC.

Yeah I've played around the with memory. Underclocked it, took some sticks out, etc. I didn't try memtest like you suggested earlier though. Either way it didn't make any difference in stability. It seemed like a memory problem when it kept BSOD (memory dump) but never failed prime. But I don't think it is. I appreciate your help, I think either there are some BIOS issues or I just have a dud. Anandtech was able to get 3.9GHz with stock cooling on my board with an ES.