@Meadow
Rufus can't create MSDOS bootable USB-drives as it's missing a .dll for that.
Edit: Luckily I had a Win7-install around, however with the MSDOS instead of FreeDOS I get the same error SPIROM not found (-8) with all updaters.

@nobi

@Artobe

Please try the updater tool from attached old FW package (if you haven't got this FW package already).
Do not use u.bat nor C:\104xfwdl /U

Use only
C:\104xfwdl /d
and
C:\104xfwdl /A
to test

@Meadow

From your post:


Newest I tried also:

@Artobe

Seemingly /A is not implemented in the old version of the updater tool. Personally I used a newer version of the updater tool together with the old .bin of the old FW package which I still use today, a version which works rock solid for me.
Give /C and /T first a try with the old version of updater tool, then try /U too with a newer .bin and then with the .bin of this old FW packagce. Note that the latter may be older than the one you have (as is reported by /d).

No change, I'm ready to give up trying :D

@Artobe

It seems that no updater tool (whether DOS or Windows) is able to access the SPIROM on your motherboard.

I have looked around on the internet regarding the issue you have and found the following two threads which may be of interest to you (if you not already found them yourself that is).

1) https://www.overclockers.com/forums/show...4-USB-3-problem
2) https://forums.tomshardware.com/threads/...-issues.382274/

In thread 1) user richard.tyfty seems to have fixed the same kind of issue by updating the motherboard BIOS to version: "P1.70 BIOS 06/06/12" (see post #1 and #16)
In thread 2) post #11 someone is using BIOS version 1.40 with working Asmedia USB3 ports (He tried 1.70 briefly but went back to 1.40)

What BIOS version do you use at the moment?
Did you already try above mentioned BIOS versions?

@Artobe

In addition to the BIOS questions:

May I know something more about the current status and history of your Asmedia USB3 ports?
1) Apart from not being able to update the USB3 firmware: Do the Asmedia USB3 ports currently work (normally) within Windows (i.e. can you read from and write to a usb stick)?
2) Did the Asmedia USB3 ports ever work "normally" in Windows (at full or lower speed or intermittently)?
3) Is the current Asmedia USB3 firmware the original firmware that came installed with the motherboard?
4) Did you ever (try to) update the Asmedia USB3 firmware before? When so did you encounter an error while updating the USB3 firmware leaving you with the update issue you have now?

I'm using 3.0 modded to include NVME support from MDCLAB.

1)They work fine except my fastest USB3 stick doesn't and I hoped it would fix that.
2)Always did work normally, other slower USB3 sticks work fine also.
3)I'd guess so.
4)A lot of times but never managed it to change version I suppose as the errors in Windows and DOS cropped up, just as they do now.

It might be the case that the modded (non standard) BIOS 3.0 doesn't work well in combination with the Asmedia updater tools (which might be developed/writtten for older BIOS versions).

It would be worth the try to flash BIOS 1.40 or 1.70 and test if you can get the updater tools to work (in DOS mode) then revert back to 3.0, but I'm not sure if that is possible to do for your setup.

I'd rather not - downgrading a BIOS is one of those few cases that has an increased chance to brick it and already pushed my luck by not bricking my Asmedia USB controller courtesy to all those flashing attempts ;).
Don't have a BIOS programmer and 2nd PC set up atm either.

Anyway, thanks for the tips @Meadow and @nobi, really appreciate trying to get it to work but alas it shouldn't be :D.

@Artobe

You're welcome.

I really love and like the way you look at it. Most of the times it is best to live with or follow the golden rule: Never change a running system (despite a non working USB3 stick :) )
And to my believe your issue might not be easy to fix at all as it seems that your motherboard is not equipped with a SPIROM containing the firmware for the Asmedia controller but instead the Asmedia controller is loaded with firmware located in your BIOS by the motherboard hardware at power-up or boot-time. And personally I would stay away (far away) from hacking BIOS firmware to adapt the Asmedia firmware.

Anyhow, good luck!

@Artobe

I am sorry I can not help you. As my PC was able to update with either firmware with P8Z68-V / GEN3, the same as ASM-1042
I think I"ve done some extra work because I"m adviced and I"m not as smart as Meadow. I"m so sorry.

See you at Artobe or somewhere else.

Zitat von cookie im Beitrag #193

---

Zitat von emilej im Beitrag #108

---

Thanks everybody, this was a great help. I can confirm this is working on an Asus P8Z68-V. Wonderful!

---

i can confirm it also works for an Asus P8Z68-V Gen 3.
1042 controller, flashed it to version 130125_00_02_00.

By the way, I came across this thread when I heard this controller is incompatible with the Oculus Rift.
At least the random usb storage disconnections are gone.

---

I confirm the authenticity of the files inside the rar-archive provided by @cookie. All files stem from version 130125_00_02_00 with one file added: "0315_123.bin" which is the old .bin file of version 110315_01_02_30 which I provided in my post #392.

I also confirm that I have used the updater tool belonging to version 130125_00_02_00 together with the old .bin file "0315_123.bin" to successfully update my Asmedia controller firmware on my ASUS P8Z77-V PRO motherboard as written in my post #287.

@lordkag and anyone who can help.

I have an ASUS P8Z68-V PRO / GEN3, and apparently a long time ago I "updated" the ASMEDIA 1042 chip with firmware for the 1042A chip. I have physically verified it is an ASM1042 chip (picture attached) but when I examine the current firmware (also attached) I see the 2104B_RCFG header (1042A)

Note:: Even though the chip and firmware are mismatched, BOTH of the USB3.0 ports work

Executing 104XFWDL /D gives only one device/SSID rather than two entries:

1 > Bus:0x03 Device:0x00 Function:0x00
FW Version : 100803_00_00_0d
(SVID:SSID = 0x174c:0x2104)

.

Executing 104XFWDL /U 131025.BIN gives:

1 > Bus:0x03 Device:0x00 Function:0x00 SPI ROM, Device[PM25LD512C]
Current : 100803_00_00_0d Update to : 131025_10_11_03
update host[0] firmware.....PASS!!

Update firmware.....PASS!!


Except it doesn't actually update the firmware. After power-off and reboot, 104XFWDL /D gives the same result as above.

I have NOT modified the CFG file as some posts in this thread say to DO and others say NOT to do.

What is my next step? How do I proceed to unbork and update the firmware.

Thanks very much
Cyberia