Yep, that's how they load from disabled->enabled... but, why not see what FID/DID are presets.

Stock is 1.2000-1.250/1.250 for both parameters. You can disable P-States and bootup at stock all auto and check in AMD PowerMonitor.

On a side, you don't need high MHz for high bandwidth on Phenom...




Tried CAS3 1000 today, my sticks can do CAS3 1066 on P35, but with this system = no go. The system will boot but it will boot with bad CMOS: reset and everything reset.

Also, I've been experimenting. Two things to note, two very important things:

* Phenom is starved for memory bandwidth. Yes, damn, I've been playing with high clocks and low clocks and Phenom performance is low at low RAM clocks (same CPU/NB) compared to at higher RAM clocks, say 400 3-3-3-3 compared to 500 4-4-4-4.

* Phenom is very IMC dependent. As you may know, running Super Pi at 70k efficiency when the best efficiency is around 75k is impossible. On an Intel chip, best you can manage is 49k when you can get 50k very easily without any tweak. But with Phenom I've tried this and you gain quite a bit of performance in applications through just IMC overclocking. Number calcs will show this up very quickly, like wPrime, Pi apps and so on. You'll be quite shocked at what you observe if you do it the right way.

Check this. My system runs 1-core 2.8G bootup fine-> http://valid.x86-secret.com/show_oc.php?id=306352

1-core 2.9GHz fine but with high volts. Minimum needed to run 2.9G is 1.45V-> (click for full image)



3GHz was max, it froze soon after-> (click for full image)




BUT... I met very bad performance going from 2.75G to 2.8G. 2.8G was 2.2s slower than 2.75G in SuperPi 1M and 2.6G was 0.3s faster than 2.8G



Yeah, it's probably called instability, I gather. I better stability test my RAM to see if it's okay, this is very typical of dying RAM.