WppRecorder.sys problem when updating Windows 10 from 1909 to 20H2

Its it absolutely necessary to update the BIOS?

I have read and heard horror stories about how a failed updating of BIOS has irrecoverably busted computers... I absolutely cannot afford to have this happen to a work computer.

Most problems related to the BIOS were many years ago.

If you follow the directions it should update smoothly.

No matter the low probability of problems, a mistake is made, and it's in the news.

There are security and performance upgrades that only appear in BIOS upgrades.

Open a new thread and have somebody walk you threw it (Asus).

OK, managed to update BIOS to 3806 (a friend talked me through it)

WDV has been started on non-microsoft drivers which I will allow to run until 7am tomorrow, that's 16 hours.

(at least I hope its running. I cant see it listed in the Task Manager, and I haven't seen any impact on performance)

At that point, I will swap to microsoft drivers and leave it running all day

Do not test Microsoft drivers.

Only test non-Microsoft drivers.

See the earlier instructions.

Start with 3 customized tests > see instruction on increasing the number of simultaneous tests

Code:

   
    [ ] (0x00000001) Special pool
    [ ] (0x00000002) Force IRQL checking
    [ ] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [ ] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [ ] (0x00000100) Security checks
    [ ] (0x00000800) Miscellaneous checks
    [ ] (0x00020000) DDI compliance checking

  ADDITIONAL FLAGS:
    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [ ] (0x00000400) IRP logging
    [ ] (0x00002000) Invariant MDL checking for stack
    [ ] (0x00004000) Invariant MDL checking for driver
    [ ] (0x00008000) Power framework delay fuzzing
    [ ] (0x00010000) Port/miniport interface checking
    [ ] (0x00040000) Systematic low resources simulation
    [ ] (0x00080000) DDI compliance checking (additional)
    [ ] (0x00200000) NDIS/WIFI verification
    [ ] (0x00800000) Kernel synchronization delay fuzzing
    [ ] (0x01000000) VM switch verification
    [ ] (0x02000000) Code integrity checks

Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool



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

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are run in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified



For any BSOD run the V2 log collector to collect new log files

Right, I misunderstood those instructions (language problem)

I am currently running the WDV on non-MS drivers

(at least I think, because there doesn't seem to be any way to tell if it is actually running (no listing in the Task Manager processes list)

I will leave it running until 3pm Tuesday (46 hours from now) but I will periodically come to work to check for a BSOD

Open administrative command prompt (ACP) and type or copy and paste:

verifier /querysettings

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

Use this link as needed when posting results:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com

If there is no immediate BSOD with 3 customized tests then add these additional tests now:

Code:

    [ ] (0x00000002) Force IRQL checking
    [ ] (0x00000008) Pool tracking
    [ ] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [ ] (0x00000100) Security checks
    [ ] (0x00000800) Miscellaneous checks

Open administrative command prompt (ACP) and type or copy and paste:

verifier /querysettings

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

Use this link as needed when posting results:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com


I'm stepping away soon and may catch up later in the day.

If you're available please upload results.

24 Hours... no BSOD so far

Microsoft Windows [Version 10.0.18363.1443]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>verifier /querysettings

Verifier Flags: 0x00100610

Standard Flags:

[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[X] 0x00000200 Force pending I/O requests.
[X] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Verified Drivers:

asupio.sys
igdkmd32.sys
teedriverw10.sys
iccwdt.sys
intcdaud.sys
dump_diskdump.sys
dump_storahci.sys
dump_dumpfve.sys
iocbios2.sys
iuprocessfilter.sys
mpksldrv.sys
iuregistryfilter.sys
iufilefilter.sys

C:\WINDOWS\system32>

Please add the 6 customized tests to have 9 simultaneous tests.

Then run verifier /querysettings