Quote Originally Posted by justapost View Post
Then i tried "i2cdetect 0" which did not show the clock generator chip at 0x69 now with the k8. I was curious if i can dump the chip and tan "i2cdump 0 0x69". I got only XX's as response. I tried "i2cdetect 0" again and now even the chip at 0x2e was gone. I thought, k the smbus interface does no longer work coreect so i tried to reboot. Since then the borad stucks at C1 no mather what cpu i put in.

Like I said in other post, the app can cause the system to go haywire. Was that first time you tried to get the dump?
That is really odd. I'd expect at least AMD Power Monitor and CBId to read from the core's msr registers.
This is what I mentioned a few days back. On different boots, different reads. Some apps get them from the same registers though
I've seen their debug dumps, you can ask VVJ.
Can it be that there are two ways to bind a task to an core. One uses the msr registers numbering and another one uses windows internal numbering (whom seems to change during reboots).
AOD, CPUZ, CBID, AMDPM, CCPUID label cores differently. Sometimes one core is another in the other app, thats what I said hindered me trying to oc individual cores. Each time you reboot, core arrangement might very well be different

For me, I change it until AMD PWM and CCPUID read similar. Thats worked fine so far...

ATM, my highest stable is 1.38v 3000/3000/2700/2800 with that method.