Works fine on the Asus USB Boost driver paired with NEC controller, its an issue with this older generic driver as it works under 10 UASP just fine. do you know of a usb to sata cable that doesn't house an ASM chipset that i can try? I'm actually not 100% sure if this is a 1051 tbh, the 55AA device id corresponds to 1051, 1053, 1151 and 1153E, the cable in question is Startech USB312SAT3CB Edit, its a 1351, Startech aren't too bright and didn't update the device info block so it reports as a 1051. 1051 vs 1351 list a different usb version, 3.0 vs 3.1. My guess is the win8 driver implements scatter gather and doesn't provide a fallback to not using it when issues are encountered. Edit I'm going to pick up a Sabrent EC-SS31,
Turns out it has nothing to do with the adapter, its a compatibiilty issue with the NT6.2 XHCI and uPD720200 with firmware 3034 that doesn't occur with the uPD720201 or uPD720202 and likely not with uPD720200a FW 4021
Final update just released: - Changed patching style, fewer code changes. - Now only signed with SHA-2 (previous release was also signed with publicly available SHA-1 signtool that will eventually be used to sign malware and have its certificate revoked). - Added vendor tags to device name. Example: USB xHCI Compliant Host Controller (Intel) - Dropped Vista support.
This is wonderful. My only wish is that the Win8/10 Bluetooth stack could be so easily transported. The Win7 one is garbage.
Has someone tried using this drivers with Asrock B550 motherboard & Ryzen 3000 series CPU? As per post from CanonKing on Winraid, Asrock motherboards give BSOD with his drivers. I have Asrock B550 & Ryzen 5 3600 on my system and not able to use USB ports in Windows 7. Any help would be appreciated.
You could try them yourself. Get a copy of Macrium Reflect (they have a free edition) and make an image of your boot drive, and restore media. Be sure and verify the image. That way if they BSOD or Windows won't boot, you can restore your existing, working operating system. I have done this many times when trying "experimental" drivers. Disclaimer: make sure you have a full image of your Windows drive before you do anything, and that it can be properly restored, otherwise you could be left with a system that won’t boot.
Strange, I can't use DISM to integrate into Windows 7 Pro unless I use /forceunsigned (on x64), however x86 works fine! I'm doing the integration on Windows 10 LTSC not that it should matter, it sees each of the signed files as valid ... dism /Add-Driver /Image:.\tmp /Driver:.\driver64 /forceunsigned Update: It still works when installing Windows 7 x64 from a flash drive, but once the system is installed there's no mouse or keyboard. F8 and disable signature enforcement works of course, but why would the drivers not be signed in the first place ...