Windows 7 Pro x64 NUT 2.6.5-4 APC RS 1200 (BR1200) and also RS 500 (BR500) Two PC's which are routinely put to sleep is giving usbhid-ups headaches. From the Event log... usbhid-ups - libusb_get_interrupt: libusb0-dll:err [submit_async] submitting request failed, win error: The system cannot find the file specified. Above is at the time of system sleep. The rest below happens when the system is woke back up. I collected the files in the programdata WER folder. It takes restarting the NUT service twice; upsd is 'unable to stop' on the first try. upsd - Data for UPS [ups] is stale - check driver. --- upsmon - Poll UPS [ups at localhost] failed - Write error: Unknown error. --- Faulting application name: usbhid-ups.exe, version: 0.0.0.0, time stamp: 0x50ae4032 Faulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeaf722 Exception code: 0xc0000005 Fault offset: 0x000101d5 Faulting process id: 0x32c Faulting application start time: 0x01cdf4473bcae202 Faulting application path: C:\Program Files (x86)\NUT\bin\usbhid-ups.exe Faulting module path: C:\Windows\syswow64\msvcrt.dll Report Id: 81638a30-60cb-11e2-90d9-001fd0a249ba --- Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: usbhid-ups.exe P2: 0.0.0.0 P3: 50ae4032 P4: msvcrt.dll P5: 7.0.7601.17744 P6: 4eeaf722 P7: c0000005 P8: 000101d5 P9: P10: Attached files: C:\Windows\Temp\WERC718.tmp.appcompat.txt C:\Windows\Temp\WERCC47.tmp.WERInternalMetadata.xml C:\Windows\Temp\WERCCC5.tmp.hdmp C:\Windows\Temp\WERCE4C.tmp.mdmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_usbhid-ups.exe_a7c32d8e6d503378bf6dadb5b28e547f78d77d1c_cab_10a8ce78 Analysis symbol: Rechecking for solution: 0 Report Id: 81638a30-60cb-11e2-90d9-001fd0a249ba Report Status: 6 --- upsd - User upsmon at 127.0.0.1 logged into UPS [ups]. --- upsmon - Poll UPS [ups at localhost] failed - Data stale. --- upsd - Send ping to UPS [ups] failed: No error [The pipe is being closed. ]. --- upsmon - Poll UPS [ups at localhost] failed - Data stale. (EVERY 5 seconds from then on!)
Kris Jordan wrote, On 1/20/2013 3:47 PM:> Windows 7 Pro x64 > NUT 2.6.5-4 > APC RS 1200 (BR1200) and also RS 500 (BR500) > > Two PC's which are routinely put to sleep is giving usbhid-ups > headaches. From the Event log...I've done further tests... It would appear that only APC UPS's cause the driver to crash on system wake. I also tested a APC ES 725 and got the same crash. An Eaton 3S 550, despite still getting the libusb_get_interrupt error, does not crash usbhid-ups and reestablishes communications fine. I downgrade to 2.6.5-3, but the usbhid-ups driver crash persisted. I made sure to clean all drivers off (pnputil -e, etc) before I downgraded. I will attempt to get driver debug output between the ES and the 3S. My current workaround is an event based task that restarts the nut service when the system wakes. Feature idea, have the nut master service restart crashed sub-processes (driver, upsmon, upsd). You would also want to limit how often this can happen in case a process will simply not start for some reason.