Hi Steve,
For us to provide a solution suited to the error message that you've provided, we need additional information. Can you answer the questions below?
- What are you doing on your PC when you get the error message?
- When I ran HLK for my old WDM driver for WIndows 10 64, I have got failures for HVCI code integrity test as below,
Non-zero Code Integrity statistic found: "Section Alignment Failures =8" Non-zero Code Integrity statistic found: "Execute-Write Section Count=1"
Driver was built with WDK 7. I have used NonPagedPoolNx and wherever I used ExAllocatePoolWithTag , I have used the pool tag with a multiple of 0x1000.
- Were there any recent changes made to your device prior to the issue?
- Changes done in the driver for making the HVCI readiness Test in HLK to pass for Windows 10.
- I have changed all paged pool usages to
NonPagedPoolNx and used ExAllocatePoolWithTag with pool tag with a multiple of 0x1000.
- Where did you get this error?
- In the HLK setup for Windows 10 USB driver.
- On which build version of Windows is your device running on?
- I have tested on on WIndows 10 x64 1607 and 1511 and 1709 versions. HLK test fails with these errors.
- Have you done any troubleshooting steps so far?
- Yes. I have enabled the driver verifier and debugged remotely with Windbg. I am getting following 8 Code integrity issues.
Driver Verifier: Enabled for driverxxx.sys, flags 0x2000000, build 10586, key
xxxxxxxx
*********** Verifier Detected a Code Integrity Issue ************
**
** The image driverxxx.sys contains section 0xFFFFF800873401F0 that is not page
aligned (name .text).
**
*****************************************************************
*********** Verifier Detected a Code Integrity Issue ************
**
** The image driverxxx.sys contains section 0xFFFFF80087340218 that is not page
aligned (name .rdata).
**
*****************************************************************
*********** Verifier Detected a Code Integrity Issue ************
**
** The image driverxxx.sys contains section 0xFFFFF80087340240 that is not page
aligned (name .data).
**
*****************************************************************
*********** Verifier Detected a Code Integrity Issue ************
**
** The image driverxxx.sys contains section 0xFFFFF80087340268 that is not page
aligned (name .pdata).
**
*****************************************************************
*********** Verifier Detected a Code Integrity Issue ************
**
** The image driverxxx.sys contains section 0xFFFFF80087340290 that is not page
aligned (name .CRT).
**
*****************************************************************
*********** Verifier Detected a Code Integrity Issue ************
**
** The image driverxxx.sys contains section 0xFFFFF800873402B8 that is not page
aligned (name INIT).
**
*****************************************************************
*********** Verifier Detected a Code Integrity Issue ************
**
** The image driverxxx.sys contains section 0xFFFFF800873402E0 that is not page
aligned (name .rsrc).
**
*****************************************************************
*********** Verifier Detected a Code Integrity Issue ************
**
** The image driverxxx.sys contains section 0xFFFFF80087340308 that is not page
aligned (name .reloc).
**
*****************************************************************
How can I trace this .text, .rdata , .data etc to the code for page alignment
issues ?
Since it is a Verifier crash, I am not able to debug even with the .pdb file in
Windbg.
Any thoughts to identify the root cause of this failure ? Please help.
We'll wait for your response.