USB Errors on Ryzen PC (and Intel???)

[NicholeMattera]

While trying to dumping the kernel, and trying to install the custom kernel I kept getting USB errors. The errors were "Can't write to USB" and a IO error that completely broke the app and had to be force closed. I tried different USB cables, ports and ultimately just ended up using it on my Intel based laptop.

AMD USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
PCI\VEN_1022&DEV_145C&SUBSYS_FFFF1849&REV_00

AMD USB 3.10 eXtensible Host Controller - 1.10 (Microsoft)
PCI\VEN_1022&DEV_43B9&SUBSYS_11421B21&REV_02

DxDiag.txt

[LGSilva]

Having the same issue with Windows 10 and Ryzen 5. Works fine on the intel i5 laptop.

[Juli199696]

Got a Ryzen 1700X works perfectly fine. Just installed the driver and works like charm. @windows10

[christopherfowers]

Have a 1700x and having the same problems. @windows10

[Terlouw]

Also have a Ryzen 1700x and having the same problems. @windows10. Cannot write the custom kernel to usb (whereas the stock kernel isn't a problem).

[joetheuseless]

what do we do anyone know a fix?

[joetheuseless]

just tried again on the new build same problem USB errors when dumping custom kernel and the OP won't respond to requests :-p

[NicholeMattera]

I would suggest anyone having the same issue is to at the very least post dxdiag.txt file so they have some information about your system to go on.

1. Press Win+R and type in "dxdiag" without the quotes.
2. Click Ok.
3. Click "Save All Information" to save a dxdiag.txt file.
4. Post it here.

The only fix I could find is to use a Intel PC. I had to use my Laptop.

[NicholeMattera]

While trying to flash back to the original kernel:

FlashingOriginalKernelLatestRelease.txt

Edit: Attached are more logs when trying to run the build you posted in issue #674 . With this build I was able to get through the flashing of the original kernel, but when half-way through flashing the custom kernel it would always error out.

FlashingOriginalKernel.txt
FlashingCustomKernel.txt

It also eventually stopped responding:

[wangyung]

I don't know the root cause of this issue, but I got the error when I used v2.21b
After I rollback to v2.20, everything works like charm.

[ThePeteCrazy]

temporary fix is to use another usb port
"worked for me"

[Terlouw]

Still an error with flashing custom kernel. (Rollback or different usb port made no difference for me.)

stack_trace.txt
DxDiag.txt

I hope this great tool will become compatible with all Ryzen users.

[joetheuseless]

i have tried everything and it still crashes at 30% when installing the custom kernel i wonder how we can fix this? using Ryzen 1700 i have a older AMD build i want to test this on but it wont be complete for another few days :-p

[christopherfowers]

Is been suggested to me that restating the Ryzen computer has worked for some. This did not work for me.

[christopherfowers]

Perhaps it will work for some though

[Drakonas]

Just so everyone doesn't get the wrong idea, this is a fault with Ryzen's drivers, not Hakchi. I don't want people blaming Cluster for this. People should try contacting AMD to have them fix this.

[FJ000]

Just wanted to comment about the closure of #542. I am having the problem with 3 separate Intel PC's. NOT AMD.

Issue for me is now on 3 separate Intel PC's. NOT AMD. One PC has USB 2.0 with Windows 7. Other two have USB 2.0 and 3.0. One running Windows 8.1 the other Windows 10. Have tried all USB ports. Two separate usb cables. Have tried up to hakchi2 version 2.21e. I have not flashed the new kernel. Only dumped the original kernel, which was successful. Since the same problem is present on 3 PC's with different configurations I am not ruling out the possibility that the fault could be my own. Still, I am no further at figuring out the problem.

[Drakonas]

@FJ000 thank you for posting this here and not the old ticket. I am keep discussion of this in one issue. Not exactly sure what's going on.

[FJ000]

More to add about the comptuers I've tested on:

Windows 10 PC - Intel 7 Series Chipset / Intel C216 Chipset
Windows 8.1 PC - Intel 8 Series Chipset / Intel C220 Chipset
Windows 7 PC - Intel 5 Series Chipset / Intel 3400 Chipset

[pcenthusiast92]

I'm having some problems with Windows 10 on my Ryzen 5 1600, motherboard asrock b350 fatality k4 gaming

Seems like the windows usb drivers 3.0 or 3.1 are the culprit, windows seems to detect my G9 mouse and g15 logitech which are usb 2.0, i did connected to my rear panel usb 2.0 ports, and windows seems to recognized as 3.0, and prompt a message like this:

Tried already to install AMD DRIVERS in WINDOWS, but without success and mouse is inconsistent, in Mouse-movement recorder app, there is inconsistent polling rate jumping, decreasing, etc

this the Mouse-movement Recorder, (this is happening in Windows 7, also windows 10 1607, and creator 1703.
1000 hz

500hz

I'm using latets Asrock Ab350 Fatality k4 gamming bios which is version 3.20
And for a weird reason that motherboard has USB features (locked-hidding) when checking AMBICIP software editor and loading my bios, i have these options that appears like (SHOW+YES) but they actually doesn't show in my bios screen.
All these options seems to be FORCE ENABLE or either disable and i dont have ACCES.

I don't have access to:

-EHCI-HAND OFF
-XHCI-HAND OFF
-Legacy USB/PORT
-USB PORT
-USB 2.0 Controller Mode

[iratemike]

Same issue here. Tried on 3 Intel PCs, tried USB 2.0/3.0, even tried a powered USB 3.0 hub.

[AbyssalWank]

I had this same problem. switching form usb 3.0 to 2.0 solved it.
ryzen 7 1800x
msi mobo
win 10
Edit: this only allowed me to dump the kernel. now i cannot write

[danmcgoo]

I have the same issue on a Thinkpad P50 (Intel processor) running Windows 7

[guillaume-duchemin]

Same issue with USB 3 here. I don't have USB 2 plugged in my motherboard (MSI Z270 Tomahawk) + Ryzen 3

[ghost]

modifying that code, it should help you :-)

(function RunUbootCmd -> 20 instead of 10)

       for (int i = 0; i < 20; i++)
        {
            Thread.Sleep(500);
            callback?.Invoke(CurrentAction.RunningCommand, command);
        }

---

[ShadySalad]

I had the same issues. Didn't work with usb 3.0, 3.1. I just used the cable that came with my NZXT Heu+ and connected to one of the 2 usb 2.0 ports on my mobo. Only got lucky with one of the two, but got it to work. Hopefully it is of some use for you guys.

[BlueScreenBuddy]

Ryzen 1800x/Windows 10 1709/Gigabyte AX370 Gaming K7. Had to keep switching USB ports until it worked.

[christopherfowers]

AbyssalWank I am where you are. I can dump. I cannot write. USB 2.0 only though. My USB3 doesn't work for this at all.

[FJ000]

Ghost's post above solved my problem running on one of the Intel machines I tested it on. (Didn't test the other two machines)

hakchi2/FelLib/Fel.cs --> change line 416 from:

for (int i = 0; i < 10; i++)
to
for (int i = 0; i < 20; i++)

Compile and everything works 👍 . I was now finally able to dump the NAND and all other functionality seems to work that I have tried.

This could be a good change for the next release if others can test with success.

Excellent program!

[Shuxo]

Same issue with Ryzen 1600 when using a usb 3.0, switch to usb 2.0 and worked, running win 10

[shogan333]

My motherboard only has USB3 support. How can I write to the NES mini using USB2?

[ferdreyfus]

Had the same issue. Removed driver from nes mini device in devices and printers,, then restarted win10, and re-ran hackchi2

[zushiDev]

DxDiag.txt

I also seem to have this issue so here is my DxDiag.txt file

[dakzilla]

I encountered the same issue using a Ryzen CPU with a X470 mobo with no USB 2.0 ports. Every USB 3.0 port I tried led to one of two errors: "USB read error: IotTimeOut" or "Can't write to USB".

Solution: I found a USB 2.0 hub I had lying around and plugged it into a USB 3.0 port, then plugged the SNES Classic into the USB 2.0 hub. Dumping and flashing the kernel then worked flawlessly. The issue only seems to appear when using USB 3.0.