Win10 BSOD when connecting to mouse on Win10 host running https://github.com/dorssel/usbipd-win

[paulpv]

I am trying a mix of your https://github.com/vadimgrn/usbip-win2/releases/download/v.0.9.3.0/usbip-win2-0.9.3.0-Debug.exe usbip client talking to https://github.com/dorssel/usbipd-win's usbipd host.

On the host I bind the mouse and start the daemon:

C:\Program Files\usbipd-win>usbipd list
Connected:
BUSID  VID:PID    DEVICE                                                        STATE
8-2    1b1c:1b8b  USB Input Device                                              Not shared

C:\Program Files\usbipd-win>usbipd bind -b 8-2

C:\Program Files\usbipd-win>usbipd server
....

On the client I list and attach:

C:\Program Files\usbip-win2>usbip.exe list -r 10.0.0.11
Exportable USB devices
======================
 - 10.0.0.11
        8-2: Corsair : unknown product (1b1c:1b8b)
           : USB\VID_1B1C&PID_1B8B\1602D03FAF7A04C55F40C0F0F5001C06
           : (Defined at Interface level) (00/00/00)
           :  0 - Human Interface Device/Boot Interface Subclass/Mouse (03/01/02)
           :  1 - (Defined at Interface level) (00/00/00)

C:\Program Files\usbip-win2>usbip.exe attach -r 10.0.0.11 -b 8-2

The connection is established, but soon after the client PC BSODs in usbip2_vhci.sys

Interestingly, after reproing this a few times, my usbipd.exe binary is now a 0 byte file! I checked Windows Defender and nothing has been reported as being quarantined.

I then tried to uninstall and reinstall usbipd-win2 and now it bluescreens during every uninstall attempt. :/

FWIW, The client PC that is BSODing also has cezanne's usbip client and host configured, so perhaps it is some conflict between the two apps?

[paulpv]

I followed @vadimgrn 's instructions at https://github.com/vadimgrn/usbip-win2/issues/11#issuecomment-1181589639 and here is the log. BSOD_usbip2_vhci.txt Hope it is good enough.

[paulpv]

Duh, I now also see the comments in the readme.md (RTFM) about how to collect logs. Let me know if the above logs are OK; if not I will get a better one.

[vadimgrn]

You should make a log as described in README.md I've reproduced a BSOD.

[vadimgrn]

Fixed, works. It could be considered as the issue of usbipd because genuine Linux server behaves differently. The workaround has applied.

usbip-win2-0.9.3.1.zip

[vadimgrn]

Run as Administrator these commands to remove the driver manually

pnputil /remove-device /deviceid USBIP\root /subtree
FOR /F %P IN ('findstr /m "CatalogFile=usbip2_vhci.cat" C:\Windows\INF\oem*.inf') DO pnputil.exe /delete-driver %~nxP /uninstall

After that remove folder "C:\Program Files\usbip-win2\" and install the new build as usual.

[paulpv]

Thanks @vadimgrn Looking in to this today....

[paulpv]

@vadimgrn Confirmed works! Thanks!

[vadimgrn]

Fixed