BSOD caused by ntoskrnl.exe after clean install of windows 10

Hello,

I recently freshly installed windows 10 on my computer due to several BSOD errors due to ntoskrnl.exe I had in the past (UNEXPECTED_KERNEL_MODE_TRAP, ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY). The problem seemed to be solved for a day, but today after some windows updates I recieved the same BSOD errors again.

Before the fresh install I performed a MemTest and found out one of my RAM sticks had 32 errors. I removed the faulty RAM stick so that shouldn't be the problem anymore. I've also ran a malware scan and sfc scan but they showed positive results.

My system is only 4 months old so i'm even surprised the RAM stick had hardware failures. Safe mode seems to work fine for the moment though so it could be a driver issue.

I also put my system info and dumpfiles in the attachment.

Attachment 239113Attachment 239114

How did you determine which stick had errors? Please describe the exact process (which sticks and slots you used, and how many passes you ran on each stick(s))
Have you re-run the MemTest again (after removing the bad stick)? If so, did the remaining sticks all pass?

These devices have problems in Device Manager:
-Microsoft Hyper-V Virtualization Infrastructure Driver ROOT\VID\0000 This device is not working properly because Windows cannot load the drivers required for this device.
-NVIDIA Virtual Audio Device (Wave Extensible) (WDM) ROOT\UNNAMED_DEVICE\0000 This device is not working properly because Windows cannot load the drivers required for this device.
-NVIDIA High Definition Audio HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_14623283&REV_1001\5&7B34673&0&0001 This device is not working properly because Windows cannot load the drivers required for this device.
-Realtek High Definition Audio HDAUDIO\FUNC_01&VEN_10EC&DEV_0887&SUBSYS_104386C7&REV_1003\4&BC42ED2&0&0001 This device is not working properly because Windows cannot load the drivers required for this device.

Please download and install the drivers for each of the devices

I'm not familiar with the Hyper-V driver - but are you using the built in Windows Virtual Machine software?
If not - I'd suggest disabling it from running (you'll have to post in the Virtualization forums for more help with that: https://www.tenforums.com/virtualization/ )

Once you reply back, I'll make some further suggestions. I'm suspecting that this is a hardware problem - but the path to isolate which piece of hardware will depend on your answers to my questions.

What slot is the good stick in?
Did you test each stick in that slot alone?
What I'm trying to figure out is if it's the stick itself - or the slot that's bad.

What happens if you don't run in Safe Mode?
The drivers are still trying to load - that's why there's an error in Device Manager. Uninstall/reinstall is the suggested fix for that

3 of the 5 memory dumps are corrupted and unusable.
I've run the other 2 and found 2 different errors

A large number of differing errors from one system is usually a symptom of a hardware problem.
But with only 2 memory dumps, we can't make that assumption.

But, with all the other stuff you're experiencing, I have to suspect a hardware problem.

What drive is the OS installed on (the SSD or the Barracuda)? I'm pretty sure it's the SSD, but want to verify with you.
Are you able to run a Seatools diagnostic test on the Barracuda? SeaTools | Seagate Support US
As there are not any reliable diagnostic tests for the SSD - do you have another drive that you can try in it's place (to see if it's the SSD that's having the problem)? If the Barracuda passes the diagnostics - you can try installing the OS on it in order to test).

I'm headed out now, but will try to check back in the morning (US Eastern Time)

The good stick is currently in the A2 slot, I've tested both sticks in that slot and only one of them passed the MemTest.
The bad stick couldn't even start my computer or crashed during the test before finishing but i could see there were errors.

When my pc is not booted in safe mode it randomly freezes or gets blue screens.

The OS is installed both on the HDD and SSD because i wanted to check if one of them was failing (turns out both might be),
although the SSD can't even boot in safe mode. I can't seem to launch SeaTools because of the following error: "Could not load file or assembly 'SpawnCLR.dll' or one of its
dependencies. The specified module could not be found. Void Startlink(Int32)"

I've installed an alternative CrystalDiskInfo which tells me both my SSD and HDD are fine and show no errors. Chkdsk also shows no errors on both disks. Kingston SSD Manager also tells me me SSD is healthy.

I've also uninstalled and reinstalled the drivers you've listed. I'm currently in normal mode on my HDD and everything works except for blue screens every 20 mins or so.
The 2 most recent BSOD's are in the attachment. Attachment 239190

Is it worth it trying to solve this problem or should I just return every component back? (I still have warranty on every component).

Do you disconnect the SSD when you boot from the Barracuda? If not, please try that (drives that have problems can affect the system even if they're not being used to boot).

The CrystalDisk stuff is just a S.M.A.R.T. application - and that is only predictive (not diagnostic)
I've seen many dead/dying hard drives that pass the S.M.A.R.T. tests

The 2 latest memory dumps are different also.
One blames the file system on the hard drive by giving an access denied error. The other is a driver not loading due to an invalid hash. Both could also be hardware issues.

If you can return it, it wouldn't hurt - it'd just be a hassle for you.
But, on the plus side, it'd save you all the time trying to isolate exactly which component is bad.
This presumes that I am correct that it is a hardware problem. I'm fairly certain that it's a hardware problem - but not 100% sure. To get to 100% sure we'd have to do all the diagnostics and then try testing each part (either by removing it or by replacing it)

I haven't tried disconnecting the SSD, didn't know it might cause problems.

Yesterday after uninstalling and reinstalling those audio drivers my pc seemed to work fine untill I shut it off, afterwards there was a windows update and my pc started crashing again.

I ran dism restore health after that in safe mode and also an sfc scan and both ran succesfully without errors.

I am now running seatools via a bootable usb and it is scanning both my HDD and SSD so i'll post updates once it's done.

- - - Updated - - -

After running all the SeaTools scans both my SSD and HDD seemed to be fine. Is it safe to rule them out of the problem also keeping in mind they are only 3 months old? The test results are in the attachment:Attachment 239246Attachment 239245

My computer also crashed before I ran the scan and produced the following error: PAGE_FAULT_IN_NONPAGED_AREA caused by the driver nstokrnl.exe Attachment 239247

I'm now going to try booting in normal mode and see if the errors persist, if they do is it likely my motherboard or cpu is the problem?

- - - Updated - - -

My computer now won't even load on safe mode on my HDD so I'm guessing it's time to send all the parts back... Thanks for the help anyways :)

Hardware diagnostics are simply software tests of hardware components.
FWIW - I've found hard drives that pass the diagnostics, yet replacing the hard drive will solve the problem.
This isn't very common, but it makes one think that diagnostics aren't 100% perfect.

In this case, as you can boot from either drive, then the definitive test would be to disconnect the SSD and boot from the Barracuda.
- If the problem goes away - then you know to blame the SSD
- If the problem doesn't go away - then the SSD is likely to be OK

Then you plug the SSD back in and disconnect the Barracuda
- If the problem goes away, then you know to blame the Barracuda
- If the problem doesn't go away - then the Barracuda is likely to be OK

Please note that I use a lot of qualifying terms (like "is likely").
The only sure thing is to test with another device (such as swapping the drives out).
Just noticed your update - good luck with the new parts!