The PC often gets stuck in reboot Loops

[martine-dee]

Hi,

Something that began to happen in August last year is that PC gets stuck in reboot loops when (re)starting. So, it never restarts on its own, but every (re)start might mean a stressful struggle to get it going. I've posted more about it here (vid included):
https://rog.asus.com/forum/showthread.php?113051-Reboots-and-SATA-drives-not-detected-when-AE-9-is-i...

Except, now that I finally got to the point to take the AE-9 out and never use it again, the box still keeps restarting. So, ultimately it is not AE-9 that causes restarting.

Something else is wrong with the box. Currently, it gets frozen in the 00 state every time before it self-restarts.

What do you suggest doing? I am close to the point of just building a whole new PC fwiw. But if I could pin down the culprit, I'd replace it.

Halp? 😕

[Jesseinsf]

martine-dee wrote:
Hi,

Something that began to happen in August last year is that PC gets stuck in reboot loops when (re)starting. So, it never restarts on its own, but every (re)start might mean a stressful struggle to get it going. I've posted more about it here (vid included):
https://rog.asus.com/forum/showthread.php?113051-Reboots-and-SATA-drives-not-detected-when-AE-9-is-i...

Except, now that I finally got to the point to take the AE-9 out and never use it again, the box still keeps restarting. So, ultimately it is not AE-9 that causes restarting.

Something else is wrong with the box. Currently, it gets frozen in the 00 state every time before it self-restarts.

What do you suggest doing? I am close to the point of just building a whole new PC fwiw. But if I could pin down the culprit, I'd replace it.

Halp? 😕

Even though your memory is not in the QVL list, just means that is has not been tested. I have a 128 GB Corsair kit in my Z390 motherboard and it is not in the QVL list and it works great. Now for your memory, How long from the time you installed the memory to the time is starting acting up?

[martine-dee]

I received notif of a reply, and cannot see the post. I think it is worth mentioning, so...

Even though your memory is not in the QVL list, just means that is has not been tested. I have a 128 GB Corsair kit in my Z390 motherboard and it is not in the QVL list and it works great. Now for your memory, How long from the time you installed the memory to the time is starting acting up?

So, luckily I can trace this record through my posts here. Let me get onto it. So, ... from the beginning (September 2017) I had problems with getting memory modules to work with this mobo (ASUS ROG Strix X299-E Gaming) ever since the beginning. I had 64 GB, Crucial CT4K16G4DFD213. Only three modules were visible, and I rode on 48 GB until sometime in 2019, when I took the step of disassembling everything and reassembling it. That fixed things.

https://rog.asus.com/forum/showthread.php?108687-Strix-X299-E-Intel-i7-consistently-seen-48-GB-out-o...

I installed the current modules on Aug 28, 2019. Initially, they only ran on 2133 MHz, because I was setting the params manually instead of using the XMP profile. With the XMP profile, they started to work well.

https://rog.asus.com/forum/showthread.php?112904-32-GB-RAM-seen-but-not-used-stuck-at-2133-MHz

On September 5, 2019, I got the AE-9. After seating it in, it turned out that I had a bad power cable stuck into it. Upon start, the box went through rapid repeated reboots. Then some SATA drives became invisible, and after that the box started to often need 3 reboots before it started to go. It was never again stable.

So, a damaged mobo and/or PSU is also an option.

However, just about then I also started OC'ing the CPU. So that could be the cause too, either alone or in concert with the microcode. Right now just not OC'ing the CPU, and keeping most BIOS settings at the optimized default seems to maintain stability. It could be that the microcode only reacts badly if the CPU is OC'd. I can run that experiment after I confirm that things are stable without it. I need some 2 weeks for that.

[martine-dee]

By the way, this is unlikely a QVL issue. Recently, I got myself a QVL listed kit (F4-3600C16Q-32GTZR), which yields the very same behavior.

More here: https://rog.asus.com/forum/showthread.php?118771-The-X299-e-gaming-stuck-in-the-00-state-after-3006-...