locked
Windows 7 Ultimate 64 SP1 STOP 0x19 BAD_POOL_HEADER RRS feed

  • Question

  • I received a STOP 0x19 BAD_POOL_HEADER while browsing the internet a few minutes ago. But I also run BOINC Manager in the background all the time.

    I ran the Windows Memory Diagnostic and although it said it would tell me the results after login it did not. I've also turned on verifier for all non-Microsoft drivers since the crash. Below is the link to the minidumps.

    Today's crash: http://sdrv.ms/ZOxrWX

    Last month's crash: http://sdrv.ms/ZOxKkv

    Thanks,

    Jim

    Saturday, April 27, 2013 7:08 PM

Answers

  • Hi,

    After checking your dump file:

    *******************************************************************************

    *                                                                             *

    *                        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: fffff8a02b883000, The pool pointer being freed.

    Arg3: 000000000000b950, The number of bytes allocated for the pool block.

    Arg4: 7913000000000000, The corrupted value found following the pool block.

    Debugging Details:

    ------------------

    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

    BUGCHECK_STR:  0x19_21

    POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80003701100

    GetUlongFromAddress: unable to read from fffff800037011c0

    fffff8a02b883000 Paged pool

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  iexplore.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff800035fc9b2 to fffff800034c9c00

    STACK_COMMAND:  kb

    FOLLOWUP_IP:

    igdkmd64+743f4

    fffff880`0511f3f4 ??              ???

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  igdkmd64+743f4

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: igdkmd64

    IMAGE_NAME:  igdkmd64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  50c92472

    FAILURE_BUCKET_ID:  X64_0x19_21_igdkmd64+743f4

    BUCKET_ID:  X64_0x19_21_igdkmd64+743f4

    Followup: MachineOwner

    ---------

    About bugcheck 0x19, you can refer this article:

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff557389(v=vs.85).aspx

    And igdkmd64.sys crash may be caused by the graphic card, please update your VGA card, also update BIOS and Chipset to the latest version.

    Regards,

    Leo   Huang

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Leo Huang
    TechNet Community Support

    • Marked as answer by ZigZag3143x Wednesday, May 8, 2013 12:22 PM
    Monday, April 29, 2013 2:58 AM
  • Jim

    In addition to LH's correct analysis there are some old drivers needing updating and if you keep crashing I would remove and replace McAfee with MSE

    Old drivers                     

    purendis.sys    10/28/2008 12:31:28 AM                        
    pnarp.sys    10/28/2008 1:57:00 AM       

    McAffe often contributes to BSOD'S

    I would remove and replace it with Microsoft Security Essentials

    http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

    http://www.microsoft.com/security_essentials/

    How To Find Drivers:


    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program

    The most common drivers are listed on this page: Driver Reference

    http://www.carrona.org/dvrref.php

    http://sysnative.com/drivers/

    - - Driver manufacturer links are on this page: http://www.carrona.org

    BugCheck 19, {21, fffff8a02b883000, b950, 7913000000000000}

    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    Probably caused by : igdkmd64.sys ( igdkmd64+743f4 )


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com


    • Edited by ZigZag3143x Monday, April 29, 2013 3:44 AM
    • Marked as answer by Leo Huang Wednesday, May 8, 2013 9:16 AM
    Monday, April 29, 2013 3:43 AM

All replies

  • Hi,

    After checking your dump file:

    *******************************************************************************

    *                                                                             *

    *                        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: fffff8a02b883000, The pool pointer being freed.

    Arg3: 000000000000b950, The number of bytes allocated for the pool block.

    Arg4: 7913000000000000, The corrupted value found following the pool block.

    Debugging Details:

    ------------------

    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

    BUGCHECK_STR:  0x19_21

    POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80003701100

    GetUlongFromAddress: unable to read from fffff800037011c0

    fffff8a02b883000 Paged pool

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  iexplore.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff800035fc9b2 to fffff800034c9c00

    STACK_COMMAND:  kb

    FOLLOWUP_IP:

    igdkmd64+743f4

    fffff880`0511f3f4 ??              ???

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  igdkmd64+743f4

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: igdkmd64

    IMAGE_NAME:  igdkmd64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  50c92472

    FAILURE_BUCKET_ID:  X64_0x19_21_igdkmd64+743f4

    BUCKET_ID:  X64_0x19_21_igdkmd64+743f4

    Followup: MachineOwner

    ---------

    About bugcheck 0x19, you can refer this article:

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff557389(v=vs.85).aspx

    And igdkmd64.sys crash may be caused by the graphic card, please update your VGA card, also update BIOS and Chipset to the latest version.

    Regards,

    Leo   Huang

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Leo Huang
    TechNet Community Support

    • Marked as answer by ZigZag3143x Wednesday, May 8, 2013 12:22 PM
    Monday, April 29, 2013 2:58 AM
  • Jim

    In addition to LH's correct analysis there are some old drivers needing updating and if you keep crashing I would remove and replace McAfee with MSE

    Old drivers                     

    purendis.sys    10/28/2008 12:31:28 AM                        
    pnarp.sys    10/28/2008 1:57:00 AM       

    McAffe often contributes to BSOD'S

    I would remove and replace it with Microsoft Security Essentials

    http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

    http://www.microsoft.com/security_essentials/

    How To Find Drivers:


    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program

    The most common drivers are listed on this page: Driver Reference

    http://www.carrona.org/dvrref.php

    http://sysnative.com/drivers/

    - - Driver manufacturer links are on this page: http://www.carrona.org

    BugCheck 19, {21, fffff8a02b883000, b950, 7913000000000000}

    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    Probably caused by : igdkmd64.sys ( igdkmd64+743f4 )


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com


    • Edited by ZigZag3143x Monday, April 29, 2013 3:44 AM
    • Marked as answer by Leo Huang Wednesday, May 8, 2013 9:16 AM
    Monday, April 29, 2013 3:43 AM
  • Hi,

    How’s everything going? Please feel free to give me any update.

    Thank you for your cooperation.

    Regards,

    Leo   Huang

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Leo Huang
    TechNet Community Support

    Thursday, May 2, 2013 8:57 AM
  • Hi,

     

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to  reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

    BTW,  we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.

     

    Regards,

    Leo   Huang

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Leo Huang
    TechNet Community Support

    Wednesday, May 8, 2013 9:16 AM