Speedfan help

[Ivan]

Anyone knows why speedfan util doesnt show my harddisks..

Config
Asus Striker Extreme (Nvidia 680i + huge load of fan controllers and temp sensors)
6GB memory (already got 4 GB extra, vista was slow on 2GB)
Vista 64 bit
Intel Core2 Quad Q6700

[*]Speedfan doesnt show ANY harddisks and there's a lot of errors in the speedfan startup text.

Code: Select all

ERROR collecting CPU Usage : 1 (Unable to locate the "Processor" performance object)
Loads of SMBus 'BUSY' errors


[*]I get only one fan sensor (while there are a lot more connected)
[*]DIMM info is a mess... should display 2x1GB and 2x 2GB instead of the crap that is in the current output


Anyone got a clue? or should i use the latest beta instead

[NickN]

The error you are showing seems in line with shutting down performance counters

If you did shut them down using exctrlst.exe, re-enter the exctrlst.exe tool, scroll down and place a CHECk in

PerfProc
PerfOS

close the tool.. reboot.. the procesor error should clear

as for not reading sensors... I can say because I do not use any nvidia MB products right now.. perhaps the newer version of SF may recognize the board.. they usually have a list of boards or chips the software will read at the SF website

[Ivan]

CPU stats were fixed by running in admin mode

But still no fan RPMs and harddisks

[NickN]

Yes, Speedfan must have admin rights.. I assumed it was being run that way so that would account for the access issue.

As for the rest.. I assume there are no registers showing in the software that are disabled from display?








Speedfan is not a install and go software, never has been and it can be a bit tricky to get set up.. there can be a bit of an involved process. If it is not reading the windbond or other monitor chip on the motherboard then it may need to be updated by the author.

Also, it does not read eveything perfectly.. sometimes you have to set the right offset to calibrate it such as the intel CPU offset for TAT.. which is about 13-15c

[Ivan]

I get all the sensor chips in that list... but the chipset related stuff doesnt work

. There is a lot of code to improve nVidia support

Maybe the next version will work better on a 680i