Gigabyte X570 Aorus Master won't power on - (temporary) solution

Could you please share the link?

https://hardforum.com/threads/the-top-5-worst-motherboards-of-all-time.1939662/

The main link for hardocp is dead as it's closed, but Dan_D and everyone had fits with that board.

I still have it - it's about to be replaced from my wife's gaming system, and will be my new plex server (or something), but once it finally dies, I fully plan on taking it outside, taking a big shit on it, and then lighting the fucking thing on fire.
 
I've written so many motherboard reviews over the last 15 years, I can't possibly remember them all. A few stand out for one reason or another. Unfortunately, it's almost always negative things I remember the most. The GIGABYTE 990FXA-UD7 was one I remember well. Although, I don't remember a whole lot beyond memory compatibility issues and poor responsiveness in the BIOS, I do recall the reaction of GIGABYTE's PR department to the article. That's one where their PR rep called me from China begging me to take the article down so they didn't get fired. There was actual crying on the phone.

I warned that I had no ability to take that article down and that the issue would have to be brought up with Kyle. I also warned that doing so would be a hilariously bad idea. I don't recall what was actually said, but Kyle told the PR rep to basically: "Get bent." That ended our relationship with GIGABYTE as an advertiser for a couple of years. All the GIGABYTE motherboards we reviewed for the following couple of years were purchased by HardOCP. They were not PR samples.

Now, the 990FXA-UD7 was also launched prior to the release of Bulldozer CPU's. All of these motherboards had problems using the older Phenom II CPU's for whatever reason. All of the 990FX chipset boards I reviewed earned negative reviews, but the GIGABYTE 990FXA-UD7 was easily the worst of them. The experiences with this GIGABYTE board were so bad that we elected to stop reviewing AM3 boards altogether until AMD released Bulldozer CPU's. Of course, as lackluster as that was we primarily concentrated on Intel releases from then on out. I did a handful of AMD based reviews (3 I think) all the way up to the release of AMD's first generation of Ryzen CPU's.

It's also worth noting that one of four motherboard reviews I've killed on the test bench was a GIGABYTE AM2 board at the launch of the Phenom processors. It remained the only motherboard that ever caught fire during testing. In my opinion, most GIGABYTE boards of that era were rarely up to scratch with their peers. These days, GIGABYTE builds some great stuff but back then, not so much.
 
Luckily, I have never owned an AMD motherboard from GIGABYTE. In fact, I have had experience with only five GIGABYTE motherboards during my lifetime (so far), and they have all been Intel motherboards with Intel chipsets (the most recent of which is an H170 mini-ITX motherboard from the quad-core Skylake i7 era of 2015). Still, I found faults with that company's implementation of UEFI. After all, what good is the company's UEFI interface's relative flashiness if it actually ends up being recalcitrant in use?

By the way, my first-ever GIGABYTE motherboard purchase was from the days when GIGABYTE was trying to shake out of its reputation as "JUNKABYTE."
 
Last edited:
I've written so many motherboard reviews over the last 15 years, I can't possibly remember them all. A few stand out for one reason or another. Unfortunately, it's almost always negative things I remember the most. The GIGABYTE 990FXA-UD7 was one I remember well. Although, I don't remember a whole lot beyond memory compatibility issues and poor responsiveness in the BIOS, I do recall the reaction of GIGABYTE's PR department to the article. That's one where their PR rep called me from China begging me to take the article down so they didn't get fired. There was actual crying on the phone.

I warned that I had no ability to take that article down and that the issue would have to be brought up with Kyle. I also warned that doing so would be a hilariously bad idea. I don't recall what was actually said, but Kyle told the PR rep to basically: "Get bent." That ended our relationship with GIGABYTE as an advertiser for a couple of years. All the GIGABYTE motherboards we reviewed for the following couple of years were purchased by HardOCP. They were not PR samples.

Now, the 990FXA-UD7 was also launched prior to the release of Bulldozer CPU's. All of these motherboards had problems using the older Phenom II CPU's for whatever reason. All of the 990FX chipset boards I reviewed earned negative reviews, but the GIGABYTE 990FXA-UD7 was easily the worst of them. The experiences with this GIGABYTE board were so bad that we elected to stop reviewing AM3 boards altogether until AMD released Bulldozer CPU's. Of course, as lackluster as that was we primarily concentrated on Intel releases from then on out. I did a handful of AMD based reviews (3 I think) all the way up to the release of AMD's first generation of Ryzen CPU's.

It's also worth noting that one of four motherboard reviews I've killed on the test bench was a GIGABYTE AM2 board at the launch of the Phenom processors. It remained the only motherboard that ever caught fire during testing. In my opinion, most GIGABYTE boards of that era were rarely up to scratch with their peers. These days, GIGABYTE builds some great stuff but back then, not so much.

I also remember that USB devices (keyboard, etc) didn't work in BIOS (I still have a PS2 keyboard for this reason), and the RAID system never, EVER, worked on ANY os.
 
Luckily, I have never owned an AMD motherboard from GIGABYTE. In fact, I have had experience with only five GIGABYTE motherboards during my lifetime (so far), and they have all been Intel motherboards with Intel chipsets (the most recent of which is an H170 mini-ITX motherboard from the quad-core Skylake i7 era of 2015). Still, I found faults with that company's implementation of UEFI. After all, what good is the company's UEFI interface's relative flashiness if it actually ends up being recalcitrant in use?

By the way, my first-ever GIGABYTE motherboard purchase was from the days when GIGABYTE was trying to shake out of its reputation as "JUNKABYTE."

I used to work in a service shop repairing systems. GIGABYTE boards used to be among my least favorite shortly before I became a reviewer. Overtime, their products and reputation have improved. To this day, one of the best motherboards I've ever used was the GIGABYTE X399 Designare EX.

I also remember that USB devices (keyboard, etc) didn't work in BIOS (I still have a PS2 keyboard for this reason), and the RAID system never, EVER, worked on ANY os.

I vaguely recall some of that. It was a huge piece of shit.
 
Got my new DP1.4 cable yesterday--and aside from a markedly better display I've noticed (it's like the color red just jumps out of the monitor, suddenly, and text seems clearer in some cases--colors, details, all better), there's no difference. System is booting fine--no cold boot issues--as those cold-boot problems were solved long ago apparently as I outlined earlier in this thread, fortunately. Wanted to make this post to mark the date of the new cable installation, in case the soft brick happens again. So far so good--no problems. My goal of course is to eliminate all possible problem sources aside from the motherboard itself. The more I think about the soft brick, the cure being the total discharging of the system by removal of the CMOS battery for ~15 minutes or more, the more it seems exactly like a UL electrical circuit override that shuts everything off to protect the system. We'll see. I'll come back here if I soft brick again, and if I don't I'll come back and report that in a couple of months.

I'm also fairly sure that my Club3d DP 1.4 cable I bought last July was faulty--and the trickle voltage on the 20th pin from the monitor building up until the motherboard UL safety circuitry shuts the system down--makes sense...;) Yeah, OK...;) We'll have to see about that...

I want to give massive kudos for this thread, though. If I hadn't read that popping the CMOS battery restored what apparently was a completely dead x570 Aorus Master in this thread I would never have even thought to do that to cure the situation--at least temporarily!

I'll see you guys in a couple of months, either way! The fact that the official Display Port site as I linked in a post of mine above acknowledges bad DP cables that can cause booting issues are a known commodity, gives me some hope that this is the right course. Here's the link, again"

https://www.displayport.org/cables/how-to-choose-a-displayport-cable-and-not-get-a-bad-one/

Here is a portion of the relevant text from the DP/Vesa article:

"As mentioned previously, it is important to avoid low quality DisplayPort cables to prevent unexpected video or audio problems, and sometimes even system power-up problems. Always buy cables from a reputable computer system or accessory brand. Or safer yet, buy a cable that is DisplayPort certified. DisplayPort certified cables are listed here.


Recently VESA has experienced quite a few complaints regarding troublesome DisplayPort operation that ended up being caused by improperly made DisplayPort cables. These “bad” DisplayPort cables are generally limited to non-DisplayPort certified cables, or off-brand cables. To further investigate this trend in the DisplayPort cable market, VESA purchased a number of non-certified, off-brand cables and found that an alarmingly high number of these were configured improperly and would likely not support all system configurations. None of these cables would have passed the DisplayPort certification test, moreover some of these cables could potentially damage a PC, laptop, or monitor. We have not seen problems with the cables supplied by major computer brands, or major computer accessory brands, nor have we seen any problems with any of the cables that have been DisplayPort certified."
 
Last edited:
I see that you are on Windows 10 Pro 2004.
I had lots of similar issues (freezing, huge audio delays, etc) when forced update to 2004.
I would suggest going back to 1909.

On second thought, ALL of my issues started after update to 2004 (cold misboot as the most nauseating of them) but this could be just a coincidence.

^^^

This is an important point to highlight. I have this same X570 board and it ran flawlessly up until one of the 2004 updates. Board is pretty max'd out with connections with 2x NVME drives, PCIE boot drive, and 2080TI plus a bunch of USB stuff connected. And then suddenly after one of the 2004 updates it would not wake from hibernate/sleep. Had the same intermittent cold boot symptom as well. It was a known issue to Microsoft related to network drivers (Intel I211 in this case) and was listed on the Windows status page at the time. Couldn't believe drivers were a factor but updated them and the problem went away. That was sometime in the May/June timeframe.

Now, last week, once again, there's another 2004 update causing what appears to be random blue screens which started the day after the forced update. Just wiped my install to roll back to 1909 which I'm using now and it's perfectly stable; sleeps, and no blue screens. Note that the 2004 update was never 'approved' for updating my system back in May as in it never became available automatically as an update. But I wanted to see the changes and used the manual method of updating and bypassing MS's supposed AI-based config validation. Can only say there is a reason why Windows 1909 is still around even with the newer 2004 (and older 1903 I think also). There's a number of issues with 2004 and hardware, and MS knows this. If anyone is using 2004 I'd rule it out before suspecting sudden hardware issues.

(One more comment one poster talks of cold boot problems after installing a new CPU: intermittent cold boots are a CPU related symptom as well - could be voltage, etc., or the CPU itself...)
 
^^^

This is an important point to highlight. I have this same X570 board and it ran flawlessly up until one of the 2004 updates. Board is pretty max'd out with connections with 2x NVME drives, PCIE boot drive, and 2080TI plus a bunch of USB stuff connected. And then suddenly after one of the 2004 updates it would not wake from hibernate/sleep. Had the same intermittent cold boot symptom as well. It was a known issue to Microsoft related to network drivers (Intel I211 in this case) and was listed on the Windows status page at the time. Couldn't believe drivers were a factor but updated them and the problem went away. That was sometime in the May/June timeframe.

Now, last week, once again, there's another 2004 update causing what appears to be random blue screens which started the day after the forced update. Just wiped my install to roll back to 1909 which I'm using now and it's perfectly stable; sleeps, and no blue screens. Note that the 2004 update was never 'approved' for updating my system back in May as in it never became available automatically as an update. But I wanted to see the changes and used the manual method of updating and bypassing MS's supposed AI-based config validation. Can only say there is a reason why Windows 1909 is still around even with the newer 2004 (and older 1903 I think also). There's a number of issues with 2004 and hardware, and MS knows this. If anyone is using 2004 I'd rule it out before suspecting sudden hardware issues.

(One more comment one poster talks of cold boot problems after installing a new CPU: intermittent cold boots are a CPU related symptom as well - could be voltage, etc., or the CPU itself...)
I am using 2004 since it was released and haven't experienced and issues.
 
  • Like
Reactions: WaltC
like this
^^^

This is an important point to highlight. I have this same X570 board and it ran flawlessly up until one of the 2004 updates. Board is pretty max'd out with connections with 2x NVME drives, PCIE boot drive, and 2080TI plus a bunch of USB stuff connected. And then suddenly after one of the 2004 updates it would not wake from hibernate/sleep. Had the same intermittent cold boot symptom as well. It was a known issue to Microsoft related to network drivers (Intel I211 in this case) and was listed on the Windows status page at the time. Couldn't believe drivers were a factor but updated them and the problem went away. That was sometime in the May/June timeframe.

Now, last week, once again, there's another 2004 update causing what appears to be random blue screens which started the day after the forced update. Just wiped my install to roll back to 1909 which I'm using now and it's perfectly stable; sleeps, and no blue screens. Note that the 2004 update was never 'approved' for updating my system back in May as in it never became available automatically as an update. But I wanted to see the changes and used the manual method of updating and bypassing MS's supposed AI-based config validation. Can only say there is a reason why Windows 1909 is still around even with the newer 2004 (and older 1903 I think also). There's a number of issues with 2004 and hardware, and MS knows this. If anyone is using 2004 I'd rule it out before suspecting sudden hardware issues.

(One more comment one poster talks of cold boot problems after installing a new CPU: intermittent cold boots are a CPU related symptom as well - could be voltage, etc., or the CPU itself...)
Regarding the cold boot bug: I had that bug without even using Windows - I was using Linux (Devuan) when it happened, and I never used suspend/hibernate. So I wouldn't relate that bug to any of those factors.
 
Haven't experienced the Issue in quite a while. Im starting to think that maybe the issue was caused by other Devices plugged in to my electric circuit. Because I always had the Problem that my Monitor would flicker or even turn off and on when i for example turn off the fan on my desk. So I thought that maybe if I do that in the wrong moment while shutting down my PC that could have caused the BIOS to go corrupt. However I had that Problem already when I was living somewhere else and had a completely different PC and I never experienced the No Power Problem back then. So I guess it's unlikely that this is the cause. Also updated Windows to 2004 so maybe that's related. But I guess its more likely that nothing is fixed and I was just lucky the last couple of weeks xD
 
Haven't experienced the Issue in quite a while. Im starting to think that maybe the issue was caused by other Devices plugged in to my electric circuit. Because I always had the Problem that my Monitor would flicker or even turn off and on when i for example turn off the fan on my desk. So I thought that maybe if I do that in the wrong moment while shutting down my PC that could have caused the BIOS to go corrupt. However I had that Problem already when I was living somewhere else and had a completely different PC and I never experienced the No Power Problem back then. So I guess it's unlikely that this is the cause. Also updated Windows to 2004 so maybe that's related. But I guess its more likely that nothing is fixed and I was just lucky the last couple of weeks xD
have you changed/used/stop used display port cable? Have you changed USB ports where you connect peripherals? I've noticed that on X570 (as well as on my new B550) top 4 USB ports still provide power to keyboard/mice when PC is switched off -- I avoid using them as want to sleep w/o red illumination like in brothel :)
Windows version is not related. There are GNU/Linux users in this thread:)
 
>> 4 USB ports still provide power to keyboard/mice when PC is switched off -- I avoid using them as want to sleep w/o red illumination like in brothel :)

Turn on "ERP" in the BIOS.

.
 
>> 4 USB ports still provide power to keyboard/mice when PC is switched off -- I avoid using them as want to sleep w/o red illumination like in brothel :)

Turn on "ERP" in the BIOS.
Thanks for the advice, but it would prevent WakeOnLAN functionality.. However during Covid WFH it is not needed:)
 
This thread is what comes up in google if searching for aurus motherboard that won't power up... just want to describe my experience for future searchers, although it's a bit buried in offtopic stuff now.

Aurus Pro Wifi TRX40, 3700 cpu (32 core), been working for months on Linux. Suspended and couldn't power up again at all, presented like no power or a dead psu. I thought it was a goner.

What eventually solved it was unplug power, remove cmos battery, short the clear cmos link for 30s and leave it like that for 30 mins. Variations on that without the 30 minutes off without battery did not help at all.

If it feels dead and unresponsive, don't give up try the above. it started into a default bios immediately on pressing power button after that. Good luck!
 
Aurus Pro Wifi TRX40, 3700 cpu (32 core), been working for months on Linux. Suspended and couldn't power up again at all,

This thread has been focused on the X570, but you are confirming the same failure on a Threadripper model mobo.
So it would appear that GB has a design problem that crosses over to different models, it's not just the X570 Master.

.
 
This thread has been focused on the X570, but you are confirming the same failure on a Threadripper model mobo.
So it would appear that GB has a design problem that crosses over to different models, it's not just the X570 Master.

.
And generations, as I've said earlier in the thread, it effected x370 boards as well. Just read through the beta bios thread on gigabyte's forum (AMD motherboard, am4 subforum). There's a link to the wayback machine in the first post–a lot of the content was lost when the thread was accidently deleted.
 
And generations, as I've said earlier in the thread, it effected x370 boards as well. Just read through the beta bios thread on gigabyte's forum (AMD motherboard, am4 subforum). There's a link to the wayback machine in the first post–a lot of the content was lost when the thread was accidently deleted.

Yep. Back on page one of this thread, I said I've seen this problem on GB boards 20 years ago.
My point above is really to point out that as far as current GB mobos, it's not just the X570.

.
 
Aorus Master Rev 1.1 board, running absolutely stock except I enabled my XMP profile. Latest BIOS (F22).

Built this system two weeks ago, and today encountered this bug after powering the system down and then attempting to boot again.
Clear cmos button on the backplate and the power button on the board light up, but as soon as I hit either the power on button on the motherboard or the one from my case, all lights go out. I remember hearing a vague coil-whiny sound, which I first thought came from my PSU, but after closer inspection came from somewhere on the board behind the GPU.

First I thought it must be my power supply that went poof, but I hooked up a PSU that I knew was working, same behaviour.
Then I thought the board must be dead. Luckily, I found this thread, and after taking out the GPU and taking out the cmos battery for a minute and popping it back in, the board boots again.

Very annoyed by this bug, which means that every power off could trigger this. :(

For completeness, my full system:
CPU: Ryzen 3900X (seems pretty common in this thread?)
Board: Aorus Master X570 Rev 1.1
GPU: MSI Geforce RTX 2070 Super (connected via DP to an LG GL850 monitor)
RAM: 32 GB Ripjaws 3600 mhz RAM
PSU: Corsair RMX 850
Cooling: Kraken Z73 AIO
Drives:
2 NVMe drives, both Samsung Evo Plus 970
2 SSD's, one Samsung, one Crucial
2 regular WD HDD's
 
Last edited:
Hi guys, another one with a similar problem this time with a B550-Aorus Pro revision 1(I read there is going to be an revision 2 for the motherboard too, could Gigabyte fix this issue?), well heres my story: I bought a new pc with this board and after just a few weeks won't turn on(no post, lights, nothing) so I went to the shop and they told me they changed the motherboard, one week later and same thing happened. I googled found this forum and tried the tip remove battery and clear cmos with a screwdriver, it worked!, But now I'm afraid about this problem happening again, how many times can you "revive" the board without really dying anyone knows?

I'll try to isolated the problem but at the moment I'm suspicius about when I connect a second monitor(a samsung-tv hdmi to the displayport) as both times happened next morning after gaming on windows then disconecting restarting to linux, worked fine, (I did use acpi-cpufreq powersave mode on the cpu) shutdown, going to bed and next morning didn't POST, "dead" again.

Could be many many things though, I'll share anything I find here.

Like others this is my full system specs:

CPU: Ryzen 3900X
Board: Aorus Pro B550 Rev 1
GPU: Gigabyte Geforce RTX 2080 Super
FIRST MONITOR: Acer 24' connected via HDMI
SECOND MONITOR: Samsung 4k-tv connected via DP adapter with a HDMI cable
RAM: 16 GB Hyperx Fury 3200 mhz(XMP)
PSU: EVGA G5 850w (eco switch on)
Cooling: amd stock
Drives:
1 M2-SSD drive, Samsung Evo 860
2 regular Seagate HDD's
 
Last edited:
Could it be your Kraken AIO whining?
No it is not. I know because I have that same "coil-whining" sound all the time with my motherboard even as I'm writing this. (maybe some LED? but turning off on rgbfusion sadly doesn't fix it)
 
Last edited:
Hi guys, another one with a similar problem this time with a B550-Aorus Pro revision 1(I read there is going to be an revision 2 for the motherboard too, could Gigabyte fix this issue?), well heres my story: I bought a new pc with this board and after just a few weeks won't turn on(no post, lights, nothing) so I went to the shop and they told me they changed the motherboard, one week later and same thing happened. I googled found this forum and tried the tip remove battery and clear cmos with a screwdriver, it worked!, But now I'm afraid about this problem happening again, how many times can you "revive" the board without really dying anyone knows?

This is on a new custom computer?

To me that is an unacceptable problem on a new computer.
Replacing with the same mobo hasn't helped so I'd tell them to replace it with an ASUS or MSI board.

Hopefully you are within your return window to give them the whole machine back for a refund if you need to.


ETA: It's not causing this problem, but turn off ECO mode on the PSU. Other users report issues with it.

.
 
Last edited:
ETA: It's not causing this problem, but turn off ECO mode on the PSU. Other users report issues with it.
I'll do it, thanks

This is on a new custom computer?

yes, why? I'd be happy with the computer if I'm able to fix this annoying cold boot problem =) everything else works great
 
Last edited:
yes, why? I'd be happy with the computer if I'm able to fix this annoying cold boot problem =) everything else works great
This could cause problem when you or your family member urgently need your PC. Your post seriously demotivated me as I also have replaced my failed X570 with Aorus B550 Pro. I'm considering not to wait for a doomsday and buy replacement from other vendor (Asus/Biostar). 230 EUR is a big price but it doesn't cost mental health. Even before your message I already have been waiting for a treason every time switching my PC on (dislike all other MBs I previously owned, B550 pro has a half a second delay between pressing the power button and lighting it on.)
 
This could cause problem when you or your family member urgently need your PC. Your post seriously demotivated me as I also have replaced my failed X570 with Aorus B550 Pro. I'm considering not to wait for a doomsday and buy replacement from other vendor (Asus/Biostar). 230 EUR is a big price but it doesn't cost mental health. Even before your message I already have been waiting for a treason every time switching my PC on (dislike all other MBs I previously owned, B550 pro has a half a second delay between pressing the power button and lighting it on.)
I understand, well you could try the new "revision 2" maybe it is better or if you want another brand I also liked the Asus B550-F and the MSI B550 Tomahawk
 
I would not holdout hope that this will be fixed, it's been going on a very long time.

I like MSI boards, I have both the B450 Tomahawk and the X570 Tomahawk.
Both of them have been great, no cold boot or any other issues.

I do like that ASUS B550-F though too.

If you let this slide for a while, the shop won't want to fix it.

.
 
HI, I've been following this post for some time after developing this issue on my GB Aorus Elite X570 running Ryzen 7 3700x and 32GB of patriot Ram under a windows 10 environment. I'm currently on Bios F21 but the issue arose at some point late into running F20. Now I made no changes to Bios F20 since I built this PC other than the initial setup of which I enabled XMP and turned on secure boot. I'm running a Seasonic Focus gold PSU and am 100% sure as others have said its not a power issue. My monitor is on a HDMI from an Asus 1060 OC 6GB so its not a display port issue but I've got to ask just to satisfy my curiosity how many people that have this issue are running a wired Corsair RGB keyboard or mouse?
 
how many people that have this issue are running a wired Corsair RGB keyboard or mouse?

Not me, first time it happened I got a usb mars-gaming-rgb mouse connected on the front on the case, but second time I had a logitech usb non-rgb on the back-IO but I'm also curious about what can be something we all have in common, like xmp? Has anyone had this power issue without never updating the BIOS? ( before AMD AGESA ComboV2 1.0.0.2), using Linux only? (I use dual boot linux and win) etc, we should try =)
 
Last edited:
HI, I've been following this post for some time after developing this issue on my GB Aorus Elite X570 running Ryzen 7 3700x and 32GB of patriot Ram under a windows 10 environment. I'm currently on Bios F21 but the issue arose at some point late into running F20. Now I made no changes to Bios F20 since I built this PC other than the initial setup of which I enabled XMP and turned on secure boot. I'm running a Seasonic Focus gold PSU and am 100% sure as others have said its not a power issue. My monitor is on a HDMI from an Asus 1060 OC 6GB so its not a display port issue but I've got to ask just to satisfy my curiosity how many people that have this issue are running a wired Corsair RGB keyboard or mouse?
Wired Logitech G19 keyboard and wired Logitech G5 mouse here.
 
Wired Logitech G19 keyboard and wired Logitech G5 mouse here.
me too, both wired logitech keyboard and wired logitech mouse

cold_steel when was your last POST failure? only twice? I used sleep a few times yesterday and today without any problem, but I'm not sure about trying to poweroff again :D
 
me too, both wired logitech keyboard and wired logitech mouse

cold_steel when was your last POST failure? only twice? I used sleep a few times yesterday and today without any problem, but I'm not sure about trying to poweroff again :D
Me personally still has only happened twice - about a month apart. Knock on wood it’s been a while. I do remember disabling sleep functions in Windows after the last time. I also never updated past BIOS F11 as I wanted to see if a later BIOS actually fixed the root issue or not before updating.
 
Me personally still has only happened twice - about a month apart. Knock on wood it’s been a while. I do remember disabling sleep functions in Windows after the last time. I also never updated past BIOS F11 as I wanted to see if a later BIOS actually fixed the root issue or not before updating.
Thank you ;) It also seems like F11 is the last bios not using agesa ComboV2 1.0.0.2. Now I'm curious if I also should go back in my BIOS
 
HI, I've been following this post for some time after developing this issue on my GB Aorus Elite X570 running Ryzen 7 3700x and 32GB of patriot Ram under a windows 10 environment. I'm currently on Bios F21 but the issue arose at some point late into running F20. Now I made no changes to Bios F20 since I built this PC other than the initial setup of which I enabled XMP and turned on secure boot. I'm running a Seasonic Focus gold PSU and am 100% sure as others have said its not a power issue. My monitor is on a HDMI from an Asus 1060 OC 6GB so its not a display port issue but I've got to ask just to satisfy my curiosity how many people that have this issue are running a wired Corsair RGB keyboard or mouse?
I have both a wired Corsair keyboard and mouse. My keyboard is the K70 (red only) and the mouse is RGB. Don't think it's anything to do with either though. I went 7 months before the issue started for me and it's been sporadic since February.
 
I have both a wired Corsair keyboard and mouse. My keyboard is the K70 (red only) and the mouse is RGB. Don't think it's anything to do with either though. I went 7 months before the issue started for me and it's been sporadic since February.
Interesting I ran a GB B450 Aorus Elite board with an OC Ryzen 1700X up until a few months back without any issues at all, I then swapped to the X570 Aorus Elite (XMP & secure boot enabled same as on the B450) and a Ryzen 7 3700X everything else was the same and yet I've only noticed this issue the last few weeks. I asked about the Corsair gear as it stuck in my mind that after an iCUE update that sometimes my keyboard would remain RGB active even though the PC had been shut down (through Windows but still powered at plug), starting the PC back up and shutting it back down again would resolve this. Question is why are some of us not seeing this, others seeing it sporadic and others like myself now seeing it virtually every time I try to boot? I have noticed that If I actually keep pressing the power button on the case with a second or so in between presses after about the 10-15th time it will fire up. Obviously I've had a multimeter on the case button even though the case is fairly new just to rule out the button itself.
So following a FMEA are we all running Nvidia cards or are some of us seeing this with AMD cards? Also drive wise what are we using? I'm running a couple of Adata XPG SX8200 Pro M.2 SSD's in a non raid format, there has to be a common element somewhere.
 
Last edited:
Also drive wise what are we using? I'm running a couple of Adata XPG SX8200 Pro M.2 SSD's in a non raid format

To be honest, I don't think it is related to storage and more to "Aorus" branding (570 and b550 problems) Hoping people here keeps sharing if this power issue is improving or getting worse with time. Me personally I just upgraded to the latest b550 bios which includes some agesa changes, don't want to give up on gigabyte so soon, we'll see.

Edit: I do have the "whiney-coil sound" which could also indicated some kind of electrical problem, who knows.
 
Last edited:
Update: I was wrong, I think I found what was causing that annoying high-pitch sound! (whiney-coil I called it before) It is some kind of electrical interference with my old Seagate HDDs, when using only the m2 samsung is not happening and it is perfecty usable in an open case close to you, (there is an almost inaudible and now low sound if you put your ear really close though, but maybe that's with every modern pc?) Would this Aorus-electricity-thing be related to our "morning cold boot"? And yes, I'm very sensitive to sound :D
 
Last edited:
Update: I was wrong, I think I found what was causing that annoying high-pitch sound! (whiney-coil I called it before) It is some kind of electrical interference with my old Seagate HDDs, when using only the m2 samsung is not happening and it is perfecty usable in an open case close to you, (there is an almost inaudible and now low sound if you put your ear really close though, but maybe that's with every modern pc?) Would this Aorus-electricity-thing be related to our "morning cold boot"? And yes, I'm very sensitive to sound :D

I was sensitive to high-pitched coil (and old tube TVs) whine when I was younger. Don't hear it much anymore these days. :)

Yes, it's common for electronics to have a coil whine like that. Coils and transformers will hum or "sing" like that sometimes.
The pitch is related to the waveform or switching frequency of the power running through it.

If you are near a big power company transformer outside, sometimes you'll hear the 60 cycle hum. With computers it's more
of a high-pitched whine because of the switching power supplies. Video cards seem to do that a lot.

While that sound can be annoying, I can't think of any reason it would be related to the cold boot issue.

.
 
@

I'll try it this weekend. so just to be clear, I need to throw the SB switch to the upper "2" position on the board? I have F11 installed on my current BIOS (position 1). If i toss the board into single bios mode will it wipe my second, factory spec bios? Or will it just sit there? Can I toggle between the BIOS profiles while in single bios mode? Or is that exclusive to dual bios being enabled?

Also, to preserve my test results, the only other thing I have done is replace the CMOS battery with a good energizer one. If I swap to single BIOS mode I WONT EFI flash to F20 until I am damn well sure that its fixed, or until it happens again while on my current settings in single bios mode.


Checking in, Just had the dead cold boot this morning, usual process fixed it. This was the first time since July 6th, so a little under 2 months, but switching to single BIOS mode did not resolve.
 
Back
Top