03-05-2010, 06:17 PM
I have m/b ASUS A7V600 and 5400 rpm 80x80 mm CPU fan. See value Fan4 163 rpm, real this sensors use EVERESRT I see real fan rpm - 5233. This calculation error.
Error read fan speed on m/b ASUS A7V600
|
03-05-2010, 06:17 PM
I have m/b ASUS A7V600 and 5400 rpm 80x80 mm CPU fan. See value Fan4 163 rpm, real this sensors use EVERESRT I see real fan rpm - 5233. This calculation error.
03-05-2010, 07:14 PM
Thanks for your report.
Please attach the Debug File from HWiNFO32 too. Then I can fix it. VictorVG Wrote:I have m/b ASUS A7V600 and 5400 rpm 80x80 mm CPU fan. See value Fan4 163 rpm, real this sensors use EVERESRT I see real fan rpm - 5233. This calculation error.
03-05-2010, 07:55 PM
Ok! I send to full reportn. don't include MAC/IP adress. I I choice anover hardware configuratin, this system don't stable - drivers for ATAPI/VIA RAID can generated kernel panic errror. This errir I see also on MS Windows and FreeBSD UNIX 6.4 - 8.0-STABLE p2 include FreeBSD fork PC-BSD 1.50 - 8.0, SUN Solaris 10/5 - 10/9 operating systems. LINUX kernel I don't like and not testing - I work on DEC service center as servis engeneer on DEC Alpha AXP systems.
03-05-2010, 08:18 PM
Sorry, what full report? I need the Debug File when running HWiNFO32 in Debug Mode. You can find instuctions how to do this in this forum.
VictorVG Wrote:Ok! I send to full reportn. don't include MAC/IP adress.
03-05-2010, 08:36 PM
Attached on previonis post. Sorry on delay - my users send me many moderators qestions - I is moderator on some resource, and personal time is zero.
![]()
03-05-2010, 09:10 PM
Please try the following build:
http://www.hwinfo.sk/beta/hw32_343_625.zip and let me know how it works. VictorVG Wrote:Attached on previonis post. Sorry on delay - my users send me many moderators qestions - I is moderator on some resource, and personal time is zero.
03-05-2010, 09:48 PM
Sorry, not stable read. I have hardware error? I uses DC cooler Titan TFD-8025TH12X. Standard work speed 5400 rpm. BIOS/Lavalys EVEREST read sensor on this fan stable, but HWiNFO32 read this sensor periodically?
03-05-2010, 11:39 PM
Are you running another sensor monitoring application in the background too? If yes, could you try to run only HWiNFO32?
03-06-2010, 12:21 AM
No. I know this effect, and running only one monitoring software at every time.
03-06-2010, 01:03 AM
I added new report, driver list XMl (source is Pserv.CPL 2.7) and old System log - disk error - I recovery controller PCB on this disk WDC2500 - disk periodical switching to "IDE Master" mode and call collision to WDC400 HDD on some IDE bus if jamper's settings choice on "Cable select" mode. I idon't know, but if hwinfo32 driver can't read SMBus data?
03-06-2010, 08:17 PM
Please try this build:
http://www.hwinfo.sk/beta/hw32_343_628.zip and let me know if the fan reading is stable and ok.
03-08-2010, 08:58 PM
Test report:
1) clean run only beta 2.43.628. Sensor CPU fan not read; 2) run Everes, read sensors, make log, unload, run HWiNFO32 2.43.628 beta - CPU fan sensor detected, but periodicaly. I check this fan - is hardware defect ??? Reports include debug data attached
03-08-2010, 09:10 PM
Can you please make and attach a Debug File of the Clean Run (when HWiNFO32 doesn't find the CPU fan)?
It is possible that the CPU fan in not configured properly after boot.
03-08-2010, 11:03 PM
I think the problems is as I said - the fans are not properly configured by default.
Please try this build and let me know: http://www.hwinfo.sk/beta/hw32_343_632.zip
03-09-2010, 01:23 AM
Beta 632 work Ok! Thanks!
Added: Hardware defect found - this fan periodically not sanded signal on speed sensor, and BIOS can't read it. I lake replace this fan than choice free time. ![]() Aditional notes: Chip ITE IT8712F, rev. G have only free fan sensor. I found base hardware specification on this chip family on to vendor suite <!-- m --><a class="postlink" href="http://www.ite.com.tw/EN/products_more.aspx?CategoryID=3&ID=5,66">http://www.ite.com.tw/EN/products_more. ... =3&ID=5,66</a><!-- m -->. Is is information data. Thanks for bug fix! |
« Next Oldest | Next Newest »
|