Windows device driver 做 WHQL 測試時遇到藍屏問題

Question

Windows device driver 做 WHQL 測試時遇到藍屏問題

MS60 CCMa 20

o 測試環境已重新建置完成 (Win11 25H2 26100 + WinServer 2025).

o 驅動程式在正常模式(關閉數位簽章)下可正常執行, 但在測試模式啟動Verifier (載入Vhf.sys & NuDL.sys), 一安裝就會造成BSOD. 根據Memory.Dump分析, 錯誤點是發生於Vhf.sys (呼叫VhfCreate )內, 問題難排除.

經Memory.dump分析, 錯誤點是發生於Vhf.sys

0 則留言

由問題作者接受的回答

Francisco Montilla 31,825 獨立顧問

你好

这个签名几乎总是在 ** Microsoft 内置驱动vhf.sys开启时出现，而不仅仅是在调用 VhfCreate 的第三方驱动上。最佳做法是将驱动验证器只针对你的驱动。验证 vhf.sys 或其他内置系统驱动程序会强制内部压力路径，并立即引发错误检查，掩盖驱动程序是否真的有责任。

在测试机器上，删除所有现有的Verifier设置，然后仅为驱动二进制开启标准设置。从一次提升命令提示符运行中：

verifier /reset

重新启动。然后运行：

verifier /standard /driver `YourDriver.sys`

再次重启并重现WHQL测试。在 vhf.sys 验证器选项中不要包含或任何其他 Microsoft 驱动。如果你是从HLK启动，确保池子不会覆盖这个范围，并且只针对你的驱动。

如果系统不再进行bug检查，就继续使用WHQL。如果没有核实还是会检查bug，vhf.sys请分享完整 0xC4 参数和输出顶部!analyze -v，这样我们就能准确指出你的代码路径中任何VHF API的误用。 VhfCreate

MS60 CCMa 20 信譽點數

2025-11-27T02:45:29.05+00:00

是从HLK启动的, 如何設定才能不包含 vhf.sys ?
Francisco Montilla 31,825 信譽點數獨立顧問

2025-11-27T05:01:07.98+00:00
When you trigger Driver Verifier from HLK, you need to scope it to your driver only so vhf.sys never gets included.

In HLK Studio, open your project, select the test machine, go to the Tests tab, search for Device Fundamentals: Driver Verifier, then choose Run with new parameters. In the parameters dialog, set Verification type to Standard, turn off any Verify all drivers option, and in the field typically labeled Drivers to verify or Driver names, enter only your third-party driver file names, for example MyDriver.sys.

Remove anything else that appears in that list so vhf.sys is not present. Start the run with these parameters so HLK applies Verifier only to your binaries.

Before you queue the job, clear any previous Verifier state on the test machine so HLK does not merge with an old configuration. On the SUT, open an elevated Command Prompt and run:

verifier /reset

Reboot the SUT, then kick off the HLK run with the scoped parameters above.

If you still see a bugcheck after this, share the 0xC4 parameters and the top of !analyze -v so we can check for a VHF API misuse on your path to VhfCreate.

1 個其他答案

您的回答

MS60 CCMa 20 信譽點數

2025-11-27T02:45:29.05+00:00

是从HLK启动的, 如何設定才能不包含 vhf.sys ?
Francisco Montilla 31,825 信譽點數獨立顧問

2025-11-27T05:01:07.98+00:00

When you trigger Driver Verifier from HLK, you need to scope it to your driver only so vhf.sys never gets included.

In HLK Studio, open your project, select the test machine, go to the Tests tab, search for Device Fundamentals: Driver Verifier, then choose Run with new parameters. In the parameters dialog, set Verification type to Standard, turn off any Verify all drivers option, and in the field typically labeled Drivers to verify or Driver names, enter only your third-party driver file names, for example MyDriver.sys.

Remove anything else that appears in that list so vhf.sys is not present. Start the run with these parameters so HLK applies Verifier only to your binaries.

Before you queue the job, clear any previous Verifier state on the test machine so HLK does not merge with an old configuration. On the SUT, open an elevated Command Prompt and run:

verifier /reset

Reboot the SUT, then kick off the HLK run with the scoped parameters above.

If you still see a bugcheck after this, share the 0xC4 parameters and the top of !analyze -v so we can check for a VHF API misuse on your path to VhfCreate.

Answer 1

MS60 CCMa 20

0xC4 parameters and the top of !analyze -v 使用者的影像

0 則留言