|
Z790M PG Lightning/D4 woes |
Post Reply 
|
Page 12> |
| Author | |
Xaltar 
Moderator Group 
Joined: 16 May 2015 Location: Europe Status: Offline Points: 31963 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: Z790M PG Lightning/D4 woesPosted: 03 Oct 2025 at 3:17pm |
|
Thanks for the chuckle, definitely would watch that video. Could be some trick to
flashing the ROM. I remember on some BIOSes back in the day I had to double up the code (2 copies) so that the board would recognize it. Unfortunately I have not flashed any of these newer boards so I can't offer any suggestion here. Maybe check out google and see if anyone else has flashed a Z790 (any brand) and see what they did. Good luck. |
|
|
|
 |
|
|
MHzTweaker
Newbie 
Joined: 27 Sep 2025 Location: US Status: Offline Points: 165 |
Post Options
Thanks(0)
Quote Reply
Posted: 02 Oct 2025 at 11:54pm |
|
I purchased a CH341A USB programmer, connected it, loaded drivers and got it working.
I flashed this ASRock motherboard with the current ROM code (erased, flashed and verified). It is still broken and stuck in a boot loop. So no, I'm not buying a defective Intel CPU caused this. B.S. It does the same thing with a brand new CPU. I flashed it yet again. Same outcome. I tried it a 3rd time with older code but the programmer will no longer recognize the flash chip. I do not know if it is the chip or the dinky low quality chip clamp. It looks very low precision. I have ordered 3 more different replacement SOP8 clamps. Yes, I am stubborn to a fault. My hope is to try going back to earlier BIOS versions to see if that makes a difference. If I cannot revive the board I will make a video testing the boards ability to deflect .308 caliber rounds and post it to youtube. The murderboard gets murdered. I guess in reality it suicided itself first. |
|
|
|
|
MHzTweaker
Newbie
Joined: 27 Sep 2025 Location: US Status: Offline Points: 165 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 Oct 2025 at 11:05pm |
|
|
|
Xaltar
Moderator Group
Joined: 16 May 2015 Location: Europe Status: Offline Points: 31963 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 Oct 2025 at 5:15am |
|
Intel committed to replacing the damaged CPUs, they did not however provide any
kind of incentive for their board partners to do the same. Possibly because they didn't think the boards were part of the issue. The problem seems to occur when the bad/dying CPU is used to flash the UEFI. Bad luck really. As for the flasher, I would look at reviews/recommendations on youtube. |
|
|
|
|
|
|
|
MHzTweaker
Newbie
Joined: 27 Sep 2025 Location: US Status: Offline Points: 165 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 Oct 2025 at 4:52am |
|
You know the crazy thing is, I have already received a brand new boxed i5-13600k replacement CPU yesterday from Intel Kentucky service center. I would have thought help from ASRock would have come before I got help from Intel in making this right.
|
|
|
|
|
MHzTweaker
Newbie
Joined: 27 Sep 2025 Location: US Status: Offline Points: 165 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 Oct 2025 at 4:48am |
|
|
|
MHzTweaker
Newbie
Joined: 27 Sep 2025 Location: US Status: Offline Points: 165 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 Oct 2025 at 4:43am |
|
|
|
Xaltar
Moderator Group
Joined: 16 May 2015 Location: Europe Status: Offline Points: 31963 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 Oct 2025 at 4:24am |
|
IIRC the issue was on intel as it effected all brands. It is frustrating for sure.
This is in no way me speaking for ASRock, I don't represent them in any kind of official capacity but from the what I have observed on the forums it seems that attempting to flash the BIOS with an already degraded CPU causes the bad flash. In my eyes that places blame on intel for not catching the issue before launch. As I understand it intel only provided support for their CPUs and gave no incentive to their board partners whatsover for this issue. I could be wrong but I have gotten pretty good at reading between the PR lines. None of this helps you though so I will leave it there. As for the flasher, you will need to look at the BIOS ROM and determine what ROM is used then google for a compatible flasher. AFAIK pretty much all boards/brands use the same family of BIOS ROMs so it will be a useful tool to have handy for your shop. There are quite a few flashers out there now that have modular attachments to support a broad variety of ROMs. Unfortunately I have been out of the game for a while now so I couldn't say which one is best currently. |
|
|
|
|
|
|
|
MHzTweaker
Newbie
Joined: 27 Sep 2025 Location: US Status: Offline Points: 165 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 Oct 2025 at 4:13am |
|
Technically, no, ASRock hasn't broken any rules.... but.
If using the board is burning up CPUs because of overvolting and the only solution is to replace the firmware... THEN using the firmware ASROCK provided causes the motherboard to cease to work, then I disagree. I feel they ARE responsible for this. I purchased this motherboard in good faith with the understanding it would not destroy things plugged into it. Well, the firmware solution caused the motherboard to destroy itself.... so I guess it won't hurt any more CPUs now. Problem solved right? I take precautions. The board and PS are plugged into a UPS battery. I make sure there isn't a bunch of stuff plugged into the board. This should have been straight forward. It was. The flash completed without an issue, it restarted after 100% completed flashing then ran off the rails. I'm not the first guy this has happened to with this board. There are others. https://forum.asrock.com/forum_posts.asp?TID=31102&title=reboot-loop-after-bios-update I did nothing wrong. The board is still fine. It isn't like it was physically abused, overclocked with liquid nitrogen or something. It sat in a law office it's entire short life basically serving a few files to attorneys. I wish I knew what I could buy to flash this chip. I would buy it and put it in my tool box. I can count on one hand the number of times this has happened to me since flashable BIOS's have even been a thing. I flash Dell RAID cards (LSI) to be used as HBA adapters all the time from a PC with a Win98 DOS partition. |
|
|
|
|
Xaltar
Moderator Group
Joined: 16 May 2015 Location: Europe Status: Offline Points: 31963 |
Post Options
Thanks(0)
Quote Reply
Posted: 01 Oct 2025 at 2:06am |
|
By all means, complain here all you like. These forums serve that purpose, a place
for ASRock's users to share their experiences, good and bad, and help each other out. The problem is, they are not actually breaking any rules or violating their warranty obligations. I have had similar issues myself with numerous brands over the years. At the end of the day I stick with the brands that hold up their end of the deal. In this instance, ASRock have no obligation to help with a product that is out of warranty. If the board was still under warranty then I am sure they would have instructed you to begin the RMA process. It can feel personal but the policies exist for a reason, a line must be drawn or their support staff will be swamped with work that isn't actually their responsibility. This slows down response times for users making valid warranty claims. It just sucks to be left out in the cold the moment the warranty period ends. Issues like this are why I no longer run my own IT store. I meant what I said about relating. Good luck with the BIOS chip replacement. It may be worth picking up a ROM flasher. That would have saved you ordering a replacement, the clip on variety are what I used to use, it saved having to desolder the original. Edited by Xaltar - 01 Oct 2025 at 2:06am |
|
|
|
|
|
|
|
Post Reply
|
Page 12> |
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
Topic Options