Reply 20 of 33, by dormcat
Vynix wrote on 2023-11-16, 10:43:
Since your board tries to seek the floppy drive, there's some hope for recovery. […]
Since your board tries to seek the floppy drive, there's some hope for recovery.
I've faced that with a very similar board (mine was a HOT-555A Rev-3.2), I tried to flash a patched BIOS, and wound up in the same boat.
I prepared a DOS boot disk with AWDFlash, the patched BIOS and a modified AUTOEXEC.BAT written to tell AWDFLASH to directly flash the patched BIOS without promoting anything, although this assumes you have access to another working PC with a floppy drive and have some spare floppy disks.
So with the floppy disk prepared, I turned off the bricked PC, put the floppy disk in it, then turned it back on, and after a few minutes, I heard the floppy drive seek back and forth, I let it sit for roughly an hour and a half just to be sure that it flashed the EEPROM, and after rebooting, it seemed to have recovered.
It's been a year and I still have no idea what went down.
That's how I "rescued" the second GA-K8VM800M and the replacement Asus K8V-MX for a brief moment. When the same symptom appeared on K8V-MX I realized that only a defective CPU or RAM could have done that before POST so I replaced the DIMM and tested it with MemTest86 on an unused, "expendable" system. Multiple error reports spun out immediately. 😠