Asus dark hero startup issue ?

[omarfgalindo]

I too have the same power on problem. So sad to see inaction from Asus on this. Make it right and initiate some sort of recall/exchange for this motherboard. I will definitely stay away from Asus in the future. Shame.

[Xairoo]

Asus said...

The impact of covid-19 epidemic is longer than estimated, and we still discuss the replacement program with our local team. I'm sorry the estimated time would be delay until the beginning of July. I will keep you updated if it is early or delayed.

I don't see the problem. There aren't many customers that know about that program. Okay, maybe there will if the program will be public, no idea.

[Reapz_90]

I am also having the issues described here but with the hero wifi board. Shame that ASUS are doing this to their customer, especially on a high end product. Unfortunately I did not find these posts before I bought the motherboard... So I guess on the chance that asus actually gets this "replacement solution" in place i will get a used refurb board that is likely older than the one I currently have as mine had this issue out of the box. does anyone think we will get answers to what is actually wrong? will this issue affect the life of the board? if so does the fix solve that? why are they being so tight lipped about what the issue/fix is? do yall think that the life of the board will be affected fixed or not and this is why they are not being open about the issue? or maybe that the fix involves them disabling/tweaking some function of the board and they know that is unacceptable?

whatever the case something shady is going on it seems. If they continue to refuse to offer an acceptable solution and stall for time what is the re-course we have for dealing with it? I have been posting about this to all the large youtube channels in hopes that they will put some pressure on asus for their unacceptable "replacement solution".

[vanbako]

For me, the startup issue is gone after applying bios 4201
The "sudden death" issue (blank screen, q-code led "00" and yellow dram q-led on) is still there.

[JBROG87]

For me, the startup issue is gone after applying bios 4201
The "sudden death" issue (blank screen, q-code led "00" and yellow dram q-led on) is still there.

No it wouldnt solve it, it is a hardware defect, no bios update can fix it.
Just keep trying the issue will re-occur.
It helps to let the PC run maybe a game or something for 30 min and then try until it occurs.

[NuadaXXX]

No it wouldnt solve it, it is a hardware defect, no bios update can fix it.
Just keep trying the issue will re-occur.
It helps to let the PC run maybe a game or something for 30 min and then try until it occurs.

Correct, that was even confirmed to me by the technical/DEV team, they have found the issue on my MB. but i have no replacement yet they need more time.

[JBROG87]

Correct, that was even confirmed to me by the technical/DEV team, they have found the issue on my MB. but i have no replacement yet they need more time.

Did they say any more details about it ? Is this something that will eventually brick the motherboard? Or will it just have this behaviour without getting worse

[Mwing]

at least you guys can power cycle and start the pc up

i cannot start the pc up, not from case power button nor the button on the mobo

power cycle the psu does not work, ram, aio rgb on, start button on the mobo is lit, but both the ROG rgb near the io shield and the chipset asus eye logo dont light up

[Xairoo]

The big question:

Does this problem appear on every board? Or is this random? And has this been fixed for newer production dates?
So getting a new board from the retailer could fix this or not.

Would be great to know.

[NuadaXXX]

Did they say any more details about it ? Is this something that will eventually brick the motherboard? Or will it just have this behaviour without getting worse

No he says only, that they have found the issue on my motherboard, and i need a new, but i have my broken MB still, i wait for a exchange, they have only analyzed the bios Profiles from me, and have found the issue.