BSoD, 0x00000116 / 0x00000117

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 24,479
    Windows 7 Ultimate X64 SP1
       #21

    Hmm, no Primary Graphics Adapter setting?
      My Computer


  2. Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       #22

    Britton30 said:
    Hmm, no Primary Graphics Adapter setting?
    The setting you linked me to is regarding the North Bridge configuration. When I press the NBC button, nothing happens.
      My Computer


  3. Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       #23

    All right, apparently I don't need to click anywhere on the item, it's better off to press enter... I am on on board now. Should I try to initiate a crash / something that would normally crash me?
      My Computer


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

    Now we have to observe how it is working with onboard graphics. If it is kinda stable (may be we may need to update the intel graphics driver at a max), we may conclude that it is a GPU failing.
      My Computer


  5. Posts : 24,479
    Windows 7 Ultimate X64 SP1
       #25

    Good job, you'll need to put your monitor cable on the VGA connector on the motherboard.
      My Computer


  6. Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       #26

    Britton30 said:
    Good job, you'll need to put your monitor cable on the VGA connector on the motherboard.
    Already did that. I have been on the onboard since the post. Also updated the Intel drivers which I never had.
    The on-board succeeded in not crashing on a game the external crashed...
    Last edited by LeetZero; 30 May 2013 at 18:01.
      My Computer


  7. Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       #27

    So, I guess it's a GPU failure?
      My Computer


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

    LeetZero said:
    So, I guess it's a GPU failure?
    Yes, it indicates that.

    If the GPU is under warranty, RMA it, otherwise replace it with a new one.
      My Computer


  9. Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       #29

    Actually, despite that game working now I received those things, while on the Intel integrated :s.
    The thing is that it still says it's an NVIDIA... but yet I don't have it plug in.
      My Computer


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

    Remove nvidia drivers from the system.

    • 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

      (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 ,uninstall all the leftovers of nvidia.

    Now let the computer run. Observe if it is crashing any more or not.
    ____________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8007147010, fffff88006150ed0, ffffffffc000009a, 4}
    
    Unable to load image 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+8e9ed0 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8007147010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88006150ed0, 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+8e9ed0
    fffff880`06150ed0 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`1af33a48 fffff880`0652b000 : 00000000`00000116 fffffa80`07147010 fffff880`06150ed0 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`1af33a50 fffff880`064fe867 : fffff880`06150ed0 fffffa80`0914e000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`1af33a90 fffff880`0652ae0f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`07147010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`1af33b40 fffff880`06437ec1 : fffffa80`073c9440 00000000`00000080 00000000`00000000 fffffa80`09149010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`1af33bc0 fffff800`02520e6a : 00000000`029ba1d6 fffffa80`0916b060 fffffa80`06ce8040 fffffa80`0916b060 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`1af33c00 fffff800`0227aec6 : fffff880`01e5e180 fffffa80`0916b060 fffff880`01e68fc0 00000000`00000018 : nt!PspSystemThreadStartup+0x5a
    fffff880`1af33c40 00000000`00000000 : fffff880`1af34000 fffff880`1af2e000 fffff880`1af32ba0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+8e9ed0
    fffff880`06150ed0 4055            push    rbp
    
    SYMBOL_NAME:  nvlddmkm+8e9ed0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  518fe8f9
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`05867000 fffff880`06348000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Mon May 13 00:39:45 2013 (518FE8F9)
        CheckSum:         00AB6DED
        ImageSize:        00AE1000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 
Page 3 of 4 FirstFirst 1234 LastLast

  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 02:56.
Find Us