Check the Windows event log for errors with the drive.
Possibly a USB issue ?
Try this please :
I've noticed several differences between this my modded firmware and your "friendly" one.
You have to use DOSFLASH in order to flash it (erase eeprom and then write file).
At offset 0x1E0004 there are slight differences. Maybe it will not change anything, but just to be 100% sure, I've attached my modded 1.01 file for comparisons.
Try it and maybe it will fix some issues you've experienced.
Clean means that the firmware is unlocked for flashing (by using a non-official patcher). It has nothing to do with UHD friendliness.And since we mentioned this (and as I asked before): In the clean firmwares found in the link of the 1st post of the thread there is also BE16NU50 1.02. How can this be clean since 1.02 is not UHD friendly? A clean firmware should be based on a UHD friendly one, right?
Clean means that the firmware is unlocked for flashing (by using a non-official patcher). It has nothing to do with UHD friendliness.
I think SPCAV may be questioning whether 1.02 is a version that closed the loophole and therefore, why is it included in the list...
The BTHUSB 34 Warning is related to Bluetooth so unlikely to be the cause.
It’s worth checking USB is set to never power down in Windows Power config.
The blue screen DATA STRUCTURE FAILURE points to a driver or Windows 10 integrity problem
After the reading/dumping process, you will need to take the clean 1.02 (or any other UHD Friendly firmware) and prepare it with data imported from the original dump. To do this, you can send me your dump, or doing yourself via HEX Editing process (see below).
You don't. You provide teddy with a dump of your 1.03 version and he'll create a working 1.02Just read through this thread and it wasn't clear to me where to get a clean 1.02 image for a WH16NS40 (mine came with 1.03 and I need to downgrade it).