Frequent BSD IRQL Not less or equal and Bad pool header


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

    Frequent BSD IRQL Not less or equal and Bad pool header


    From what I've noticed there isn't much of a pattern of when it happens, except that it happens when my pc is working on a lot of processes. Several times it's happened while playing League of Legends. It started on the 15th and on the 17th it crashed multiple times. From what I understand it is a bad driver, but I haven't installed any new hardware in weeks and I don't see any issues in the device manager.
      My Computer


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

    Welcome to the forum.

    Please check for an update for this driver: Driver Reference Table

    Code:
    
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\YUSRA\Downloads\AARON-HP-Wed_02_18_2015__00553_86\021715-43103-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
    Machine Name:
    Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`0305f890
    Debug session time: Wed Feb 18 06:06:43.036 2015 (UTC + 6:00)
    System Uptime: 0 days 0:04:34.534
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    .........................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {21, fffffa8003d1c000, 7810, 0}
    
    *** WARNING: Unable to verify timestamp for rtwlanu.sys
    *** ERROR: Module load completed but symbols could not be loaded for rtwlanu.sys
    Probably caused by : rtwlanu.sys ( rtwlanu+122fd )
    
    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: 0000000000000021, the data following the pool block being freed is corrupt.  Typically this means the consumer (call stack ) has overrun the block.
    Arg2: fffffa8003d1c000, The pool pointer being freed.
    Arg3: 0000000000007810, The number of bytes allocated for the pool block.
    Arg4: 0000000000000000, The corrupted value found following the pool block.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x19_21
    
    POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c9100
    GetUlongFromAddress: unable to read from fffff800030c91c0
     fffffa8003d1c000 Nonpaged pool
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  GetPopupInfo.e
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre
    
    DPC_STACK_BASE:  FFFFF80000BA0FB0
    
    LAST_CONTROL_TRANSFER:  from fffff80002fc49c2 to fffff80002e8fec0
    
    STACK_TEXT:  
    fffff800`00ba0158 fffff800`02fc49c2 : 00000000`00000019 00000000`00000021 fffffa80`03d1c000 00000000`00007810 : nt!KeBugCheckEx
    fffff800`00ba0160 fffff880`014ab845 : 00000000`00000000 fffffa80`03d1c094 00000000`37383138 00000000`00000000 : nt!ExFreePool+0xa5a
    fffff800`00ba0210 fffff880`074962fd : fffff6fb`7ea000f0 fffff6fd`4001e8e0 fffffa80`03d1c018 000a41f8`0613be00 : ndis!NdisFreeMemory+0x15
    fffff800`00ba0240 fffff6fb`7ea000f0 : fffff6fd`4001e8e0 fffffa80`03d1c018 000a41f8`0613be00 fffffa80`066f5e40 : rtwlanu+0x122fd
    fffff800`00ba0248 fffff6fd`4001e8e0 : fffffa80`03d1c018 000a41f8`0613be00 fffffa80`066f5e40 fffff880`074a01f3 : 0xfffff6fb`7ea000f0
    fffff800`00ba0250 fffffa80`03d1c018 : 000a41f8`0613be00 fffffa80`066f5e40 fffff880`074a01f3 fffffa80`03d1c018 : 0xfffff6fd`4001e8e0
    fffff800`00ba0258 000a41f8`0613be00 : fffffa80`066f5e40 fffff880`074a01f3 fffffa80`03d1c018 fffff800`0000091c : 0xfffffa80`03d1c018
    fffff800`00ba0260 fffffa80`066f5e40 : fffff880`074a01f3 fffffa80`03d1c018 fffff800`0000091c fffffa80`03d1c018 : 0x000a41f8`0613be00
    fffff800`00ba0268 fffff880`074a01f3 : fffffa80`03d1c018 fffff800`0000091c fffffa80`03d1c018 fffffa80`0602fffc : 0xfffffa80`066f5e40
    fffff800`00ba0270 fffffa80`03d1c018 : fffff800`0000091c fffffa80`03d1c018 fffffa80`0602fffc fffffa80`066f5e40 : rtwlanu+0x1c1f3
    fffff800`00ba0278 fffff800`0000091c : fffffa80`03d1c018 fffffa80`0602fffc fffffa80`066f5e40 fffff880`074c571a : 0xfffffa80`03d1c018
    fffff800`00ba0280 fffffa80`03d1c018 : fffffa80`0602fffc fffffa80`066f5e40 fffff880`074c571a 00000000`00000000 : 0xfffff800`0000091c
    fffff800`00ba0288 fffffa80`0602fffc : fffffa80`066f5e40 fffff880`074c571a 00000000`00000000 00000000`00000000 : 0xfffffa80`03d1c018
    fffff800`00ba0290 fffffa80`066f5e40 : fffff880`074c571a 00000000`00000000 00000000`00000000 fffffa80`03d1c018 : 0xfffffa80`0602fffc
    fffff800`00ba0298 fffff880`074c571a : 00000000`00000000 00000000`00000000 fffffa80`03d1c018 00000000`00000000 : 0xfffffa80`066f5e40
    fffff800`00ba02a0 00000000`00000000 : 00000000`00000000 fffffa80`03d1c018 00000000`00000000 fffffa80`06029000 : rtwlanu+0x4171a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    rtwlanu+122fd
    fffff880`074962fd ??              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  rtwlanu+122fd
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: rtwlanu
    
    IMAGE_NAME:  rtwlanu.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f28f37e
    
    FAILURE_BUCKET_ID:  X64_0x19_21_rtwlanu+122fd
    
    BUCKET_ID:  X64_0x19_21_rtwlanu+122fd
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x19_21_rtwlanu+122fd
    
    FAILURE_ID_HASH:  {0f332ab0-4cd5-3625-918e-fed8b5187c4f}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm rtwlanu
    start             end                 module name
    fffff880`07484000 fffff880`0759a000   rtwlanu  T (no symbols)           
        Loaded symbol image file: rtwlanu.sys
        Image path: \SystemRoot\system32\DRIVERS\rtwlanu.sys
        Image name: rtwlanu.sys
        Timestamp:        Wed Feb 01 14:10:38 2012 (4F28F37E)
        CheckSum:         00103823
        ImageSize:        00116000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


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

    So I got the tool, and found the outdated driver, what is the other link for?
      My Computer


  4. Posts : 2,781
    Windows 10 Pro x64
       #4

    Upgrade the outdated driver.
      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 18:48.
Find Us