OP posted WHOCRASHED results, which clearly showed a 3rd party driver.
I ran Windbg and no 3rd party driver was present, which was somewhat odd as it was a 0xc4 Driver Verifier BSOD.
My version of Windbg -
philc43's version of Windbg -
This post in that same thread shows my Windbg version was out-of-date as philc43's version of Windbg showed the same 3rd party driver named by WHOCRASHED (my version of Windbg did not).
Windows 10 BSOD paradise, multiple drivers and dumps
Be sure to keep your version of Windbg updated!
Regards. . .
jcgriff2
I ran Windbg and no 3rd party driver was present, which was somewhat odd as it was a 0xc4 Driver Verifier BSOD.
My version of Windbg -
Microsoft (R) Windows Debugger Version 10.0.10075.9 AMD64
philc43's version of Windbg -
Microsoft (R) Windows Debugger Version 10.0.18317.1001 AMD64
This post in that same thread shows my Windbg version was out-of-date as philc43's version of Windbg showed the same 3rd party driver named by WHOCRASHED (my version of Windbg did not).
Windows 10 BSOD paradise, multiple drivers and dumps
Be sure to keep your version of Windbg updated!
Regards. . .
jcgriff2