Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

OSR Seminars


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 3  
11 May 18 08:20
vinayashree ks
xxxxxx@gmail.com
Join Date: 11 May 2018
Posts To This List: 4
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.
  Message 2 of 3  
11 May 18 16:09
Tim Roberts
xxxxxx@probo.com
Join Date: 28 Jan 2005
Posts To This List: 12028
Unknown: DEBUGCHK failed in file d:\bt\2520\private\winceos\net\ndis\sys\miniport.c

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 <...excess quoted lines suppressed...> 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.
  Message 3 of 3  
16 May 18 00:43
vinayashree ks
xxxxxx@gmail.com
Join Date: 11 May 2018
Posts To This List: 4
Unknown: DEBUGCHK failed in file d:\bt\2520\private\winceos\net\ndis\sys\miniport.c

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
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 23:48.


Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license