Frustrating Computer Issue

[Kennesy]

Let me start with specs:
Ryzen 5 1600x
MSI B450M Gaming Plus mATX
2x 8gb G-Skill Fortis 2300(I think) DDR4
eVGA GeForce 1060 6gb
Seasonic M12 II Evo 650w
150GB SSD for Windows
1TB HD for Storage

As the title states, Im having some very frustrating computer issues. Since I put this computer together, it has had some quirks. When the computer has to restart, most times it will either BSOD or show a solid red CPU debug LED on the motherboard. Typically, it takes about 3-4 restart button/hard power down cycles, but eventually it will start and run. Once its running, as long as I don't restart or power down, it will run as long as I want it to (hence why I've been able to put up with it).

So recently, my 1TB HD took a crap and took quite a few files with it. I was able to recover most of the important things using EaseUS recovery software (worth the $70 for anyone who gets caught with no backups like I did). After removing the storage HD, I noticed that it seemed to be booting up fine the few times I tried so I assumed it was just a faulty HD causing some strange issues, ordered a new one, and planned to do a re-install of Windows.

Fast forward to today, my new 500gb SSD replacement storage shows up and I begin the data saving/re-installing process. Immediately after attempting to download windows from a USB flash, I have the same BSOD and restart loops I was having before. Long story short, I finally got windows to install on the new SSD (but couldn't get it to install fully on the previous installation SSD despite formatting and deleting partitions) and still have the BSOD/CPU LED loops. If I restart or force power down 4-5 times in a row, the computer works fine but anytime there is a restart (for example, windows updates) it will go into this loop, causing any manner of issues with major installations.

The BSOD error codes I was getting would mostly be these 3:
KMODE_EXCEPTION_NOT_HANDLED
IRQL_NOT_LESS_OR_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA

sometimes showing a specific file and sometimes not. The files I can remember were:
wdf01000.sys

amdppm.sys

Ran memtest86 for 4 tests on both the CPU and RAM sticks, showing 0 errors. CPU runs at 50 degrees C max 95% of the time since it was built. No overclock on RAM, CPU, or GPU. BIOS is fully default settings.

Once the computer is finally running, it seems perfectly normal and healthy. I've played video games, ran multiple programs, streamed, basically pushed every limit I could (including passmark and various stress tests) with 0 issues ever. Its only during any type of power down or restart that these issues come up. Im concerned that the failure of my drive is somehow linked to this however considering the issues I had trying to install windows and subsequent updates both times. I don't want to keep spending money recovering data and replacing drives, and I'd like to have a computer I can turn off and on without a ten minute power struggle (pun intended) every single time.

My current suspects are the CPU and the motherboard, however I do not have a spare system I can use to test my theory. My next step will probably be to take it to geek squad to have them isolate the mobo and CPU to hopefully diagnose them.

Before I spend any more money, my questions are as follows:
Do those specific BSOD codes or restart symptoms give any evidence as to what may be the underlying issue?
Is the memtest86 CPU testing comprehensive enough to rule out the CPU as the issue? Same goes for the RAM
Are there any other reliable ways to troubleshoot this type of restart issue that I have overlooked or am not aware of? (I've tried everything I could think to)

Thanks for reading and for any help you guys can offer.

[Kennesy]

Oh, and following the initial installation all drivers including BIOS were updated to the latest stable versions from manufacturer websites. The issue seemed to exist both before and after driver updates.

[Kennesy]

I haven't tried, but according to the AMD RMA form, if I don't have the serial number from the actual box (I don't) I cant RMA anyways. Im expecting to pay out of pocket for either a new CPU, a new MOBO, or both. In which case I will probably simply upgrade to the 2600x or some variant considering they are similar in price now.

Could all of these issues be potentially caused by a fault MOBO as well or would there be some other symptoms? Is a faulty MOBO unlikely given these specific circumstances?

Also, the hardest part for me to wrap my head around... Why is it that once the computer is up and running it can undergo multiple CPU specific stress tests and weeks of being powered on with no issue if the CPU itself were faulty? This to me seems the strangest part of the whole issue.

[NunoLava1998]

All of these error codes point to the CPU/RAM/driver fucking up. 

Considering it has a red CPU debug LED and doesn't always start, it's not any type of driver which would lead me to believe it's the CPU or RAM.

Try troubleshooting these.

[Kennesy]

So far, I've run memtest86 from a bootable image for 3 hours on the full test (CPU and RAM) and got back a clean report card with 0 errors. All of my CPU cores were recognized, all of the cache was recognized and sized appropriately, as was the RAM both for size, speed, and timing.

[NunoLava1998]

4 minutes ago, Kennesy said:

So far, I've run memtest86 from a bootable image for 3 hours on the full test (CPU and RAM) and got back a clean report card with 0 errors. All of my CPU cores were recognized, all of the cache was recognized and sized appropriately, as was the RAM both for size, speed, and timing.

 

8 minutes ago, Kennesy said:

I haven't tried, but according to the AMD RMA form, if I don't have the serial number from the actual box (I don't) I cant RMA anyways. Im expecting to pay out of pocket for either a new CPU, a new MOBO, or both. In which case I will probably simply upgrade to the 2600x or some variant considering they are similar in price now.

Could all of these issues be potentially caused by a fault MOBO as well or would there be some other symptoms? Is a faulty MOBO unlikely given these specific circumstances?

Also, the hardest part for me to wrap my head around... Why is it that once the computer is up and running it can undergo multiple CPU specific stress tests and weeks of being powered on with no issue if the CPU itself were faulty? This to me seems the strangest part of the whole issue.

 

I don't think it's the motherboard. None of these errors and faults you have point to a motherboard problem.

It's likely the CPU or RAM but from what you've done it's pretty much impossible to determine which; so try using just a basic 4gb stick of RAM and see if it works or exhibits the same issues. Does it work? It's the RAM. Does it not? It's the CPU.

 

12 minutes ago, Genwyn said:

Page fault errors are usually related to failing ram or storage where the page file is held. If you had a drive die, you would see that message.

Page fault has nothing to do with the page-file unless Windows does some shitfuckery where the pagefile is involved which is a bit confusing

also sorry for editing this 3 times

[Kennesy]

As regards the page file, when I researched that specific error code originally I tried resizing the page file, moving the page file location from one drive to the other, and completely disabling page filing as well. None of them changed that error coming up during restart/BSOD loops.

[Kennesy]

I will try swapping around the RAM I have currently tomorrow and see if I get any other results. Its starting to look more and more like a replacement CPU is in my near future...

[NunoLava1998]

1 minute ago, Kennesy said:

As regards the page file, when I researched that specific error code originally I tried resizing the page file, moving the page file location from one drive to the other, and completely disabling page filing as well. None of them changed that error coming up during restart/BSOD loops.

In that case it could still be the CPU or RAM. It's pretty much impossible to determine until you replace the RAM/CPU and find out yourself unfortunately

[Kennesy]

Thanks for the help. Anyone else have any insight into this particular problem?