Stuck in reboot cycle

turkeyinabox

Prominent
Sep 1, 2017
10
0
510
Speccs:
Motherboard: ASUS ROG STRIX X299-E GAMING - ATX / X299
CPU: Intel Core i7-7820X
Memory: 2 x Corsair Vengeance LPX for Intel 200 Red - 16GB (2x8GB) / 4333MHz / DDR4 / CL18 / CMK16GX4M2E4333C19R (4 memory modules in total)
Graphics Card: ASUS ROG STRIX GeForce GTX 1080 8GB GAMING (STRIX-GTX1080-A8G-GAMING)
PSU: EVGA PowerSupply (PSU) SuperNOVA G2 850W
Hard Drives: 3 SSD, 2 standard. 120GB-2TB


My computer crashes then enters an endless reboot loop until i disconnect the PSU.
The reboot loop triggers every 3 seconds or so, so the system has no chance to boot properly.
Everything seems to fire up but then abruptly power shuts causing a new boot cycle.
I have tried a lot of things clearing CMOS Bios. Removing individual HW components, i.e grapics card, all hard drives, fans and yeah pretty much everything but the issue persists. I also swapped out my PSU but the issue showed up again.
So i'm down to debugging the Motherboard and/or the CPU. I've removed and remounted the CPU once already and saw no obvious faults. i've checked the tempratures of the GPU and CPU etc and it's all good in between 30-40*C degrees with no sign of increasing.
If i leave the computer be for a while i.e (hours) i usually can boot it up and get into windows briefly before it crashes again and the short reboot cycle starts.
it's like it managed to charge up overtime which led me to believe it was the PSU at first but turned out to be false.

I had the computer up and running before without seemingly and issues for a few days then it stated crashing all of the sudden one day.

I've reverted back to default bios settings so there isn't any real overclocking going on.

I'm really stuck at this point.
As i've seen no overheating issues with the CPU and i've even remounted it, i suspect there's something wrong with the motherboard, the strange thing is that it's brand new. All other components as well...

I saw there was a new bios update and i even managed to install it before my computer started the reboot cycle again. But it didn't seem to change anything i.e shortly after my computer crashed again and entered the reboot cycle.

Please help..

//Erik
 

turkeyinabox

Prominent
Sep 1, 2017
10
0
510


Tried that before i.e booting with only 1 memory stick or no memory, but it was still shutting down and rebooting.
I booted it up today and got a HW crash shortly after but then i managed to boot it up in safe mode with network and it seems to be stable for now i.e haven't crashed yet but might just be a matter of time.
Tried to install some new drivers but not allowed to do much in safe mode only manage to get graphics drivers updated and some other minor driver but i doubt it will make a difference.

I will try to upload some minidumps from a crash when the computer actually boots and gets blue screen, i'll get the one from today, not sure if these crashes are the cause of my reboot cycle behavior but it seems likely.
Some short info from minidump:
Crash: ntoskrnl.exe
Cause: hal.dll - Caused by driver.
Code: 0x00000124
File version: 10.0.15063.502
Build: WINBUILD.160101.0800
Major Version: 15
Minor Version: 15063

Here is a link to the full minidump and i also included another dump from a few days ago:
minidumps
 

turkeyinabox

Prominent
Sep 1, 2017
10
0
510


Hi Kasper, I have 4 8GB ram sticks in total, what i've tried is to remove all of them computer still entered boot loop. I put 1 back in still entered boot loop. I could run some tests again possibly but my hopes aren't high.

Some update, i shut down safe mode and booted normally to install some drivers and diagnostics programs.
Manage to install the drivers and was going to verify my CPU before doing a reboot so i started the newly installed intel diagnostics tool to check if it could find anything wrong with my CPU. As soon as i booted the program the computer shut down i.e crashed. Could be coincidence but seems fishy.
What's more is that it didn't enter the normal reboot loop, after the crash i just shut off and stayed off.
I've tried to boot again but now it shuts down more or less immediately i.e in less than a second.

Gonna let it rest for a bit and see if it can boot up later like before or if it's totally given up now. Still lean towards it being the motherboard or CPU that's the issue.
 

turkeyinabox

Prominent
Sep 1, 2017
10
0
510


Hi again Kasper.
I'm pretty sure it's not the memory causing issues, i pulled out all memory and hard drives. cleared CMOS for the 54th time. Then i reinserted a single memory stick and connected only my Windows SSD.
I manage to boot up and have it working for an hour or so then pooff sudden crash/powerloss and computer entered the reboot cycle again as usual.
It behaves so strange it's like it's charging up when i leave it alone then running out of power, or maybe there's some component overheating but i've looked and the temperatures and see nothing out of the ordinary unless there' so small component failing somewhere.
They way it seems to work is if i leave it off for a while and come back it manage to boot up after a few tries the it can go for a little while before sudden shutdown or blue screen. Then it tries to reboot but fails but it seems to do it gradually, first reboot maybe fails after 8 seconds then it's 6 seconds, 4 seconds and down to barely any boot time.

Same applies if i just wait a few minute then maybe i can boot for 15 seconds then it goes down to 13 sec etc..
So it gradually gets better the more i leave it be.
This seems to indicate some kind of overheating and component failing right ?
Or can it behave like this is the CMOS battery is running low or is faulty somehow ?

When i had the uptime iI ran intels CPU diagnostics tool and all tests passed.
I didn't try to burn-in test or whatever it's called because it was going to run for 2 hours and i highly doubt my computer will work that long.

I lean toward possibly motherboard issue but i have no way to verify it... and it's not like it's cheap just to buy a new one considering it needs support for 2066 porcessor and memory that are mean't to run on over 4ghz when overclocked.
So i need to possibly try to return it and get a new one unless anyone knows how to run some tests on it ?

Any know if there's something else i can do to narrow this down or debug further ?
 

turkeyinabox

Prominent
Sep 1, 2017
10
0
510


hi again kasper, as i wrote in my earlier posts yes i've tested with swapping ram sticks, swapping slots, booting with 1 hard drive already but it made no difference. I have another GPU i can test with but i've kind of already ruled out the graphics card since it reboots even when there's no graphics card connected.
 

turkeyinabox

Prominent
Sep 1, 2017
10
0
510


As posted earlier i've alredy swapped hardrives and removed all of them and issue persists.
 

turkeyinabox

Prominent
Sep 1, 2017
10
0
510


Read my original first post i pretty much outlien it all there. I think i've tried everything except replacing Motherboard and CPU at this point.
Here's a snipped form my original post:
"I have tried a lot of things clearing CMOS Bios. Removing individual HW components, i.e grapics card, all hard drives, fans and yeah pretty much everything but the issue persists. I also swapped out my PSU but the issue showed up again.
So i'm down to debugging the Motherboard and/or the CPU. I've removed and remounted the CPU once already and saw no obvious faults. i've checked the tempratures of the GPU and CPU etc and it's all good in between 30-40*C degrees with no sign of increasing."
 

turkeyinabox

Prominent
Sep 1, 2017
10
0
510


Indeed that's my only logical choice at this point it seems. Guess i'll have to put up the cash for another one, and hope i can get refunded for my old one.
The motherboard is pretty pricey so just hope it works, cause the CPU costs even more.
 

turkeyinabox

Prominent
Sep 1, 2017
10
0
510
Got a new motherboard through the RMA process and my computer has been running fine the whole day so far with the new motherboard, so this seems to have been a case of faulty motherboard, most likely some small component overheating. Very frustrating to debug :p