Some WHLK (Windows Hardware Lab Kit) tests are failing both with and without our driver installed. Need assistance to determine how to proceed

Question

We have a 64bit Keyboard Kernel Mode Upper Filter Driver that was previously certified for Windows 10 back in 2021.

This driver is used to add data to keyboard device generated IRP's (Interrupt Request Packets) for use by a Barcode Scanner Service that we install and use with the driver.

We need to get our driver re-certified with a new EV Certificate for Windows 11 64bit.

While attempting to run the WHLK Keyboard tests within WHLK Studio, for 2 "HID Keyboard Driver" devices, we found 6 tests (each run twice) failing (displaying a red X next to each of these tests) but not finding any error code or indication of an error within the log file. (Te.wtl). 
The failing tests are:
DF - Sleep and PNP (disable and enable) with IO Before and After (Development and integration)

DF - Sleep and PNP (disable and enable) with IO Before and After (Reliability)

DF - Sleep with fixed processor utilization (Development and Integration)

DF - Sleep with IO Before and After (Bring Up)

DF - Sleep with IO During (Development and Integration)

DF - Sleep with IO During (Reliability)

For each of these tests, if I right click on its "Run Test" node, the Error option opens a window with the following error description:

      Cause: Machine Rebooted Unexpectedly when Task "Run Test" was running

      Failure: Task Cancelled Because of an Unexpected Reboot

 

Note, however, that none of this error data appears in the actual log file (Te.wtl)

We uninstalled our driver and re-ran the same tests and ended up seeing these same failed tests.
In addition, we had failures for two test runs of "HyperVisor Code Integrity Readiness Test"

Are these failing tests buggy or do they require some additional configuration?

Are we running tests that should be excluded for our driver or whose results should be filtered out of our results package for submittal to Microsoft?

Answer 1

Hey Martin,Try this

1. Kernel Debugging: Use WinDbg to monitor the system during the tests. Check for BSODs or kernel crashes and analyze crash dumps to pinpoint the root cause.
2. Driver Verifier: Enable Driver Verifier to catch driver-related issues, especially IRP handling errors. This can help identify conflicts or stability problems during sleep and PNP transitions.
3. Advanced Logging: Use xperf (Windows Performance Toolkit) to record performance traces during the tests. Check logs from C:\Windows\Logs\HLK\Jobs for insights into what triggered the unexpected reboot.
4. Exclude Non-Relevant Tests: Verify whether the failing tests are even applicable to your keyboard filter driver. Some tests might be unnecessary and can be filtered out in the submission packa