Lots of BSOD, like MEMORY_MANAGEMENT and IRQL_NOT_LESS_OR_EQUAL


  1. Posts : 2
    Windows 7 64-bit
       #1

    Lots of BSOD, like MEMORY_MANAGEMENT and IRQL_NOT_LESS_OR_EQUAL


    Hi, i've been having some BSOD, and it's getting worse. I hope someone can help me with is.

    My OS is Windows Seven x64, not the original and OEM. The hardware is 3 years old and i re-installed the OS a month ago.

    (sorry my english)
      My Computer


  2. Posts : 6,668
    Windows 7 x64
       #2

    You are using a outdated copy of poweriso.
    You should remove it, the virtual drive function it uses is not properly compatible with windows 7
    I suggest magiciso as a replacement.

    In addition you are getting memory corruption errors, this could very well mean that you do have failing memory.

    The best check for that is to run memtest86 overnight and see if it finds any issue with your ram.
    RAM - Test with Memtest86+

    Code:
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+52b )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffa8d45db681b, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002ab15d5, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf9100
     fffffa8d45db681b 
    
    FAULTING_IP: 
    nt!MiAgeWorkingSet+52b
    fffff800`02ab15d5 410fb6461b      movzx   eax,byte ptr [r14+1Bh]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff880031db7c0 -- (.trap 0xfffff880031db7c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000004 rbx=0000000000000000 rcx=fffff68000005660
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002ab15d5 rsp=fffff880031db950 rbp=0000000000000000
     r8=0000000000000001  r9=fffffa8003afd8e8 r10=0000000000000005
    r11=0000000000000005 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac po cy
    nt!MiAgeWorkingSet+0x52b:
    fffff800`02ab15d5 410fb6461b      movzx   eax,byte ptr [r14+1Bh] ds:00000000`0000001b=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002a713bf to fffff80002ac6c40
    
    STACK_TEXT:  
    fffff880`031db658 fffff800`02a713bf : 00000000`00000050 fffffa8d`45db681b 00000000`00000000 fffff880`031db7c0 : nt!KeBugCheckEx
    fffff880`031db660 fffff800`02ac4d6e : 00000000`00000000 fffffa8d`45db681b 00000000`00001000 fa80046c`9e780460 : nt! ?? ::FNODOBFM::`string'+0x44791
    fffff880`031db7c0 fffff800`02ab15d5 : 00000000`00000002 00000000`00000001 fffff880`031dbb00 00000000`00000009 : nt!KiPageFault+0x16e
    fffff880`031db950 fffff800`02b42ac5 : fffffa80`03afd8e8 fffff880`00000001 00000000`00000001 fffff880`031dbbb0 : nt!MiAgeWorkingSet+0x52b
    fffff880`031dbb00 fffff800`02ab1826 : 00000000`0000140b 00000000`00000000 fffffa80`00000000 00000000`00000007 : nt! ?? ::FNODOBFM::`string'+0x4d786
    fffff880`031dbb80 fffff800`02ab1cd3 : 00000000`00000008 fffff880`031dbc10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
    fffff880`031dbbd0 fffff800`02d61fee : fffffa80`018ccb60 00000000`00000080 fffffa80`018ab040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
    fffff880`031dbd40 fffff800`02ab85e6 : fffff880`02f63180 fffffa80`018ccb60 fffff880`02f6dfc0 00000401`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`031dbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiAgeWorkingSet+52b
    fffff800`02ab15d5 410fb6461b      movzx   eax,byte ptr [r14+1Bh]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiAgeWorkingSet+52b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+52b
    
    BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+52b
    
    Followup: MachineOwner
    ---------
      My Computer


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

    Thank you, i will try to remove poweriso.

    I will keep you in touch.
      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 02:16.
Find Us