Persistent BSOD ntoskrnl.exe

1) Update the system specs in the "My Computer" section:
System Specs - Fill in at Ten Forums | Windows 10 Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

For RAM please specify whether DDR3 or DDR4.

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

2) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

3) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

System specs have been updated as requested. Please see requested images below:

Attachment 197757
Attachment 197758
Attachment 197759

For startup and recovery system failure:
a) Uncheck automatically restart
b) reboot to fix the setting change

With automatically restart un-checked for each BSOD you should see a bugcheck and : (
Sometimes you may see a misbehaving driver in the form *.sys
At the very beginning of each BSOD you may see a % counter.
Allow this % counter to rise to 100% before rebooting so that there is sufficient time to create the dump file.

For DDR4 RAM testing please use this software:
MemTest86 - Official Site of the x86 Memory Testing Tool
After each test please post images into the thread.
It may take a long time to run 124 GB or RAM.
Label the RAM modules and DIMM.
Testing can be done in pairs and testing can be performed overnight.
Once a test has started please make sure that the testing is continuous.

Just got this one before I was able to execute your latest instructions and I was editing After Effects's GUI at the time. I was able to notice that it did cite tcpip.sys for this one which it has done in the past. As I'm in the middle of a project I'm not going to be able to run MemTest until afterwards which will be several weeks from now. Do you know exactly how long it will take to test 128gb of RAM?

1) After each BSOD:
Run this link and post a zip into the thread:
(extract > open)
Windows 10 Help Forums

Use the txt and images in this thread in case there are problems running the BETA log collector: (post #5)
DM Log tool problem Solved - Windows 10 Forums
DM Log tool problem Solved - Windows 10 Forums

2) post a one drive or drop box link for c:\windows\memory.dmp

3) Turn off Windows updates of non-Microsoft drivers:

Enable or Disable Driver Updates in Windows Update in Windows 10 | Windows 10 Tutorials

4) For Memtest86+ version 5.01 RAM testing takes approximately 1 - 2 hrs / GB ram.
The Memtest (Passmark) has a faster algorithm.
At this time I don't have a number to gauge the test time.

5) The computer appears to have two different GPU cards:

NVIDIA GeForce GTX 1080
NVIDIA GeForce GTX 1080 Ti

Please confirm and update the system specs

Code:

Name	NVIDIA GeForce GTX 1080
PNP Device ID	PCI\VEN_10DE&DEV_1B80&SUBSYS_336C1462&REV_A1\4&1C3D25BB&0&0019
Adapter Type	GeForce GTX 1080, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1080
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll
Driver Version	24.21.13.9836
INF File	oem0.inf (Section102 section)
Color Planes	Not Available
Color Table Entries	Not Available
Resolution	Not Available
Bits/Pixel	Not Available
Memory Address	0xEC000000-0xECFFFFFF
Memory Address	0xB0000000-0xBFFFFFFF
Memory Address	0xC0000000-0xC1FFFFFF
IRQ Channel	IRQ 54
Driver	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_485c1c3102021986\nvlddmkm.sys (24.21.13.9836, 16.40 MB (17,200,392 bytes), 7/28/2018 12:28 PM)
	
Name	NVIDIA GeForce GTX 1080
PNP Device ID	PCI\VEN_10DE&DEV_1B80&SUBSYS_336C1462&REV_A1\4&3685BFFF&0&000B
Adapter Type	GeForce GTX 1080, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1080
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll
Driver Version	24.21.13.9836
INF File	oem0.inf (Section102 section)
Color Planes	Not Available
Color Table Entries	Not Available
Resolution	Not Available
Bits/Pixel	Not Available
Memory Address	0xAC000000-0xAD0FFFFF
Memory Address	0x90000000-0xA1FFFFFF
Memory Address	0xA0000000-0xA1FFFFFF
IRQ Channel	IRQ 64
Driver	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_485c1c3102021986\nvlddmkm.sys (24.21.13.9836, 16.40 MB (17,200,392 bytes), 7/28/2018 12:28 PM)
	
Name	NVIDIA GeForce GTX 1080 Ti
PNP Device ID	PCI\VEN_10DE&DEV_1B06&SUBSYS_36051462&REV_A1\4&2A366DF3&0&0019
Adapter Type	GeForce GTX 1080 Ti, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1080 Ti
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll
Driver Version	24.21.13.9836
INF File	oem0.inf (Section102 section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	1920 x 1200 x 59 hertz
Bits/Pixel	32
Memory Address	0xAA000000-0xAB0FFFFF
Memory Address	0x70000000-0x81FFFFFF
Memory Address	0x80000000-0x81FFFFFF
I/O Port	0x0000E000-0x0000EFFF
IRQ Channel	IRQ 86
I/O Port	0x000003B0-0x000003BB
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_485c1c3102021986\nvlddmkm.sys (24.21.13.9836, 16.40 MB (17,200,392 bytes), 7/28/2018 12:28 PM)
	
Name	NVIDIA GeForce GTX 1080
PNP Device ID	PCI\VEN_10DE&DEV_1B80&SUBSYS_33691462&REV_A1\4&288C77C7&1&000B
Adapter Type	GeForce GTX 1080, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1080
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_485c1c3102021986\nvldumdx.dll
Driver Version	24.21.13.9836
INF File	oem0.inf (Section102 section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	1600 x 900 x 59 hertz
Bits/Pixel	32
Memory Address	0xEE000000-0xEEFFFFFF
Memory Address	0xD0000000-0xDFFFFFFF
Memory Address	0xE0000000-0xE1FFFFFF
IRQ Channel	IRQ 32
Driver	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_485c1c3102021986\nvlddmkm.sys (24.21.13.9836, 16.40 MB (17,200,392 bytes), 7/28/2018 12:28 PM)

Please see my responses below:

1. Sorry this doesn't make sense to me. Are you saying run the beta log collector after each BSOD and post the zip file generated from it into this thread? If so please see the log collection here.

2. I don't have a one drive or dropbox account but have been using Google Drive successfully during this troubleshooting. Is this sufficient?

3. This has been successfully executed.

4. Would Memtest (Passmark) be helpful here considering I wont be able to run MemTest86 for several weeks?

5. My system specs have been updated. I have 1xGTX1080ti and 3xGTX1080s which I use for GPU rendering. They are all Pascal cards...

Thanks so much for the aid.

After each BSOD the BETA log collector will collect more useful files than the DM log collector so the BETA log collector is preferred.
The BETA log collector is designed to collect most of the needed files.
At times the memory.dmp file provides more useful information on the dumps that can be used in the debugging.
If the size is up to 2 GB then zip > post a share link with either one drive , drop box, or google.
There was a recurrent driver in the crash.
It seems that the crash was caused by another driver.
So when there are additional crashes they can be debugged.
Some testing can be done overnight.
Consider testing two RAM modules at a time and see how far the testing is overnight.
If the testing is complete with just two RAM modules then you may be able to perform testing while sleeping.
Also one RAM module can be tested at a time however it does not check the multichannel capability of the motherboard.

Were you able to identify the driver that caused the latest crash?

Are you saying to post the memory.dmp and the beta log collected zip after each BSOD and are you also saying you need to see more .dmps/logs to hopefully gain a clearer understanding of what's causing the crashes?

I appreciate your RAM test description but unfortunately cannot do this right now as I'm in the middle of a project. Would running Memtest (Passmark) be a waste of time?

Would a clean install of Windows 10 be advisable in the sense that if there are still problems after then we would know it's most likely hardware related?

philc43 may have more suggestions.
For a crash there can be many drivers involved.
If the root cause can be identified then it may be more efficient to fix the root cause than fix every driver involved in the crash.
So with more dumps there will be more information.
For every dump run the BETA log collector and post a new zip into the thread.
And to get a better assessment of the crashes please continue to find and post the memory.dmp.
Over time Windows or other software can delete the needed troubleshooting files and once they are in the thread they have been saved and viewed.
For the latest crash there was a recurrent driver but from the other information in the dump it appears that another driver may be the root cause and this root cause driver was not yet seen in the crash. With more dumps this should become apparent.
There is no direct test of the motherboard. So RAM testing will test DIMM and parts of the MB. It may provide useful information when there are multiple hardware drivers seen in crashes.

Ok understood and thanks again for your help. I'll continue to post logs and .dmp's as BSODs occur and will test memory as soon as I can. One final question. Is there any other test aside from MemTest that would be helpful?