View Issue Details

IDProjectCategoryView StatusLast Update
0000079SpeedFanOtherpublic2004-09-14 23:23
ReporterBelgarius Assigned Toalfredo  
Status resolvedResolutionopen 
PlatformPCOSWindowsOS VersionXP Pro, SP2
Product Version4.15 
Summary0000079: After a time, Speedfan causes full load to one virtual CPU, and runs fans full tilt as a result
DescriptionAfter Speedfan has ran for a time, it will cause CPU1 to hit 100% and stay there until shut down and restarted. I am also getting an error message in the screen, however, I am not able to see the full message. SMBus msg: Unsuccessful SELB $0
(I am unable to see the remainder of the message, as it is outside the window)
Steps To ReproduceStart Speedfan, and let it run for a time - happens every time...
Additional InformationAbit IC7, 2.8C Northwood @ 3.2 (233FSB) 1G Corsair PC3700 TwinX DDR466. Also running MBM5 concurrently...
TagsNo tags attached.
Motherboard Model
Video Card ModelGeForce FX5600, 256M



2004-09-14 22:56

manager   ~0000301

I guess some other software is accessing your video card's hardware monitoring sensors. You might run SpeedFan with the following command line switch:


Does it fix your issue?
You might try without MBM5 too.


2004-09-14 23:16

reporter   ~0000302

I hadn't thought of that, now that you mention it, the error does indicate $4C, which is where the MAX6648 is located. While I can't think of any software that I would have running that would access these sensors, the problem DID occur with upgrading to 4.15 from 4.09, which didn't see my video card at all. I've ran without MBM5 loaded, and the same problem occurs, so my bet is that it does have something to do with video sensors. It was nice to see those temps listed, and use the core temp to help speed up the radiator fans if needed. Oh, well ;-)


2004-09-14 23:23

manager   ~0000303

Unfortunately, nVidia seems not to care that much about their users. nVidia never answered any email of mine. The code I wrote to access nVidia video cards was the result of one year of tests and of some money spent in nVidia hardware. There must be some kind of software/driver that interferes with SpeedFan. Before coding some workaround (if any), I'm trying to figure out how many users are experiencing this issue.
It looks like they are not that many.
We'll see.
In the meantime, I will close this issue assuming /NONVIDIAI2C fixed it.

Issue History

Date Modified Username Field Change
2004-09-14 21:50 Belgarius New Issue
2004-09-14 21:50 Belgarius Video Card Model => GeForce FX5600, 256M
2004-09-14 22:56 alfredo Note Added: 0000301
2004-09-14 22:56 alfredo Status assigned => acknowledged
2004-09-14 23:16 Belgarius Note Added: 0000302
2004-09-14 23:23 alfredo Note Added: 0000303
2004-09-14 23:23 alfredo Status acknowledged => resolved