BSOD - Bad_Pool_Header


  1. Posts : 3
    Windows 7 Home Premium 64 bit
       #1

    BSOD - Bad_Pool_Header


    Running Win7 Home Premium, 64 bit, 4GB RAM, on a two year old ASUS Notebook K50IJ.

    Have been getting these BSODs for about a year and a half. Re-installed Win 7 once, but that didn't take care of the problem. Stopped it for a while, but it did come back. Get them every couple of weeks or so, it seems. Almost always says BAD_POOL_HEADER. There was another message twice, but don't remember what it is.

    Since the warranty is up soon (24th of Feb), I took it into Best Buy for them to fix some other issues (broken keyboard, hinge cover) and mentioned the BSOD. They kept it for a day, then called on the 15th and assured me after running a check on the memory and the HD that it could be a 'minor adware issue' causing the BSOD (FYI, I ran checks on my system for adware before and after taking it in, and found none - I do this regularly, so...). They said they tried to make it do the BSOD with no luck. I went and picked it up that night, deciding to fix the keyboard and hinge cover myself.

    So, tonight, I was downloading some files and got the good old BAD_POOL_HEADER BSOD.

    I went into the Event Viewer and saw the errors from around the time of the BSOD - Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider, Catastrophic Failure. Don't know if that's any help or not.

    After looking at the Event Viewer, I used the SF Diagnostic Tool and the zip file is attached.

    If anyone can be of any assistance, I would certainly appreciate it - thank you kindly.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to SevenForums.

    From the dump files (even the one from 2012) looks as if Asus Data Security Manager Driver is the cause of the BSOD. Driver description and information: Driver Reference Table - AsDsm.sys

    You might find this tutorial useful: Clean Up Factory Bloatware
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {20, fffff8a00b70d000, fffff8a00b70d410, 5410100}
    
    *** WARNING: Unable to verify timestamp for AsDsm.sys
    *** ERROR: Module load completed but symbols could not be loaded for AsDsm.sys
    Probably caused by : AsDsm.sys ( AsDsm+7afd )
    
    Followup: MachineOwner
    ---------
    
    0: 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: 0000000000000020, a pool block header size is corrupt.
    Arg2: fffff8a00b70d000, The pool entry we were looking for within the page.
    Arg3: fffff8a00b70d410, The next pool entry.
    Arg4: 0000000005410100, (reserved)
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x19_20
    
    POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800030be100
    GetUlongFromAddress: unable to read from fffff800030be1c0
     fffff8a00b70d000 Paged pool
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  explorer.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002fb9cae to fffff80002e85c40
    
    STACK_TEXT:  
    fffff880`0a9f2588 fffff800`02fb9cae : 00000000`00000019 00000000`00000020 fffff8a0`0b70d000 fffff8a0`0b70d410 : nt!KeBugCheckEx
    fffff880`0a9f2590 fffff880`012b0afd : fffffa80`049d5b40 fffffa80`0ba3a380 fffffa80`6e705341 fffff8a0`0b70d010 : nt!ExDeferredFreePool+0x12da
    fffff880`0a9f2640 fffffa80`049d5b40 : fffffa80`0ba3a380 fffffa80`6e705341 fffff8a0`0b70d010 fffff880`0a9f26a0 : AsDsm+0x7afd
    fffff880`0a9f2648 fffffa80`0ba3a380 : fffffa80`6e705341 fffff8a0`0b70d010 fffff880`0a9f26a0 fffff800`031913b2 : 0xfffffa80`049d5b40
    fffff880`0a9f2650 fffffa80`6e705341 : fffff8a0`0b70d010 fffff880`0a9f26a0 fffff800`031913b2 00000000`00000000 : 0xfffffa80`0ba3a380
    fffff880`0a9f2658 fffff8a0`0b70d010 : fffff880`0a9f26a0 fffff800`031913b2 00000000`00000000 00000000`00000000 : 0xfffffa80`6e705341
    fffff880`0a9f2660 fffff880`0a9f26a0 : fffff800`031913b2 00000000`00000000 00000000`00000000 00000000`00000200 : 0xfffff8a0`0b70d010
    fffff880`0a9f2668 fffff800`031913b2 : 00000000`00000000 00000000`00000000 00000000`00000200 fffffa80`0af86970 : 0xfffff880`0a9f26a0
    fffff880`0a9f2670 fffff800`031880fc : 00000000`00000005 fffffa80`0bba9cc8 fffffa80`04840f20 fffffa80`04840fb8 : nt!IopAllocRealFileObject+0x282
    fffff880`0a9f2720 fffff800`03183a78 : fffffa80`049c43d0 fffff800`00000000 fffffa80`0bba9b10 fffff8a0`00000001 : nt!IopParseDevice+0x14d3
    fffff880`0a9f2880 fffff800`03184c96 : 00000000`00000000 fffffa80`0bba9b10 00000000`00000000 fffffa80`03d38f30 : nt!ObpLookupObjectName+0x588
    fffff880`0a9f2970 fffff800`0318659c : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ObOpenObjectByName+0x306
    fffff880`0a9f2a40 fffff800`03191b64 : 00000000`036fecb8 00000000`80100080 00000000`036fed08 00000000`036fecc8 : nt!IopCreateFile+0x2bc
    fffff880`0a9f2ae0 fffff800`02e84ed3 : 00000000`002ca640 00000000`036fecc0 00000000`0ab57778 00000000`20004000 : nt!NtCreateFile+0x78
    fffff880`0a9f2b70 00000000`774d186a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`036fec38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774d186a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    AsDsm+7afd
    fffff880`012b0afd ??              ???
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  AsDsm+7afd
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AsDsm
    
    IMAGE_NAME:  AsDsm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  49950fc2
    
    FAILURE_BUCKET_ID:  X64_0x19_20_AsDsm+7afd
    
    BUCKET_ID:  X64_0x19_20_AsDsm+7afd
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm AsDsm
    start             end                 module name
    fffff880`012a9000 fffff880`012b6000   AsDsm    T (no symbols)           
        Loaded symbol image file: AsDsm.sys
        Image path: \SystemRoot\System32\Drivers\AsDsm.sys
        Image name: AsDsm.sys
        Timestamp:        Fri Feb 13 12:14:26 2009 (49950FC2)
        CheckSum:         0001216E
        ImageSize:        0000D000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Use Revo uninstaller free Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems, uninstall using Advanced mode to remove the leftover registry of the software.

    Perform a System File Check to check the integrity of all protected Windows 7 :
    1. Click on the start
    2. Type CMD on Search
    3. Left click and Run as Administrator
    4. Type
      Code:
      SFC /scannow

    Full tutorial here:

    Disk Check on your hard drive for file system errors and bad sectors on it.

    Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.

    Let us know the results.
       Information
    BTW & FYI here's a thread where the same software was causing BSOD for another usr. Go through for reference: BSOD in normal mode (various errors), Runs fine in Safe Mode
      My Computer


  3. Posts : 3
    Windows 7 Home Premium 64 bit
    Thread Starter
       #3

    Thank you kindly for taking the time to assist me - I will do as you've directed. I very much appreciate it.
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    Happy to help and look forward to the results! :)
      My Computer


  5. Posts : 3
    Windows 7 Home Premium 64 bit
    Thread Starter
       #5

    So far, so good! I'm going to mark this solved. You rock! Thank you!
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    Good to hear :)

    Be sure to post if you have any problems again.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:03.
Find Us