Quote:
Originally Posted by g__day
Guylain,
I notice if i leave BackyardEOS active - with the camera connected somewhere in a 24 hour windows the CPU utilisation under Windows7 Ultimate 64bit - goes to nearly 98%, with System Interrupts - Deferred Procedure Calls and Interrupt Servic Routines being the culprit.
BackyardEOS is the only new software I have added to the Astrolab's main computer this month. When I close BackyardEOS CPU utilisation immediately goes back down below 20% on both cores.
The problem doesn't manifest immediately - sometimes it takes 6 - 16 hours - but this PC is on 7 * 24 and would normally have maybe 16 programs open and dormant - and only use 12% CPU on system tasks and 8% or less on apps. Seeing over 85% system CPU usage when every program bar BackyardEOS is the only thing active is a worry.
From my understanding of microsoft knowlegde bases - such a high System Interrupt allocation is put down to Windows searching and not finding the correct hardware driver.
I'm about to download 2.5GB of tools - run The Windowshttp://images.intellitxt.com/ast/adT...lass_10x10.gif Performance Tools (WPT) Kit http://www.msfn.org/board/topic/1402...dpc-interrupt/
utility and get more information. It would be useful if you can share if there is anything else I should check. Does the Canon driver possibly not register with Windows correctly (unless BackyardEOS is first run as administrator)? |
Ummm... I'm not doing much when the application is idling... but I do check for updated weather information every 30 seconds and I'm wondering if maybe it could be related to the TEMPerHUM reading if none is available. Can you try setting the weather provider to "YAHOO" and _not_ configure the WOEID. This configuration should bypass reading the usb TEMPerHUM device. If this is the culprit we should know quickly.
Keep me posted, I'll run a few test here too.
Guylain