Windows 10 stuck in a reboot loop

Hey everyone.

A week ago, I picked up a build based on this thread. The only real departure from the Smarticov suggestion was the power supply—I ended up going with this one.

Last weekend, I got everything set up: installed Windows 10, the motherboard drivers (System & Chipset + LAN), plus the GPU and monitor drivers (using what came on the provided disk). Everything ran smoothly until yesterday, when the system started crashing. Today, I can't even get it to boot properly; it just enters a continuous reboot loop. Here are some of the error codes popping up (roughly in this order):

Code:

After a bit of Googling, my gut feeling is that it's a driver issue, though I'm not entirely sure which one. I tried a clean reinstall of Windows 10—wiped the previous partition on disk 1 and started fresh. It gets through the initial setup until the first reboot, then it hits the same wall with the same errors. At this point, I'm starting to wonder if we're looking at an actual HP hardware failure?

A few observations that might be worth noting:
1. CPU temperature in the BIOS sits at about 50
2. Motherboard temperature in the BIOS is around 40
3. When I was still able to run HWMonitor yesterday, the CPU temp was a bit lower—somewhere in the 44-46 range. Nothing else stands out.
4. The SSD I'm installing the OS on is disk 1, not disk 0.

The fans are spinning fine. I’m hesitant to crack the case open since it's a brand-new build (warranty concerns, you know?) and there doesn't seem to be any dust buildup.

Does anyone have any suggestions before I call Best Buy on Monday?

Thanks.

I ran into some pretty similar glitches on an old machine back in the day because of a crappy RAM stick....try typing "memory" into your search bar and running the Windows Memory diagnostic once you can actually get things open, then try testing your sticks one at a time.

I downloaded MemTest86 and ran it during boot-up. Is this sufficient for a solid diagnosis, or should I be looking at something more robust?

Alright, MemTest86 is finished. Here are the final results:
View on imgur
View on imgur

So, every single mistake is "bad," and you've got a whole mountain of them...

Pull one stick out and run memtest again until you pin down which specific module is acting up. Once you find the culprit, take it back for a warranty claim... though honestly, you might have to return both sticks (just give them a call first to check)

I think I’ll just take the whole rig in—it’s pretty much brand new, so it still carries that free diagnostic warranty (provided I don't crack the case open myself). Thanks for the help so far. 🙂