Phenom 9500 w/ MSI K9A2 Platinum

[KTE]

It's very simple.

Using the parameter coremask you can set the number of cores to boot.

You can either use the CPU-Z.exe application Right-Click>Properties>Target area to set this or use Command Prompt like I do.

First you'll have to type the application path followed by -coremask=x.

x = the number of cores you want to have after bootup. Change this value appropriately.

So, if I want to have 4 cores showing, then I type this in the Target box of CPU-Z shortcut or in Command Prompt:

"C:\Documents and Settings\Tye_2\My Documents\cpuz_144\cpuz.exe" -coremask=F

The "x" replaceable values are these:

F = 1111 = 4 cores
7 = 0111 = 3 cores
3 = 0011 = 2 cores
1 = 0001 = 1 core

Thus when I set "C:\Documents and Settings\Tye_2\My Documents\cpuz_144\cpuz.exe" -coremask=7 and then I restarted, my system booted up as follows with 3 cores.




If I now want to change it to 4-cores on the next bootup, I type the following:



When it restarts, it'll restart with 4-cores as I set it. Easy really.

Hmm mine does not freeze idling. It freezes above 2.5GHz-2.55GHz after ~3hrs. At 2.6GHz it freezes ~2hrs prime95.

If its P95 freezing then that's just plain old instability. Usually lack of VCore/cooling.

If I leave 1.28V on 2.7G it fails only on core 3 after 3-4 hours repeatedly while all others pass. Moving up every notch until I get to 1.372V will fail. It needs minimum 1.372V to pass for that core, massive jump. Then as the core frequency scaling ends, you see that you reach the area of diminishing returns: massive voltage > little increase.

I can bench 2.84GHz with decent cooling but it's actually slower than 2.754GHz, because the system is past it's limits.

Does a higher nb multi have an positive impact on the oc capability of the core's? I did not try it with a higher nb multi till now.

No way, higher NB multi will actually be tougher as your CPU Nb will require more volts and give off more heat altogether.
Keeping low Nb, HT, RAM is the best way to check for core limits.

So far I'm running 2665MHz again. It's not froze yet, but this time I have Memset open in view so when it does, I can see the various speed readings to determine if they are part of the cause.