BSOD help - probably graphics card issue


  1. Posts : 11
    Windows 7 Home Premium 64bit
       #1

    BSOD help - probably graphics card issue


    Hello,

    Lately my ACER laptop has been resetting itself randomly. This has happened during playing a game, surfing the net, watching a video etc. Laptop shuts down, opens up again but nothing comes up on the monitor. Several seconds later the same thing happens. I'm not pressing any buttons at this point but the laptop goes into the cycle of starting and shutting down until monitor shows up again...or, I'm guessing, when the graphics card successfully kicks in.

    The reason I'm posting this here in the BSOD forums is that when windows starts the following error message comes up (in Turkish but I assume it won't be a problem for you guys to get the gist):

    Sorun imzası:
    Sorunlu Olay Adı: BlueScreen
    OS Sürümü: 6.1.7601.2.1.0.768.3
    Yerel Kimlik: 1055

    Sorun hakkında ek bilgiler:
    BCCode: 116
    BCP1: FFFFFA8009C87330
    BCP2: FFFFF880089C1F38
    BCP3: FFFFFFFFC000009A
    BCP4: 0000000000000004
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Sorunu açıklamaya yardımcı olan dosyalar:
    C:\Windows\Minidump\031415-26005-01.dmp
    C:\Users\acer\AppData\Local\Temp\WER-111259-0.sysdata.xml

    Çevrimiçi gizlilik bildirimimizi okuyun:
    Windows 7 Gizlilik Bildirimi - Microsoft Windows

    Çevrimiçi gizlilik bildirimi yoksa, lütfen çevrimdışı gizlilik bildirimimizi okuyun:
    C:\Windows\system32\tr-TR\erofflps.txt
    So I'm fairly sure this has something to do with the graphics card/driver, but not completely sure. I haven't tried anything yet, wanted to post it in here first. Hoping it's not purely hardware related. I've attached the BSOD file.

    Regards.
      My Computer


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

    Roland9 said:
    I'm fairly sure this has something to do with the graphics card/driver, but not completely sure.
    You are right.

    A stop ox116 is a display related issue. And you have the latest version of the display driver installed. So not altering it at the first time, but will do that too, if situation demands.

    Make it sure that the hardware components are not overclocked.

    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. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Stress test the Graphics Card using Furmark.Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

    Let us know the results.
    _______________________________________
    Code:
    BugCheck 116, {fffffa8009c87330, fffff880089c1f38, ffffffffc000009a, 4}
    
    *** 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+7a3f38 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8009c87330, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880089c1f38, 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+7a3f38
    fffff880`089c1f38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`0889b230)]
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    STACK_TEXT:  
    fffff880`067f0b88 fffff880`08c8d134 : 00000000`00000116 fffffa80`09c87330 fffff880`089c1f38 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`067f0b90 fffff880`08c60867 : fffff880`089c1f38 fffffa80`08dcf000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`067f0bd0 fffff880`08c8cf43 : fffffa80`ffffd846 00000000`00000000 fffffa80`09c87330 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`067f0c80 fffff880`08d5d03d : fffffa80`096a46a0 00000000`00000080 00000000`00000000 fffffa80`0417c010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`067f0d00 fffff800`03567b8a : 00000000`02f9a8ae fffffa80`08de9060 fffffa80`0416b040 fffffa80`08de9060 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`067f0d40 fffff800`032ba8e6 : fffff880`031d3180 fffffa80`08de9060 fffff880`031ddfc0 fffff880`033ca701 : nt!PspSystemThreadStartup+0x5a
    fffff880`067f0d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+7a3f38
    fffff880`089c1f38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`0889b230)]
    
    SYMBOL_NAME:  nvlddmkm+7a3f38
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  54d3b001
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}
    
    Followup: MachineOwner
    ---------
    
    3: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0821e000 fffff880`08c30000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Thu Feb 05 23:31:37 2015 (54D3B001)
        CheckSum:         009D4DDE
        ImageSize:        00A12000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 11
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    Hi, thanks for your response.

    Here's the speccy screenshot:

    http://speccy.piriform.com/results/x...6brfaVSS8HCXA7

    Stress test is attached. Ran it for 17 minutes, frankly I had no idea when it was going to finish (or whether there was a finish) so I took a screenshot and stopped it myself. I didn't experience any crashes. I assume this is probably not temp related then?

    I forgot to mention in my first post: I've updated the NVDIA driver to the latest version after I first encountered the issue, hoping it would be an answer.
      My Computer


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

    Roland9 said:

    I forgot to mention in my first post: I've updated the NVDIA driver to the latest version after I first encountered the issue, hoping it would be an answer.
    All those reports are fine.

    Have you experienced any more BSOD after updating the nvidia driver?
      My Computer


  5. Posts : 11
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    ^ Yes, it didn't help. I still get random crashes.
      My Computer


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

    Well, then try 347.25 WHQL, but do it as suggested only.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update
      • GeForce Experience
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

    • That means, Install the display driver and PhysX only, and nothing else.

    See how it goes. Let us know for any further BSOD.
      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:01.
Find Us