SuperPI4M time with different NB clock

2350(B1) @1.8G=200x9, NB@1.8G=200x9: 3m47.453s
http://www.oohashi.jp/c-board/file/S..._NB1.8_UnG.png

2350(B1) @1.8G=200x9, NB@1.6G=200x8: 3m47.359s
http://www.oohashi.jp/c-board/file/S..._NB1.6_UnG.png

Almost same time...difference is within fluctuation, I think.
NB@1.6G may be enough for single thread program with dual DDR2-667 access!?
or I suspect my NB multiplier changing method is incomplete
I have no detail info about L3 clock and its behaviour...


3DMark06 score with different HT Link clock

2350(B1)@2.0G, GeForce8800GT@default clock, HT Link@1000MHz=200x5: 9418
http://www.oohashi.jp/c-board/file/3..._HTx5_88GT.png

2350(B1)@2.4G, GeFoce8800GT@default clock, HT Link@962.8MHz=240.7x4: 10926
http://www.oohashi.jp/c-board/file/3..._HTx4_88GT.png

We can observe slight improvement compared to previous results, 9353 and 10796:
http://www.oohashi.jp/c-board/file/3....0G-200x10.png
http://www.oohashi.jp/c-board/file/3....4G-240x10.png


K10 support in MchbarEdit and MemSet
FELIX provided me beta programs, both are working fine

Now we can change NorthBridge & HT Link multiplier with MchbarEdit,
and memory timing with MemSet, on Windows...both 32bit and 64bit
(Good old WPCREDIT has no support for Win x64)
Screenshots are located on my BBS:
http://www.oohashi.jp/c-board/c-boar...ne;no=5239;id=


CineBench10 32bit/64bit

32bit, 2346(BA)@1.8G, NB@1.6G, DDR2-667: 1483, 5731, 3.86 x
http://www.oohashi.jp/c-board/file/C..._NB1.6_333.png

32bit, 2346(BA)@1.8G, NB@1.6G, DDR2-800: 1487, 5730, 3.85 x
http://www.oohashi.jp/c-board/file/C..._NB1.6_400.png

32bit, 2350(B1)@1.8G, NB@1.6G, DDR2-667: 1484, 5743, 3.87 x
http://www.oohashi.jp/c-board/file/C..._NB1.6_333.png

32bit, 2350(B1)@1.8G, NB@1.6G, DDR2-800: 1493, 5736, 3.84 x
http://www.oohashi.jp/c-board/file/C..._NB1.6_400.png

32bit, 2350(B1)@2.4G, DDR2-640: 1973, 7654, 3.88 x
http://www.oohashi.jp/c-board/file/C..._NB1.8_320.png

32bit, 2350(B1)@2.4G, DDR2-800: 1977, 7672, 3.88 x
http://www.oohashi.jp/c-board/file/C..._NB1.8_400.png

64bit, 2346(BA)@1.8G, NB@1.6G, DDR2-667: 1793, 7315, 4.08 x
http://www.oohashi.jp/c-board/file/C..._NB1.6_333.png

64bit, 2350(B1)@1.8G, NB@1.6G, DDR2-667: 1789, 7327, 4.09 x
http://www.oohashi.jp/c-board/file/C..._NB1.6_333.png

64bit, 2350(B1)@2.4G, DDR2-800: 2402, 9642, 4.01 x
http://www.oohashi.jp/c-board/file/C....4_x10_400.png

64bit, 2350(B1)@2.3G=230x10, DDR2-768: 2279, 9191, 4.03 x
http://www.oohashi.jp/c-board/file/C....3_x10_384.png

64bit, 2350(B1)@2.3G=242x9.5,DDR2-808: 2306, 9239, 4.01 x
http://www.oohashi.jp/c-board/file/C...3_x9.5_404.png

Summary from above:
* B1 and BA show almost same performance.
* DDR2-667 or 800 makes almost no difference.
* 32bit -> 64bit score gain is about 20%.
* K10 has no performance degradetion at half(*.5) multiplier.

BTW, Franck provides me CPU-Z latest beta
Now we can see K10 VID on CPU-Z(for example, in the 64bit, 2346(BA)@1.8G case above),
and also can choose a clock showing core#


I intend to test a rendering software, Shade...familiar in Japan,
and then, I'll try voltage modification