locked
BAD_POOL_CALLER when woken up from sleep? RRS feed

  • Question

  • Whenever i wake up my laptop after sleeping, it gives me the blue screen with the BAD POOL CALLER error on it?

    my laptop is only a few days old?

    Wednesday, November 27, 2013 12:54 PM

Answers

  • BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 0000000000000007, Attempt to free pool which was already freed
    Arg2: 00000000000011c1, (reserved)
    Arg3: 0000000004440000, Memory contents of the pool block
    Arg4: fffffa8005201010, Address of the block of pool being deallocated
    
    Debugging Details:
    ------------------
    
    
    POOL_ADDRESS:  fffffa8005201010 Nonpaged pool
    
    FREED_POOL_TAG:  aPmI
    
    BUGCHECK_STR:  0xc2_7_aPmI
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff800a0a77a5a to fffff800a0882040
    
    STACK_TEXT:  
    fffff880`1cc4b188 fffff800`a0a77a5a : 00000000`000000c2 00000000`00000007 00000000`000011c1 00000000`04440000 : nt!KeBugCheckEx
    fffff880`1cc4b190 fffff880`01e577a9 : fffffa80`05201010 00000000`00000000 fffffa80`042cc6d0 fffffa80`6370444e : nt!ExFreePool+0x97c
    fffff880`1cc4b270 fffff880`04e2dbac : fffff880`1cc4b4b0 fffffa80`07dc8778 fffffa80`07dc8778 fffffa80`07dc8778 : ndis!NdisFreeMemory+0x15
    fffff880`1cc4b2a0 fffff880`1cc4b4b0 : fffffa80`07dc8778 fffffa80`07dc8778 fffffa80`07dc8778 fffff880`04e37100 : HssDrv+0x2bac
    fffff880`1cc4b2a8 fffffa80`07dc8778 : fffffa80`07dc8778 fffffa80`07dc8778 fffff880`04e37100 fffff800`00000004 : 0xfffff880`1cc4b4b0
    fffff880`1cc4b2b0 fffffa80`07dc8778 : fffffa80`07dc8778 fffff880`04e37100 fffff800`00000004 fffffa80`081dab00 : 0xfffffa80`07dc8778
    fffff880`1cc4b2b8 fffffa80`07dc8778 : fffff880`04e37100 fffff800`00000004 fffffa80`081dab00 fffffa80`05201010 : 0xfffffa80`07dc8778
    fffff880`1cc4b2c0 fffff880`04e37100 : fffff800`00000004 fffffa80`081dab00 fffffa80`05201010 fffffa80`07dc8778 : 0xfffffa80`07dc8778
    fffff880`1cc4b2c8 fffff800`00000004 : fffffa80`081dab00 fffffa80`05201010 fffffa80`07dc8778 fffffa80`00000000 : HssDrv+0xc100
    fffff880`1cc4b2d0 fffffa80`081dab00 : fffffa80`05201010 fffffa80`07dc8778 fffffa80`00000000 00000000`00000000 : 0xfffff800`00000004
    fffff880`1cc4b2d8 fffffa80`05201010 : fffffa80`07dc8778 fffffa80`00000000 00000000`00000000 fffff8a0`0dcb84f0 : 0xfffffa80`081dab00
    fffff880`1cc4b2e0 fffffa80`07dc8778 : fffffa80`00000000 00000000`00000000 fffff8a0`0dcb84f0 fffffa80`081dab40 : 0xfffffa80`05201010
    fffff880`1cc4b2e8 fffffa80`00000000 : 00000000`00000000 fffff8a0`0dcb84f0 fffffa80`081dab40 fffffa80`05201010 : 0xfffffa80`07dc8778
    fffff880`1cc4b2f0 00000000`00000000 : fffff8a0`0dcb84f0 fffffa80`081dab40 fffffa80`05201010 fffffa80`0c7d91e8 : 0xfffffa80`00000000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    HssDrv+2bac
    fffff880`04e2dbac ??              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  HssDrv+2bac
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: HssDrv
    
    IMAGE_NAME:  HssDrv.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c7fe308
    
    FAILURE_BUCKET_ID:  0xc2_7_aPmI_HssDrv+2bac
    
    BUCKET_ID:  0xc2_7_aPmI_HssDrv+2bac

    According to the dump file,I suggest you update or remove HotSpotShield to check the result.

    It seems that it is not compatible with Windows 8.

    Hope this helps.

    Regards,


    Kelvin hsu
    TechNet Community Support

    • Proposed as answer by 暁北 Friday, November 29, 2013 6:29 AM
    • Marked as answer by ZigZag3143x Saturday, November 30, 2013 2:38 AM
    Thursday, November 28, 2013 12:58 PM
  • SkullyxHead

    Kelvin Hsu is correct.  These were related to Hot Shield.  Yours is 3+ years old.  You may be able to keep using it if You update it to current but IMHO there are much better products on the market.

    9/2/2010 12:46:48 PM is before win 8 was released.


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Saturday, November 30, 2013 2:38 AM
    Thursday, November 28, 2013 4:32 PM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont know what it is you probably are not overclocking.

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  

    *

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy (compress them)

    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.

     

    Link for how to  upload below.
    *
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    *
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...

    You can read more about BSODS here
    You can learn how to test your memory here
    Asking an effective question to get help fast here
    Basic troubleshooting tips can be found here
    Driver verifier-Tracking down a mis behaving driver  here
    Links to out other wiki's can be found here.


    Co-Authored by  JMH3143

    Wanikiya and Dyami--Team Zigzag

    Wednesday, November 27, 2013 1:34 PM
  • Hello, i uploaded everything here.

    http://rapidshare.com/share/A5E14A5117F1C083BF2E7749A1DFA0B0

    thanks in advance.

    Thursday, November 28, 2013 5:09 AM
  • BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 0000000000000007, Attempt to free pool which was already freed
    Arg2: 00000000000011c1, (reserved)
    Arg3: 0000000004440000, Memory contents of the pool block
    Arg4: fffffa8005201010, Address of the block of pool being deallocated
    
    Debugging Details:
    ------------------
    
    
    POOL_ADDRESS:  fffffa8005201010 Nonpaged pool
    
    FREED_POOL_TAG:  aPmI
    
    BUGCHECK_STR:  0xc2_7_aPmI
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff800a0a77a5a to fffff800a0882040
    
    STACK_TEXT:  
    fffff880`1cc4b188 fffff800`a0a77a5a : 00000000`000000c2 00000000`00000007 00000000`000011c1 00000000`04440000 : nt!KeBugCheckEx
    fffff880`1cc4b190 fffff880`01e577a9 : fffffa80`05201010 00000000`00000000 fffffa80`042cc6d0 fffffa80`6370444e : nt!ExFreePool+0x97c
    fffff880`1cc4b270 fffff880`04e2dbac : fffff880`1cc4b4b0 fffffa80`07dc8778 fffffa80`07dc8778 fffffa80`07dc8778 : ndis!NdisFreeMemory+0x15
    fffff880`1cc4b2a0 fffff880`1cc4b4b0 : fffffa80`07dc8778 fffffa80`07dc8778 fffffa80`07dc8778 fffff880`04e37100 : HssDrv+0x2bac
    fffff880`1cc4b2a8 fffffa80`07dc8778 : fffffa80`07dc8778 fffffa80`07dc8778 fffff880`04e37100 fffff800`00000004 : 0xfffff880`1cc4b4b0
    fffff880`1cc4b2b0 fffffa80`07dc8778 : fffffa80`07dc8778 fffff880`04e37100 fffff800`00000004 fffffa80`081dab00 : 0xfffffa80`07dc8778
    fffff880`1cc4b2b8 fffffa80`07dc8778 : fffff880`04e37100 fffff800`00000004 fffffa80`081dab00 fffffa80`05201010 : 0xfffffa80`07dc8778
    fffff880`1cc4b2c0 fffff880`04e37100 : fffff800`00000004 fffffa80`081dab00 fffffa80`05201010 fffffa80`07dc8778 : 0xfffffa80`07dc8778
    fffff880`1cc4b2c8 fffff800`00000004 : fffffa80`081dab00 fffffa80`05201010 fffffa80`07dc8778 fffffa80`00000000 : HssDrv+0xc100
    fffff880`1cc4b2d0 fffffa80`081dab00 : fffffa80`05201010 fffffa80`07dc8778 fffffa80`00000000 00000000`00000000 : 0xfffff800`00000004
    fffff880`1cc4b2d8 fffffa80`05201010 : fffffa80`07dc8778 fffffa80`00000000 00000000`00000000 fffff8a0`0dcb84f0 : 0xfffffa80`081dab00
    fffff880`1cc4b2e0 fffffa80`07dc8778 : fffffa80`00000000 00000000`00000000 fffff8a0`0dcb84f0 fffffa80`081dab40 : 0xfffffa80`05201010
    fffff880`1cc4b2e8 fffffa80`00000000 : 00000000`00000000 fffff8a0`0dcb84f0 fffffa80`081dab40 fffffa80`05201010 : 0xfffffa80`07dc8778
    fffff880`1cc4b2f0 00000000`00000000 : fffff8a0`0dcb84f0 fffffa80`081dab40 fffffa80`05201010 fffffa80`0c7d91e8 : 0xfffffa80`00000000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    HssDrv+2bac
    fffff880`04e2dbac ??              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  HssDrv+2bac
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: HssDrv
    
    IMAGE_NAME:  HssDrv.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c7fe308
    
    FAILURE_BUCKET_ID:  0xc2_7_aPmI_HssDrv+2bac
    
    BUCKET_ID:  0xc2_7_aPmI_HssDrv+2bac

    According to the dump file,I suggest you update or remove HotSpotShield to check the result.

    It seems that it is not compatible with Windows 8.

    Hope this helps.

    Regards,


    Kelvin hsu
    TechNet Community Support

    • Proposed as answer by 暁北 Friday, November 29, 2013 6:29 AM
    • Marked as answer by ZigZag3143x Saturday, November 30, 2013 2:38 AM
    Thursday, November 28, 2013 12:58 PM
  • SkullyxHead

    Kelvin Hsu is correct.  These were related to Hot Shield.  Yours is 3+ years old.  You may be able to keep using it if You update it to current but IMHO there are much better products on the market.

    9/2/2010 12:46:48 PM is before win 8 was released.


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Saturday, November 30, 2013 2:38 AM
    Thursday, November 28, 2013 4:32 PM