Blue Screen of Death (BSOD) BSOD error 0x0000016


  1. Posts : 1
    Windows 7 profeshonal
       #1

    Blue Screen of Death (BSOD) BSOD error 0x0000016


    hii
    i have a problem
    my laptop (lenovo z710 ) goes blue memoty dump and an error
    BSOD error 0x0000016





    please help me
      My Computer


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

    Hi hemzki.

    A stop 0x116 is a display/graphics related issue. For a laptop a stop 0x116 is either a GPU failure or a display driver failure.

    Your computer is a laptop with a 700 series nvidia GPU. It seems to be a new one.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    If it problems during furmark, RMA the laptop.

    But if it is not, then it is a driver issue.

    And unfortunately I dont know any driver version that works good with GTX 700 series. You may try the drivers on a trial and error basis:

    • 320.49 WHQL
    • 327.23 WHQL
    • 331.58 WHWL
    • 331.65 WHQL
    • 331.82 WHQL
    • 332.21 WHQL
    • Any other driver version after that.

    Get them from Drivers - Download NVIDIA Drivers

    Do a clean install on all of them. Uninstall the previously installed driver first.
    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

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Download the target WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    Lengthy process, but the only stable version of nvidia is 314.22 lately, which does not support 700 series GPU.

    Hope one of the drivers will work good for you.
    ______________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8007ac84e0, fffff8800513c15c, 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+8f415c )
    
    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: fffffa8007ac84e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800513c15c, 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+8f415c
    fffff880`0513c15c 803d560af0ff00  cmp     byte ptr [nvlddmkm+0x7f4bb9 (fffff880`0503cbb9)],0
    
    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.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`02921a48 fffff880`0566b140 : 00000000`00000116 fffffa80`07ac84e0 fffff880`0513c15c ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`02921a50 fffff880`0563e867 : fffff880`0513c15c fffffa80`0b442000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02921a90 fffff880`0566af4f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`07ac84e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`02921b40 fffff880`0573a03d : fffffa80`0d7d6510 00000000`00000080 00000000`00000000 fffffa80`0b448010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`02921bc0 fffff800`031132ea : 00000000`03722072 fffffa80`0b45ba00 fffffa80`072f3040 fffffa80`0b45ba00 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`02921c00 fffff800`02e678e6 : fffff800`02ff1e80 fffffa80`0b45ba00 fffff800`02fffcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`02921c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+8f415c
    fffff880`0513c15c 803d560af0ff00  cmp     byte ptr [nvlddmkm+0x7f4bb9 (fffff880`0503cbb9)],0
    
    SYMBOL_NAME:  nvlddmkm+8f415c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  526ed93b
    
    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
    ---------
    
    7: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`04848000 fffff880`05347000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Tue Oct 29 03:08:03 2013 (526ED93B)
        CheckSum:         00AD0AFE
        ImageSize:        00AFF000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 17,322
    Win 10 Pro x64
       #3

    mechhead said:
    Arc,
    All that aside, the issue is a 016 error, not a 116 error.
    Actually, it is a 116 error, that is an obvious typo from the OP of the thread linked.

    BSOD error 0x0000016 - nvlddmkm.sys

    And the dump file clearly shows a BCC 116,

    Code:
    BugCheck 116, {fffffa8007ac84e0, fffff8800513c15c, 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+8f415c )
    
    Followup: MachineOwner
      My Computer


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


    mechhead said:
    Arc,
    All that aside, the issue is a 016 error, not a 116 error.
    Strange!
      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 17:53.
Find Us