Unexpected kernel mode trap and automatic repair loop issue

So today I was in the middle of a game and my PC crashed with the unexpected_kernel_mode_trap BSOD. So my computer rebooted with the automatic repair but when it was about to start the BSOD with the frowny face would pop up real quick and close again. This has been happening all day with sometimes it will only show a quarter of the BSOD before restarting and repeating. Also, everytime this happens my fans get extremely loud. I have the Inspiron 5680 and have only been using it for about 3 weeks. Any help would be extremely appreciated.

This sometimes indicates a hardware problem.

Does the machine consistently pass full ePSa tests?

Yes, everytime I've run the ePSA tests it's passed.

Run the Dell diagnostics, accessed by F12 at power on.  

If the diagnostics do not show anything and it works OK except for the game, I would suspect the game is the problem.  

---

@fireberd wrote:

Run the Dell diagnostics, accessed by F12 at power on.  

If the diagnostics do not show anything and it works OK except for the game, I would suspect the game is the problem.  

---

The OP bought a non-gaming computer to do gaming.

Not the smartest of moves.

.

The Inspiron 5680 is in fact a gaming desktop.

There is the problem. I'm stuck in a loop and cannot even get to the login screen.

Yes, this model is sold as a gaming PC.  

If you can't get to the log in screen, that suggests it will probably take restoring to the original factory image.

Here are the various options for a Dell and Win 10.

https://www.dell.com/support/article/us/en/19/sln297920/reset-or-reinstall-windows-10-on-your-dell-computer?lang=en

If you don't want to do this, as it is still almost new and under warranty contact Dell tech support for assistance and guidance.

---

@Beegster wrote:

Yes, everytime I've run the ePSA tests it's passed.

---

Sounds like it's time to call Dell and use your (paid for) warranty.

Depending on time-period you might be eligible for a full return.

And please don't double-post the same problem...