Question KMODE Exception into Boot Loop, Help Appreciated!

Apr 15, 2021
4
0
10
0
Howdy! New to the forums, please let me know if this post belongs in a troubleshooting specific thread.

I am experiencing a boot loop into repeated KMODE EXCEPTION NOT HANDLED errors, on a self-built computer that has been functioning fine for 6 months, with no recent hardware changes or program installations/driver updates.

Spec below:
MOBO: GIGABYTE X570 I AORUS Pro Wi-Fi
CPU: AMD Ryzen 9 3900X
RAM: Corsair Vengeance LPX 32GB (2X16GB) DDR4 3200 (PC4-25600) C16 1.35V
SSD: addlink S70 512GB SSD NVMe PCIe 3x4 M.2 2280 (C Drive+Boot) + Crucial P2 1TB 3D NAND NVMe PCIe M.2 SSD Up to 2400MB/s - CT1000P2SSD8 (D Drive)
GPU: Radeon R9 290X
PSU: Corsair SF Series, SF600, 600 Watt, 80+ Gold Certified
Monitor: Monoprice Zero-G Gaming Monitor - 27 Inch, WQHD With AMD FreeSync, 2560x1440p@144Hz, 1ms, HDR, 400nits, TN
OS: Windows 10 Home 64 bit
FANS: 2 Noctua 120mm (for many months was run on 1 stock 120mm, though that was some time ago)

Description:
--The first Blue Screen of Death happened after the comp had been on for many hours, and was not correlated to any intense workload.
--For a time, I could boot to a blue "solution screen" of potential fixes like Restore Point or repave the OS, but once a fix got started it invariably BSoD's back into a boot loop.
--Then, after maybe 10 attempts, I began receiving a BIOS warning that the CMOS had been cleared at the top of each loop. I tried manually shorting the CMOS pins, and also flashed the BIOS to the latest version (only 6 months newer than my previous one), no change.
--I have tried every configuration of a single 16gb RAM in each slot, thinking maybe a stick or slot was the culprit. No change in behavior.
--I have tried swapping the 512gb boot ssd and the newer 1tb ssd between the A and B mobo m.2 slots, no change. And also tried to repave the os fresh onto the 1tb (this also crashed shorly after the wizard got started). The BIOS can scan both drives and confirms they are functional.

Potential red herrings: On long DOOM sessions, I have seen a couple instances of grey static on the screen (but the R290X is an old beast, doing its best, and I'm assuming that since I still have graphics and the fan spins, it is not the problem). And a week ago, I did install a new m.2 ssd, but this was in the B slot (back of motherboard) and has been working perfectly.

My instinct is that it must be a hardware failure. I don't think it's graphics, the PSU works fine, the mobo seems functional and I can access the BIOS (although the clear cmos warnings are worrying). The RAM could be messed up, but it's unlikely to have affected both sticks simultaneously and no combination of them in either slot or individually seems to make a difference in behavior. The BIOS can see the 3900X CPU, but I don't know of another way to test its functionality.

Any thoughts would be much appreciated!
 
Howdy! New to the forums, please let me know if this post belongs in a troubleshooting specific thread.

I am experiencing a boot loop into repeated KMODE EXCEPTION NOT HANDLED errors, on a self-built computer that has been functioning fine for 6 months, with no recent hardware changes or program installations/driver updates.

Spec below:
MOBO: GIGABYTE X570 I AORUS Pro Wi-Fi
CPU: AMD Ryzen 9 3900X
RAM: Corsair Vengeance LPX 32GB (2X16GB) DDR4 3200 (PC4-25600) C16 1.35V
SSD: addlink S70 512GB SSD NVMe PCIe 3x4 M.2 2280 (C Drive+Boot) + Crucial P2 1TB 3D NAND NVMe PCIe M.2 SSD Up to 2400MB/s - CT1000P2SSD8 (D Drive)
GPU: Radeon R9 290X
PSU: Corsair SF Series, SF600, 600 Watt, 80+ Gold Certified
Monitor: Monoprice Zero-G Gaming Monitor - 27 Inch, WQHD With AMD FreeSync, 2560x1440p@144Hz, 1ms, HDR, 400nits, TN
OS: Windows 10 Home 64 bit
FANS: 2 Noctua 120mm (for many months was run on 1 stock 120mm, though that was some time ago)

Description:
--The first Blue Screen of Death happened after the comp had been on for many hours, and was not correlated to any intense workload.
--For a time, I could boot to a blue "solution screen" of potential fixes like Restore Point or repave the OS, but once a fix got started it invariably BSoD's back into a boot loop.
--Then, after maybe 10 attempts, I began receiving a BIOS warning that the CMOS had been cleared at the top of each loop. I tried manually shorting the CMOS pins, and also flashed the BIOS to the latest version (only 6 months newer than my previous one), no change.
--I have tried every configuration of a single 16gb RAM in each slot, thinking maybe a stick or slot was the culprit. No change in behavior.
--I have tried swapping the 512gb boot ssd and the newer 1tb ssd between the A and B mobo m.2 slots, no change. And also tried to repave the os fresh onto the 1tb (this also crashed shorly after the wizard got started). The BIOS can scan both drives and confirms they are functional.

Potential red herrings: On long DOOM sessions, I have seen a couple instances of grey static on the screen (but the R290X is an old beast, doing its best, and I'm assuming that since I still have graphics and the fan spins, it is not the problem). And a week ago, I did install a new m.2 ssd, but this was in the B slot (back of motherboard) and has been working perfectly.

My instinct is that it must be a hardware failure. I don't think it's graphics, the PSU works fine, the mobo seems functional and I can access the BIOS (although the clear cmos warnings are worrying). The RAM could be messed up, but it's unlikely to have affected both sticks simultaneously and no combination of them in either slot or individually seems to make a difference in behavior. The BIOS can see the 3900X CPU, but I don't know of another way to test its functionality.

Any thoughts would be much appreciated!
See if this helps please
 
Apr 15, 2021
4
0
10
0
Thanks! I did indeed find this before posting. As I can't boot to windows, I can't address the driver / fast startup notes. But there were no driver updates before the first crash, and I do not believe I have fast startup enabled (there is an option for it in my BIOS as well, which is/was disabled). As for RAM: I think I ruled it out by trying each stick individually in each of my two slots, with no change in behavior. I don't have another mobo to run diagnostics for the ram on, but the current mobo does see each of them.
 
Apr 15, 2021
4
0
10
0
I guess my main question is: does this sound like a hardware failure to folks? Is there a way to rule out or confirm the functionality of the cpu, without another motherboard to test it on?
 
Apr 15, 2021
4
0
10
0
That's awesome to hear! I cannot boot from a UEFI thumb drive, unfortunately. When I set that as the primary boot, I get 15 seconds of the static Aorus motherboard logo and then that same BSoD with KMODE Exception error. So if it's a corrupted update, shouldn't the issue only crop up when trying to access the currently installed OS?
 
That's awesome to hear! I cannot boot from a UEFI thumb drive, unfortunately. When I set that as the primary boot, I get 15 seconds of the static Aorus motherboard logo and then that same BSoD with KMODE Exception error. So if it's a corrupted update, shouldn't the issue only crop up when trying to access the currently installed OS?
Yes indeed so it maybe hard ware but generally most common is ram that causes this... My question to you is did something in the bios somehow get adjusted without your knowlage? Or bios up-to-date?
 

ASK THE COMMUNITY