The windbg had not pointed to a misbehaving driver that we could uninstall and reinstall.
The bluescreenview and the whocrashed had reported:
ntoskrnl.sys
ntoskrnl.exe
ntfs.sys

You have checked:
memory using memtest64+ with more than 8 runs and found no problems
operating system with sfc /scannow and dism /online /cleanup-image /restorehealth and found no problems
ran chkdsk /x /f /r and found that it had corrected errors in the Volume Bitmap.
In event reporting there were two recurrent problems:
1) driver \Driver\WUDFRd failed to load
2) driver \Driver\klhk failed to load


It is possible that the chkdsk repairs in the volume bitmap have fixed the bsod problems. If you have another bsod with similar results then we will know the chkdsk repair was insufficient. If you don't have another bsod related to the previously reported findings then we will know that the chkdsk repair successfully repaired the bsod problems.

These are the steps that could be done at this juncture:

1) uninstall and reinstall all drivers related to intel
2) uninstall Kaspersky with the Kaspersky uninstall tool and reinstall the application
3) view the CBS and DISM logs to see if there is any information about the operating system related to the bsod
4) run windows driver verifier with the following settings:
https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983
For windows driver verifer I have been using it for years and recently had a bad experience where it had an incompatibility problem with windows defender offline. The windows defender offline in windows version 1607 was improperly configured. It was repaired with windows 1703 so there is no longer a windows defender offline blue screen boot loop.
You had had a prior problem using it so I know the pro and the con.
It may be our only remaining method to find the misbehaving driver.
If you want to use it you must know how to navigate through the windows advanced troubleshooting menu. That is worth practicing before using it and making trial runs. You must be able to navigate to startup options and choose option number 6: safe mode with command prompt. After reboot enter verifier /reset. Then you should be back on the desktop. You can then run bluescreenview and whocrashed and find the misbehaving driver. Then uninstall the driver. Then reinstall the driver. Then rerun windows driver verifier. When you find that there are no longer any more bsod you then run windows driver verifier for 36 hours with normal computer use. If there is no misbehaving driver then windows driver verifier is turned off. You have completed the preventative maintenance.
The administrative command prompt command to practice navigating through the windows advanced troubleshooting menu is shutdown /r /o /f /t 00
Troubleshoot>advanced options>startup settings>restart>6 (enable safe mode with command prompt)>enter password>It should open with title bar: Administrator: cmd.exe This is where you type verifier /reset and reboot to the desk top.



Clean boot can be modified and run without interfering with networking:
Using msconfig all non-microsoft items are unchecked
Using task manager > startup all items are disabled
For any of the above anything that you are concerned about networking can be left checked or left enabled.
The goal is to turn off as many non-Microsoft drivers on boot.
You will have the fastest boot times.
Some items will require time to load as they were not turned on at boot.
Performance overall should be improved in selective boot.