CBID and CPUZ report different vcore

[nebula]

Just came across CBID after using CPUZ for quite some time, I thought hey since it's Athlon only why not. Well, I just put together a new system (see sig) and they both report my vcore differently, very differently.

CPUZ ? 1.424
CBID ? 1.124

I got the impression that CBID was more "specialized" for Athlon only so I thought it should be more correct than anything. I didn't check what the BIOS was reading but the Venice is supposed to be 1.4 right?

 

[Duvie]

Well i would think the 1.124 reading would have answered that...default vcore is 1.4v and was 1.5v with the newcastle 130nm chips and was 1.6-1.75v throught the Athlon Xp and Barton days....

Venice is newer and needed to be bios supported for correct recognition by most motherboards, so it is likely the software needs an update as well...cpu_Z has been updated quite regularly....I have 4 version in the last 6 months...

 

[nebula]

Yes I was pretty sure CBID was wrong. I guess it "feels" like the CBID author has some insider info because of some of the stuff in the app so I thought it should be up to date.

 

[Painman]

Do you have the most recent 7.50 CBID release? Seems odd. I get the same VCore reading out of CBID, MBM, CPU-Z and Everest... 1.52 volts.

 

[Xcobra]

dont trust software completely, it reports inaccuratly so a multimeter would be handy here...but oh well

 

[nebula]

Originally posted by: Painman
Do you have the most recent 7.50 CBID release? Seems odd. I get the same VCore reading out of CBID, MBM, CPU-Z and Everest... 1.52 volts.

Yep, just downloaded it from their site. Maybe they have a bug with the sensor/chipset on my particular Asus board.

I emailed the author and just checked, I got this response, "Double click on the VCORE FIELD!"

Not on my main rig right now so have to try it out later.