TechSpot

BSOD and system reboot with error 0x19_21

By ppawlowski
May 2, 2011
Post New Reply
  1. Dear all,

    Yesterday I've faced problem with BSOD and automatic server restart.
    In EventLog I have only info, that Computer has been rebooted from bugcheck. The bugcheck was: 0x00000019

    Below is my minidump:

    Code:
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 0000000000000021, the data following the pool block being freed is corrupt.  Typically this means the consumer (call stack ) has overrun the block.
    Arg2: fffff8a000a9b000, The pool pointer being freed.
    Arg3: 00000000000010e0, The number of bytes allocated for the pool block.
    Arg4: 0000000000000000, The corrupted value found following the pool block.
    
    Debugging Details:
    ------------------
    
    GetUlongFromAddress: unable to read from fffff800016731b0
    
    BUGCHECK_STR:  0x19_21
    
    POOL_ADDRESS:  fffff8a000a9b000
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff800016003cd to fffff800014cd740
    
    STACK_TEXT: 
    fffff880`0f68ba88 fffff800`016003cd : 00000000`00000019 00000000`00000021 fffff8a0`00a9b000 00000000`000010e0 : nt!KeBugCheckEx
    fffff880`0f68ba90 fffff800`01775edc : 00000000`000010d0 00000000`00000000 fffff880`50777445 fffff8a0`00000001 : nt!ExDeferredFreePool+0xf8a
    fffff880`0f68bb40 fffff800`014cc993 : fffffa80`06b4a060 00000000`04f3c858 00000000`000010d0 fffff880`0f68bc20 : nt!NtTraceControl+0x208
    fffff880`0f68bbb0 00000000`76fe0efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`04f3c838 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fe0efa
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP:
    nt!NtTraceControl+208
    fffff800`01775edc 8bc3            mov     eax,ebx
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!NtTraceControl+208
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd
    
    FAILURE_BUCKET_ID:  X64_0x19_21_nt!NtTraceControl+208
    
    BUCKET_ID:  X64_0x19_21_nt!NtTraceControl+208
    
    Followup: MachineOwner
    ---------
    
    
    Thank you in advance for any help in understanding this minidump output.

    Regards,
    Piotr
  2. Route44

    Route44 TechSpot Ambassador Posts: 12,140   +29

    Please use the Manage Attachments button the next time you post and attach that minidump. The button can be found when you scroll down.


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.