Reading driver verifier crash dump

Hi everyone.
I'm attempting to debug my frequent BSODs I'm receiving. I have mainly noticed that when I leave my PC on overnight, I'm back on the Win 10 login screen. Upon trying to log in, I would sometimes get crashes. Rarely, my system would crash when I was actively working within windows.

After the recent Windows 10 update mess on the 24th, the crashes have only seem to have gotten worse.
I keep receiving multiple different errors such as IRQL_NOT_LESS_OR_EQUAL, KERNEL_SECURITY_CHECK_FAILURE, UNEXPECTED_KERNEL_MODE_TRAP and likely others as well.

I was attempting to use Driver Verifier to create a dump and WinDbg to analyze the dump but it seems to be having problems connecting to Microsoft Symbol Server and I'm unable to view the dump file.

Below are the attached the log collector files.
Attachment 252762

Alternately, I have uploaded the .zip on my OneDrive HERE

One thing that I would suspect could be conflicting somehow is the fact that I have this AMD Sapphire HD7850 GPU installed in my computer at the moment, I'm unsure if it could conflict with the AMD Ryzen APU (Vega 8) somehow. They both run on the same driver version AFAIK, AMD Radeon 19.9.2. I remember seeing a bios setting for discrete GPU that I believe is set to "Auto Detect" so I haven't messed around with that yet. But for all i know, the problems could be something else entirely .

Any help in debugging this issue would be greatly appreciated, I would enjoy it if my system could be stable again :')
Thank you,
Aaron

How did you setup Driver Verifier? We recommend that you use the method described below:

Diagnostic Test

DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please read and run driver verifier.

If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Update:
BIOS (Support For X470 GAMING PLUS | Motherboard - The world leader in motherboard design | MSI Global)
In addition, probably among the drivers for verification in Driver Verifier you have carelessly chosen Microsoft drivers because the crash dump where the error checking is 0xC4 refers to the driver vmswitch.sys which is responsible for the operation of the Hyper-V service (Windows system service)

I set up Driver Verifier and rebooted. My system crashed about 10+ times upon trying to start up and generated a dump so I figure I was doing it somewhat correctly.

Today, WinDbg is deciding to work properly and I'm able to analyze my dumps.

Its showing this module in the DRIVER_VERIFIER_FAULT_DETECTED dump:

Code:

MODULE_NAME: vmswitch

IMAGE_NAME:  vmswitch.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.387

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  42b

FAILURE_BUCKET_ID:  0xc4_1001_VRF_vmswitch!VmsScPortIpsecStateCleanup

BUCKET_ID:  0xc4_1001_VRF_vmswitch!VmsScPortIpsecStateCleanup

PRIMARY_PROBLEM_CLASS:  0xc4_1001_VRF_vmswitch!VmsScPortIpsecStateCleanup

I would have to guess this is Hyper-V causing the problem. Which is unfortunate because I like using the virtualization.

- - - Updated - - -

MrPepka, is that not appropriate? I wasn't aware Microsoft's drivers could never be the root of crashing issues, and some such as Hyper V support, can be disabled if need be.

Microsoft drivers are usually not verified because these are 99% well tested. Run Driver Verifier as you have it set, but when choosing drivers do not choose those from Microsoft

AaronOlson said:

I set up Driver Verifier and rebooted. My system crashed about 10+ times upon trying to start up and generated a dump so I figure I was doing it somewhat correctly.

The tutorial I linked for you on Driver Verifier specifically tells you to only select the non-Microsoft Drivers. This is because they have all been verified internally by MS.

Got it, thank you guys. I updated BIOS and set up Driver Verifier properly this time. Of course now everything seems to be running just fine with no crashes but I'll leave it running overnight and see if a crash occurs when the system is idle, seems to be doing that majority of the time. I'll update new logs when I get them.

Can I essentially rule out Hyper-V being the issue for now? I previously had issues with BSODs after enabling Hyper V before a few windows updates that seemed to finally allow me to use it on my PC.

I think, just like you have uploaded all the updates to Windows 10 (just check it in Windows Update)

Another crash at 5AM while i was sleeping, a SYSTEM_SERVICE_EXCEPTION instead of something caught by driver verifier it looks like. Yet I still have no clue.

Attachment 252958

In Driver Verifier check ALL standard settings and leave 2 additional options enabled (Force pending I/O requests and IRP logging)