BSOD BCCode 116 while idle

Hi KingKaster.

A stop 0x116 is usuallu a graphics/display related error.

We have seen lately that the latest version of the display driver is somehow unstable. Install the 314.22 WHQL 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
  
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).

• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

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

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.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Try to update the BIOS to Version FI dated 2010/08/12..... the latest one available at http://www.gigabyte.in/products/prod...?pid=3134#bios .

Let us know the results.
______________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005a654e0, fffff8800493fe30, ffffffffc00000b5, a}

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+13be30 )

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: fffffa8005a654e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800493fe30, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+13be30
fffff880`0493fe30 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`05a98a68 fffff880`0534b054 : 00000000`00000116 fffffa80`05a654e0 fffff880`0493fe30 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`05a98a70 fffff880`0534ae2f : fffff880`0493fe30 fffffa80`05a654e0 00000000`00000000 fffffa80`05781410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05a98ab0 fffff880`03f76f13 : fffffa80`05a654e0 00000000`c00000b5 00000000`00000000 fffffa80`05781410 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`05a98ae0 fffff880`03fa0d50 : fffffa80`00000000 00000000`00a2b5dc 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05a98bc0 fffff880`03f722e1 : fffffa80`05781410 fffffa80`00000000 00000000`00a2b5dc 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`05a98bf0 fffff880`03f9eff6 : 00000000`00000000 fffffa80`03dc6880 00000000`00000080 fffffa80`05781410 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`05a98d00 fffff800`03117bae : 00000000`02a48a16 fffffa80`05611b50 fffffa80`03b6a040 fffffa80`05611b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05a98d40 fffff800`02e6a8c6 : fffff800`02ff4e80 fffffa80`05611b50 fffff800`03002cc0 fffff880`05a98e40 : nt!PspSystemThreadStartup+0x5a
fffff880`05a98d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+13be30
fffff880`0493fe30 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+13be30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c41788

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04804000 fffff880`052e9000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 21 14:36:16 2013 (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4