Quote Originally Posted by KTE View Post
It's very simple.

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

Code:
"C:\Documents and Settings\Tye_2\My Documents\cpuz_144\cpuz.exe" -coremask=F
The "x" replaceable values are these:
Code:
F = 1111 = 4 cores
7 = 0111 = 3 cores
3 = 0011 = 2 cores
1 = 0001 = 1 core
Looks like it can be used to disable specific cores. Nice find, thank you.

Quote Originally Posted by KTE View Post
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.
Yepp, just had to find a good starting point to go for 2.6GHz. A direct jump via multi with just upped voltages vcore 1.4 vnbcore 1.3V did not work.
Making my way with 12x212+ now by increasing the ref HT in small steps.
2.5GHz worked fine with 1.22V vcore 1.07V vnbcore. Seems 1.275V/1.2V was not enough for 2.505GHz going on with 1.3V vcore 1.2275V vnbcore atm. Will look at this point closer once I reached the cpu limit looks like a big step must be done to get over this point with my cpu.

Quote Originally Posted by KTE View Post
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.
I thought about better stability due to lesser difference between nb and cpu speed.