Post code 00

Same here:

2 weeks ago the server beeper beeped a couple of times, the OS died, but the system itself stayed on. IPMI was still working.

After a reset the debug led showed 00. After a power-off incl. removing the power cable to the PSU I started the system by the power button, the whole set of components came up, but the board remained at 00.
IMPI continued to be available, but told me that the host is off.
Tried to power up the host thru BMC but it said: Performing power action failed.


I attempted everything: resetted bmc to factory defaults, cleared cmos, varied ram configuration, updated bmc, removed and checked cpu: nothing.
I then kept the system powerless for a couple of days, did this and that, started it one day with zero hope and out of the sudden after minutes of code 00 the code numbers changed. Consequently the

I expected the cpu to be faulty. Hence I did thourough tests: CPU is OK.


Today it happened again, this time without beeps. Symptoms are identical to the incident before. Code 00.

Very annoying.


Specs:
B650D4U, 7700, KSM48E40BD8KM-32HM

BMC version: 4.10.00
BIOS version: 10.15

Thank you for your pointing me to Asrock (Rack).

Opened a ticket. Let's see what it brings.

In my case the board is equipped with a tame 7700 (65 W TDP), thus I don't belong to this scheme.

But it worries me to read that such a high number of units is struggling aka ending bricked.
I'm getting the impression that it could be a serial defect.


As I'm in the comfortable position of an end consumer who has bought the board directly at Amazon, I don't have the stress the do a RMA at ASRock. Amazon promised me already to give me a full refund.
The RMA department of ASRock wrote that I would have to ship the board at my own expenses to them. At worst this could be costy because it seems that the RMA department is in another country.
Which leads back to the theory of a serial defect: Why should I pay for ASRocks fault?
Interestingly in my communication with the ASRock departments, no-one seemed to be keen on isolating the cause for the defect.

Anyway, to be is uncertain if I should buy a board of the same model again, when the error could hit me at any time for a 2nd time.
Tres dommage, that the market only leaves the Gigabyte MC13 as (a half-backed) alternative.
For me the ASRock board is, as long as it is running, a marvelous product.

Board ran into this issue a couple weeks ago. I've just sent it in for RMA. Feeling nervous putting a replacement back in production after seeing so many other with this problem.