locked
BSOD BAD POOL CALLER error in my HP envy 15 Windows 8.1 Laptop? RRS feed

  • Question

  • My HP Envy 15 Laptop is getting this BAD POOL CALLER error and keep restarting more often. I have windows 8.1 in my laptop. Can anyone please help me to solve this. This is the link for my Minidump files. Thank you!

    https://drive.google.com/file/d/0B5JX5f-rzA4-emJuNWpnOE9sMVE/view?usp=sharing

    Tuesday, May 12, 2015 5:48 PM

Answers

  • ASW

    Related to ewusbnet.sys USB NDIS Miniport Driver from Huawei Technologies Co., Ltd.  I would remove the current drier and install the newest driver available.

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\051215-26234-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
    Machine Name:
    Kernel base = 0xfffff802`3607c000 PsLoadedModuleList = 0xfffff802`36355850
    Debug session time: Mon May 11 21:38:04.046 2015 (UTC - 4:00)
    System Uptime: 0 days 12:45:52.808
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ........
    Loading User Symbols
    Loading unloaded module list
    ............................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C2, {10, fffff802363682c0, 36368340, fffff802363682f0}
    
    *** WARNING: Unable to verify timestamp for ewusbnet.sys
    *** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
    Probably caused by : ewusbnet.sys ( ewusbnet+24b5 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: 0000000000000010, type of pool violation the caller is guilty of.
    Arg2: fffff802363682c0
    Arg3: 0000000036368340
    Arg4: fffff802363682f0
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    ndis!NdisFreeMemory+15
    fffff801`6aa6fba1 4883c428        add     rsp,28h
    
    BUGCHECK_STR:  0xc2_10
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff802363210cc to fffff802361ccca0
    
    STACK_TEXT:  
    ffffd000`25f14758 fffff802`363210cc : 00000000`000000c2 00000000`00000010 fffff802`363682c0 00000000`36368340 : nt!KeBugCheckEx
    ffffd000`25f14760 fffff801`6aa6fba1 : 00000000`00000000 00000000`00000000 ffffe000`08afc010 fffff802`00000036 : nt!ExAllocatePoolWithTag+0x11dc
    ffffd000`25f14850 fffff801`6da564b5 : 00000000`00000002 fffff802`36131c2a 00000000`00000000 00000000`00000000 : ndis!NdisFreeMemory+0x15
    ffffd000`25f14880 00000000`00000002 : fffff802`36131c2a 00000000`00000000 00000000`00000000 ffffe000`08f30fb3 : ewusbnet+0x24b5
    ffffd000`25f14888 fffff802`36131c2a : 00000000`00000000 00000000`00000000 ffffe000`08f30fb3 fffff802`3613403a : 0x2
    ffffd000`25f14890 fffff801`6da6a291 : 00000000`00000000 fffff802`36368d88 ffffd000`ad76ba02 fffff802`36369480 : nt!KeSetEvent+0x2aa
    ffffd000`25f14950 00000000`00000000 : fffff802`36368d88 ffffd000`ad76ba02 fffff802`36369480 00000000`000005b0 : ewusbnet+0x16291
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    ewusbnet+24b5
    fffff801`6da564b5 ??              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  ewusbnet+24b5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ewusbnet
    
    IMAGE_NAME:  ewusbnet.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bdabd9c
    
    FAILURE_BUCKET_ID:  0xc2_10_ewusbnet+24b5
    
    BUCKET_ID:  0xc2_10_ewusbnet+24b5
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xc2_10_ewusbnet+24b5
    
    FAILURE_ID_HASH:  {1ac0c4e2-e488-03d2-629b-fc57c549fc4d}
    
    Followup: MachineOwner
    ---------
    


    Wanikiya and Dyami--Team Zigzag


    Tuesday, May 12, 2015 6:10 PM

All replies

  • ASW

    Related to ewusbnet.sys USB NDIS Miniport Driver from Huawei Technologies Co., Ltd.  I would remove the current drier and install the newest driver available.

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\051215-26234-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
    Machine Name:
    Kernel base = 0xfffff802`3607c000 PsLoadedModuleList = 0xfffff802`36355850
    Debug session time: Mon May 11 21:38:04.046 2015 (UTC - 4:00)
    System Uptime: 0 days 12:45:52.808
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ........
    Loading User Symbols
    Loading unloaded module list
    ............................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C2, {10, fffff802363682c0, 36368340, fffff802363682f0}
    
    *** WARNING: Unable to verify timestamp for ewusbnet.sys
    *** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
    Probably caused by : ewusbnet.sys ( ewusbnet+24b5 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: 0000000000000010, type of pool violation the caller is guilty of.
    Arg2: fffff802363682c0
    Arg3: 0000000036368340
    Arg4: fffff802363682f0
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    ndis!NdisFreeMemory+15
    fffff801`6aa6fba1 4883c428        add     rsp,28h
    
    BUGCHECK_STR:  0xc2_10
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff802363210cc to fffff802361ccca0
    
    STACK_TEXT:  
    ffffd000`25f14758 fffff802`363210cc : 00000000`000000c2 00000000`00000010 fffff802`363682c0 00000000`36368340 : nt!KeBugCheckEx
    ffffd000`25f14760 fffff801`6aa6fba1 : 00000000`00000000 00000000`00000000 ffffe000`08afc010 fffff802`00000036 : nt!ExAllocatePoolWithTag+0x11dc
    ffffd000`25f14850 fffff801`6da564b5 : 00000000`00000002 fffff802`36131c2a 00000000`00000000 00000000`00000000 : ndis!NdisFreeMemory+0x15
    ffffd000`25f14880 00000000`00000002 : fffff802`36131c2a 00000000`00000000 00000000`00000000 ffffe000`08f30fb3 : ewusbnet+0x24b5
    ffffd000`25f14888 fffff802`36131c2a : 00000000`00000000 00000000`00000000 ffffe000`08f30fb3 fffff802`3613403a : 0x2
    ffffd000`25f14890 fffff801`6da6a291 : 00000000`00000000 fffff802`36368d88 ffffd000`ad76ba02 fffff802`36369480 : nt!KeSetEvent+0x2aa
    ffffd000`25f14950 00000000`00000000 : fffff802`36368d88 ffffd000`ad76ba02 fffff802`36369480 00000000`000005b0 : ewusbnet+0x16291
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    ewusbnet+24b5
    fffff801`6da564b5 ??              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  ewusbnet+24b5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ewusbnet
    
    IMAGE_NAME:  ewusbnet.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bdabd9c
    
    FAILURE_BUCKET_ID:  0xc2_10_ewusbnet+24b5
    
    BUCKET_ID:  0xc2_10_ewusbnet+24b5
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xc2_10_ewusbnet+24b5
    
    FAILURE_ID_HASH:  {1ac0c4e2-e488-03d2-629b-fc57c549fc4d}
    
    Followup: MachineOwner
    ---------
    


    Wanikiya and Dyami--Team Zigzag


    Tuesday, May 12, 2015 6:10 PM
  • Thanks a lot. I will do that!
    Wednesday, May 13, 2015 4:22 PM
  • Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          6/10/2015 3:05:10 PM
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      HP-ENVY
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>3</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000002</Keywords>
        <TimeCreated SystemTime="2015-06-10T10:05:10.833208300Z" />
        <EventRecordID>3888</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>HP-ENVY</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">0</Data>
        <Data Name="BugcheckParameter1">0x0</Data>
        <Data Name="BugcheckParameter2">0x0</Data>
        <Data Name="BugcheckParameter3">0x0</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">0</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
        <Data Name="BootAppStatus">0</Data>
      </EventData>
    </Event>
    Wednesday, June 10, 2015 10:49 AM
  • how to solve bad pool caller
    Wednesday, June 10, 2015 10:50 AM
  •  
    We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask


    Wanikiya and Dyami--Team Zigzag

    Wednesday, June 10, 2015 11:09 AM