TechSpot

System Error - Event Category (102) - Event ID 1003

By Dewotine
Mar 22, 2007
  1. Hello,


    I've got a problem with two serveurs I'm using (running under Widows Server 2003). The 2 computers stop quite often and on both there is the same error message : System Error - Event Category (102) - Event ID 1003
    I used windbg to see what's happening but I'm not able to determine what is the problem. I put the report below. Has anyone got an idea?

    Thanks


    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 7c94ed54, The address that the exception occurred at
    Arg3: f5b59d64, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction "0x%08lx" emploie l'adresse m moire "0x%08lx". La m moire ne peut pas tre "%s".

    FAULTING_IP:
    +7c94ed54
    7c94ed54 ?? ???

    TRAP_FRAME: f5b59d64 -- (.trap fffffffff5b59d64)
    ErrCode = 00000004
    eax=c0000005 ebx=00000000 ecx=0053f124 edx=7c94ed54 esi=00000000 edi=09a03a60
    eip=7c94ed54 esp=0053f124 ebp=0053f188 iopl=0 nv up ei pl nz na pe nc
    cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202
    7c94ed54 ?? ???
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR: 0x8E

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 00000000 to 7c94ed54

    STACK_TEXT:
    0053f120 00000000 00000000 00000000 00000000 0x7c94ed54


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    +7c94ed54
    7c94ed54 ?? ???

    FAULTING_SOURCE_CODE:


    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    BUCKET_ID: INVALID_KERNEL_CONTEXT

    Followup: MachineOwner
    ---------
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...