Constant BSOD after upgrading from Win7 to Win10 - Bugcheck error

I upgraded to Win10 from Win7 when Win7 support ended. I was not having any issues with Win7. Win10 Version: 1909 OS Build 18363.592

After upgrading, I get regular BSODs stating CRITICAL STRUCTURE CORRUPTION. Event Manager shows the error as: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a023e415dea670, 0xb3b7306a6860f5f5, 0xffffe48b7dbc7cf0, 0x000000000000001c). A dump was saved in: C:\WINDOWS\Minidump\011720-10843-01.dmp. Report Id: f2143aa8-6069-4c4e-a39d-8c0a5d9a91cc.

Here is what I have done so far to troubleshoot:
- Checked for errors in Device Manager - none
- Upgraded to latest ASUS BIOS v1603
- DISM CheckHealth option - no issues found
- Checked all drivers for outdated versions - updated
- Ran Memtest86 - all tests passed with 0 errors after 4 passes
- Enabled Driver Verifier - system will not boot with it enabled. Error: DRIVER VERIFIER DETECTED VIOLATION
- Looked at miniumps in BlueScreenView - caused by address: ntoskrnl.exe+1c14e0

There is a Warning that always appears in Event Manager about 5 seconds prior to the Bugcheck error: The driver \Driver\WudfRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&2. I don't know if that is related and I don't know what that driver is.

Would anyone be able to assist analyzing the latest dump?

V2 log file: here

Do you have crash dumps from when you had Driver Verifier enabled? Probably there is information about the driver that may cause the error

MrPepka said:

Do you have crash dumps from when you had Driver Verifier enabled? Probably there is information about the driver that may cause the error

Now when I use Driver Verifier, I do not get the immediate BSOD. I instead get stuck in a restart loop. I tried this 2 ways in Driver Verifier: 1) using default settings (all drivers), and 2) checking only non-Microsoft drivers. Both results in the restart loop.

No new Minidumps were created. Are there other log files to provide?

1) Uninstall: Driver Easy 5.6.13

2) Uninstall any drivers installed by this software

3) If it's unclear which drivers were installed please download and install all applicable drivers displayed on the Asus website:
MAXIMUS VI HERO Driver & Tools | Motherboards | ASUS USA

4) Turn off windows fast startup:
Turn On or Off Fast Startup in Windows 10

5) Open administrative command prompt and type or copy and paste:
6) sfc /scannow
7) dism /online /cleanup-image /scanhealth
8) dism /online /cleanup-image /restorehealth
9) sfc /scannow
10) chkdsk /scan
11) wmic recoveros set autoreboot = false
12) wmic recoveros set DebugInfoType = 7
13) wmic recoveros get autoreboot
14) wmic recoveros get DebugInfoType
15) bcdedit /enum {badmemory}

16) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

17) Make sure that there is no over clocking while troubleshooting

18) Uninstall and reinstall HP laserjet software

19) Make a new restore point

20) After completing all of the above steps > reboot

21) Start windows driver verifier with the customized settings in the Ten Forums link (3 customized settings)

22) Increase the number of simultaneous settings by 3 - 5 / hour up to the 19 customized settings in the Microsoft link

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

23) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

For what it's worth, DriverEasy was installed after the Win10 upgrade to try to assist with this issue. I used it to identify out of date drivers, then I updated them manually. I will still uninstall it and go through the rest of your steps.

Thanks.

Disable Driver Verifier in safe mode and send new crash dumps

MrPepka said:

Disable Driver Verifier in safe mode and send new crash dumps

Here you go, latest minidump: Dropbox - 011720-10546-01.dmp

1. Enable Driver Verifier Manager and select "Create custom settings (for code developers)"
2. Tick all standard settings and 2 additional (force pending i/o request and irp logging)
3. Select "Select driver names from a list"
4. Select all 3rd party drivers for now without Microsoft drivers and reboot computer
Observe if the system displays BSOD at startup or not

zbook said:

5) Open administrative command prompt and type or copy and paste:
6) sfc /scannow
drive

This step fails for me at 46% every time:

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 46% complete.

Windows Resource Protection could not perform the requested operation.

- - - Updated - - -

MrPepka said:

1. Enable Driver Verifier Manager and select "Create custom settings (for code developers)"
2. Tick all standard settings and 2 additional (force pending i/o request and irp logging)
3. Select "Select driver names from a list"
4. Select all 3rd party drivers for now without Microsoft drivers and reboot computer
Observe if the system displays BSOD at startup or not

This results in a restart as soon as I enter my password to log into windows. I then started in safe mode to disable Driver Verifier. No minidumps were created.

Continue with steps 7 and 8 then scannow is ran the second time.