Windows 10: Constant BSODs caused by ntoskrnl.exe

1) Please confirm that there has never been malware found only PUPs.
2) Quarantine everything that was found and then delete.
3) Uninstall Malwarebytes during the troubleshooting
4) Perform these scans:
a) tdsskiller: https://usa.kaspersky.com/downloads/tdsskiller
b) zemana antimalware: Zemana Anti-Malware | Advanced Malware Removal Software
d) run windows defender advanced scan: offline scan
5) Uninstall all antivirus products and just use windows defender during the troubleshooting process.

 

Here is the memory.dmp file i was asked in post #38
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

The memory.dmp when debugged did not display a definitive misbehaving driver.

After you complete the above remaining scans plan to use this tool to find misbehaving drivers. It will help by producing bsod which will be debugged and may enable differentiating misbehaving hardware from software and hardware drivers.

Windows driver verifier is a tool that is used to find misbehaving drivers.
It will repetitively produce bsod until misbehaving drivers are fixed or until it is turned off.
Before using it you must know how to turn off windows driver verifier.
There are 3 methods and all are done with the windows recovery or advanced troubleshooting menu.
1) startup options (not startup repair) > #6 safe mode with command prompt: type: verifier /reset
2) command prompt > Administrator X: \windows\system32\cmd.exe: > type: verifier /bootmode resetonbootfail
3) restore
The restore method leads to a lost of the mini dump file and little progress is made in the troubleshooting.
To practice using the windows advanced recovery open administrative command prompt and type or copy and paste:
shutdown /r /o /f /t 00

To have time to view the bsod windows during each dump > system control panel > advanced system settings > startup and recovery settings > un-check automatically restart
During each windows driver verifier bsod there is a stop code typically driver verifer detected violation and sometimes the misbehaving driver is displayed in the form *.sys. If you see the driver please record it and post it in the thread.
Please download and install both bluescreenview and whocrashed.
Blue screen of death (STOP error) information in dump files.
Resplendence Software - WhoCrashed, automatic crash dump analyzer
After each bsod you will uninstall each misbehaving driver. Then you can restart windows driver verifier and look for another misbehaving driver or reinstall a new copy of the misbehaving driver. The methods should end up with the same result and it is personal preference whether you uninstall all misbehaving driver first and reinstall drivers later or reinstall after each misbehaving driver is uninstalled.
After each bsod you will return to the desktop top and run bluescreenview and whocrashed and you can post a new zip so that we can guide you through the process: BSOD - Posting Instructions - Windows 10 Forums
Once all bsod have been fixed you will run windows driver verifier for an additional 36 hours of typical computer use. If there are no more bsod troubleshooting and preventative maintenance will have been completed.

Before using windows driver verifier:
1) create a brand new restore point
2) backup files to another drive or to the cloud
3) create a backup image using Macrium: Macrium Software | Your Image is Everything
4) place the backup image on another drive

The first link has the customized testing settings and the second link has the methods to turn on and off windows driver verifier.
Please read both so that you are comfortable using the tool.

1) Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

2) Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

3) Microsoft Community

 

Please download and install: Intel processor identification utility > Click CPU technologies tab > post image into the thread.

 

Something I found in the MEMORY.DMP:

Code: >[IRP_MJ_FILE_SYSTEM_CONTROL(d), N/A(0)] 1 1 ffff800bd7a4d030 ffff800bebe84ef0 00000000-00000000 pending \FileSystem\NTFS Args: 00000018 0000000c 00090240 00000000[/quote]
Looks strange for me. At this point I really recommend a clean install of Windows 10

Clean Install Windows 10 Windows 10 Installation Upgrade Tutorials

 

So, it's been 4 days since my last post, and you're probably asking "where did he go?". Well, since that last post, i decided to take out 16GB (2x8) sticks of RAM. I haven't had any crashes since. I guess this specific model (Team Vulcan 16gb (2x8gb) DDR4 2400, model #: TLGD416G2400HC14DC01) isn't supposed to be paired with another of these. I want to thank y'all for helping me along this troubleshoot, and to say sorry for any inconveniences this caused. Have a good one!