- #USBHUB SYS BLUE SCREEN WINDOWS 7 INSTALL#
- #USBHUB SYS BLUE SCREEN WINDOWS 7 SERIAL#
- #USBHUB SYS BLUE SCREEN WINDOWS 7 DRIVER#
- #USBHUB SYS BLUE SCREEN WINDOWS 7 CODE#
- #USBHUB SYS BLUE SCREEN WINDOWS 7 PC#
I cannot run Windows 7 in any of the boot modes - Safe Mode, Safe Mode with command prompt, Low-resolution video, Last Known Good Configuration, Disable Driver Signature Enforcement, Debugging Mode etc. My guess is that the driver installed with this hard drive corrupted something. Everything worked fine until I rebooted (from sleep mode) this morning. When I returned yesterday, one of the first things I did was plug in a USB hard drive a friend had lent me.
#USBHUB SYS BLUE SCREEN WINDOWS 7 PC#
I have been out of my apartment for three weeks so the PC has not been used in that time.Regardless, I keep my PC fairly up to date
#USBHUB SYS BLUE SCREEN WINDOWS 7 INSTALL#
I do not have automatic updates running - I install them manually as the forced reboots annoy me.My system had been working fine for months but the following may be useful to know: I'm hoping someone here can help me fix it. And it happens in Win 7 using the same Win XP driver that worked in XP.Ĭould this be a data rate issue having three devices using virtual COM ports (2 usbser and 1 ftdi)? Why does this happen only in Win7? And what can I do? I'm really running out of ideas here. I used the Windows XP version because until now the error didn't happen in Windows XP but only in Windows 7. With all of these versions, the blue screen happens. I also switched to different usbser.sys versions: It seems to never happen when only one device is connected and it seems to happen quicker when there is an additional third (different) sensor device attached (that is also having a virtual COM port but that one uses FTDI drivers). I don't know what to think about the timeouts, as they are in the whole log, not only where the crash happens. I pasted the last lines before the crash below the posting. We also had portmon (Sysinternals) running but that also didn't give a hint, what went wrong. It happens on two different PCs but both are running Win7 SP1 32bit. Sometimes it happens after two minutes of continuous data transfer, sometimes it may last half an hour until it happens. Unfortunately we are unable to narrow down when this happens. USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
USBPORT!USBPORT_Core_iCompleteDoneTransfer+0圆e0 Memory dump analysis with WinDbg always shows the same call stack: Quite randomly we observe blue screens in usbser.sys. The device is a sensor that is creating new data as soon as the buffer has been emptied completely.
Using the ReadFile function we continuously poll data from the Microchip device.
#USBHUB SYS BLUE SCREEN WINDOWS 7 CODE#
It is C++ code compiled with MS VC10 SP1 compiler. Our PC application running on Windows 7 SP1 32bit uses standard WinAPI calls (CreateFile, ReadFile) to access the virtual COM ports.
#USBHUB SYS BLUE SCREEN WINDOWS 7 SERIAL#
We have two custom (basically identical) USB CDC devices using a PIC32MX575F 512L chip that show up as virtual serial devices in device manager. I read lots of topics related to usbser.sys but I'm not getting much wiser
0 kommentar(er)
