TechSpot

MiniDump 100000C5 DRIVER_CORRUPTED_EXPOOL

By Verbetex
Sep 17, 2005
  1. Hi guys, this is my first post and I really need your help!

    My parents machine just started crashing randomly the other day, no new hardware has been installed recently, and I've run memtest86+ for a while with no errors being reported.

    The only other possible error I've been reading about for this error is antivirus (I'm using Avast 4.6.691)

    I'm really at a loss as to what to do next!!! Any suggestions are most welcome!
    I've attached the minidump for your info...

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

    DRIVER_CORRUPTED_EXPOOL (c5)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is
    caused by drivers that have corrupted the system pool. Run the driver
    verifier against any new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.
    Arguments:
    Arg1: 00000004, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 805505a1, address which referenced memory

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


    CUSTOMER_CRASH_COUNT: 6

    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

    BUGCHECK_STR: 0xC5

    LAST_CONTROL_TRANSFER: from 8056c4ab to 805505a1

    STACK_TEXT:
    aa02d640 8056c4ab 00000000 00000001 e5726854 nt!ExAllocatePoolWithTag+0x66a
    aa02d664 8056c606 82115e20 c0010f01 00000000 nt!ObpAllocateObject+0xc8
    aa02d698 80573bd0 c0010f01 823c8ca0 00000000 nt!ObCreateObject+0x12a
    aa02d7f4 80584c40 0012eeb4 001f03ff 00000000 nt!PspCreateThread+0xb3
    aa02d86c 804dd99f 0012eeb4 001f03ff 00000000 nt!NtCreateThread+0x118
    aa02d86c 7c90eb94 0012eeb4 001f03ff 00000000 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012ee0c 00000000 00000000 00000000 00000000 0x7c90eb94
    aa02db48 8056e253 aa02dc04 aa02dc08 aa02dbd8 nt!KiCallUserMode+0x4
    aa02dba4 bf813dcd 00000002 aa02dbe8 00000018 nt!KeUserModeCallback+0x87
    aa02dc28 bf813f74 bc6a7170 00000463 00000000 win32k!SfnDWORD+0xa8
    aa02dc70 bf814155 0a6a7170 00000463 00000000 win32k!xxxSendMessageToClient+0x118
    aa02dcbc bf836de7 bc6a7170 00000463 00000000 win32k!xxxSendMessageTimeout+0x1a6
    aa02dce0 bf80f780 bc6a7170 00000463 00000000 win32k!xxxWrapSendMessage+0x1b
    aa02dd10 aae1ba05 000503ac 00000463 00000000 win32k!NtUserMessageCall+0x8a
    000503ac 00000000 00000000 00000000 00000000 vsdatant+0x19a05


    FOLLOWUP_IP:
    nt!ExAllocatePoolWithTag+66a
    805505a1 894804 mov [eax+0x4],ecx

    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: nt!ExAllocatePoolWithTag+66a

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

    STACK_COMMAND: kb

    BUCKET_ID: 0xC5_nt!ExAllocatePoolWithTag+66a

    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...