So I'm using Speedfan 4.18, monitoring three fan speeds....everything's ok.. Then I installed MBM (last version) because I knew my board supported it, and I wanted the additional temp icons in the tray.

Well as soon as I installed MBM, neither prog would read RPMs below 1350....reading drops to zero. I adjusted the Speedfan settings.....the fan devisor setting. Then both progs read RPMs ok.

It's hard to figure how a Speedfan setting would affect the MBM reading...

Both programs are using the same bus to communicate with the same chip. Running them at the same time can result in all kinds of weird effects. Just like the one you reported.

The fan devisor setting in Speedfan is not just an internal setting in Speedfan. If you change it, Speedfan gives the chip a command to report in a different way.

Well that makes sense.....except I have used the two progs together without seeing any conflict, many times in the past on numerous computers.

The other thing is this....I uninstalled Speedfan, and MBM still would not read low rpms. When I reinstalled Speedfan and changed the fan devisor setting, both programs started reading ok. My brain hurts....

FYI, running the config program of MBM usually cures most "stuck" readings and MBM can also change fan divisors.

This sounds like MBM changed the divisor during the configuration wizard in MBM. I think that You should have powered off the entire computer to make MBM work alone (maybe resetting would have cured it too). All those HW monitoring chips are initialized on cold boot (some even if the computer is reseted).

As Tibors said, the settings aren't program-specific. Uninstalling SpeedFan didn't change any registers in the chip itself, so the divisor was still wrong.

If I run DTemp and MBM at the same time, I loose the ability to monitor SMART temps with MBM; shows 0°C constantly, while DTemp shows the temperatures just fine. The moment I shut down DTemp, MBM readings come back to life.

Cheers,

Jan

I get a conflict between ITE SmartGuardian (works like SpeedFan, comes with my mainboard) and MBM; once I select the diode for MBM to read the CPU temp from, SmartGuardian's and MBM's CPU temp readings fly up to 71C and stick there. It sucks because MBM has a wonderful logging system while SmartGuardian can't log temperature history.

-Ed

I'll reiterate what I've already stated here on countless occasions:

DO NOT run two monitoring apps at the same time. They will "fight" for the same sensors and at best, give you inaccurate readings, and at worst, make your system unstable. Some folks go so far as to not even install multiple monitoring apps, I don't go that far but I always check the startup folder (and where ever else) to make sure only one will be running at any given time.