Windows 10: 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.
RAIDEN-(2019-10-28_11-06-30).zip

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

:)

 

Driver verifier not creating dump file

I'm getting frequent BSOD. I started the driver verifier as suggested.

At first, windows stuck at the boot loop, It didn't even show any BSOD. It just kept booting and turning off again and again. It didn't go past motherboard logo.

After some changes in the verifier, It was able to show windows logo but crashed before fully booting to "Driver verifier detected violation"

And it didn't even create any dump file. (All dump file setting are correct one ) As it is known that a driver is causing BSOD. How to know which one?

 

Driver Verifier BSOD on Start Up DRIVER_VERIFIER_DETECTED_VIOLATION

OK I'm going to keep this thread updated as I go through troubleshooting this issue.

As I have received no help with my minidumps, I am going through the process of learning to do it myself.

This seems
like a good guide to learn the very basics.

What has happened so far:

• New computer build, unstable windows install, slowly degrades to where the computer is unusable. Happens on multiple clean installs.

• Continuous error and critical messages in Event Viewer, some events of note are:
  • Event 219 Kernel-PnP, failed to load driver
  • Event 7031 service control manager (dozens on start up)

• First crash will happen on start up and it eventually degrades with below events.
  • Event 5 kernel general
  • Event 2 kernel-event-tracing
  • Event 3 kernel-event-tracing
  • Event 29 kernel-boot

• Tested hardware - no faults found

• Ran Driver Verifier and Windows will keep crashing with DRIVER_VERIFIER_DETECTED_VIOLATION until Driver Verifier is reset in safe mode

• Started this thread, PC became too unstable and had to do a system restore, restore had minimal changes (see above)
• Have not installed the applications and drivers removed after system restore.
• PC is heading down same road again, BSOD now appearing on startup.
• Ran Driver Verifier again - same resuslts
• Installed WinDBG to start analyzing new dumps from crashes that have been happening on startup.
  • dump 1 - pool_corruption
  • dump 2 - memory_corruption
  • dump 3 - memory_corruption
  • dump 4 - ntkrnlmp.exe

From the limited knowledge I got from the guide the only information I can get from WinDBG is shown above.

So that's where I am at the moment. My next step is to run Driver Verifier again and see what I can find.

 

Driver verifier dump file BSOD

The Memory dump you uploaded was had a bugcheck of 50, not C4(Driver verifier Detected Violation). Nothing constructive was found in the dump, though.

Step 1:

Configure your PC to generate MiniDumps:

Configure Windows 10 to Create Minidump on BSOD

Step 2:

Do a memory Test:

Memory problems.