BSOD Usually code 1a


  1. Posts : 2
    Windows 7 Ultimate x64
       #1

    BSOD Usually code 1a


    Blue screens about every 20 minutes or so, about 50 crash dumps attached. thanks for any help you can provide.

    Windows 7 Ultimate
    AMD athlon II 645 processor
    ASRock K10N78D Mobo
    Nvidia 720D chipset
    Geforce GTX 260
    8 gigs ram
    430W PS
    2TB Raid 0
    VIA high definition audio
      My Computer


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

    Most the dumps actually point to memory corruption. Enough so that I'm going to go ahead and say you have bad timings/overclock or a bad ram stick.
    Running memtest86 overnight is usually the best test for this, and it takes windows and other processes out of the mix.

    There's a detailed tutorial with screens and instructions for it's use here.
    RAM - Test with Memtest86+

    Code:
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+425 )
    
    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: fffffa80cdf8901b, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002a7b4cf, 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 fffff80002cc3100
     fffffa80cdf8901b 
    
    FAULTING_IP: 
    nt!MiAgeWorkingSet+425
    fffff800`02a7b4cf 410fb65e1b      movzx   ebx,byte ptr [r14+1Bh]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff880037167c0 -- (.trap 0xfffff880037167c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000058000000000 rbx=0000000000000000 rcx=fffff6fcc0197230
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a7b4cf rsp=fffff88003716950 rbp=007ffffcc0197233
     r8=0000000000000001  r9=fffff80002cc6ac0 r10=0000000000000005
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiAgeWorkingSet+0x425:
    fffff800`02a7b4cf 410fb65e1b      movzx   ebx,byte ptr [r14+1Bh] ds:77d8:00000000`0000001b=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002a3b3bf to fffff80002a90c40
    
    STACK_TEXT:  
    fffff880`03716658 fffff800`02a3b3bf : 00000000`00000050 fffffa80`cdf8901b 00000000`00000000 fffff880`037167c0 : nt!KeBugCheckEx
    fffff880`03716660 fffff800`02a8ed6e : 00000000`00000000 fffffa80`cdf8901b 00000000`00001000 f8a00044`a8300400 : nt! ?? ::FNODOBFM::`string'+0x44791
    fffff880`037167c0 fffff800`02a7b4cf : 00000000`04d3b000 04100000`23ec3921 00000000`00000000 00000000`00012041 : nt!KiPageFault+0x16e
    fffff880`03716950 fffff800`02b0cac5 : fffff800`02cc6ac0 fffff880`00000001 00000000`00000001 fffff880`03716bb0 : nt!MiAgeWorkingSet+0x425
    fffff880`03716b00 fffff800`02a7b826 : 00000000`00000706 00000000`00000000 fffffa80`00000000 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x4d786
    fffff880`03716b80 fffff800`02a7bcd3 : 00000000`00000008 fffff880`03716c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
    fffff880`03716bd0 fffff800`02d2bfee : fffffa80`06a47200 00000000`00000080 fffffa80`069a5b30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
    fffff880`03716d40 fffff800`02a825e6 : fffff880`03364180 fffffa80`06a47200 fffff880`0336efc0 fef5bdff`bfffdbe7 : nt!PspSystemThreadStartup+0x5a
    fffff880`03716d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiAgeWorkingSet+425
    fffff800`02a7b4cf 410fb65e1b      movzx   ebx,byte ptr [r14+1Bh]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiAgeWorkingSet+425
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+425
    
    BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+425
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 2
    Windows 7 Ultimate x64
    Thread Starter
       #3

    I have pulled RAM sticks out 1 by 1 as I get new BSOD. Have been running fine now for over an hour without a crash. Will leave it running overnight and will mark this solved tomorow. thank you Maguscreed for your time and assistance!
      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 00:47.
Find Us