Phenom 9500 w/ MSI K9A2 Platinum

Quote:

---

Originally Posted by Blacklash

I may try another AMD chip that overclocks better. Phenom overclocking is just depressing. Not to mention, I have been hanging around in the Intel section where folks are getting 4.7GHz with the new E8500s.

---

While C2 or the QX oc's far better air/water (there's no doubt about it since long) with retail <E8400/Q9550, I doubt it. Not what I'm seeing at all, stuck sub 3.7-4GHz <1.5V. I'll pick up a retail E8400 very soon if not this weekend anyway. Intel started the games again with this commanding position of offering crap locked multis even though the chips are capable of more with a higher multi. But E8500 here is no where found, none of them are yet and the E8500 is 200USD more than the 9500 here. <E8400 will be same price as 9500 here.

Quote:

---

Originally Posted by jonspd

http://www.jonspd.com/jonspd_uploads...nies/test2.GIF

---

Have you never tried max HT of the chip yet?
272MHz is very high. My chip did 270ish max and it ran 265HT perfectly at 10x, so try for more. Maybe you need better cooling.

Nope I haven't. Maybe I should try a 9x muilti tomorrow. Yes my temps do concern me at this point on air. I did however manage to run alittle lower vcore.


off to bed and fold for a while gotta turn in a unit tom sometime also got the F@H 2653 smp wu's down under 12min a frame.

Quote:

---

Originally Posted by Blacklash

I may try another AMD chip that overclocks better. Phenom overclocking is just depressing. Not to mention, I have been hanging around in the Intel section where folks are getting 4.7GHz with the new E8500s.

---

You know what... Phenom is mysterious, I've had it for almost 3 weeks, I've kinda treated it like a new car. I'll be nice to it most times, but I'm not afraid to take it out on the highway either, and I'm not gonna Drive 55! :D

I'm probably crazy... But I always feel like theres that little something missing that will make this chip shine, whether it be Bios, OS, Drivers, Software, SB700 or my Tweaking ability....

I can't find the link right now, but I think it was Tom's Hardware (Don't Hate!) that showed the Phenom kicking butt on UT3, seems like the programmers spent alot of time on multi-thread for that game and it did really well on Phenom.....

But your absolutely right.. That 5000 BE is looking pretty tempting for $99!

Bet I could hit 3.5 on that bad boy.... :up:

Quote:

---

Originally Posted by jonspd

Nope I haven't. Maybe I should try a 9x muilti tomorrow. Yes my temps do concern me at this point on air. I did however manage to run alittle lower vcore.


off to bed and fold for a while gotta turn in a unit tom sometime also got the F@H 2653 smp wu's down under 12min a frame.

---

So your running 272 HT with an 8x NB, WOW.. :eek:

Sounds like you got a good one Man!! What was that stepping again? :p:

so just curious whats the fasted 1M time so far? I have a x2 6400+ that can do a 22.75 and wondering if a phenom will ever beat it.

Quote:

---

Originally Posted by Daveburt714

So your running 272 HT with an 8x NB, WOW.. :eek:

Sounds like you got a good one Man!! What was that stepping again? :p:

---

9600BE (CAAWB AA 0748DPGW)


it still a b2 with a bug tho :D

I hope that when the b3 comes out they get alot better clocks....

Quote:

---

Originally Posted by =[PULSAR]=

so just curious whats the fasted 1M time so far? I have a x2 6400+ that can do a 22.75 and wondering if a phenom will ever beat it.

---

Time depends on clock speeds most, simple as that. If you want to see 1M times, then Wolfdale is the way because AMD is never been fast at it.
Throw a 2.8GHz clock speed and get your best 1M and post it back. ;)

BIOS P0F: v.bad for oc

*Problems:
Only boots 1066 at 1.8V - runs nothing less than 1:2.66 divider
NO CPU DID/FID/VID options anymore
NO CPU NB voltage options
NO NB FID/DID/VID options anymore
RAM voltages still increment in 0.1V (In BIOS)
CPU voltages still increment in 0.05V
HT is set to 1.225V on stock bootup when its supposed to be 1.2V
Low HT ref. limit.
AOD oc'ing still freezes the system yet (even when downclocking from 2350->2300)
Higher than 1.26 VID makes system reboot/unstable at stock frequency, higher or lower.

What the heck MSI! :(

*Good additions:
At least boots 1066 and CAS3. :D
TLB patch is user choice in BIOS
Allows CPU/HT multi choosable in decimal figures
Shows current CPU/RAM speed and DCT mode
RAM voltages go up in 0.05V in AOD now
CPU voltages go up in one lower increments between 1.24V-1.5V

*We WANT:
All the above *problems fixed please
Boots 1.8V, why not 1.9/2.0V to allow more RAM compatibility?
RAM voltages to go up in 0.025V
Lower CPU voltage increment (not ~0.05V but 0.015V)
Lower tRP tRTC tRAS options

I've not had a Phenom boot since 14hrs now since flashing that BIOS and setting 200 13.5x (2700) @ 1.45V...

How many of you notice that your Phenom (like mine) has a problem with high VCore/VID and high multi specifically? :confused:

Meaning any of these at low CPU speed can cause a crash/no boot/freeze.

yep I have noticed that also with higher multi for sure.

I seem to have another issue when I set 2.3 for ram it changes in HWmonitor. when I set 2.2 it changes to that also but when I set 2.1 it doesn't change I haven't tried lower 2.05 or 2.0 but I thinking that I might be stuck at a 2.2vddim as my lowest allowable.



I would for sure like to see a more wide spread voltage pattern as I dont like changing ram with .1 increments.

Quote:

---

Originally Posted by KTE

How many of you notice that your Phenom (like mine) has a problem with high VCore/VID and high multi specifically? :confused:

Meaning any of these at low CPU speed can cause a crash/no boot/freeze.

---

Addition; you may also crash/freeze your system if you select a too low CPU/NB speed with a high CPU/NB VID. A balance needs to be achieved it seems.

Good afternoon Tye how are you feeling since the accident?:) ,Hey what kind of ram are you running to get cas3?

Quote:

---

Originally Posted by Brother Esau

Good afternoon Tye how are you feeling since the accident?:) ,Hey what kind of ram are you running to get cas3?

---

I'm good Bro, Crucial RAM sticks do 4-4-4-4 600 easy at 2.2V on P35, so 2.2V 1066 boots 3-5-5-15. I mean 1.8V 1066 5-5-5-15 boots perfect. ;)

ATM this BIOS doesn't allow over 550 on RAM speed, it just reboots. And it seems RAM can only boot 2.1V and its setting bootup stock speed as oc'd (below).

Look at this for one core fluctuations :eek:

http://img227.imageshack.us/img227/1236/fluctru8.png


This is what I said messes oc up badly.

Well I played with vmware and smp clients last night still gonna play around some today but the adapter for my better cooling should be here soon and hopefully there after I will be able to come back around and post a better overclock with the system :D

untill then fold and clock on!!!

Yeah, quick update part 5000: :(

*It 'aint the AMD CPU which is freezing. It's something other related to either MB/RD790/PLL/AOD. Because my chip has now started going whacko and boots stock (defaults) at 1.184V 2369MHz and 1.8V DIMMs. So when I try to underlock it to 2.3G after bootup, it freezes at 2.32G, 2.34, 2.35G. :confused:

This is why I said it's all just so flocked up and convoluted!!

*Also, I tried some cold at work v.quickly and whilst it booted -15C, the oc limit was still the same and now my temp sensors inside the cores have stopped working -> stuck at 0C. Even the internal tjunction sense is reading a little too low, usually it was at 33C idle in this environment 1.192V and now its at 23C, which is ambient. So its incorrect.

*And whilst my chip never booted 1.184V (reboot loops) I thought I'd get into Windows and P95 test and bench 1.184V idle/1.176V load 2.3G to see what happens. Well whadya know, it runs it perfectly fine, I gamed it after that:

http://img301.imageshack.us/img301/5...1176gf2.th.png

This just makes no sense :confused:
So now I'm curious to know why the hell it won't boot with 1.184V.

*BIOS P0F even wth the patch disabled through the BIOS still degrades perf by a long margin. 1880KB/s compression to 666KB/s.

*People talk about "IPC" a lot but I don't know if they're unaware or not understanding enough but IPC is never constant and differs with every sort of software (instructions) used because some instructions are more complex and do more useful work than other simple ones, thus most software never utilizes max IPC capability of a core even for 1% of the runtime. Thus some software only utilize 0.8 i/c while others can get 2 i/c out of the same core. Those utilization near the maximum of the architectural limit show better perf. quite obviously and higher CPU power usage.

For instance. I ran benches and looked at IPC and L1/L2 accesses. Any benchmark/software which accesses L1 greatly with high IPC=higher power draw. As an example, Super Pi 32M only used maximum IPC of 0.8 i/c whilst EVEREST FPU Julia used 2.5 i/c and Prime95 utilized 1.7 i/c fixed (hence the power -> v.high each core utilization). Any software which can utilize near the maximum IPC limit with complex instructions will in effect perform far better than if it used simple instructions with low IPC usage. You can see P95 above and EVEREST FPU Julia here:

http://img301.imageshack.us/img301/6937/ipcug1.th.png

*Another problem I noticed whilst debugging SuperPi on this platform. There's an unnecessary delay hence the times are slower than they should be (which doesn't happen on X2/P4/C2). No idea about others but this is the case with mine. Writes to HD by SuperPi are being denied which is adding latency/wasting clock cycles because until that data is written the calculation doesn't move on. Out of 37,xxx events a minimum of 500 (v.reserved there) were write failures and another 500 were just rewrite attempts. Why? The reason given was "too fast I/O". See below for what I mean:

http://img237.imageshack.us/img237/1152/spizp3.th.png

More confusion, more problems. :(

Here's some Pi 32M action for you to compete with. :p: :D
1.5minute compared to 32minutes for SPi mod 1.5, talk about inefficiency.

http://img132.imageshack.us/img132/255/qpi32mld3.png

KTE very nice find, driver issue? somesort of bug? im confused now :D

Quote:

---

Originally Posted by KTE

*Also, I tried some cold at work v.quickly and whilst it booted -15C, the oc limit was still the same and now my temp sensors inside the cores have stopped working -> stuck at 0C. Even the internal tjunction sense is reading a little too low, usually it was at 33C idle in this environment 1.192V and now its at 23C, which is ambient. So its incorrect.

---

How much higher could you get with cooling and what where your load temps?

Quote:

---

Originally Posted by KTE

*Another problem I noticed whilst debugging SuperPi on this platform. There's an unnecessary delay hence the times are slower than they should be (which doesn't happen on X2/P4/C2). No idea about others but this is the case with mine. Writes to HD by SuperPi are being denied which is adding latency/wasting clock cycles because until that data is written the calculation doesn't move on. Out of 37,xxx events a minimum of 500 (v.reserved there) were write failures and another 500 were just rewrite attempts. Why? The reason given was "too fast I/O". See below for what I mean:

---

You might try running it from a ramdisk.

No higher with cold, it was a 10 minute test at work mainly to check for CB. In fact not even a hair over 2.5G this time. Dropping the chip off in 2 hours and starting my Q6600 G0 up instead.

As for temps, I have no idea. See: http://www.xtremesystems.org/forums/...9&postcount=19

Temp. sensors work fine now, I rested it for a few hours and restarted it briefly at work 10 minutes ago. Back to normal it seems, idling 33C.

Spi problem occurs because? IDK, it shouldn't happen, it slows any short bench down.

Don't have a RAMdisk Achim.

Quote:

---

Originally Posted by KTE

No higher with cold, it was a 10 minute test at work mainly to check for CB. In fact not even a hair over 2.5G this time. Dropping the chip off in 2 hours and starting my Q6600 G0 up instead.

As for temps, I have no idea. See: http://www.xtremesystems.org/forums/...9&postcount=19

Temp. sensors work fine now, I rested it for a few hours and restarted it briefly at work 10 minutes ago. Back to normal it seems, idling 33C.

---

Gained ~50MHz here lowering the load temps from 64&#176; to ~40&#176;. Have you tried it with a lower vddc?
EDIT: Saw you did in your other post
EDIT2: Have you tried the latest coretemp should handle temps in the range -49&#176; - 206&#176; maybe it's an everest issue.

Quote:

---

Originally Posted by KTE

Spi problem occurs because? IDK, it shouldn't happen, it slows any short bench down.

Don't have a RAMdisk Achim.

---

I mean a software based ram drive. Might fix the too-fast io issue. Link.

BTW: Your mobo also has an promise sata controller. Have you benched your hd on that controller?

Quote:

---

Originally Posted by justapost

Gained ~50MHz here lowering the load temps from 64&#176; to ~40&#176;. Have you tried it with a lower vddc?

---

This is one thing I have to try yet, I've been planning to but not found the time. I'll try it later today to see if different volts/VIDs gets different oc.

Quote:

---

I mean a software based ram drive. Might fix the too-fast io issue.

---

I have it, just waiting to get a new Phenom now. Shouldn't be too long. Thanks for the link too. :)

Quote:

---

BTW: Your mobo also has an promise sata controller. Have you benched your hd on that controller?

---

Those above tests were with the Promise controller in IDE mode (AHCI causes BSOD). I don't remember the perf. with SB600 and I can't find any saved pics of it either. I'll give it a try soon. ;)

EDIT: thanks for the CoreTemps headsup. I stopped using it because the previous versions were so errorsome but the new version works fine. :up:

http://img137.imageshack.us/img137/5362/ctevlu4.th.png

Quote:

---

Originally Posted by KTE

I have it, just waiting to get a new Phenom now. Shouldn't be too long. Thanks for the link too. :)

---

Lol, just tried it here and gained 3s in sp1m at stock, ~1s in xs sp1m.
EDIT: Had CnQ enabled, without it this difference is marginal ~0,1s. Do you know if super pi counts while disc operations?
Make shure you set Start=1 for the FastFat Service in the registy (HKLM\System\CurrectControlSet\services\FastFat).

Quote:

---

Originally Posted by KTE

Those above tests were with the Promise controller in IDE mode (AHCI causes BSOD). I don't remember the perf. with SB600 and I can't find any saved pics of it either. I'll give it a try soon. ;)

---

Installed system with the drivers integrated and sata in ahci mode. It worked and I can boot into windows but it freezes after ~1 minute. Did not yet look into it again, as ide mode worked.

Quote:

---

Originally Posted by KTE

EDIT: thanks for the CoreTemps headsup. I stopped using it because the previous versions were so errorsome but the new version works fine. :up:

---

NP

@KTE ...& Gang.....Hey, guys do any of you know what these settings are on the new architecture and if they are related to Phenom or new chips? I know you guys have different board but perhaps you may have insight asto what these HT Settings pertain too and what they relate to. I know what the First 2 settings are for obviously but what of the remaining four?

I have no Idea the flowcontrol I think is network related.

2xlclk has to have something to do with some kinda timing IMO


google doesn't offer much support :D

You can read the specs at www.hypertransport.org.
Sorta like 120 pages, so I did not yet read it.

Thanks brother I'll do that:)

GL 120 pages is worse then this thread :D

running 2 vmware ubuntu clients with smp client on each and graphical F@H to take up the left over 3-8 &#37; gonna see what PPD I can crunch.

Got it at 10x250 ATM for stability.

I can't find the quote now, But your gonna leave us for the Dark Side KTE? (Q6600).... ;)

Have Fun!! D*mn, I wish I could get free stuff to play with... Thanks for all your help with Phenom though man!! I'm pretty sure you'll be back... :D

Phenom is just too much fun..... :up: