locked
blue screen occurs very often during playing game(2k16). RRS feed

  • Question

  • Hi guys,

    Recently the blue screen problem occurs frequently when i playing the game 2k16.Page fAULT IN NON PAGED AREA is the detail show up at that time. I try to use the Windbg to open the minidump file.  I also use sfc/scannow and the repair system fix all broken file in system disk (at least it said so).Here is the information I got from the Windgb. 

    I really appreciate it if you guys can help me to find the problem cause the blue screen, it really annoyed.



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\011716-14390-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
    Machine Name:
    Kernel base = 0xfffff801`e9087000 PsLoadedModuleList = 0xfffff801`e934b990
    Debug session time: Sun Jan 17 13:24:36.378 2016 (UTC - 6:00)
    System Uptime: 0 days 0:01:05.117
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {ffffd000242961b0, 0, fffff801e91c74e8, 1}


    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt!output_l+338 )

    Followup: MachineOwner
    ---------

    7: 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: ffffd000242961b0, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff801e91c74e8, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000001, (reserved)

    Debugging Details:
    ------------------


    Could not read faulting driver name

    OVERLAPPED_MODULE: Address regions for 'vwifimp' and 'luafv.sys' overlap

    READ_ADDRESS: fffff801e9339340: Unable to get special pool info
    fffff801e9339340: Unable to get special pool info
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     ffffd000242961b0 

    FAULTING_IP: 
    nt!output_l+338
    fffff801`e91c74e8 443800          cmp     byte ptr [rax],r8b

    MM_INTERNAL_CODE:  1

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff801e91ea0fd to fffff801e91d4ca0

    STACK_TEXT:  
    ffffd000`24cbc1a8 fffff801`e91ea0fd : 00000000`00000050 ffffd000`242961b0 00000000`00000000 ffffd000`24cbc390 : nt!KeBugCheckEx
    ffffd000`24cbc1b0 fffff801`e90e80fd : 00000000`00000000 ffffe000`02531880 ffffd000`24cbc390 fffff800`02796010 : nt! ?? ::FNODOBFM::`string'+0x4f6d
    ffffd000`24cbc250 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x7ed


    STACK_COMMAND:  .bugcheck ; kb

    FOLLOWUP_IP: 
    nt!output_l+338
    fffff801`e91c74e8 443800          cmp     byte ptr [rax],r8b

    SYMBOL_NAME:  nt!output_l+338

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  52341cf4

    FAILURE_BUCKET_ID:  X64_0x50_nt!output_l+338

    BUCKET_ID:  X64_0x50_nt!output_l+338

    Followup: MachineOwner
    ---------

    Sunday, January 17, 2016 9:09 PM