Almico's Bug Tracker - ISSUES

0001638: fan contraol just on CPU fan

The board above has an AMD 790GX chipset with an IT8718F chip to control the fans. It does have three fan control connectors. The first one for the CPU is PWM based and recognized in Speedfan as fan 3. Control is possible, but not down to 0rpm (minimum 105rpm).

The other two fan controls don't work (tried all setting under advanced configuration(software controlled, SmartGuardian, ON/OFF) -no reaction.

The controller chip is IT8718F and all three fans are recognized as Pwm1 - 3. Fan connectors 2 + 3 (which I want to control) are just 3-pin connectors.

Do you have any suggestions for me?

0001528: No CPU Fan Speed Control

Fans connected to Sys_Fan 1 (4 pin) and Sys_Fan 2 (3 pin) are controlled at the same time by "Speed01" with no problems.
Fan connected to CPU_FAN 4 pin connector has no fan speed control by "speed02" and "speed03" regulators.

S.M.A.R.T is not accessible for HDD Samsung HD502HJ (ACHI mode) also

0001637: No more fan speeds on Intel DG45ID since 4.41

Since the new version 4.41 (final) speedfan does not detect anymore the Intel QST. This causes that speedfan does not show any fan speeds at all. In version 4.40 (final) speedfan could read them and also detected the Intel QST on startup.

If you need any further info then let me know.

0001636: General Speedfan options question

Can Speedfan assign 2 separate PWM fans to one sensor? For example in my case, CPU_1 and CHA_1 fans, both to the CPU sensor. I will be running Windows 7 on an Asus P7H57D-V Evo motherboard. Any help would be greatly appreciated, as this determines whether or not to buy a second fan for my CPU cooler. Thank you,

Lynn Johnson

0001630: beta 15 swapped the speed controls for sys and cpu fan (Rampage II GEne)

beta 15 swapped the speed controls for chassis and cpu fan (Rampage II GEne)

0001352: No fan detection on Dell Latitude E6400 and other Dells running 64 bit OS

Fans are not detected on Dell Latitude E6400, speed fan is run with admin rights and the Dell option checked.

0001635: Fan speeds incorrect with RC24P resistor

Fan speeds are reported incorrectly when using a cpu cooler (fan) that uses a RC24P resistor.

Example: Zalman CNPS10X Performa

0001634: Program hangs OS at startup

I have SpeedFan 4.40 installed on my 64 bit Windows 7 running on Intel Core i7 Q 720 1.60 GHz (Hyperthreaded Quad Core)

Whenever I start SpeedFan, if the mouse pointer is located over the SpeedFan window, it hangs the whole Operating System and forces me to do a hard boot. If I keep the mouse pointer somewhere, it starts good and works good.

I tried the option of starting SpeedFan as minimized. Even with this, if the mouse pointer stays somewhere in the middle of the screen the Operating Systems hangs.

I can see the below readings on the SpeedFan window until it hangs

Win9x:NO 64Bit:YES GiveIO:NO SpeedFan:YES
I/O properly initialized
Linked ISA BUS at $0290
Scanning ISA BUS at $0290

At times I see one additional reading as well - "SuperIO Chip=IT8512E"

This has stopped me from using SpeedFan for the time being.

0001609: Extend Speedfan to adding another input channel / bus = serial port ie ComX.

This would open up huge possibilites for custom hardware and PIC or Arduino etc based projects. Currently these tools can act as standalone hardware, or some do provide software control within the operating system, but they are not integrated with the built-in mainboard controls.

Extending Speedfan with a ComX bus input would allow Speedfan to display ALL information and control ALL devices. This is especially important for these additional custom devices as they generally exist to overcome shortcoming of the built-in systems

It would also simplify for commercial products as they would no longer have to interface to the o/s via usb + driver + software, just simple logging via serial (and optionaly read settings/commands).

The use of Speedfan to send commands could become complex and require standards and care, or a simple action/event based system could just allow user definition of the text to send. This would hopefully fit in well with the existing Event capability by addition of another "Then" = "Send to ComX".

Thinking "big" - it would be great to allow for several of these devices - which would require several com ports.

Once word gets out - this feature should be quite popular.

0001633: Text in tray hint is turnicated

Text in tray hint is turnicated
See Screenshot

0001632: Wrong temperature reading on Winbond W83791D

Sensors "Temp1" and "Temp2" are OK but sensor "Temp3" always show wrong values.
"Temp3" reports "0C", "1C" or "-128C".

0001631: Wrong Winbond W83627DHG control

When trying to set "PWM 3 Type" to "DC Output" (default is PWM output) PWM type actually not changed but "PWM 2 mode" changed to "Thermal Cruise" (from "Manual PWM Control")

0001627: Several bugs in 4.41 beta 15

Hi Alfredo,
I tested 4.41 beta 15 but it has several new and some older issues.
Tested on Asus P7P55D-E with Windows 7 64 bit:

Several errors at startup for Winbond W83667HG-B
- caused by invalid settings from previous version (4.40)
- no more errors when changed to valid settings

No voltage readings (all 0)

Core temps are around 38 C while CPU is 52
- shouldn't Core temp be higher than CPU?

Unable to set Fan divisors higher than 8
- need 16 to show Sys fan running at 30%

No fan control for CPU and Sys fan
- Using 4 pin CPU fan, 3 pin Sys fan
- PWM modes set to Manual
- version 4.40 controls only Sys fan, not CPU fan
Asus Smartfan/Qfan is able to control both fans (now disabled).

I attached a report file.
If I can help you please let me know.

0001629: Speedfan aborts while starting

Installed Speedfan.exe (V-4.40), installation finished with no errors.
Short after starting Speedfan.exe a message box appears:
"Access violation at address 00000000. Read of address 00000000."
After selecting "OK" the application is active but did not recognise any sensor.

Before that I was using Speedfan.exe (V-4.26). Some data were not reported correctly, so I decided to try V-4.40.
V-4.26 ran without errors though some data were not realistic. CPU temperature was sometimes reported as reasonable 42°C , sometimes as 0°C. Operating an outside fan influenced the value - so I assume this to be CPU temperature indeed.

0001628: Hard crashes, black screen, buzzing looping sound and complete unresponsiveness requires psu shutdown

When opening speedfan, the entire computer crashes when it begins to scan hardware, I get a black screen and some buzzing sound and I can not switch off the computer at all, not even holding down the power button for more than 3 seconds, therefore I have to turn it off from the power supply switch. This happens even after updating the bios, installing latest drivers and using right settings in bios like having S.M.A.R.T enabled.

Other users with same problems;
http://forums.techguy.org/hardware/915474-speedfan-crashes-system.html [^] (similar motherboard)

http://www.overclock.net/amd-general/65101-computer-crashes-when-i-open-speedfan.html [^] (I think DFI, I am in this thread my name is abdidas)

0001513: Speed fan crashes when used in DELL Studio 1555 with DELL Support enabled

Speed fan crashes when used in DELL Studio 1555 with DELL Support enabled.
Used Run With Administrator Privileges.

0001626: Fan Speeds Randomly reverse

I use two fan speed settings to control speeds on my mobo. The "sys" sensor changes speed of both the "sys fan" and "aux2 fan" at the same time (i.e. changing the % value changes 2 fans simultaneously).

The "CPU" speed setting changes the speed of the CPU fan.

Sometimes the speed % values reverse and the CPU speed %value controls the sys fan and the sys fan %value controls the CPU fan.

0001625: same as 0001540 but on a very different system

S.M.A.R.T. short test just hangs at in progress...
smartmontools short and long tests work fine. There are 4 UNC errors, could this be the cause? Otherwise pretty much everything works, the fanspeeds can't be controlled on this system and there is an open temperature sensor connection (both normal). Video is S3 onboard, VIA chipset, P3 1.2GHz.

0001624: Multiple problems

Ok, where to start?... On startup, Speedfan momentarily locks up for about 1 minute when "Scanning nForce2 SMBus at $1C00...", then it comes up fine. However at least 2 temperatures are wrong... the Temp1 on IT8712F-J is too low, around 60 F. The Core temp on AMD K8 is also too low, 52 F at idle. The ACPI temp never changes from 104 F. The GPU reads 32 F (0 C).

It detects 5 fans, yet there are only 2 fan connectors on the motherboard itself.

0001623: Incorrect and non-functioning temperatures. Cannot detect/control any fans.

I'm re-reporting my issue to better describe my problem(s). I'm also uploading a couple reports.

In either Windows XP or Windows 7, my ACPI temp, Temp1, does not update at all. It stays stuck at a certain temperature. Whether it's just come out of standby, has been running for hours, is running a Prime95 torture test, it always seems to stay the same. My HDD temp is the only one that ever updates. As for the the AMD K8 temp, the Core temp, it's stuck at a polar -56F...

Using CPUID HWMonitor, I am able to read the ACPI temperature normally, it updates just fine. The Core temp doesn't exist is HWMonitor.

I am also unable to detect any fans in the laptop. In the config dialog, "Fans", "Voltages", and "Speeds" tabs list nothing whatsoever. In the "advanced" tab, only the temperature offsets can be changed, for the only ones in the list, "HD0, ACPI, and AMD K8."

0001618: CPU temperatures not updating, and one temperature obviously not working

I'm using the latest beta, 4.41. However this happened with 4.40 as well.

In either Windows XP or Windows 7, my ACPI temp, Temp1, does not update at all. It stays stuck at 93F. Whether it's just come out of standby, has been running for hours, is running a Prime95 torture test, it always stays the same. My HDD temp is the only one that ever updates. As for the the AMD K8 temp, the Core temp, it's stuck at a polar -56F...

I'm on an Emachines E627 laptop. It has a AMD TF-20 1.6GHz CPU, 2 gigs of ram, ATI Radeon HD 3200 graphics, an AMD M780G Chipset.

0001400: Fan speeds reset to about 50% every few seconds after speed fan starts

All fan speeds reset to about 50% every few seconds after speed fan starts. Changing the speeds with speed fan only lasts a few seconds. This is different than the system's natural fan speeds. This persists after speed fan exits. The issue also remains after a system standby.

If the system is hibernated speedfan works as expected until the next time speed fan is re-opened.

0001622: No voltage readings available for Fintek F75387

Not sure if this is necessarily an issue, and I know this is not a "supported" motherboard. SpeedFan successfully identifies a Fintek F75387 chip on the motherboard and offers up fan speed and temperature information, but no voltage monitoring seems to be available. We were needing to be able to monitor voltage information for this particular hardware. Only program I've found so far that successfully identifies the four voltage monitoring inputs on this chipset has been HWiNFO32.

0001566: speedfan hans after at the end of detection.

cpu:e8400
MB:abit ip35 pro xe
memory:4 gb ddr2 patriot 800 LLK
VGA:zotac geforce 9800 Gtx+
speedfan 4.40 hangs at the end of detection
tried it with /NOUGURUSCAN it worked but the program doesn't show voltages and cpu fan speed.i know it is obvious that it is because it doesn't read values from UGURU but just wanted to know that will this problem be solved soon or not.
thanks

0001581: W83667HG not found unless CPU-Z or PC Probe II started before Speedfan

Speedfan won't seem to find W83667HG and therefore won't list fan speeds, voltages, or CPU temperature, unless I start CPU-Z or Asus PC Probe II before starting Speedfan. After that everything reports normally.

CPU-Z or PC Probe II won't have to be running at the same time with Speedfan. Only starting and closing either one once makes Speedfan detect W83667HG. CPU core, GPU and HD temperatures are always reported without problems. Attached is Speedfan info before and after running CPU-Z.