Constant BSOD ntoskrnl.exe

[Yen Han Shih]

Put your system into a clean boot, for testing, and run driver verifier
Clean boot: https://www.tenforums.com/tutorials/41804-perform-clean-boot-windows-10-troubleshoot-software-conflicts.html
Driver verifier: https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista.html

NOTE: if whilst being in a clean boot a BSOD occurs please stay in clean boot.

Very interesting, verifier started on 6/13/2017 around 12:25 PM

It is now 6/14/2017 6:45 PM.

Looks like it's been running for over 30ish hours and I haven't encountered a BSOD yet (I'd usually get 1-3 BSODs a day).
Wondering if clean boot helped.

Status of the verifier here

 

[axe0axe0]

Keep it running for another day, 2-3 days of running driver verifier should be enough.

 

[Yen Han Shih]

Keep it running for another day, 2-3 days of running driver verifier should be enough.

I woke up with a BSOD but it was stuck at 0% and did not produce a DMP file. I restarted the PC and kept verifier running and it BSOD with the same exception again, stuck at 0% no DMP file produced.

Here's a photo

EDIT: Did some googling, I'm going to try updating killer network driver. When you pointed that to me earlier, I grabbed the updated drivers from the msi website. I'm going to grab the updated drivers directly from killer networking instead and see if this helps.

I'm going to disable verifier and clean boot for now.

 

[axe0axe0]

The error code doesn't mention any specific driver.
If you could provide a dump, it may show what driver caused the crash.

 

[Yen Han Shih]

The error code doesn't mention any specific driver.
If you could provide a dump, it may show what driver caused the crash.

Yeah...which was not helpful at all, I now updated the killer network driver that was from
here http://www.killernetworking.com/driver-downloads
instead of here https://us.msi.com/Motherboard/support/Z97-GAMING-7.html#down-driver&Win10 64 (site says 1/2017, that's a lie, driver installed was from 2016)

I'll observe and see if this improves stability and reply back here.

Thanks for your help!

 

[axe0axe0]

Since 1 of feature updates for Windows 10 they changed the BSOD. Instead of providing driver names to search for they provided a QR code leading to a page for generic troubleshooting which usually doesn't help. I'm gonna miss the old BSOD screens.

Hope you won't run in any more trouble

 

[Yen Han Shih]

Here's an update BSODs still occurring. It was stable for a bit (a week) then the issue started occurring again.

Here's a list of all the BSODs that occurred after this thread here

If it's not memory that's causing this. What other hardware components can be causing this?