-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Win10 BSOD when connecting to mouse on Win10 host running https://github.com/dorssel/usbipd-win #15
Comments
I followed @vadimgrn 's instructions at #11 (comment) and here is the log. |
Duh, I now also see the comments in the readme.md (RTFM) about how to collect logs. |
You should make a log as described in README.md |
Fixed, works. It could be considered as the issue of usbipd because genuine Linux server behaves differently. The workaround has applied. |
Run as Administrator these commands to remove the driver manually
After that remove folder "C:\Program Files\usbip-win2" and install the new build as usual. |
Thanks @vadimgrn Looking in to this today.... |
@vadimgrn Confirmed works! Thanks! |
Fixed |
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'susbipd
host.On the host I bind the mouse and start the daemon:
On the client I list and attach:
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?
The text was updated successfully, but these errors were encountered: