|
|
Speedfan442b4Capture.JPG (30,858 bytes) |
|
|
Speedfan442b4wherePause.PNG (50,907 bytes) |
|
|
|
|
|
|
|
|
I have monitored the clipping behaviour further. It doe not happen always, but maybe 2/3 of the time. When it happens, the Speedfan window first opens in regular size, then the Speedfan startup continues for a while. At one point there seems to be a long wait, maybe 10-15 seconds, after which the window gets clipped and Speedfan then continues its startup. From Speedfan's console: Scanning ISA BUS at $0680... Found Intel QST 2.x -----> 15 sec pause and window clipping happening is here <----- Found ST9500420AS on AdvSMART Found Intel(R) Core(TM) i5 CPU 660 @ 3.33GHz (I attached a screenshot, where I have indicated the place where it happens.) I have attached debug.nfo files for both a normal successful startup and for a failed clipped startup. When looking those files, the failed startup takes about 50 secs, failed the successful takes 30 secs. It seems to me that there is a USB related pause of 7-8 secs mentioned in two places in the failed startup log: 30.10.2010 12:22:44 - Server Connect took 19 ms to execute 30.10.2010 12:22:52 - Find USB Controllers took 7421 ms to execute 30.10.2010 12:22:52 - DeviceID=PCI\VEN_8086&DEV_3B3C&SUBSYS_474A8086&REV_06\3&33 30.10.2010 12:22:53 - Name=Generic USB Hub 30.10.2010 12:22:53 - USB Drive Search took 8920 ms to execute 30.10.2010 12:22:53 - Find 1394 Controllers took 31 ms to execute With the failed startup, there is an 8 sec wait right at the start: 30.10.2010 12:22:13 - CPU#0.MSR[$1B]=00000000FEE00900 30.10.2010 12:22:13 - CPU#1.MSR[$1B]=00000000FEE00800 30.10.2010 12:22:14 - CPU#2.MSR[$1B]=00000000FEE00800 30.10.2010 12:22:14 - CPU#3.MSR[$1B]=00000000FEE00800 30.10.2010 12:22:14 - CollectCPUDataInternal.02 30.10.2010 12:22:14 - CollectCPUDataInternal.03 30.10.2010 12:22:14 - CollectCPUDataInternal.04 30.10.2010 12:22:14 - CollectCPUDataInternal.05 30.10.2010 12:22:14 - CollectCPUDataInternal.06 30.10.2010 12:22:14 - CollectCPUDataInternal.07 30.10.2010 12:22:14 - CollectCPUDataInternal.08 30.10.2010 12:22:14 - CollectCPUDataInternal.09 30.10.2010 12:22:14 - CollectCPUDataInternal.10 30.10.2010 12:22:14 - CollectCPUDataInternal.11 30.10.2010 12:22:22 - SpeedFan version : SpeedFan 4.42 beta 4 30.10.2010 12:22:22 - Command line : "C:\Program Files (x86)\SpeedFan\speedfan.e 30.10.2010 12:22:22 - FORMCREATE : before icon support Additionally, neither with a successful nor a failed startup there is any initial fan ramp-up to 100%, like there has usually been. |
|
|
My guess is that there is something that changes the video resolution. SpeedFan sometimes finds the resolution properly set and sometimes it doesn't. You might delay SpeedFan's startup. When you start a software using a different user, you should make sure that the software will access the same files. |
|
|
> My guess is that there is something that changes the video resolution. Speedfan window gets clipped from the same position independent of the window's location on the screen. I initially thought, too, that it might be related to screen size detection, but that would then cause the Speedfan window getting clipped differently depending on the window's position on the desktop, wouldn't it? It seems to be getting clipped always from the same point in Speedfan window independent of the window position at desktop. I might try delaying the start somehow. but it is a bit difficult as I have to start Speedfan as a task in Task scheduler. Or have you figured out any other good way to start Speedfan in an Win7 x64 system? (without running as administrator it doesn't detect any fans in x64 systems with QST, and that "run as admin" seems to only work through a task.) |
- Anonymous
