ASUS may need missed a severe flaw of their newest ROG Maximus Z690 HERO motherboard as a number of customers have reported circumstances of boards burning up and failing to publish.
ASUS’s ROG Maximus Z690 HERO Motherboard ‘Orange Mild of Demise’ Challenge Causes Boards To Burn Up
Over in ASUS ROG Boards and ASUS’s subreddit, there are a number of stories of the ROG Maximus Z690 HERO motherboards burning up. There have been at the very least six stories previously few days and several other customers who bought their RMA models have seen the identical subject happen, even on the newer boards.
So what’s the entire subject about? Effectively it is too early to inform however based mostly on the data shared by consumer, Maximumrog57, it appears to be like like the problem occured a number of days after the system was fired up. The consumer mentions that he heard a clanky noise however there was no seen indication of any injury on the board itself. Nevertheless, the very subsequent day, the motherboard did not boot and reported the 53 error on the QCODE ‘DEBUG’ whereas the QLED lit up in orange shade. The consumer additionally noticed seen burn injury on the chips proper under the QLED.
As for what the 53 QCODE is, it’s typically associated to the incompatible reminiscence or issues with the put in reminiscence modules. This was one consumer on the ASUS ROG Boards however after this, there have been a number of different customers who began reporting related points with their ROG Maximus Z690 HERO motherboard. Following are all of the stories from the customers on Reddit:
One other Z690 Maximus Hero right here with q-code 53 that I acquired from a newegg combo with g.ability 6000cl40 (F5-6000U4040E16GX2-TZ5RS). I used to be operating stress checks simply fantastic. Afterward whereas solely browsing the net I heard a really audible pop and the system instantly locked up, the board was glowing within the higher proper nook, after which I smelled burned electronics. Mine does present injury on the PCB, not as excessive as what’s seen within the ASUS discussion board nevertheless.
I had not finished something with my BIOS but, truthfully I used to be unaware that this was a factor till I begin trying up z690 qcode 53 on-line. Early adopter tax I assume… I figured I might see some bugs until updating on a brand new platform, I wasn’t anticipating it to be a hearth hazard. lol
o… This SUCKS! I lastly bought to construct my PC final night time (i9 12900k, Z690 Asus Hero, Gskill DDR5 6000) and in the present day it won’t publish in any respect.
After ending the construct final night time I powered it on and it went to the BIOS with 0 points. After studying some feedback on right here and on the Asus discussion board about XMP stability I up to date to bios to 0803 as suggested. I booted it again up and within the BIOS every part was exhibiting because it ought to. After that was working I began Memtest through the BIOS and it bought to about 50% by means of the check earlier than I went to mattress.
I awoke this morning and now it won’t publish it doesn’t matter what I do. I get the Q-Code 53 with an orange gentle which implies that it’s having a problem with the Reminiscence. I attempted every part I might consider:
- Testing every RAM stick in every DIMM slot individually
- Clearing the CMOS and eradicating the CMOS battery
- Unplugging the GPU / RAM / Reseating the CPU Cooler
- Flashed again to the unique BIOS and NOTHING!
Asus help says that the RAM I’m utilizing just isn’t on the Z690 Hero “authorized checklist” which is nuts as a result of I acquired that RAM and Mobo from a Newegg combo! The agent linked me the checklist and certain sufficient that CAS 36 model of the GSkill Z5 6000 just isn’t on that checklist! I requested him why it might have 0 points attending to the BIOS final night time and so forth and he stated that it could possibly work for awhile after which cease working all collectively.
My pal has some Dominator Platinum 5200 C40 coming within the mail on Thursday I consider and I checked the ASUS checklist and that is also NOT supported! What’s loopy is the GSkill z5 6000 at totally different CAS (aside from 36) is supported and the identical factor with the Corsair. The CAS 40 model of the Dominator package is NOT supported, nevertheless the CAS 36 is!!! Asus stated they’d RMA it, however I need to exhaust all of my choices (restricted as they could be) earlier than I am going by means of that nightmare…
I simply thought I’d publish right here in case anybody had any perception to this drawback and if not, at the very least I might possibly save somebody a future headache.
Because the title states, it seems like there could doubtlessly be a problem with the Z690 Hero motherboard. I constructed myself a model new pc utilizing the brand new Hero board. Purchased instantly from newegg through a combo that included ddr5 as a result of shortage of ddr5 at this second. Obtained all of the parts and constructed the system. Powers on, I set up home windows, all is sweet. About 5 hours in unexpectedly, solely simply looking the web, it laborious shuts off, like the ability went out. I strive turning it again on however nothing. I scent burning coming from the motherboard.
To search out out what was improper, I went to microcenter and bought 3 objects, one other 12700k (in case the primary one died with the mobo), one other z690 hero, and one other corsair rm1000x (in case it was the ability provide). I made up my mind the ability provide was not useless, and the motherboard was. So we changed the motherboard (fortunately it didn’t take some other part together with my GTX 1080). I rebuild all of it from scratch once more, making completely sure no wire is being positioned incorrectly or sitting the place it shouldnt be. I flip it on, it really works and I get it up and operating. As a little bit of a sanity test, I run AIDA 64 on the cpu and ram, and run Furmark on the GPU, each for roughly two hours, simply as a intestine test to make sure nothing is severely improper. All is sweet, no points. I play some BF2042 later within the day, no issues there both. Then late at night time I’m merely browsing the net and unexpectedly it laborious shuts off once more, and this time once I look over there I see a part on the motherboard actually on hearth. I shortly change the psu off and unplug it from the wall (the mobo additionally tried to restart throughout this endeavor earlier than I turned the psu off and yanked the twine from the psu socket to make sure I wasn’t going to burn my home down.
At this level I’m suspicious. One unhealthy lemon, fantastic. Two, with the very same failure doubtlessly, that is no coincidence. I felt prefer it may very well be the motherboards are unhealthy, or the ram is unhealthy (which I doubt, ram shouldn’t trigger one of these failure, however its new ram, and I’m not an knowledgeable when it comes pc and electrical engineering), or my energy provide is unhealthy (both the unit or one of many cables). So I am going on this reddit to see if possibly simply possibly anybody else has stated something. Effectively to my shock, I discover another person has had the very same part go.
Different Customers Reporting in on the identical subject:
- Simply had each my hero and a buddies hero final night time after constructing our pcs do precisely the identical. Was simply watching YouTube my complete computer shut down and solely the beginning and flex key buttons had been lit. Tried recognized good psu nonetheless nothing. Associates computer was furmarking over night time got here again within the morning to the identical drawback. My buddy has one other z690 hero and goes to check it tonight. Clearly this taking place to sufficient those who it is a board drawback.
- Sounds similar to what occurred to me simply final night time. All labored nice after a meticulous construct, bought Home windows put in, video games arrange, however a few hours into use (gaming – Rust), all died. Couldn’t energy up once more. Now, at all times get a Q Code 53 (reminiscence) on tried boot.
- System ran usually for a night by means of setup and downloading of sport installers, and ran two video games every for a number of moments with out subject. System entered sleep a few instances within the night time. The system shut off the subsequent morning whereas getting used for net looking, and every try to show it on after that leads to Q Code 53.
- OMG, I’ve been by means of TWO Asus ROG Maximus Z690 Hero boards in 3 days, BOTH dying inside hours of use. The primary time, I didn’t know why it died. It was a tough shut off, simply browsing the web, and out of the blue the system simply laborious shut off, by no means besides again up.
What’s extra regarding is that there are a number of customers inside this subreddit threads who’re dealing with the identical points and several other even have their ASUS ROG Maximus Z690 HERO motherboards fritter away and exhibiting the orange gentle of demise on the QLED in an analogous approach. Some customers report that these two ICs ‘4C10B MOSFET’ do not have something to do with the DDR5 DIMM slots whereas others on Overclock.web have reported that some DDR5 producers are flashing unhealthy SPD info in XMP profiles for particular kits so unwantedly excessive voltages may very well be inflicting this injury, resulting in the primary ICs answerable for dealing with DDR5 DIMMs burning up and exhibiting the 53 QCODE on the board.
Now this is not confirmed but and ASUS does have a QVL for their ROG Maximus Z690 HERO board talked about on their website for customers to test earlier than buying or putting in any particular reminiscence package however no matter that, an unsupported reminiscence package should not trigger any motherboards to finish up in flames. There are some stories that the 8011 BIOS for the motherboard enormously improves reminiscence stability and results in much less QCODE 53 & orange gentle of demise points however whether or not this can be a everlasting repair or an intermediate answer must be investigated. We are going to cross this info to ASUS and see what they need to say on the matter.
