TechSpot

Windows XP 64 Crash reports

By glhglh
Nov 6, 2007
  1. i have been having two to three crashes per day. here is what the crash dump says.

    i don't know what it means.

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff97fff0d6bad, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffffadf8a54b420, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

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




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

    FAULTING_IP:
    win32k!GetDCEx+394
    fffff97f`ff0d6bad ?? ???

    CONTEXT: fffffadf8a54b420 -- (.cxr 0xfffffadf8a54b420)
    rax=0000000000000001 rbx=fffffadf9b8a9bf0 rcx=fffff97ff7d64100
    rdx=0000000004939c30 rsi=000000000dc43ab0 rdi=0000000000000020
    rip=fffff97fff0d6bad rsp=fffffadf8a54bc38 rbp=fffffadf8a54bcf0
    r8=fffffadf98876af0 r9=fffffadf9b8a9bf0 r10=fffff80001175180
    r11=fffffadf9b8a9bf0 r12=000000007ef80000 r13=000000000ec9fd00
    r14=000000000ec9f110 r15=0000000078b83980
    iopl=0 nv up ei ng nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    win32k!GetDCEx+0x394:
    fffff97f`ff0d6bad ?? ???
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: iexplore.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff97fff0d6bad

    STACK_TEXT:
    fffffadf`8a54bc38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!GetDCEx+0x394


    FOLLOWUP_IP:
    win32k!GetDCEx+394
    fffff97f`ff0d6bad ?? ???

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: win32k!GetDCEx+394

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310

    STACK_COMMAND: .cxr 0xfffffadf8a54b420 ; kb

    FAILURE_BUCKET_ID: X64_0x3B_win32k!GetDCEx+394

    BUCKET_ID: X64_0x3B_win32k!GetDCEx+394

    Followup: MachineOwner
    ---------

    kd> .cxr 0xfffffadf8a54b420
    rax=0000000000000001 rbx=fffffadf9b8a9bf0 rcx=fffff97ff7d64100
    rdx=0000000004939c30 rsi=000000000dc43ab0 rdi=0000000000000020
    rip=fffff97fff0d6bad rsp=fffffadf8a54bc38 rbp=fffffadf8a54bcf0
    r8=fffffadf98876af0 r9=fffffadf9b8a9bf0 r10=fffff80001175180
    r11=fffffadf9b8a9bf0 r12=000000007ef80000 r13=000000000ec9fd00
    r14=000000000ec9f110 r15=0000000078b83980
    iopl=0 nv up ei ng nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    win32k!GetDCEx+0x394:
    fffff97f`ff0d6bad ?? ???
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.