BSOD Plannetside 2 (steam) black screen> reboot> BSOD crash report


  1. Posts : 7
    win 7 64bit
       #1

    BSOD Plannetside 2 (steam) black screen> reboot> BSOD crash report


    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 116
    BCP1: FFFFFA8010C69010
    BCP2: FFFFF880069CD6AC
    BCP3: FFFFFFFFC000009A
    BCP4: 0000000000000004
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\040913-9204-01.dmp
    C:\Users\Phantom\AppData\Local\Temp\WER-21060-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    ==========================================================

    changed bios settings from RAID to IDE didnt seem to help this has occurred multiple times during playing planet side 2 the game runs fine then suddenly crashes im pretty sure i have the latest drivers and everything is up to date can someone clever help me please :)
    Last edited by alexthepie; 09 Apr 2013 at 13:24. Reason: attachement
      My Computer


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

    A stop 0x116 is a display/graphics related issue. Many a factors or components may cause such a BSOD.

    First of all, it is the display driver. From your BSOD dumps, I have noticed that it crashed the same irrespective of the driver version over time. So overlooking this part right now. Will concentrate it on later again, if needed.

    Next thing is overclocking, which sometimes lead display to crash. And, you are slightly overclocked.
    Code:
    CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3411
    As the system is crashing, you should stop overclocking. Set all the hardware elements like CPU, GPU and RAM to default; and reset the BIOS to default too.
    How To Clear CMOS (Reset BIOS)

    Heat is another factor. Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

    Also, dust accumulation causes heat, and dust accumulation depends on the age of the system. How old the system is? If possible, dismantle it and clean the inside carefully .... specially the air vents and fan grills, so that it can blow the hot air out easily.
    Dont forget to apply thermal paste to the CPU when re-seating the system.

    Insufficient power supply is also a great cause of display crash. Check if the CPU is supplying adequate power there or not.
    eXtreme Power Supply Calculator

    It GPU itself may not perform upto the mark. Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Let us know the results.
    _______________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800f27a010, fffff88006bc36ac, 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+9336ac )
    
    Followup: MachineOwner
    ---------
    
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800f27a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88006bc36ac, 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+9336ac
    fffff880`06bc36ac 4055            push    rbp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`02f8ea48 fffff880`0568e000 : 00000000`00000116 fffffa80`0f27a010 fffff880`06bc36ac ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`02f8ea50 fffff880`05661867 : fffff880`06bc36ac fffffa80`0b386000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02f8ea90 fffff880`0568de0f : fffffa80`ffffd84d 00000000`00000000 fffffa80`0f27a010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`02f8eb40 fffff880`0575cec1 : fffffa80`0b395d50 00000000`00000080 00000000`00000000 fffffa80`0b37a410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`02f8ebc0 fffff800`0337234a : 00000000`01a8ca70 fffffa80`0b3a1060 fffffa80`09d3eb30 fffffa80`0b3a1060 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`02f8ec00 fffff800`030c2946 : fffff800`0324de80 fffffa80`0b3a1060 fffff800`0325bcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`02f8ec40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+9336ac
    fffff880`06bc36ac 4055            push    rbp
    
    SYMBOL_NAME:  nvlddmkm+9336ac
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51427b3c
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    
    7: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`06290000 fffff880`06d3b000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Fri Mar 15 07:07:00 2013 (51427B3C)
        CheckSum:         00A8D47C
        ImageSize:        00AAB000
        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 01:41.
Find Us