So Tell Me Now and I Wonã¢â‚¬â„¢t Ask Again
-
12-27-202104:35 PM #41
ROG Enthusiast Array
I would effort to find Corsair QVL against ASUS every bit both gskill cl36 kits I had with 5600 and 6000 weren't listed on asus hero'southward page only on their corresponding QVL pages they have hero listed.
Originally Posted by Nozyspy 
Im in a flake of a pickle cheers to all this. I bought this mobo a short while ago and i don't know what to do about information technology. (https://rog.asus.com/forum/showthrea...usion&p=851934) I even recently practical for the Asus x Intel promotion cashback.
These reports of motherboards combusting are rather worrying. And it seems that the return period has airtight for me since information technology was just 14 days. :/
highly possible they're not OC friendly so stick to a stock config. I believe BIOS and QVL will keep updating and it's a lot of try and catch right now.
most folks had BSOD issues on OC which persisted more often than not on xmp1, then again, I'm simply reading out every bit much every bit you already may have.
skilful luck!
-
12-27-202104:43 PM #42
New ROGer Array Ribellu PC Specs
Ribellu PC Specs Motherboard Asus Maximus Z690 HERO Processor I7 12700KF Retentiveness (office number) Corsair Vengeance DDR5 2X16Gb 5200Mhz 38/38/38/74 Graphics Menu #1 Asus ROG-STRIX-RTX3080TI-O12G-GAMING Monitor Asus VG27AQ Storage #1 SSD Samsung 970 EVO Plus 1T Storage #2 SSD Samsung 960 EVO 500gb CPU Cooler MSI MAG CoreLiquid C240 Example Thermaltake Commander C31 TG Ability Supply Corsair HX850 Keyboard Razer Huntsman Tournament Edition Mouse Razer Bazilisk V2 Headset/Speakers Hyper X Cloud Blastoff Os Windows x Pro 21H2
Everything should be fine at present Originally Posted by maximumrog57 New motherboard received, double checked screws and spacers/standoffs, all present and setup the same.
no OC done this time, just 0811 official update and SecureBoot UEFI and REBAR. monitoring for any issues for the side by side few days.
AM
-
12-27-202104:47 PM #43
New ROGer Assortment Ribellu PC Specs
Ribellu PC Specs Motherboard Asus Maximus Z690 HERO Processor I7 12700KF Memory (office number) Corsair Vengeance DDR5 2X16Gb 5200Mhz 38/38/38/74 Graphics Card #1 Asus ROG-STRIX-RTX3080TI-O12G-GAMING Monitor Asus VG27AQ Storage #1 SSD Samsung 970 EVO Plus 1T Storage #2 SSD Samsung 960 EVO 500gb CPU Cooler MSI MAG CoreLiquid C240 Case Thermaltake Commander C31 TG Power Supply Corsair HX850 Keyboard Razer Huntsman Tournament Edition Mouse Razer Bazilisk V2 Headset/Speakers Hyper X Deject Alpha Bone Windows 10 Pro 21H2
indeed ever proceed in mind that this is a whole new generation of CPU and Chipset, so a lot of updates will arrive over time, just be patient, before doing big RAM or CPU overclocking .. Originally Posted past maximumrog57 I would try to find Corsair QVL confronting ASUS as both gskill cl36 kits I had with 5600 and 6000 weren’t listed on asus hero’s page but on their respective QVL pages they take hero listed.
highly possible they’re not OC friendly so stick to a stock config. I believe BIOS and QVL will keep updating and it’s a lot of try and catch right at present.
most folks had BSOD issues on OC which persisted mostly on xmp1, so again, I’m just reading out as much as you already may take.
good luck!
-
12-27-202104:52 PM #44
ROG Enthusiast Array
Cheers! No problems so far, some software hiccups which worst case I can reinstall windows for as had to remove and reinstall a bunch of drivers and utilities. Originally Posted by Ribellu Everything should exist fine now
-
12-27-202106:32 PM #45
ROG Enthusiast Array
Swell! I practice not have enough deep dive particular to utilise congenital in presets with any fine tuning to adventure this again, given that information technology's been a mix handbag… Originally Posted by Spicedaddy I used XMP2 but (default SPD settings on Asus boards). Crucial ran at i.1V 4800CL40 and G.Skill (Samsung) running at i.2V 5600CL36.
-
12-27-202106:39 PM #46
ROG Enthusiast Assortment
Sorry to hear that, Resetting CMOS after the update may aid. I ended upwardly getting stuck on d6,d7 and 98 as the graphics card wasn't responding first, then the input devices weren't existence registered, using the mobo hdmi to a different monitor went to bios, updated 0811,, and secureboot and went to windows, so updated graphics driver and switched information technology to graphics carte du jour and gaming monitor. Originally Posted by Louis_Kleiman I have a Z690 Maximus Hero that I bought at launch, but have been waiting until I could go RAM to complete my build. I finally got 32GB (2x16) of Trident Z5 6000 CL40 (all I could find) and finished the machine assembly. I have spent hours playing with settings, flashing and re-flashing the UEFI to version 0811, and cannot boot successfully with more than than 1 stick. Sometimes I tin can get to BIOS (safe manner) with two sticks, but when I just save and restart (no configuration changes), I tin can no longer kicking or POST. I have tried all different combination of sticks and RAM slots, seating and re-seating the RAM and the CPU/cooler -- all to no avail. Default, XMP I, XMP Two -- even so no joy. The machine has been trying to Post for the last hour cycling through various codes and restarting itself, but still no POST with two sticks. I have no burned or blown chips on the MB as far every bit I tin can see. I've been edifice my own machines since 1984 (yes, really), but I take never seen a state of affairs similar this. Whatsoever thoughts on settings to try would really be appreciated.
no issues after that, I did reseat the graphics and memory and gpu once again and that didn't help either till I switched it out to the onboard graphics on post
-
12-28-202102:50 AM #47
ROG Enthusiast Assortment
-
12-28-202105:37 AM #48
ROG Member Array
Glad to hear that it seems to be working for you so far! Originally Posted by maximumrog57 Thanks! No problems then far, some software hiccups which worst case I tin can reinstall windows for as had to remove and reinstall a bunch of drivers and utilities.
Ane interesting affair, on this thread (https://www.reddit.com/r/ASUS/commen...d_in/?sort=new)
dapk1nmasta says: "I'chiliad not sure if anyone has noticed, just comparison the photo of u/JayzTwoCents's working board with a few images of failed boards, it appears the large diode higher up the DIMM slots labeled "150 sixteen?PY" is soldered in contrary polarity (identified past the gray stripe on the correct side of the diode) on the boards that have failed."
Would you be able to check that scrap on your board and have a picture to see if it is in the 'correct' orientation? information technology might exist some testify for his theory.
-
12-28-202105:45 AM #49
New ROGer Array
Mine would not boot with Ram in the A slots.
Pretty certain my code was 53 as well. Was a few weeks back. Sent mine in for RMA, the emailed me back pics of two small-scale bent pins on the USB iii.0 connector. I rejected their quote of over $700 to repair the board because it appears they didn't even check the RAM issue. Running Corsair dominators, 2x16.
I'm impatient, bought the first board pre launch thru Amazon, secured a second from Microcenter that I'm running now. And now this fire run a risk issue? I'one thousand pretty pissed at this point because it seems at BEST I'll have two boards I tin can't trust not to burst into flames and at worst they won't supercede my original lath, I won't trust this new one, and I'll have to buy someone else's lath. I've been buying Asus products for 20 years! Hell my dwelling house server is running a 3770k on a P*Z77-V Pro and I have a Strix Z490 with a 10700k and a Strix Z590 with an 11900k, I thought bumping upwards to the Maximus series would give me even more of the quality I've come to expect from Asus. They seriously need to address this upshot.
-
12-28-202111:54 AM #50
ROG Junior Member Array
I'm nonetheless sure of the bodily source of the problem, only it'southward amazing to me how many similarities at that place are between this story and mine. Do y'all mean the the USB 3.0 connector just below the USB 3.ii connector and higher up the SATA ports? These pins were also bent when I received the board, but initially this seemed to cause no problems. While using the system a twenty-four hour period afterwards (web browsing), information technology shut down and every attempt to commencement it simply resulted in Q Code 53. I've likewise posted this on the related reddit thread, so this is one of the original five-6 reports there rather than another failure to add together to the listing. Originally Posted by 911gt3 Pretty sure my lawmaking was 53 as well. Was a few weeks dorsum. Sent mine in for RMA, the emailed me back pics of 2 modest bent pins on the USB 3.0 connector. I rejected their quote of over $700 to repair the lath considering it appears they didn't even check the RAM issue. Running Corsair dominators, 2x16.
I'one thousand impatient, bought the first lath pre launch thru Amazon, secured a second from Microcenter that I'm running now. And now this fire hazard consequence? I'yard pretty pissed at this point because information technology seems at All-time I'll have two boards I tin't trust non to burst into flames and at worst they won't replace my original board, I won't trust this new i, and I'll take to buy someone else'due south lath. I've been ownership Asus products for twenty years! Hell my domicile server is running a 3770k on a P*Z77-V Pro and I take a Strix Z490 with a 10700k and a Strix Z590 with an 11900k, I idea bumping upwards to the Maximus serial would requite me even more of the quality I've come up to expect from Asus. They seriously demand to address this outcome.
I don't think it'southward actually the aptitude pins, just I could believe that some kind of impact to a specific location of the box could exist causing problems for the board. The employees working RMA are probably not the same that blueprint packaging, simply if they go repeated show of this they might need to accost the packaging itself.
Asus is my first choice for components and will probably keep to be, but there is some room for improvement in regards to their support for enthusiast electronics. If you hear these kinds of reports showing upwards, the response pretty much has to be:
- Automatically escalate whatsoever reports related to fire/smoke/popping sounds to senior management for analysis, and get those affected boards in paw for concrete inspection.
- Later receiving more than one study of a specific failure (Q Code 53 for instance) for a product that has been released in the last xc days, create a task to investigate potential related root causes, and notify the support team of possible trends. RMA for anyone reporting similar circumstances should be about instant without pushing them through many troubleshooting steps.
- Subsequent reports that fit this aforementioned trend should be added to the list and RMA'd as speedily as possible to gather prove and prevent any potential liability from failure of the related parts.
It sounds really enervating, but the costs would really be almost nada for a company of this size to prevent reputation damage (which is happening now even if we all somehow caused this ourselves) or potential legal liability.
lopezeaddelartion.blogspot.com
Source: https://rog.asus.com/forum/showthread.php?127013-ASUS-Z690-Maximus-Hero-Motherboard-Burnt-with-QCODE-53-and-QLED-Orange%2Fpage5
0 Response to "So Tell Me Now and I Wonã¢â‚¬â„¢t Ask Again"
Post a Comment