USB-6008 Loss of communication after running for a couple of days

[wb2nvy]

I have the same problem. I'm using an IBM T43 Laptop with WinXP, and have used 2 different USB hubs to connect a Chroma 61602 power source and Softlog gang programmer, among other things. I found when I leave the laptop idle for an hour or more, I lost comm with the Chroma, & couldn't re-establish w/o rebooting (I didn't try unplugging & replugging the USB). This was very repeatable. The Chroma is driven from the laptop to the hub to an Agilent 82357A USB to GPIB converter, although I had the same problem when driving it through a USB to serial hub, and a serial cable to the Chroma. I extended my laptop System Standby from 1 to 4 hours and had a complete system update done, and the problem persists. I've called upon Chroma to deal with the problem. Now, not using the Chroma, I have a similar problem with the Softlog device, as overnight (idle) comm was lost. The com port (11) showed ok in my device manager, but didn't show at all in MAX. Restarting the laptop re-established comm. HOWEVER during the restart, I got a blue screen with this message "Runtime Error!" Program:....gram Files\National Instruments\Shared\Tagger\tagsrv.exe   This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information." The laptop hung up after this message and didn't finish the restart, so I had to manually shut it down & restart. Is this a clue? I now have the Softlog USB cable plugged into the laptop by itself w/o the hub. By the way, the Softlog has its own power supply.

[JoeFriedchicken]

wb2nvy,

tagsrv.exe is used by the DSC toolkit and shared variables. If you're using either of those in your VIs, then it may be helpful in finding the problem. There is a KnowledgeBase article that discusses how to end orphaned processes started by the Tag Server so you can shut down cleanly in the future:

Tagsrv.exe Error When Shutting Down PC
http://digital.ni.com/public.nsf/allkb/27A007940341705B8625716500723B97?OpenDocument

This should fix your blue screen behavior, and if it doesn't please reply with what you tried and what happened afterward.

Considering that you're not using any NI hardware at this point, I'm not sure how an NI driver would affect the system. Given that the problem persisted after you increased your System Standby limit, it appears your problem is a Windows or ACPI control glitch when entering standby mode.