BSOD crash PAGE_FAULT_IN_NONPAGED_AREA


  1. Posts : 2
    win7 x64
       #1

    BSOD crash PAGE_FAULT_IN_NONPAGED_AREA


    Hello, few days ago i had BSOD crash when i was playing online poker. I did not launch any specific apps, only apps and programs that i usually use.
    Can you help me?
    Also i checked the error number, it's 0x00000050
    - win7 x64
    - not original installed OS
    - Age of system (hardware) is 2 years
    - Age of OS installation 2 years
    - Did not re-install the OS
    Attaching necesary files

    I had BSOD crash only one time but i want to prevent new crashes.
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #2

    Code:
    1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\andreynofx\Windows_NT6_BSOD_jcgriff2\112911-21153-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03017000 PsLoadedModuleList = 0xfffff800`0325c670 Debug session time: Tue Nov 29 10:13:34.156 2011 (UTC - 7:00) System Uptime: 0 days 0:50:01.092 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa80bfbf2010, fffff8800fa3ff10, ffffffffc000009a, 4} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+801f10 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa80bfbf2010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800fa3ff10, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000004, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+801f10 fffff880`0fa3ff10 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`05c8db88 fffff880`0ff4e000 : 00000000`00000116 fffffa80`bfbf2010 fffff880`0fa3ff10 ffffffff`c000009a : nt!KeBugCheckEx fffff880`05c8db90 fffff880`0ff21867 : fffff880`0fa3ff10 fffffa80`05cfa000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`05c8dbd0 fffff880`0ff4de0f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`bfbf2010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3 fffff880`05c8dc80 fffff880`047dbec1 : fffffa80`05ecbc00 00000000`00000080 00000000`00000000 fffffa80`05cf3010 : dxgkrnl!TdrResetFromTimeout+0x23 fffff880`05c8dd00 fffff800`0332efee : 00000000`03597449 fffffa80`05cf0060 fffffa80`036d09e0 fffffa80`05cf0060 : dxgmms1!VidSchiWorkerThread+0x101 fffff880`05c8dd40 fffff800`030855e6 : fffff800`03209e80 fffffa80`05cf0060 fffff800`03217cc0 fffff880`01431384 : nt!PspSystemThreadStartup+0x5a fffff880`05c8dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+801f10 fffff880`0fa3ff10 4883ec28 sub rsp,28h SYMBOL_NAME: nvlddmkm+801f10 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68 FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
    2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\andreynofx\Windows_NT6_BSOD_jcgriff2\122711-23665-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`03249670 Debug session time: Tue Dec 27 06:46:26.664 2011 (UTC - 7:00) System Uptime: 0 days 5:50:40.600 Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff6810011d670, 0, fffff8000306b27b, 5} Could not read faulting driver name Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 ) Followup: MachineOwner --------- 4: 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: fffff6810011d670, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff8000306b27b, 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 fffff800032b3100 fffff6810011d670 FAULTING_IP: nt!MiAgeWorkingSet+1d1 fffff800`0306b27b 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: postgres.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880035e77c0 -- (.trap 0xfffff880035e77c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff6810011d670 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000306b27b rsp=fffff880035e7950 rbp=000000010011d670 r8=0000000000000001 r9=fffffa8006cf3ec8 r10=0000000000000005 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe cy nt!MiAgeWorkingSet+0x1d1: fffff800`0306b27b 488b19 mov rbx,qword ptr [rcx] ds:0488:fffff681`0011d670=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000302b3bf to fffff80003080c40 STACK_TEXT: fffff880`035e7658 fffff800`0302b3bf : 00000000`00000050 fffff681`0011d670 00000000`00000000 fffff880`035e77c0 : nt!KeBugCheckEx fffff880`035e7660 fffff800`0307ed6e : 00000000`00000000 fffff681`0011d670 00000000`00001000 00000980`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791 fffff880`035e77c0 fffff800`0306b27b : 00000003`00000000 c4700000`be1bb867 00000000`00000000 00000000`00007c47 : nt!KiPageFault+0x16e fffff880`035e7950 fffff800`030fcac5 : fffffa80`06cf3ec8 fffff880`00000001 00000000`00000001 fffff880`035e7bb0 : nt!MiAgeWorkingSet+0x1d1 fffff880`035e7b00 fffff800`0306b826 : 00000000`00005231 00000000`00000000 fffffa80`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x4d786 fffff880`035e7b80 fffff800`0306bcd3 : 00000000`00000008 fffff880`035e7c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e fffff880`035e7bd0 fffff800`0331bfee : fffffa80`036fc040 00000000`00000080 fffffa80`036d09e0 00000000`00000001 : nt!KeBalanceSetManager+0x1c3 fffff880`035e7d40 fffff800`030725e6 : fffff880`009b1180 fffffa80`036fc040 fffff880`009bc0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`035e7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiAgeWorkingSet+1d1 fffff800`0306b27b 488b19 mov rbx,qword ptr [rcx] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiAgeWorkingSet+1d1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1d1 BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1d1 Followup: MachineOwner ---------
    Your two blue screens were unrelated and spanned by nearly a month, so I wouldn't worry about the first one.

    My guess is the second was caused by sptd.sys, which is a part of Alcohol 120. sptd.sys is known to cause BSODs. Use the sptd.sys uninstaller

    I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

    Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
      My Computer


  3. Posts : 2
    win7 x64
    Thread Starter
       #3

    Thx! I will uninstall alcohol 120 and use TotalMounter. If i have any troubles in future i will post here.
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #4

    andreynofx said:
    Thx! I will uninstall alcohol 120 and use TotalMounter. If i have any troubles in future i will post here.
    No problem. Good luck!
      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 16:23.
Find Us