Getting a lot of IRQL bluescreens, but not sure if it's the RAM.


  1. Posts : 3
    Win 7 Ult. x54
       #1

    Getting a lot of IRQL bluescreens, but not sure if it's the RAM.


    They seem to happen pretty randomly, often I'll just be browsing in chrome (once while typing this out)

    I've run a few instances of memtest86 which haven't found anything, and I've swapped three sets of different RAM (three different brands at different speeds) in both of my dual-slots, which sometimes seems to help, but inevitably I get more BSOD.

    I did a clean install of win 7, and had a lot of issues with the updater; I ended up using the standalone/offline installer which should have me more or less up to date.

    I reapplied thermal paste to my CPU, and my temps are hovering around 50 C. Voltages/speeds are the ASUS Mobo's autodetect settings.


    Thanks for the help.
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2

    Hi owenflass,

    Did any BSOD occur when you had nothing installed?

    Please remove PowerISO while troubleshooting.
      My Computer


  3. Posts : 3
    Win 7 Ult. x54
    Thread Starter
       #3

    Ironically, I just got this BSOD whilst uninstalling PowerISO:

    Code:
    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: fffffa801c64f370, 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: fffff80002d934b6, address which referenced memory
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    OVERLAPPED_MODULE: Address regions for 'dump_dumpfve' and 'crashdmp.sys' overlap
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0f100
    GetUlongFromAddress: unable to read from fffff80002f0f1c8
     fffffa801c64f370 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+86
    fffff800`02d934b6 480fb328        btr     qword ptr [rax],rbp
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  explorer.exe
    
    TRAP_FRAME:  fffff88007ab7c60 -- (.trap 0xfffff88007ab7c60)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa800c64f010 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002d934b6 rsp=fffff88007ab7df0 rbp=0000000080001b03
     r8=fffff88007ab7e20  r9=0000058000000000 r10=0000000fffffffff
    r11=000fffffffffffff r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiReleaseConfirmedPageFileSpace+0x86:
    fffff800`02d934b6 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`0c64f010=0000000000000001
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002cd29a9 to fffff80002cd3400
    
    STACK_TEXT:  
    fffff880`07ab7b18 fffff800`02cd29a9 : 00000000`0000000a fffffa80`1c64f370 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`07ab7b20 fffff800`02cd1620 : fffff8a0`01727140 fffff8a0`03c2e2f0 fffff8a0`01727010 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`07ab7c60 fffff800`02d934b6 : 00000000`00000000 00000000`00000000 fffffa80`0b45d100 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`07ab7df0 fffff800`02c9c234 : fffffa80`001380f0 fffff800`02cdca72 00000580`00000000 00000000`00000204 : nt!MiReleaseConfirmedPageFileSpace+0x86
    fffff880`07ab7e70 fffff800`02cc3b04 : 92500000`06805863 fffffa80`001380f0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1551b
    fffff880`07ab7ee0 fffff800`02cc2fd1 : fffff900`00000000 00000000`0000055f 00000000`00000000 00000000`00000000 : nt!MiDeleteSystemPagableVm+0x254
    fffff880`07ab8040 fffff800`02e075b1 : fffff900`c2581010 00000000`00000000 fffff880`07ab8290 00000000`00004000 : nt!MiFreePagedPoolPages+0x12d
    fffff880`07ab8190 fffff800`02e0a8b7 : 00000000`00000000 fffff880`07ab8360 fffff880`07ab82e0 00000000`00000001 : nt!MiFreePoolPages+0x2b1
    fffff880`07ab82a0 fffff960`00128338 : fffff900`c4000238 fffff960`0012832e 00000000`35316847 00000000`00000000 : nt!ExFreePoolWithTag+0x7c7
    fffff880`07ab8350 fffff900`c4000238 : fffff960`0012832e 00000000`35316847 00000000`00000000 00000000`00000000 : win32k+0xc8338
    fffff880`07ab8358 fffff960`0012832e : 00000000`35316847 00000000`00000000 00000000`00000000 fffff960`00128b0a : 0xfffff900`c4000238
    fffff880`07ab8360 00000000`35316847 : 00000000`00000000 00000000`00000000 fffff960`00128b0a fffff900`c00d6280 : win32k+0xc832e
    fffff880`07ab8368 00000000`00000000 : 00000000`00000000 fffff960`00128b0a fffff900`c00d6280 fffff900`c4000000 : 0x35316847
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    win32k+c8338
    fffff960`00128338 ??              ???
    
    SYMBOL_STACK_INDEX:  9
    
    SYMBOL_NAME:  win32k+c8338
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  581f53d9
    
    FAILURE_BUCKET_ID:  X64_0xA_win32k+c8338
    
    BUCKET_ID:  X64_0xA_win32k+c8338
    
    Followup: MachineOwner
    ---------
    And to answer your other question, I maybe remember (not sure) running into a BSoD or two while installing Windows updates (which was a huge struggle for some reason- wuauserv constantly froze or ate up 100% processor). But it only happens under machine load- so if i have nothing installed, or potentially even if i dont run any programs, it sits on the desktop indefinitely with no problem. I think.
    Last edited by Brink; 08 Jan 2017 at 11:47. Reason: code box
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #4

    I could almost say that that behaviour of Windows Update is normal, it is usually due to a buggy update or missing certain updates.

    I would recommend to remove all programs and install all Windows Updates, then see if another problem occurs.

    I'm currently suspecting the motherboard as a possible cause,
    - RAM is most likely not the issue since you've used a few kits.
    - HDD issues would've been visible, mentioning this one due to a few bugchecks you've had in the past
    - GPU is similar to the HDD, issues would've been visible.
    - Drivers unlikely if an up to date OS without any software has the same issue
    - Cabling would usually show similar issues as HDD issues
    - PSU? can't yet call this as a possible cause due to lack of information
    - CPU? can't yet call this as a possible cause, no signs that this one could currently be a possible cause.

    How old is the hardware?
      My Computer


  5. Posts : 3
    Win 7 Ult. x54
    Thread Starter
       #5

    I bought the mobo and processor together in October of 2013:

    Intel Core i5-3350P Ivy Bridge Quad-Core 3.1GHz (3.3GHz Turbo) LGA 1155 69W BX80637i53350P Desktop Processor - Newegg.com
    ASUS P8Z77-V LK LGA 1155 Intel Z77 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard with UEFI BIOS-Newegg.com

    The GPU is less than a year old, and the RAM falls somewhere between the two, I think. PSU may be as much as 4 or 5 years old now, I'm not sure.

    Is there a way I can view the draw of my system to see if it's approaching the capacity of my (650W Earthwatts PSU)?

    I've had two more BSOD trying to post this, the latest being:

    Code:
    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.23572.amd64fre.win7sp1_ldr.161011-0600
    Machine Name:
    Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e5f730
    Debug session time: Sun Jan  8 15:25:29.219 2017 (UTC - 5:00)
    System Uptime: 0 days 0:05:07.592
    *******************************************************************************
    *                                                                             *
    *                        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: fffffa801c571370, 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: fffff80002d4d4b6, address which referenced memory
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec9100
    GetUlongFromAddress: unable to read from fffff80002ec91c8
     fffffa801c571370 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+86
    fffff800`02d4d4b6 480fb328        btr     qword ptr [rax],rbp
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  chrome.exe
    
    TRAP_FRAME:  fffff88007e203c0 -- (.trap 0xfffff88007e203c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa800c571010 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002d4d4b6 rsp=fffff88007e20550 rbp=0000000080001b03
     r8=fffff88007e20580  r9=0000000000000000 r10=fffffa80065d14e8
    r11=fffff88007e205a0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiReleaseConfirmedPageFileSpace+0x86:
    fffff800`02d4d4b6 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`0c571010=0000000000000001
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002c8c9a9 to fffff80002c8d400
    
    STACK_TEXT:  
    fffff880`07e20278 fffff800`02c8c9a9 : 00000000`0000000a fffffa80`1c571370 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`07e20280 fffff800`02c8b620 : 00000000`00000000 00000000`00000002 000fffff`ffffffff 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`07e203c0 fffff800`02d4d4b6 : fffffa80`0025f200 00000000`00000000 fffffa80`0c55f060 fffffa80`001380f0 : nt!KiPageFault+0x260
    fffff880`07e20550 fffff800`02c50309 : 80001b03`00000080 fffffa80`001380f0 fffffa80`00174450 00000000`00000000 : nt!MiReleaseConfirmedPageFileSpace+0x86
    fffff880`07e205d0 fffff800`0304d015 : fffffa80`09d016e0 00000000`00000000 fffffa80`09d016e0 00000000`00001001 : nt!MiDeleteSegmentPages+0x37f
    fffff880`07e20680 fffff800`02cc0b9c : fffffa80`09d01700 00000000`00000000 fffffa80`09d016e0 fffff800`02e20588 : nt!MiSegmentDelete+0xd5
    fffff880`07e206c0 fffff800`02c5ee8d : ffffffff`ffffffff fffffa80`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0x26c
    fffff880`07e207e0 fffff800`02f658e4 : fffff8a0`02df5460 fffff880`07e20ae0 fffffa80`09d15060 fffffa80`09d15060 : nt!MmCleanProcessAddressSpace+0x231
    fffff880`07e20830 fffff800`02f4a41d : fffffa80`00000000 00000000`00000001 000007ff`fffd3000 00000000`00000000 : nt!PspExitThread+0x944
    fffff880`07e208f0 fffff800`02c80574 : 00000000`00000000 00000000`00000001 fffffa80`09d15060 fffff800`02c8304d : nt!PsExitSpecialApc+0x1d
    fffff880`07e20920 fffff800`02c808c0 : 00000000`ffffffff fffff880`07e209a0 fffff800`02f4a390 00000000`00000001 : nt!KiDeliverApc+0x2e4
    fffff880`07e209a0 fffff800`02c8c737 : fffffa80`09d15060 00000000`ffffffff 00000000`00000000 fffffa80`06b57fe0 : nt!KiInitiateUserApc+0x70
    fffff880`07e20ae0 00000000`77c3bd7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    00000000`0377f788 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c3bd7a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiReleaseConfirmedPageFileSpace+86
    fffff800`02d4d4b6 480fb328        btr     qword ptr [rax],rbp
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+86
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  57fcfdf3
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
    
    BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
    
    Followup: MachineOwner
    ---------
    Last edited by owenflass; 08 Jan 2017 at 15:53. Reason: Forgot Info
      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 23:30.
Find Us