Phenom 9500 w/ MSI K9A2 Platinum

[KTE]

i manage to change 11.5, 200fsb and it OCed to 2300mhz accrding to cpuid...

one thing i notice can i change my NB setting to x13 or is this the HT speed?am running it to auto..

when i change it to x13 NB frequency reading is 2600mhz and HT speed is 1800mhz, is this normal?

Pretty normal, a known bug.

Check AMD OverDrive and see what real values it reads
If it changed, then it would read what they read for mine.
Also even better, benchmark it.

Why was your HT stuck at 9x? Because so is your NB.
Start AOD, you won't be able to move HT plus 9x because your NB is only 9x real. If you actually moved it up, the HT will move up along with it. We've been through this many times in this and many other threads.

any chance i can get P0J from someone to see if i can make it work? (on accound P0H still causes BSOD even with new install)

On MSI site for a while, but courtesy of Suosaaski: http://www.yourfilehost.com/media.ph...e=A7376AMS.P0J

Your own liability entirely.

Hmmm does the new P0J bios have the option to change nb/IMC multi again? And possibly voltage/vid if needed? I may consider updating to that one since the TLB fix can be fully disabled. Granted as far as NB volts go I shouldn't have much issue since I was doing 2.4 at stock VID before.

Nope.

On a side note, while underclocking using MSR values, have a look at this using decimal multiplier and DID. Very very very slow, took long to save a basic 200KB image, about 45 seconds.








Lowest underclock? Quite low that, it crashed very soon after the 1M run due to changing volts past 0.850/1.038. Power for that idle and load differed 2W AC.

Anyway, I've tested very slow, observantly and hard. I's true, my 4th core is the weak link and by far. Any time my system freezes or reboots, it's the 4th core spiking and getting stuck at full load. Luckily the 4th core is not needed for much at all. When I tested stability with high NB volts and higher CPU volts not gaming/lengthy testing on just core3 but on all others, for over 15hrs now, I've had no failure or error. This is what I'm running since then.