PAGE_FAULT_IN_NONPAGED_AREA 0x00000050


  1. Posts : 149
    Windows 7 Professional (64x)
       #1

    PAGE_FAULT_IN_NONPAGED_AREA 0x00000050


    I get these BSOD's when playing ARMA2 as well as Witcher 3. Very infrequent and I cant make any sence of them, I've tried following both, https://support.microsoft.com/en-us/kb/329293 as well as tried to stress test my RAM's. RAM stresstest turned out nothing and the "solution from MS didnt help either.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Uninstall the installed display driver using Display Driver Uninstaller. Then install an earlier version, say 347.25 WHQL or 350.12 WHQL.

    And free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept then restart.

    Report us for any further BSOD.

    ______________________________________________________
    Code:
    BugCheck 50, {fffffb240f7e1300, 0, fffff8800499a940, 7}
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    
    Could not read faulting driver name
    Probably caused by : nvlddmkm.sys ( nvlddmkm+ee940 )
    
    Followup: MachineOwner
    ---------
    
    8: 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: fffffb240f7e1300, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff8800499a940, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000007, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003918100
    GetUlongFromAddress: unable to read from fffff800039181c0
     fffffb240f7e1300 Nonpaged pool
    
    FAULTING_IP: 
    nvlddmkm+ee940
    fffff880`0499a940 428b8401a4230000 mov     eax,dword ptr [rcx+r8+23A4h]
    
    MM_INTERNAL_CODE:  7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    TRAP_FRAME:  fffff880095f35f0 -- (.trap 0xfffff880095f35f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000ffffffff rbx=0000000000000000 rcx=000000a3ffffff5c
    rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800499a940 rsp=fffff880095f3780 rbp=fffff880095f37f0
     r8=fffffa800f7df000  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nvlddmkm+0xee940:
    fffff880`0499a940 428b8401a4230000 mov     eax,dword ptr [rcx+r8+23A4h] ds:fffffb24`0f7e1300=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003755732 to fffff800036db8c0
    
    STACK_TEXT:  
    fffff880`095f3488 fffff800`03755732 : 00000000`00000050 fffffb24`0f7e1300 00000000`00000000 fffff880`095f35f0 : nt!KeBugCheckEx
    fffff880`095f3490 fffff800`036d99ee : 00000000`00000000 fffffb24`0f7e1300 00000000`00051600 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3fd21
    fffff880`095f35f0 fffff880`0499a940 : 00000000`000143c0 fffffa80`0f7ce000 fffffa80`104f6000 00000000`00000001 : nt!KiPageFault+0x16e
    fffff880`095f3780 00000000`000143c0 : fffffa80`0f7ce000 fffffa80`104f6000 00000000`00000001 00000000`000143c0 : nvlddmkm+0xee940
    fffff880`095f3788 fffffa80`0f7ce000 : fffffa80`104f6000 00000000`00000001 00000000`000143c0 fffffa80`0f7ce000 : 0x143c0
    fffff880`095f3790 fffffa80`104f6000 : 00000000`00000001 00000000`000143c0 fffffa80`0f7ce000 00000000`00000001 : 0xfffffa80`0f7ce000
    fffff880`095f3798 00000000`00000001 : 00000000`000143c0 fffffa80`0f7ce000 00000000`00000001 fffff880`0499adbc : 0xfffffa80`104f6000
    fffff880`095f37a0 00000000`000143c0 : fffffa80`0f7ce000 00000000`00000001 fffff880`0499adbc 00000000`00000000 : 0x1
    fffff880`095f37a8 fffffa80`0f7ce000 : 00000000`00000001 fffff880`0499adbc 00000000`00000000 fffff8a0`1ba2792c : 0x143c0
    fffff880`095f37b0 00000000`00000001 : fffff880`0499adbc 00000000`00000000 fffff8a0`1ba2792c 00000000`00000000 : 0xfffffa80`0f7ce000
    fffff880`095f37b8 fffff880`0499adbc : 00000000`00000000 fffff8a0`1ba2792c 00000000`00000000 00000000`000dd1d0 : 0x1
    fffff880`095f37c0 00000000`00000000 : fffff8a0`1ba2792c 00000000`00000000 00000000`000dd1d0 fffffa80`00000001 : nvlddmkm+0xeedbc
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+ee940
    fffff880`0499a940 428b8401a4230000 mov     eax,dword ptr [rcx+r8+23A4h]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nvlddmkm+ee940
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5566824f
    
    FAILURE_BUCKET_ID:  X64_0x50_nvlddmkm+ee940
    
    BUCKET_ID:  X64_0x50_nvlddmkm+ee940
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x50_nvlddmkm+ee940
    
    FAILURE_ID_HASH:  {168bd647-490e-e9b3-4c7b-a3e40b783371}
    
    Followup: MachineOwner
    ---------
    
    8: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`048ac000 fffff880`0536f000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Thu May 28 08:19:51 2015 (5566824F)
        CheckSum:         00A7E4BD
        ImageSize:        00AC3000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      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 05:45.
Find Us