Skip to main content

 none
DF SurpriseRemove test issue for Network cards (only RS5 17763 build) RRS feed

  • Question

  • Hi everyone,

    I've met an issue with SurpriseRemove on RS5 (17763 build) test while passing WHQL Certification on following network cards:

    - Intel X-540

    - Aquantia AQtion 10 Gbit Network Adapter

    - TP-Link 1 Gbit

    - Realter 1 Gbit

    Errors according test logs in HLK Studion 17763 (for all the drivers of the cards marked above):

    WDTF_PNP : Result: Failed to receive IRP_MN_REMOVE_DEVICE after receiving IRP_MN_SURPRISE_REMOVAL. Ensure that there are no open handles or references to the test device (in user mode or in kernel mode) preventing IRP_MN_REMOVE_DEVICE from being sent. You may need to terminate any processes or services that may have open user mode handles to this device. ( 80004005 ).

    WDTF_PNP : Result: Successful , but device not started, ( Status=1802102 (DN_DRIVER_LOADED DN_NEED_RESTART DN_DISABLEABLE DN_NT_ENUMERATOR DN_NT_DRIVER ) Problem=0 () )..

    WDTF_TARGET               :          WDTF.ConcurrentIO.1 SetTarget() ERROR : CWDTFConcurrentIOImpl::SetTarget() Failed to open the EDT device Win32=1 - Incorrect function.
     Win32=1 - Incorrect function.
    
    WDTF_TARGET               : WDTF.ConcurrentIO.1 SetTarget() ERROR : CWDTFConcurrentIOImpl::SetTarget() Failed to open the EDT device Win32=1 - Incorrect function.
     Win32=1 - Incorrect function.
     Win32=1 - Incorrect function

    WDTF_PNP : Result: Device is not started.

    WDTF_PNP : Result: Successful , but device not started, ( Status=1802102 (DN_DRIVER_LOADED DN_NEED_RESTART DN_DISABLEABLE DN_NT_ENUMERATOR DN_NT_DRIVER ) Problem=0 () )..

    Is this issue common and known for the last Windows 10 build? The tests have been successfully passed for previous windows versions. 

    I have to submit my driver into developer dashboard but can't finish WQHL for rs5. Maybe there is some Errata exist for this test?

    Thank you and best regards,

    Egor



    • Edited by EgorZv Wednesday, October 24, 2018 11:08 AM
    Wednesday, October 24, 2018 10:57 AM

All replies

  • The DevFun test for device and system testing has some excellent documentation for troubleshooting failures in these tests. Check out these two links.

    https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/device-devfund-additional-documentation
    https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/review-common-device-fundamentals-reliability-test-failures

    Note that while a test may have pass on a previous OS release with a previous kit, the OS or HLK jobs could have had bug fixes taken which now expose driver bugs that were previously hidden. 


    Thursday, October 25, 2018 7:34 PM