News:

Follow BoincTasks on Twitter Facebook        Visit our website here.
BoincTasks cloud login is working again

Main Menu

Lost connection to CPU

Started by jjwhalen, February 08, 2010, 10:48:12 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

jjwhalen

After several weeks running fine I noticed that BoincTasks stopped displaying core temps for one remote host.  Checking the local Tthrottle control panel showed that core temps were blank, & the OSD read 0.  Restarting Tthrottle had no effect, nor did rebooting the machine.  Removing & reinstalling Tthrottle restored normal function.

Tthrottle v1.73, running on Vista SP2 32bit.  The CPU is Intel T5450 Core2 Duo.


fred

Quote from: jjwhalen on February 08, 2010, 10:48:12 AM
After several weeks running fine I noticed that BoincTasks stopped displaying core temps for one remote host.  Checking the local Tthrottle control panel showed that core temps were blank, & the OSD read 0.  Restarting Tthrottle had no effect, nor did rebooting the machine.  Removing & reinstalling Tthrottle restored normal function.

Tthrottle v1.73, running on Vista SP2 32bit.  The CPU is Intel T5450 Core2 Duo.
Hard to tell, what caused that problem. Blank temperatures may suggest a problem with the driver, something that went wrong with the registry, or a firewall thing. But installing did resolve the problem so...
Next time, if this should ever happen again, check the log for the driver entry. Should report the driver version. In that case send me the log and I check it.

jjwhalen

I kind of thought driver myself.  I doubt that firewall is the issue...immediately after install yes, but after running great for awhile, not so much. But just in case, the firewall on my 32bit machine is ZoneAlarm Security Suite v9.1.  (I use Kaspersky on my 64bit platforms.)

If this problem does crop up again I'll capture that log data and send it along.

Best wishes.


jjwhalen

Well, it happened again, with similar circumstances, after running OK for ~2 days.  And again it took uninstall/reinstall to restore normal function.  (Note that the problem occurred while Tthrottle was already running, not on startup.)  Captured log data from the failure mode is as follows:

Quote11 February 2010 - 16:09:19 Error: CreateFile Failed : 5
11 February 2010 - 16:09:19 (L01) ERROR: Driver NOT installed properly
Program version: 1.73 32Bit
Microsoft Windows Vista Ultimate Edition, 32-bit Service Pack 1 (build 6001)
Vista or higher detected

Language: User: 1033 ENU ,System: 1033 ENU

Vendor ID: GenuineIntel
Vendor: INTEL
HighestIntegerValue: 0000000A - Processor Signature: 000006FD
Misc. info: 01020800
Feature Flags1 0000E39D
Feature Flags2 BFEBFBFF

Processor: Intel(R) Core(TM)2 Duo CPU     T5450  @ 1.66GHz               
Processor: Family: 6h, Model: F, Stepping: D
Processor: Type: T5450, Stepping: M0, Cores: 2
Processor: Max Case Temperature: 100.0 °C, Max Power 35.0W
Processor: Speed: 1.66 GHz, Busspeed: 667 MHz
Processor: tSpec: SLA4F, Technology: 65 nm, Cache: 2 MB
Processor: VoltageLow: 1.1 V, VoltageHigh: 1.2 V


BOINC:
boinc.bakerlab.org_rosetta
boinc.bakerlab.org_rosettasymbols
boinc.bio.wzw.tum.de_boincsimap
climateprediction.net
setiathome.berkeley.edu
setiweb.ssl.berkeley.edu_beta
spin.fh-bielefeld.de
www.primegrid.com
www.rechenkraft.net_yoyo
www.worldcommunitygrid.org

You can help by reading www.efmer.eu/boinc/faq.html How can I help!
Select the send EMail button,or copy everything in this logging window and mail it to me!
boinc@efmer.eu. We use this information to improve this product.

11 February 2010 - 16:09:21 , WSAStartup ok
11 February 2010 - 16:09:21 BT: CreateListeningSockets, Creating the list of sockets to listen for ...
11 February 2010 - 16:09:21 BT: CreateListeningSockets, getaddrinfo successful.Enumerating the returned addresses ...
11 February 2010 - 16:09:21 BT: CreateListeningSockets, Processing Address 1 returned by getaddrinfo : [::]:31417
11 February 2010 - 16:09:21 BT: CreateListeningSockets, Created socket with handle = 444
11 February 2010 - 16:09:21 BT: CreateListeningSockets, bind failed. Only one usage of each socket address is normally permitted.
11 February 2010 - 16:09:21 BT: CreateListeningSockets, Processing Address 2 returned by getaddrinfo : 0.0.0.0:31417
11 February 2010 - 16:09:21 BT: CreateListeningSockets, Created socket with handle = 444
11 February 2010 - 16:09:21 BT: CreateListeningSockets, bind failed. Only one usage of each socket address is normally permitted.
11 February 2010 - 16:09:21 BT: CreateListeningSockets, Freed the memory allocated for res by getaddrinfo
11 February 2010 - 16:09:21 BT: Accept, Start listening for BoincTasks

Log data from after the reinstall reads as follows:

Quote11 February 2010 - 19:18:50 Driver installed properly. Driver Version: 1.9

Program version: 1.73 32Bit
Microsoft Windows Vista Ultimate Edition, 32-bit Service Pack 1 (build 6001)
Vista or higher detected

Language: User: 1033 ENU ,System: 1033 ENU

Vendor ID: GenuineIntel
Vendor: INTEL
HighestIntegerValue: 0000000A - Processor Signature: 000006FD
Misc. info: 01020800
Feature Flags1 0000E39D
Feature Flags2 BFEBFBFF

Processor: Intel(R) Core(TM)2 Duo CPU     T5450  @ 1.66GHz               
Processor: Family: 6h, Model: F, Stepping: D
Processor: Type: T5450, Stepping: M0, Cores: 2
Processor: Max Case Temperature: 100.0 °C, Max Power 35.0W
Processor: Speed: 1.66 GHz, Busspeed: 667 MHz
Processor: tSpec: SLA4F, Technology: 65 nm, Cache: 2 MB
Processor: VoltageLow: 1.1 V, VoltageHigh: 1.2 V

Core Temperature: 75 °C, Raw Data: 88190000
881c0000,88190000,88190000,88190000
88190000,88190000,88190000,88190000,01111111
881b0000,88190000,88190000,88190000
88190000,88190000,88190000,88190000,01111111
881b0000,88190000,88190000,88190000
88190000,88190000,88190000,88190000,01111111

BOINC:
boinc.bakerlab.org_rosetta
boinc.bakerlab.org_rosettasymbols
boinc.bio.wzw.tum.de_boincsimap
climateprediction.net
setiathome.berkeley.edu
setiweb.ssl.berkeley.edu_beta
spin.fh-bielefeld.de
www.primegrid.com
www.rechenkraft.net_yoyo
www.worldcommunitygrid.org

You can help by reading www.efmer.eu/boinc/faq.html How can I help!
Select the send EMail button,or copy everything in this logging window and mail it to me!
boinc@efmer.eu. We use this information to improve this product.

11 February 2010 - 19:18:51 BT: Accept, Start listening for BoincTasks

Since you mentioned the Registry, I'm guessing that the user settings (Preferences, Rules etc.) live there?  The settings certainly survive the uninstall.  If you send a list of the Tthrottle registry keys, I can try editing them out.  This wouldn't be my first dance with RegEdit.

Best wishes.


fred

Quote from: jjwhalen on February 12, 2010, 03:29:37 AM
Well, it happened again, with similar circumstances, after running OK for ~2 days.  And again it took uninstall/reinstall to restore normal function.  (Note that the problem occurred while Tthrottle was already running, not on startup.)  Captured log data from the failure mode is as follows:

Since you mentioned the Registry, I'm guessing that the user settings (Preferences, Rules etc.) live there?  The settings certainly survive the uninstall.  If you send a list of the Tthrottle registry keys, I can try editing them out.  This wouldn't be my first dance with RegEdit.

Best wishes.
The driver is controlled by the Windows Installer.
It should load automatically at startup.
Try running the installer tool that's in the program folder. InstallDriver.exe
Click remove driver, exit the program and run it again and hit install driver.
Run this program as administrator both times.

Before you do so check: device manager
Set the option for show hidden devices, so you can see all non PNP drivers.

Non Plug and Play drivers.
CpuTemperature is the one you need.
Check the properties. Should be started as type system.
---------------------------------------------------------
Click Start, click Run, type sigverif, and then click OK.
Click on advanced and show log, cputemperature should be listed.
---------------------------------------------------------
Click Start, click Run, type verifier, OK
Default setting, Select drivers from a list (last one)  and check if cputemperature is in the list.

jjwhalen

Just to be sure I uninstalled/reinstalled Tthrottle on the affected machine. After reinstalling & starting Tthrottle I checked the device manager--cputemperature was not listed in the Non-Plug and Play Drivers.  I ran the InstallDriver tool twice as directed.  The uninstall option read as successful.  The install driver option failed with errorcode 126--ERROR: Driver not installed properly. (LoadDriver Dlg).

But Tthrottle is running, the OSD is correct, and BoincTasks is reading temps from the machine.  What am I missing?  My other machines show the cputemperature driver in device manager, but both are running Tthrottle64.


fred

Quote from: jjwhalen on February 13, 2010, 10:31:26 PM
Just to be sure I uninstalled/reinstalled Tthrottle on the affected machine. After reinstalling & starting Tthrottle I checked the device manager--cputemperature was not listed in the Non-Plug and Play Drivers.  I ran the InstallDriver tool twice as directed.  The uninstall option read as successful.  The install driver option failed with errorcode 126--ERROR: Driver not installed properly. (LoadDriver Dlg).

But Tthrottle is running, the OSD is correct, and BoincTasks is reading temps from the machine.  What am I missing?  My other machines show the cputemperature driver in device manager, but both are running Tthrottle64.

Strange, the 64 bit system is the more complicated one.
Go to C:\Windows\System32\drivers and try deleting the cputemperature.sys, the driver.
Try the remove and install again.

jjwhalen

Quote from: fred on February 13, 2010, 10:46:07 PM
Strange, the 64 bit system is the more complicated one.
Go to C:\Windows\System32\drivers and try deleting the cputemperature.sys, the driver.
Try the remove and install again.

OK, did that: no change in symptoms.

I also ran 'FC /b' on the driver I removed from C:\...System32\drivers\ against the one from the reinstall--identical (i.e., not corrupted) ???  And the fun continues; meanwhile, the PrimeGrid Year of the Tiger challenge is going well :)


fred

Quote from: jjwhalen on February 14, 2010, 10:23:04 PM
Quote from: fred on February 13, 2010, 10:46:07 PM
Strange, the 64 bit system is the more complicated one.
Go to C:\Windows\System32\drivers and try deleting the cputemperature.sys, the driver.
Try the remove and install again.

OK, did that: no change in symptoms.

I also ran 'FC /b' on the driver I removed from C:\...System32\drivers\ against the one from the reinstall--identical (i.e., not corrupted) ???  And the fun continues; meanwhile, the PrimeGrid Year of the Tiger challenge is going well :)
But removing it may alert the virus scanner that something changed, as I suspect a problem there. Or the rights of the driver were not set correctly. A strange problem.
Good luck with the PrimeGrid challenge.

jjwhalen

Quote from: fred on February 14, 2010, 10:27:07 PM
But removing it may alert the virus scanner that something changed, as I suspect a problem there. Or the rights of the driver were not set correctly. A strange problem.

Good hint.  My 32bit system uses ZoneAlarm Pro Security Suite (with Anti-Virus turned off) and NOD32 Anti-Virus.  In ZAP Program Control I set both the Tthrottle .exe & the driver installer/uninstaller .exe as Trusted applications.  In NOD32 I set an exception for the \eFMer\Tthrottle\ path for on-access scanning.  After yet another reinstall, that combination did the trick & the driver is now loading.  Since I just opened a back door wide, I'd appreciate it if you wouldn't package any viruses/trojans/worms with future releases ;)

I should probably switch that machine over to Kaspersky Internet Security like the other 2.  Just haven't gotten around to it yet.

Thanks for the help ;D