BSOD caused by ntoskrnl.exe (Windows 10)

[Fadeley]

I am aware that there are other threads discussing the notskrnl.exe bug and that most of these threads recommend updating drivers and all that good stuff. For the better part of a year I've been dealing with crashes on startup. Most of these crashes have been attributed to Memory_Management or Page Fault in Non-page Area. Something to that effect. This is a custom built desktop running an i5 4690k, r9 290 4gb gaming edition, 8 gb crucial ballistix ram, an ASROCK H97M Pro Motherboard, and an SSD and Western Digital Blue harddrive (the SSD is what's running windows, I used to run windows on the HDD but I tried swapping it over. didn't work)
Things that I've already tried
I've already tried scanning each individual driver in detail to make sure that they're all up to date
I've done a clean install of Windows, twice, with the same software. both times I've experienced the crashing and they're all attributed to the same reasons

I've run Driver Verifier and left it on for 24 hours straight to make sure that all of my drivers were up to date and that there is nothing wrong with them. Results came up clean

I've run MemTest for a sold 30 hours thinking that it may be a hardware issue, these results came back with 0 issues.

I updated my UEIF on the motherboard via flash-media.

I've turned the Virtual Memory on Windows 10 from 1000 MB down to 0 MB in hopes that it would remove the virtual RAM it sets aside.

I've also disabled help and tips from Windows. It didn't do anything, but some people suggested it as a cause for memory leak with Windows 10.

I'm currently running sfc/scannow in the command prompt as a last resort before coming here but I'm pretty much giving up. (the results of this came back that there are corrupt files and those files are usermgr.dll & flightsettings.dll)

All of these crashes are caused by the same file name, ntoskrnl.exe from address ffffff800'18cb0000.

I'm pretty much fresh out of ideas at the moment.

 

[Colif]

ntoskrnl - New Technology Operating System Kernel. Without it, windows doesn't work. One of its jobs is the action driver requests and often gets the blame for their behavior

turning virtual memory off just means you more likely to get out of memory errors. The virtual ram is just your hard drive and most people don't have such small drives that its size will effect them.

You will need to set it to operating system managed to fix this problem. Not cause its the cause but because without a page file the same size as your ram, your PC won't be creating memory dumps that we need to use to figure out the cause of the BSOD

Once you have a page file and before next bsod, do this:
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[Fadeley]

ntoskrnl - New Technology Operating System Kernel. Without it, windows doesn't work. One of its jobs is the action driver requests and often gets the blame for their behavior

turning virtual memory off just means you more likely to get out of memory errors. The virtual ram is just your hard drive and most people don't have such small drives that its size will effect them.

You will need to set it to operating system managed to fix this problem. Not cause its the cause but because without a page file the same size as your ram, your PC won't be creating memory dumps that we need to use to figure out the cause of the BSOD

Once you have a page file and before next bsod, do this:
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

I have the minidump files here
https://1drv.ms/f/s!Ajpv-KH_pVTXhR9VrC0nMbo1ulpq

 

[Fadeley]

turns out it was a faulty stick of RAM

 

[Colif]

well, that will cause data errors. I often try to solve everything from the software side and don't always think of the hardware straight away. GLad you fixed it