Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting... Please check out the Community Guidelines in the
Announcements and Administration Category.

Unknown: DEBUGCHK failed in file d:\bt\2520\private\winceos\net\ndis\sys\miniport.c

Hi,

I'm debugging my NDIS 6.0 ethernet driver under WEC7. Right after my Initialize function returns NDIS_STATUS_SUCCESS, the folowing is on the debug port:

==>NdisMRegisterAdapterShutdownHandler: Miniport B5F40450
<==NdisMRegisterAdapterShutdownHandler: Miniport B5F40450
Unknown: DEBUGCHK failed in file d:\bt\2520\private\winceos\net\ndis\sys\miniport.c at line 12464
KdTrap: JIT debugging requested, waiting for OEM selection
KdTrap: JIT debugging accepted
+KITLRegisterDfltClient, service:2

!KITLRegisterDfltClient called before KitlInit. KITLGlobalState=00000080
DEBUG_BREAK @ef67ff74 Ignored.
==>ndisMCommonHaltMiniport: Miniport B5F40450
Can anyone suggest me where to find this miniport.c file ??? And how to check what is the issue after miniport initialize is successfull??? Got struck in this ,not able to find the issue itself.

Comments

  • Tim_RobertsTim_Roberts Posts: 12,623
    xxxxx@gmail.com wrote:
    > I'm debugging my NDIS 6.0 ethernet driver under WEC7. Right after my Initialize function returns NDIS_STATUS_SUCCESS, the folowing is on the debug port:
    >
    > ==>NdisMRegisterAdapterShutdownHandler: Miniport B5F40450
    > <==NdisMRegisterAdapterShutdownHandler: Miniport B5F40450
    > Unknown: DEBUGCHK failed in file d:\bt\2520\private\winceos\net\ndis\sys\miniport.c at line 12464
    > KdTrap: JIT debugging requested, waiting for OEM selection
    > KdTrap: JIT debugging accepted
    > +KITLRegisterDfltClient, service:2
    > ...
    > ==>ndisMCommonHaltMiniport: Miniport B5F40450
    > Can anyone suggest me where to find this miniport.c file ??? And how to check what is the issue after miniport initialize is successfull??? Got struck in this ,not able to find the issue itself.

    How are you building this?  Usually, as an OEM, you get the source code
    for the whole operating system.  DEBUGCHK means there was probably an
    assertion failure.  Did you start from a sample?  Have you checked all
    your attributes for consistency?

    --
    Tim Roberts, xxxxx@probo.com
    Providenza & Boekelheide, Inc.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • Thanks for the reply

    Yes I started from a sample driver and found the reason for DEBUGCHK failure.

    As my register entries were mismatching the general attributes mediatype,physicalmediatype and Iftype .I was getting that DEBUGCHK failure and then driver was unloaded.

    I changed the values in regester entries .reg file and now able to call OidRequest functions
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!