BSOD Page Fault


  1. Posts : 20
    Windows 7 64bit
       #1

    BSOD Page Fault


    When starting some programs I get this Page fault In Nonpaged Area
    Then BSOD Reboot And Things Seem Fine
    Please see Dump File

    Thanks billy
    Attachment 59780
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    billyh said:
    When starting some programs I get this Page fault In Nonpaged Area
    Then BSOD Reboot And Things Seem Fine
    Please see Dump File

    Thanks billy
    Attachment 59780

    Hi Billy and welcome


    Straight foward... Memory corruption

    I would download memtestx86 and run it for 5 passes to check your memory for errors and possible heat issues.

    Let us know the results

    Ken

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\030910-19141-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02e68000 PsLoadedModuleList = 0xfffff800`030a5e50
    Debug session time: Tue Mar  9 23:00:09.712 2010 (GMT-5)
    System Uptime: 0 days 4:55:36.414
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    .......................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff682003b2f08, 0, fffff80002eedae2, 5}
    
    
    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )
    
    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: fffff682003b2f08, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002eedae2, 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 fffff800031100e0
     fffff682003b2f08 
    
    FAULTING_IP: 
    nt!MiAgeWorkingSet+1c2
    fffff800`02eedae2 488b19          mov     rbx,qword ptr [rcx]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  NeroStartSmart
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff880033167a0 -- (.trap 0xfffff880033167a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff682003b2f08
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002eedae2 rsp=fffff88003316930 rbp=00000002003b2f08
     r8=0000000000000001  r9=fffffa800daccec8 r10=0000000000000005
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe cy
    nt!MiAgeWorkingSet+0x1c2:
    fffff800`02eedae2 488b19          mov     rbx,qword ptr [rcx] ds:fffff682`003b2f08=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002f57b91 to fffff80002ed9f00
    
    STACK_TEXT:  
    fffff880`03316638 fffff800`02f57b91 : 00000000`00000050 fffff682`003b2f08 00000000`00000000 fffff880`033167a0 : nt!KeBugCheckEx
    fffff880`03316640 fffff800`02ed7fee : 00000000`00000000 00000980`00000000 00000000`00001000 fffff800`0300cbfe : nt! ?? ::FNODOBFM::`string'+0x40f5b
    fffff880`033167a0 fffff800`02eedae2 : 00000003`00000000 28500002`0e5aa025 00000000`00000000 00000000`00000285 : nt!KiPageFault+0x16e
    fffff880`03316930 fffff800`02f5aa0e : fffffa80`0daccec8 fffff880`00000001 00000000`00000001 fffff880`03316bb0 : nt!MiAgeWorkingSet+0x1c2
    fffff880`03316ae0 fffff800`02eee6e2 : 00000000`0000454a 00000000`00000000 fffffa80`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x49926
    fffff880`03316b80 fffff800`02eee96f : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
    fffff880`03316bd0 fffff800`0317d166 : fffffa80`06a29680 00000000`00000080 fffffa80`06a05040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
    fffff880`03316d40 fffff800`02eb8486 : fffff880`02f64180 fffffa80`06a29680 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03316d80 00000000`00000000 : fffff880`03317000 fffff880`03311000 fffff880`03316620 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiAgeWorkingSet+1c2
    fffff800`02eedae2 488b19          mov     rbx,qword ptr [rcx]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiAgeWorkingSet+1c2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1c2
    
    BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1c2
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 20
    Windows 7 64bit
    Thread Starter
       #3

    Memtest86+


    Hi zigzag3143 And Thank you

    Ran prime95 torture test all was stable.
    Ran memtest86+ one error at test #7 same place every time on every pass?
    Billy
      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 14:08.
Find Us