Sorry for the long post, but tried to cover all possible bases.
Just assembled a new system and am getting periodic readings on the software--Asus PC Probe--that my CPU fan has stopped for a few seconds. My sys is all new, AMD-approved hardware:
A7V266-E, rev 1004b
mobo: jumper-free and BIOS defaults
newest AVI drivers
Samsung 256M PC2100
Volcano 6Cu HS
Sparkle FSP350 PS
Enlight case with chassis fan
WD 60G HD
Win 98 (all service packs installed)
The Asus PC Probe software is set to install at boot-up. Periodically, and with no apparent pattern (ie, what might be a catalyst), I get a warning that the CPU fan has stopped. Monitor comes on screen and shows 0 RPMs, but just for a few ticks and then resumes normal readings of around 4720; threshold on software is 2200. HS is rated at 4550 /-10%. On software CPU cooling menu I have checked "always" on software cooling.
I've read about the inaccuracy of software reading mobo temps, so have basically attributed erratic CPU fan readings to software. Perhaps not?? When I had the cover off and it perhaps happened once, it was so short that I did not have time to visually check to see if the fan had actually stopped.
The idle/unloaded CPU temp is around 51C with room temps around 20C. I likely would not be concerned, but the other night while the machine was idle for awhile, I wandered into the room and saw the CPU fan montior ticking at 0 (not sure for how long) and when I checked the temps the CPU was at 57C, but then dropped to normal a few minutes later. Should I yank the top off and try to catch if the software is accurately reading? Are these temp/fan variances worth worrying about given the software? Should I make any setting changes to the software or BIOS?
PS. A public thanks to Larry for his how to guides. Been a few years since I assemble a computer and his detailed guides were about the best I could find. Made for a much less stressful assembling process.