Windows CE6.0 R3 wzcsvc.dll data abort RRS feed

  • Question

  • Hi,

    I met wzcsvd.dll data abort issue when I using WINCE6.0 R3 device, the log as follow:

    Exception 'Data Abort' (4): Thread-Id=07610006(pth=85877af0), Proc-Id=00400002(pprc=82c42308) 'NK.EXE', VM-active=00400002(pprc=82c42308) 'NK.EXE'
    PC=c00832c4(k.coredll.dll+0x000532c4) RA=c06dedb4(wzcsvc.dll+0x0000edb4) SP=dc03ec74, BVA=dbfdf000

    According to my understanding:


     Timestamp is 57709795 (Mon Jun 27 11:03:49 2016)

     Preferred load address is 10000000

    SO RA = 1000 0000 + 0000 edb4

     0001:0000dbb0       ?FindCachedPMK@CPMKCacheManager@@QAA_NQAEPAUPMKCacheEntry@@@Z 1000ebb0 f   wzcsvc:pmkcache.obj
     0001:0000dcc8       ?UpdatePMKIdList@CPMKCacheManager@@IAAKPA_N@Z 1000ecc8 f   wzcsvc:pmkcache.obj
     0001:0000dec8       ?ProcessNewCandidateList@CPMKCacheManager@@QAAKKPAU_PMKID_CANDIDATE@@PA_N@Z 1000eec8 f   wzcsvc:pmkcache.obj

    so the RA shoud be UpdatePMKIdList but anyhow, i can not find the pmkcache.obj file,

    can anybody give some hint or suggestion?

    Thanks a lot

    Monday, January 16, 2017 3:11 AM

All replies

  • Hi Sinojapan,

    My suspicion is you either have bad data or corrupt memory.  The WZCSVC is Wireless Zero Config Service but it does rely on correctly constructed data.  When you follow the steps to reproduce the data abort, do you know what configuration setting WZC is trying to load?



    Wednesday, January 18, 2017 11:28 PM
  • Hi,

    The data abort location points to an OS component. This would point to issues elsewhere as the OS component (Wireless Zero Config) would hardly be at fault.

    You should check the driver for PMKID list. Specifically a status indication should be made from the miniport driver that supports your wireless NIC.

    More here:

    Link is from Windows Desktop site, but should hold equally well for NDIS 5.1 based Windows CE 6.0.



    Monday, January 30, 2017 4:03 AM