Overclock.net banner

[Solved] Gigabyte AX370 Gaming 5 died spontaneously in the night?

15K views 30 replies 9 participants last post by  Colordude 
#1 ·
I haven't even changed any bios settings or any hardware for several days now. Last night, I shut my computer down, and this morning, I hit the power button- nothing.
My motherboard is less than 2 months old, and has been working wonderfully since then, with just minor complaints about ram compatibility, and I'm not a huge fan of the BIOS layout.

As far as I know, there wasn't a power outage overnight, and my computer is plugged in via a UPS, so voltage fluctuations shouldn't cause any problems unless they were REALLY bad.

Took the side panel off, and the power light on the motherboard isn't even on. Unplug everything, press power button, wait several hours, still doesn't work upon re-connection.
mad.gif

Yes, the PSU switch is on.
I've tested the PSU using the "short the green wire to black" method, and it turns on, I can hear my disk drive / hard drives spin up.
Tested PSU with psu tester, all rails seem fine.
I've tried Resetting the BIOS, even though that shouldn't make a difference, since the power light isn't even lit.
I've tried switching the the backup BIOS, just in case, still no difference.
I tried it with the Video card disconnected
Tried with the NVMe drive disconnected
Tried again with EVERYTHING disconnected from the motherboard but the 24-pin, the 8-pin, and CPU fan.

I don't have any ideas what to do now, except take the motherboard out, and try it bare on a table.
Is there any chance my Motherboard really has spontaneously died overnight?
 
See less See more
1
#2 ·
Pull the power and pull the CMOS battery for 5 minutes. It will be fine. The board basically bricks itself upon shutdown randomly. The red power LED goes out on the mobo. Typical issue with these Gigabyte X370 boards. Gigabyte can never get their BIOS right.
 
#3 ·
Quote:
Originally Posted by SLK View Post

The board basically bricks itself upon shutdown randomly. The red power LED goes out on the mobo. Typical issue with these Gigabyte X370 boards. Gigabyte can never get their BIOS right.
Lol, seriously? That's terrible. I was totally set on a Gaming 5 board for my next build, but this is incredibly disconcerting.
 
#4 ·
Gigabyte still can't figure out how to keep a board from boot looping either (Since the Z77 series). I replaced my 4 sticks of Team Dark memory with Corsair Dominator ON THE QVL LIST and let the boot loops commence. Wouldn't post past 2133mhz with bios F5. I got burnt so many times by Gigabyte, I am done.
 
#5 ·
Quote:
Originally Posted by SLK View Post

Pull the power and pull the CMOS battery for 5 minutes. It will be fine.
Huh, haven't tried taking the CMOS battery out yet. Would have thought the normal BIOS reset would have worked. Will do so and reply back in 10 minutes or so.
 
#6 ·
Quote:
Originally Posted by SLK View Post

Pull the power and pull the CMOS battery for 5 minutes. It will be fine. The board basically bricks itself upon shutdown randomly. The red power LED goes out on the mobo. Typical issue with these Gigabyte X370 boards. Gigabyte can never get their BIOS right.
...Yup that fixed it!

Not incredibly comforting, no. The only complaint I had about the board before now was that I wasn't a fan of the GUI used in the bios, but if this is a thing that happens with any frequency whatsoever, it definitely drops my opinion a few notches.
 
#7 ·
Gigabyte hasn't even acknowledged the issue yet. My theory is that when this board pulls a code 56 on the diag LED, it will potentially shut down in a bricked manner. So far I noticed the new version of Corsair Link and HWinfo64 can cause this issue.
 
#8 ·
Quote:
Originally Posted by SLK View Post

Gigabyte hasn't even acknowledged the issue yet. My theory is that when this board pulls a code 56 on the diag LED, it will potentially shut down in a bricked manner. So far I noticed the new version of Corsair Link and HWinfo64 can cause this issue.
Hmmm, I do use HWinfo64, but isn't code 56 "Invalid CPU type or speed"?

How on earth could HWinfo64 cause that?

EDIT: If I experience it again, I may look into trying to narrow it to be actually caused by that. If it is, perhaps it's caused by HWinfo64 doing something not quite right, or the mobo not handling it right? There's a lot of safety options in it that I may look into if this happens again.
 
#10 ·
Hmm, mine doesn't seem to go to '56' just by a load of HWinfo64.
Not saying it always doesn't, but it didn't in the 2 times I tested it.

In fact, mine is showing '24' at the moment, which the manual doesn't even list.....
 
#11 ·
Dang, it happened twice just today. I'm going to try disabling HWInfo64, and seeing if It prevents it for happening, since I normally have it run on startup for my rain-meter gadgets to hook into...
 
#12 ·
Hi

Thanks a lot for this thread- I found myself in the same situation.
I JUST replaced my MSI B350 tomahawk since it bricked itself during bios flash, and thought I'd grab a dual bios board.
While installing my watercooling I accidentally spilled some on it.. oh the horror. But I dried everything and it was fine for a few days.
Come home today after work and it's dead. No lights, nothing.
Luckily, a few minutes without battery and I'm back in business! THANKS!

Did you ever find out what caused it? I uninstalled HWINFO in case that was the culprit.
 
#13 ·
Quote:
Originally Posted by Mawrtin View Post

Hi

Thanks a lot for this thread- I found myself in the same situation.
I JUST replaced my MSI B350 tomahawk since it bricked itself during bios flash, and thought I'd grab a dual bios board.
While installing my watercooling I accidentally spilled some on it.. oh the horror. But I dried everything and it was fine for a few days.
Come home today after work and it's dead. No lights, nothing.
Luckily, a few minutes without battery and I'm back in business! THANKS!

Did you ever find out what caused it? I uninstalled HWiNFO in case that was the culprit.
There is a good chance that it's caused by HWiNFO64, or similar programs. I've been testing to try and prove that.
So far it has not happened since I disabled HWiNFO64 from starting on boot, and have not had it happen yet.
However, I have launched HWiNFO64 once during that, and it still booted fine upon next boot.
I'm planning on waiting another several days, then going back to HWiNFO64 and see if the symptoms return. If I can pin down reliably that that's causing it, I may play with it's settings, as it's got a lot of advanced settings that access things differently or more conservatively just to try and prevent problems like this.

TL;DR: Likely HWiNFO64 or similar, but no proof yet.
 
#15 ·
Quote:
Originally Posted by jopy View Post

welp this just happened to me, thank god for this thread, will uninstall HWiNFO64 and observe if my pc will still soft brickx, reporting back in a few days
Yup, I haven't had any issues at all since removing HWiNFO64, but I'm planning on reinstalling it tomorrow, and see if my problems start back up again.....
 
#17 ·
Quote:
Originally Posted by Mawrtin View Post

Hey, just wanted to chime in and inform that I haven't had this issue since I uninstalled hwinfo. It's a shame, I really like sending values to rivatuner
frown.gif
I just want to chime in that I HAVEN'T had this problem jet after re-installing HWiNFO64, but that isn't really enough to base anything on, but we'll see.....
 
#18 ·
Quote:
Originally Posted by 1n5aN1aC View Post

I just want to chime in that I HAVEN'T had this problem jet after re-installing HWiNFO64, but that isn't really enough to base anything on, but we'll see.....
maybe its just the case of badly written micro code for all the current bios,
after flashing new bios, better be on the safe side and do a cmos reset.
 
#21 ·
Quote:
Originally Posted by Mawrtin View Post

I reinstalled hwinfo and it was okay for a few days but now it died again. Removing battery etc solved it, thankfully.
I'll be using aida instead now. It's a shame, I like hooking into rivatuner but hey, gotta fill that 2nd monitor with something I guess.
I've re-installed HWiNFO64, and haven't had any problems yet for about a week, but it was the new version, so perhaps that contains the fix?
 
#24 ·
I have an Aorus Gaming 5, until last weak it works fine with my Patriot Memories, Profile 3200Mhz, but since last weak they no longer work at 3200Mhz, only 2133 (default settings), I tested it on another motherboard and the memories are okay, already Tried everything, reset bios, etc, But the problem persists, I tried other memories and none works with the profile, and also does not allow to change any memory configuration, if trying the motherboard goes into loop and does not start more, I believe it is a problem in the memory controller, but still I'm not sure what's happening???
mad.gif
mad.gif
mad.gif
mad.gif
mad.gif


Forgive my English by google...
tongue.gif
 
#26 ·
Quote:
Originally Posted by jopy View Post

lol the installer version v5.52 bricked my mobo within 4 days of installation.
just going to stick with the portable version for now
By bricked you mean it won't boot into LiveUSB Linux from Backup BIOs?

Or "soft-bricked" as in your windows doesn't work at all? Or maybe soft-bricked as in it doesn't boot into Main BIOS anymore?

So many people using the word "bricked" for Gigabyte X370 boards that I am unsure of what it means anymore.

I had the power button thing once after a bad overclock but I just flashed the Main BIOs from the backup BIOs. No big troubles.
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top