If you test drivers on Windows 11, and use Windows Driver Verifier, you need to know that Driver Verifier on Windows 11 is effectively useless for diagnosing most errors.
Check out the OSR Developer's Blog here: Big Bug in Driver Verifier == HUGE Problem for the Community – OSR
Thanks Peter! Just had Bug Check 0xC4: 0x2000 from Driver Verifier Code integrity checks a few days ago, so that's is still working on Windows 11.
Important Update: It seems the behavior we seen in Driver Verifier is a bug and applies only to when/if Verifier is enabled via the GUI. If you use the command line to configure/enable Verifier, everything works as it should.
We've updated our blog post to reflect this:
Big Bug in Driver Verifier == HUGE Problem for the Community – OSR
We're in touch with Microsoft about this issue and will continue to provide info as we can.
If you're not familiar with the verifier.exe command line, and the documentation seems as impenetrable to you as it does to me, here's some help:
Rules you always want to enable:
Special Pool (1)
Forced IRQL Checking (2)
Pool Tracking (4)
I/O Verification (5)
Deadlock Detection (6)
DMA checking (8)
Security Checks (9)
Miscellaneous Checks (12)
DDI Compliance Checks (18)
DDI Compliance additional (20)
Kernel Synchronization Delay Fuzzing (24)
Code Integrity Checks (26)
Additional IRQL Checks (35)
So... that gets you:
verifier /rc 1 2 4 5 6 8 9 12 18 20 24 26 35 /driver <mydriver.sys>
The short-hand equivalent appears to be:
verifier /standard /driver <mydriver.sys>
The following may optionally be added to the above:
Force Pending (10)
Invariant MDL Checks (14 and 15)
Power Framework Delay Fuzzing (16)
Enable WDF Verification: 34
Enable File System Filter Verification: 37
So, for WDF:
verifier /rc 1 2 4 5 6 8 9 12 18 20 24 26 35 34 /driver nothing_kmdf.sys
Using /standard on a WDF driver apparently also enables WDF Verifier.
And for File Systems:
verifier /rc 1 2 4 5 6 8 9 12 18 20 24 26 35 37 /driver MyFilter.sys
If you have other settings that you use, we'd be curious to see what they are.
Thank you @Peter_Viscarola_OSR 
for this. I will check out the OSR Developers Blog to get more details on the issue.
Do you have any suggestions or tips for alternative tools or methods for driver verification and debugging on Windows 11?
By all means, continue to use Driver Verifier! Just... be sure you enable it from the command line.
@Robin77 -- After re-considering... I'm deleting your post as inflammatory nonsense, which is not substantiated by our experience here at OSR.
If you have confirming evidence for your (now deleted) claim, please get in touch with me directly (email/message here) or post a topic to me in the Announcements & Admin section.
And to close the loop on this, from our Developer's Blog post:
Microsoft has issued a fix ( KB5040442 ) for this problem. In Windows Update the update is identified as “2024-07 Cumulative Update for Windows 11 Version 23H2”.
Microsoft's page on "deprecated features for Windows client" now has this bit:
Driver Verifier GUI, verifiergui.exe, is deprecated and will be removed in a future version of Windows. You can use the Verifier Command Line (verifier.exe) instead of the Driver Verifier GUI.
Apparently announced May 2024