Share via

Non-zero Code Integrity statistic found: "Section Alignment Failures =8" and "Execute-Write Section Count=1"

Anonymous
2018-02-01T11:22:40+00:00

Non-zero Code Integrity statistic found: "Section Alignment Failures =8" 

Non-zero Code Integrity statistic found: "Execute-Write  Section Count=1"

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2018-02-02T12:21:12+00:00

Thank you for the information. Since driver verifier crashed, check this thread that we've found from our Microsoft Developers Network Forum and see if it helps. You can also post directly on the forum to have further assistance from developers and IT Professionals in resolving the issue.

Let us know if you need anything else. We're here to help.

Was this answer helpful?

0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-02-06T06:19:31+00:00

    This problem solved by removing the DRIVERTYPE=WDM parameter.

    Can we remove the the RWX from INIT section, while in the WDK 7 build environment. Any parameter or any settings in make files ?.

    As per Microsoft,  latest version of the WDK and Visual Studio 2015 has to be used. Since this is a Driver built with WDM framework, do we have any other settings to remove/change the RWX flag of INIT section.

    Any clues on this, please suggest.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-02T09:49:21+00:00

    I have even tried with below ones into my build, still the page alignment issues persists.

    First try.

    LINKER_FLAGS=/ALIGN:4096 

    Second try.

    LINKER_FLAGS=/SECTION:.text!RX,ALIGN:4096 

    DRIVER_ALIGNMENT=0x1000

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-02T05:46:25+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-01T15:39:08+00:00

    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?
    • Were there any recent changes made to your device prior to the issue?
    • Where did you get this error?
    • On which build version of Windows is your device running on?
    • Have you done any troubleshooting steps so far?

    We'll wait for your response.

    Was this answer helpful?

    0 comments No comments