none
Windows CE 6.0 R3 Dr. Watson native access exception RRS feed

  • Question

  • Our application on a embedded controller with a PXA310 Windows CE 6.0 with DirectShow playing a marketing video(wmf) will throw an exception after playing continously for several days.  Using Window Error Reporting with Complete Dump, WinDbg for the .kdmp file reports.

    5:085:armce> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                      Win CE Exception Analysis                              *
    *                                                                             *
    *******************************************************************************


    Debugging Details:
    ------------------

    StackTrace failed
    Unable to load image kernel.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for kernel.dll
    Unable to load image coredll.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for coredll.dll
    Unable to load image quartz.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for quartz.dll
    Unable to load image ole32.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ole32.dll
    Unable to load image k.coredll.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for k.coredll.dll
    Unable to load image gwes.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for gwes.dll
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for mscoree3_5.dll -
    DbsSplayTreeRangeMap::Add: Conflicting region 40a81000 - 40b50dff
    Unable to map mscoree3_5.dll region at 40a81000, NTSTATUS 0xC0000018
    Unable to load image mmtimer.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mmtimer.dll
    Unable to load image platformsupport.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for platformsupport.dll
    Unable to load image afd.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for afd.dll
    Unable to load image wspm.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for wspm.dll
    Unable to load image ssllsp.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ssllsp.dll
    Unable to load image ws2.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ws2.dll
    *** WARNING: Unable to verify checksum for _mongoose.dll
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for _mongoose.dll -
    DbsSplayTreeRangeMap::Add: Conflicting region 40c81000 - 40c88bff
    Unable to map _mongoose.dll region at 40c81000, NTSTATUS 0xC0000018
    Unable to load image lcmdriver.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for lcmdriver.dll
    Unable to load image devmgr.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for devmgr.dll
    Unable to load image aserial.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for aserial.dll
    Unable to load image mscdriver.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mscdriver.dll

    FAULTING_IP:
    wmvdmod!g_AddNull_SSIMD+f8
    4098eb40 043091e5 ldr         r3, [r1, #4]

    EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 4098eb40 (wmvdmod!g_AddNull_SSIMD+0x000000f8)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000001
    NumberParameters: 0

    FAULTING_THREAD:  058e2a62

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    READ_ADDRESS:  00000000

    FOLLOWUP_IP:
    wmvdmod!g_AddNull_SSIMD+f8
    4098eb40 043091e5 ldr         r3, [r1, #4]

    MOD_LIST: <ANALYSIS/>

    LAST_CONTROL_TRANSFER:  from 00000000 to 4098eb40

    DEFAULT_BUCKET_ID:  STATUS_ACCESS_VIOLATION

    PRIMARY_PROBLEM_CLASS:  STATUS_ACCESS_VIOLATION

    BUGCHECK_STR:  APPLICATION_FAULT_STATUS_ACCESS_VIOLATION

    STACK_TEXT: 


    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    STACK_COMMAND:  ~85s ; kb

    BUCKET_ID:  APPLICATION_FAULT_STATUS_ACCESS_VIOLATION

    FAILURE_BUCKET_ID:  STATUS_ACCESS_VIOLATION_c0000005_Unknown_Image!Unknown
     *** Followup info cannot be found !!! Please contact "Debugger Team"

    As best as I can tell, the callstack for the wmvdmod.dll tread appears to be corrupted.  The software has all updates through February 2011.

    This seems to be a wmvdmod.dll problem?  Any thoughts on how to troubleshoot or other suggestions>

    Regards

    Tuesday, May 10, 2011 6:04 PM

All replies

  • Hi , John Smitly

    You can Uses The CE toolskit name is "CEDebugX" to debug 。kdmp File。

    The  video  “Using CEDebugX with Windows Embedded CE 6.0 SP1” on here .

    http://www.microsoft.com/showcase/en/us/details/674f72b3-39ad-4394-839e-ff53e3f30651

    Sunday, May 15, 2011 11:27 AM
  • Try using PB as the viewer?

    1) Put the KDMP file in the flat release directory, or any directory that contains the symbols (PDB files)

    2) Open the KDMP file as a Project in PB: File->Open->Project/Solution and navigate to the kdmp file. 

    3) Attach to the device: Target->Attach

     

    At this point, it is just like you are running a debugger and have halted at the point of the exception.  You can view call stacks, memory etc depending on how much data the dump collected.

    If you're having problems with the call stack being corrupted, try increasing the amount of memory that is reserved for Dr Watson.  Large call stacks, or systems with lots of threads can exceed the buffer making the Watson dumps useless.


    Dean Ramsier eMVP BSQUARE Corporation
    Wednesday, May 18, 2011 12:49 PM