View Issue Details

IDProjectCategoryView StatusLast Update
0001093SpeedFanOtherpublic2008-04-05 15:32
ReporterSQUALL_LEONHART69R Assigned Toalfredo  
PrioritynormalSeveritycrashReproducibilitysometimes
Status resolvedResolutionno change required 
PlatformWindows NT5.1OSWindows XP SP2 
Summary0001093: Speedfan causes a full system freeze when a 3D application or application that uses hardware acceleration is running
DescriptionRunning a 3D application (tested on oblivion, and unreal tournament GOTYE, and NFSU2 and Firefox running a Flash applet),
Speedfan works as it should at first, but shortly after the cpu usage for speedfan increases till it reaches 80% usage, and if the process is not closed quickly enough, locks up the entire system.

It does not occur during normal usage, only when hardware acceleration is applied to either a game, or a 3D applet in a web page (Flash).

With a flash applet or NFSU2 or UT GOTYE in full screen, it usually just locks up the system.

With Oblivion in fullscreen, the display crashes and becomes pixellated, but audio is heard playing for a few more seconds, this occured across 2 video cards.
With UT in windowed mode, is where i was able to pinpoint that the problem was Speedfan, since in fullscreen mode, 3d apps are given utmost priority over background tasks, it would just freeze, but in windowed mode, after about 15 mins, i found that gameplay would suddenly lag like crazy and raising task manager showed that speedfan was at 80% usage. leaving it like this, the entire system locked up.

I again tested with speedfan closed for about an hour with no lockups or crashes
Steps To Reproduce1. Run speedfan.
2. Startup a fullscreen game that uses hardware intensively.
3. try to put it into windowed mode to monitor speedfans cpu usage.

Results
Speedfan suddenly eats up cpu time and crashes the system.
Additional InformationThe hardware this occurs on is

AthlonXP 3000
Asus A7N8X Deluxe
1GB ram
Geforce 6600GT (Winfast A6600GT TDH)
SoundBlaster Live

Speedfan is set to lower the fan speed to 80% until cpu temps reach 48c then it bumps to 100%
TagsNo tags attached.
Motherboard Model
Video Card ModelGeforce 6600GT (Winfast A6600GT TDH)

Activities

2008-03-09 14:51

 

debug.nfo (84,580 bytes)

alfredo

2008-03-09 15:56

manager   ~0003292

What if you run SpeedFan with /NONVIDIAI2C command line parameter?

SQUALL_LEONHART69R

2008-03-09 17:00

reporter   ~0003295

i shall try that now, though i didn't have trouble with the nvidiai2c in 4.33

alfredo

2008-03-09 17:34

manager   ~0003297

ISA bus is a different thing. Please, send me a SEND REPORT from the latest beta now and add a few notes there.

SQUALL_LEONHART69R

2008-03-09 18:18

reporter   ~0003299

Last edited: 2008-03-09 18:29

will do, do you want me to send the report with or without the /NONVIDIAI2C parameter?


edit
sent one of each.

SQUALL_LEONHART69R

2008-03-09 19:31

reporter   ~0003301

1 question, afredo,

do you know whether the temp2 and temp3 on the ASB100 at Address $2D are sensors on the mainboard, or if they are sensors on RAM modules?

alfredo

2008-03-09 20:18

manager   ~0003302

I don't think that your motherboard has any sensor on RAM modules. On your system there seems to be another tool that is accessing the SMBus and this causes collisions with SpeedFan. While gaming, SpeedFan might have too low a priority and this causes problems. Certainly, the use of the /NONVIDIAI2C command line parameter will help mitigate this. You will lose no useful reading with that switch.
If you still experience problems, try to use /NONVIDIATEMP.

SQUALL_LEONHART69R

2008-03-09 22:01

reporter   ~0003304

Last edited: 2008-03-09 23:05

This could be why the smbus for those 2 plays up


Why do my two LM75's report "-48 degrees"?

SQUALL_LEONHART69R

2008-03-10 02:45

reporter   ~0003309

I've just noticed, that disabling debug mode, stops those multiple error messages at startup.

alfredo

2008-03-10 09:39

manager   ~0003310

If debug mode is disabled, those messages are just hidden.
What are your findings?

SQUALL_LEONHART69R

2008-03-10 09:55

reporter   ~0003311

Last edited: 2008-03-10 09:56

unfortunately, 4.34 was still freezing the system, so i took it back to 4.33, and it also crashed with debug mode on, after disabling debug mode, i haven't seen it lock up since.

im yet to try 4.34, but i will do so in the next few hours.

SQUALL_LEONHART69R

2008-03-10 11:26

reporter   ~0003312

Testing is ongoing, i'll post an update when i have any new info.

alfredo

2008-03-10 11:35

manager   ~0003313

Thank you.

SQUALL_LEONHART69R

2008-03-10 13:08

reporter   ~0003317

Last edited: 2008-03-10 13:10

in both 4.33 and 4.34, with debug enabled, possibly due to the SMbus collisions, maybe not, it appears that a buffer overflow occurs in the speedfan.exe.

The first sympton is a heavy slowdown if in windowed mode, since the cpu is shared more in windowed mode,

When in Fullscreen, your more likely to experience a crash.
So far, i have not been able to reproduce a crash, without running debug mode.
im going to run some tests with nvidiai2c reenabled, in the coming days.

SQUALL_LEONHART69R

2008-04-05 15:05

reporter   ~0003360

Well after heavy testing, it turned out that Speedfan was crashing because the graphics card was failing.

i've put the card in a system that has weaker components (via kt133a) and while it does freeze after heavy play, it is fine for light play.

i guess this system was just pushing the card to hard.

Sorry to trouble you Alfredo

alfredo

2008-04-05 15:31

manager   ~0003361

I'm sorry that you found out that the graphic card was failing. Nice to know that it' wasn't SpeedFan's fault though.

Issue History

Date Modified Username Field Change
2008-03-09 14:51 SQUALL_LEONHART69R New Issue
2008-03-09 14:51 SQUALL_LEONHART69R Status new => assigned
2008-03-09 14:51 SQUALL_LEONHART69R Assigned To => alfredo
2008-03-09 14:51 SQUALL_LEONHART69R File Added: debug.nfo
2008-03-09 14:51 SQUALL_LEONHART69R Video Card Model => Geforce 6600GT (Winfast A6600GT TDH)
2008-03-09 15:56 alfredo Note Added: 0003292
2008-03-09 15:56 alfredo Status assigned => acknowledged
2008-03-09 17:00 SQUALL_LEONHART69R Note Added: 0003295
2008-03-09 17:34 alfredo Note Added: 0003297
2008-03-09 18:18 SQUALL_LEONHART69R Note Added: 0003299
2008-03-09 18:29 SQUALL_LEONHART69R Note Edited: 0003299
2008-03-09 19:31 SQUALL_LEONHART69R Note Added: 0003301
2008-03-09 20:18 alfredo Note Added: 0003302
2008-03-09 22:01 SQUALL_LEONHART69R Note Added: 0003304
2008-03-09 22:17 SQUALL_LEONHART69R Note Edited: 0003304
2008-03-09 22:19 SQUALL_LEONHART69R Note Edited: 0003304
2008-03-09 22:24 SQUALL_LEONHART69R Note Edited: 0003304
2008-03-09 23:05 SQUALL_LEONHART69R Note Edited: 0003304
2008-03-10 02:45 SQUALL_LEONHART69R Note Added: 0003309
2008-03-10 09:39 alfredo Note Added: 0003310
2008-03-10 09:55 SQUALL_LEONHART69R Note Added: 0003311
2008-03-10 09:56 SQUALL_LEONHART69R Note Edited: 0003311
2008-03-10 11:26 SQUALL_LEONHART69R Note Added: 0003312
2008-03-10 11:35 alfredo Note Added: 0003313
2008-03-10 13:08 SQUALL_LEONHART69R Note Added: 0003317
2008-03-10 13:10 SQUALL_LEONHART69R Note Edited: 0003317
2008-04-05 15:05 SQUALL_LEONHART69R Note Added: 0003360
2008-04-05 15:31 alfredo Note Added: 0003361
2008-04-05 15:32 alfredo Status acknowledged => closed
2008-04-05 15:32 alfredo Resolution open => no change required
2008-04-05 15:32 alfredo Status closed => resolved