PII Black Edition + CnQ + Multipliers

[swaaye]

So, is there any way to keep CnQ working when one changes a BE CPU's multiplier? It's really unfortunate that there doesn't seem to be a way....

[roofsniper]

you could try using K10 Stat.

[vengance_01]

So, is there any way to keep CnQ working when one changes a BE CPU's multiplier? It's really unfortunate that there doesn't seem to be a way.... Yes it works just fine on my 940 BE and Foxconn 790GX board. When you change the HTT from 200 to anything else, this is when CnQ gets borked.

[Lostfaith]

crustalcpuid's "multiplier management" should work even with an "fsb" overclock:

http://www.silentpcreview.com/article231-page1.html

[Cheffy]

just use rmclock.

works for me - with fsb oc

you need to boot up with STOCK multi and your desired oc voltage, fire up rmclock and set it to PST performance maximal on mains for now, set the FID MAX to match your new multi (eg, 12x for me down from 16x) and find which vid max setting matches the vcore you want - this should be the same as the stock vid (1.4v in my case) (you should see the current core voltage - USE SPEEDFAN OR SIMMILAR - altering when you change the max vid and hit apply. usually the stock vid in rm clock matches the selected v-core in bios. meaning you often have anther .05v-.15v you can boost in rmclock). once you know the values for maximal VID and FID move to minimal. set the min VID to match max for now and experiment to find out the minimal fid starting with the same as max and movin down 1 at a time - set the PST performance to minimal. eg x2 be's can drop to 4x, non be's to 5x - dunno about phenoms.
Once you know the desired max FID, max VID and min FID, turn off pc and reboot. make sure your settings have saved and applied correctly and set the PST to maximal again
reboot and set your oc
when in windows fire up prime or occt and lock into the PST minimal. you should now slowly reduce the v-core untill yyou find it bcomes unstable - of you reach the lowest VID. finishing this run sandras power efficiency tests a few times, even burn overnight. if it crashes at any point you need to either make a custom setting for that specific fid (if able to tell) or raise the min vid by a few notches to achieve the same.
if you find you get random hangs while loading to desktop usually just after rmclock loads and you see the gear icon is 1/2 red - same thing. bump u the min vid another notch. once its at a good point thats it. you should never noice it again.
http://img187.imageshack.us/img187/9199/scalets5.jpg
shows a few of the possible ways you can find your chip behaves. red is cpu min volts for stability. black is the C&Q voltage steps. you have voltage on the y axis, and frequency on the x. in arbitary units.
1) chip scales very well with volts to the last second. you can gain a lot more power saving by tweaking each of the FID/VID pairings to avoid the large "overvoltage"
2) chip scales badly to begin but scaling improves - you need to tweak up the lower end results OR boost the min VID(at the cost of efficiency)
3) chip scales better at low end than high end - you need to tweak up the min VID a LOT or customise the upper VID/FID pairings.
4) Chip exhibits linear scaling - theres a chance of unpredictable instability at certain values of htt due to the stable line crossing the stepping of c&q. a minor boost to min AND max vid should cure. (eg at 7x multi cpu stable at 1.2v for 1500mhz but unstable at 1505 raising from 220fsb to 221 will make this fid unstable while others may well remain stable. eg 9x stable at 1.25v upto 2000mhz (=222mhz htt)

the best way to work out what sort of scaling you do have is to record the vid/fid thats running during a sandra efficiency test for each level. then pick the mid point, lower quarter and upper quarter values set the min fid to match. select PST min then do a min vid hunt using price/occt/etc once you have all 5 points (min, 1/4 1/2 3/4 max) you can work out the curve and where it is worth spending time customising.

NB the easiest version to get started with is 1.5 - this does NOT support customising at each level however.
the more recent versions allow this but are less simple to start with.

[swaaye]

RMClock doesn't work with Vista 64 though. And CrystalCPU doesn't work with Phenom 2. I should've mentioned that I'm working with a Phenom 2. Oops.

[swaaye]

Yes it works just fine on my 940 BE and Foxconn 790GX board. When you change the HTT from 200 to anything else, this is when CnQ gets borked.

HTT changes on my Gigabyte 780G board don't seem to screw up CnQ. Multiplier changes do though.