Random BSoD - IRQL_NOT_LESS_OR_EQUAL

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by TheRealOne, Jun 1, 2011.

  1. TheRealOne

    TheRealOne New Member

    Joined:
    Jun 1, 2011
    Messages:
    6
    Likes Received:
    0
    Hi all,

    Long time reader, first time poster.

    I've been recently having troubles with a new PC build of mine (constructed at Xmas '1View attachment 060111-22807-01.dmpView attachment 060111-24258-01.dmp 0), whereby I am getting completely random BSoDs. These happen at varying intervals, anywhere from immediately after startup to 5-6 days after the previous one.

    As it's only very quick (memory dump), I've managed to catch that the main error seems to be IRQL_NOT_LESS_OR_EQUAL.

    Having little knowledge on interpreting such messages, I've tried all the usual bluescreen repairs (memory tests, chkdsk, various hardware drivers), all to no avail.

    I've attached the most recent two bluescreen minidumps, hopefully they can be of assistance in rectifying this problem.

    Thanks in advance :)

    View attachment 060111-24258-01.dmpView attachment 060111-22807-01.dmp
     
  2. TheRealOne

    TheRealOne New Member

    Joined:
    Jun 1, 2011
    Messages:
    6
    Likes Received:
    0
  3. kaos

    kaos Senior Member

    Joined:
    May 9, 2011
    Messages:
    1,747
    Likes Received:
    33
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 19, {3, fffffa80069dbb20, fffffa80069dbb20, fffffa80069db320}
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c7b )
    Followup: Pool_corruption
    ---------
    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: 0000000000000003, the pool freelist is corrupt.
    Arg2: fffffa80069dbb20, the pool entry being checked.
    Arg3: fffffa80069dbb20, the read back flink freelist value (should be the same as 2).
    Arg4: fffffa80069db320, the read back blink freelist value (should be the same as 2).
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x19_3
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from fffff80002da610b to fffff80002c73700
    STACK_TEXT:  
    fffff880`0acb6c68 fffff800`02da610b : 00000000`00000019 00000000`00000003 fffffa80`069dbb20 fffffa80`069dbb20 : nt!KeBugCheckEx
    fffff880`0acb6c70 fffff800`02da84c1 : fffffa80`042117e0 fffffa80`042117e0 00000000`00000000 fffffa80`042117f0 : nt!ExDeferredFreePool+0xc7b
    fffff880`0acb6d00 fffff800`02f20ec4 : 00000000`00000000 00000000`000000b5 fffff8a0`62507452 fffff8a0`000002bc : nt!ExFreePoolWithTag+0x411
    fffff880`0acb6db0 fffff800`02f1df84 : 00000000`00000000 00000000`00169990 fffff880`0acb76f0 fffffa80`05e88a9c : nt!PspAllocateProcess+0xf24
    fffff880`0acb7080 fffff800`02c72953 : 00000000`000003ee 00000000`0068c9d0 00000000`00000000 0000007f`ffffffff : nt!NtCreateUserProcess+0x4a3
    fffff880`0acb7bb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!ExDeferredFreePool+c7b
    fffff800`02da610b cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt!ExDeferredFreePool+c7b
    FOLLOWUP_NAME:  Pool_corruption
    IMAGE_NAME:  Pool_Corruption
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    MODULE_NAME: Pool_Corruption
    FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+c7b
    BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+c7b
    Followup: Pool_corruption
     
    
    Code:
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {100f660f0, 2, 1, fffff80002c7d3e3}
    Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2b3 )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000100f660f0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
     bit 0 : value 0 = read operation, 1 = write operation
     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002c7d3e3, address which referenced memory
    Debugging Details:
    ------------------
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eab0e0
     0000000100f660f0 
    CURRENT_IRQL:  0
    FAULTING_IP: 
    nt!KiTimerWaitTest+2b3
    fffff800`02c7d3e3 48894108        mov     qword ptr [rcx+8],rax
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    LAST_CONTROL_TRANSFER:  from fffff80002c8124a to fffff88003fa27f2
    STACK_TEXT:  
    fffff800`0413dc98 fffff800`02c8124a : 00000000`0032e358 fffffa80`05b7a5e8 fffff800`02dfbc40 00000000`00000001 : 0xfffff880`03fa27f2
    fffff800`0413dca0 fffff800`02c7bebc : fffff800`02dede80 fffff800`00000000 00000000`00000000 fffff800`02d93d00 : nt!PoIdle+0x53a
    fffff800`0413dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
    
    STACK_COMMAND:  .bugcheck ; kb
    FOLLOWUP_IP: 
    nt!KiTimerWaitTest+2b3
    fffff800`02c7d3e3 48894108        mov     qword ptr [rcx+8],rax
    SYMBOL_NAME:  nt!KiTimerWaitTest+2b3
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34
    FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+2b3
    BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+2b3
    Followup: MachineOwner
    ---------
     
    
    
    Also have u tried memtest86 ? , this will check your ram if ther are any errors
     
  4. TheRealOne

    TheRealOne New Member

    Joined:
    Jun 1, 2011
    Messages:
    6
    Likes Received:
    0
    Cheers kaos, just ran memtest86 through my system, turns out it was an issue with my memory, some new RAM and a clean install of windows has fixed it right up :)
     
  5. kaos

    kaos Senior Member

    Joined:
    May 9, 2011
    Messages:
    1,747
    Likes Received:
    33
    glad that helped :p
     

Share This Page

Loading...