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

zbook · 04 Apr 2021

Which post has HD Tune full error scans for each drive?

Code:

Event[36664]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:48.223
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36665]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:48.331
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36666]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:48.441
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36667]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:48.551
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36668]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:56.760
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36669]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:56.869
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36670]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:56.981
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36671]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:57.229
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36672]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:57.341
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36673]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:57.543
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36674]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:57.658
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36675]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:57.765
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36676]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:07:57.979
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36677]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:08:01.382
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36678]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:08:01.382
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
An error was detected on device \Device\Harddisk9\DR12 during a paging operation.

Event[36679]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:08:01.382
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
An error was detected on device \Device\Harddisk9\DR12 during a paging operation.

Event[36680]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:08:01.382
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
An error was detected on device \Device\Harddisk9\DR12 during a paging operation.

Event[36681]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:08:01.490
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Event[36682]:
  Log Name: System
  Source: disk
  Date: 2021-03-15T15:08:01.601
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Photolab
  Description: 
The device, \Device\Harddisk9\DR12, has a bad block.

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: B:
 Free Space: 407.3 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: WD Elements 25A2 USB Device

      Drive: C:
 Free Space: 35.5 GB
Total Space: 113.7 GB
File System: NTFS
      Model: ADATA SP550

      Drive: D:
 Free Space: 226.7 GB
Total Space: 953.4 GB
File System: NTFS
      Model: Samsung SSD 840 EVO 1TB

      Drive: T:
 Free Space: 73.5 GB
Total Space: 114.5 GB
File System: NTFS
      Model: ADATA SP550

      Drive: E:
      Model: ASUS DRW-24D5MT
     Driver: C:\WINDOWS\SYSTEM32\DRIVERS\CDROM.SYS, 10.00.18362.0001 (English), 3/19/2019 15:39:26, 125952 bytes

smartcooky · 04 Apr 2021

Yes. I did that straight away after I posts the last lot of results.

Only been running for half an hour, but here are the next lot of results...

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

C:\WINDOWS\system32>verifier /querysettings

Verifier Flags: 0x00100fba

Standard Flags:

[ ] 0x00000001 Special pool.
[X] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[X] 0x00000020 Deadlock detection.
[X] 0x00000080 DMA checking.
[X] 0x00000100 Security checks.
[X] 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
iuregistryfilter.sys
iufilefilter.sys

C:\WINDOWS\system32>

zbook · 04 Apr 2021

If there are no major performance problems or very slow boot add:

Code:

[ ] 0x00020000 DDI compliance checking.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

Run verifier /querysettings

smartcooky · 04 Apr 2021

zbook said:

Which post has HD Tune full error scans for each drive?

Post 29, but the images are missing because I have a faulty Dropbox installation. I will fix this when I get back to work. Have to go now, but will be back later

zbook · 04 Apr 2021

Please run WDV with the additional drivers.

smartcooky · 05 Apr 2021

I have fixed the Dropbox issue in Post #29. It now has all the three HDD HDTune results.

smartcooky · 16 Apr 2021

zbook said:

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

Then run verifier /querysettings

OK, done that, had it running since wednesday

No slowing down or crashes
Results:

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

C:\WINDOWS\system32>verifier /querysettings

Verifier Flags: 0x00100fba

Standard Flags:

[ ] 0x00000001 Special pool.
[X] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[X] 0x00000020 Deadlock detection.
[X] 0x00000080 DMA checking.
[X] 0x00000100 Security checks.
[X] 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
iuregistryfilter.sys
iufilefilter.sys

C:\WINDOWS\system32>

zbook · 16 Apr 2021

Please add :

[ ] 0x00000001 Special pool.
[ ] 0x00020000 DDI compliance checking.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.

Post a new V2 and query.

If there are no major performance problems or very slow boot then add these in 1 hour:

[ ] 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.
[ ] 0x02000000 Code integrity checks.

smartcooky · 16 Apr 2021

zbook said:

Please add :

[ ] 0x00000001 Special pool.
[ ] 0x00020000 DDI compliance checking.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.

Post a new V2 and query.

If there are no major performance problems or very slow boot then add these in 1 hour:

[ ] 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.
[ ] 0x02000000 Code integrity checks.

OK, here are the result for the first of these two tests after just over an hour with no problems

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

C:\WINDOWS\system32>verifier /querysettings

Verifier Flags: 0x00ba0fbb

Standard Flags:

[X] 0x00000001 Special pool.
[X] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[X] 0x00000020 Deadlock detection.
[X] 0x00000080 DMA checking.
[X] 0x00000100 Security checks.
[X] 0x00000800 Miscellaneous checks.
[X] 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.
[X] 0x00080000 DDI compliance checking (additional).
[X] 0x00200000 NDIS/WIFI verification.
[X] 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

Extensions:

wdm: rules.all
ndis: rules.default

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
iuregistryfilter.sys
iufilefilter.sys
ndis.sys
netadaptercx.sys
wdiwifi.sys

C:\WINDOWS\system32>

Will now add the second batch and leave running overnight

- - - Updated - - -

OK, message came up saying

"Invariant MDL checking for stack cannot be enabled without
I/O verification"

"Would you like to enable I/O verification too"

I replied "yes" and proceeded

Will leave this running overnight as its getting late

- - - Updated - - -

OK, system crashed to BSOD on reboot

Stop Code: DRIVER VERIFIER DETECTED VIOLATION

- - - Updated - - -

I thought the BSOD was supposed to proceed to Windows Recovery, but it just stays on the BSOD, and rebooting takes it straight back to the BSOD

- - - Updated - - -

I have I let windows repair finish, the system rebooted, so used the admin command prompt to "verifier /reset" and the computer rebooted fine.

At this stage I will go home and check later for further instructions.

zbook · 16 Apr 2021

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

From post #34:

Code:

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

There will be more than 19 customized tests.