Blue screen of death loop windows 10

Oct 25, 2018
5
0
10
Hey guys, over the past couple of days i have been getting a bsod loop and unable to start my pc. I’ve gone through a good amount of troubleshooting steps with no success

-Bought new ram
-Unplugged gpu and all other nonessentials
-wiped my ssd (2tb no other hdd)
-Ran memtest86+ which showed i had no ram installed (maybe mobo issue?)
-even tried using a boot usb which would still cause bsod
-reset bios to default and reset cmos

Now im at a standstill im starting to think its my motherboard but i can get to bios screen and it shows the correct ram installed and the correct cpu installed and temps are all good

Only recent hardware change was adding a liquid cooler.

Specs:
-I7-6700(non k)
-Msi gtx 1080ti gaming x
-Hyper x 16gb 2133mhz (2x8gb)
(Also brand new corsair vengeance 16gb 2400mhz (2x8gb) all ddr4)
-2tb western digital sata ssd
-asus z270e strix motherboard
-650watt evga gold psu
-corsair h100i pro cooler

Now im lost at this point and any help would be appreciated thanks.

Btw the 2 ram versions are not in at the same time the corsair ram is the ones i just bought from bestbuy to see if they’d fix the error which they did not.
 
memtest86+
LATEST VERSION : 5.01
LAST UPDATE : 27/09/2013
https://www.memtest.org/

Memtest86+ is reported to have issues with UEFI BIOS motherboards. Support was discontinued in 2013. I suggest you use MemTest86:
https://www.memtest86.com/

I suggest you reinstall Windows 10.
 


i have formated my ssd and have tried to re install windows via boot usb, but it still bsod before even getting to the repair/install part of windows all it shows is the asus logo before freezing the spinning wheel and blue screening.
 



i can't because i already formatted my ssd and the only files i have on anything is just the usb with the windows boot tool created onto it
 
what was the bucgcheck code and parameter 1? (the error code)


 


multiple

-irql_no less or equal to
kernal security check fail
another kernal code error type
page fault in nonpaged area
 
can not really help if i can not see the first line of the bugcheck codes
something like this:
0x1A (0x41790, 0xFFFFFA80051D6EC0, 0xFFFF, 0x0)

each parameter has special meanings and can provide a clue as to the cause of the bugcheck.






 


sadly there is no code just the sad face windows support link and the error message.
 
the codes will also be in the event viewer logs.
or you might download and run whocrashed.exe