BSOD and PC Freeze randomly-Maybe because of graphic card failure

Hi Sevenforums :)

My PC is lately beginning to freeze randomly. Sometimes I just surf the web and then my music lags for 20 seconds and everything freezes. Sometimes Windows says that it has recovered from a "Video Hardware Error". And other times it's just coming back to normal without any message.

Today I came back to my PC, it was turned on. And my monitor was on "standby" which it does automatically after 10 minutes. But when I moved on the mouse it didn't turn on or the PC didn't respond, then after 30 seconds the PC restarted with the screen where you press enter to start normally again.

When I checked in the problem registry there where three problems. Two "Video Hardware Errors", and one BSOD error.

I find it pretty annoying so I hope you can help me. I've attached the zip.

kfrandsen

koolkat77 said:

Welcome to the forum.

Please take a look at this thread: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\kfrandsen\SF_29-11-2013\112913-22417-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`0328e6d0
Debug session time: Sat Nov 30 02:20:38.424 2013 (UTC + 6:00)
System Uptime: 0 days 4:03:44.611
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800a0a42c0, fffff880073bc6b4, 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+14d6b4 )

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: fffffa800a0a42c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880073bc6b4, 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+14d6b4
fffff880`073bc6b4 803d4e3e6a0000  cmp     byte ptr [nvlddmkm+0x7f1509 (fffff880`07a60509)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03e479c8 fffff880`080c7140 : 00000000`00000116 fffffa80`0a0a42c0 fffff880`073bc6b4 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`03e479d0 fffff880`080c6f1b : fffff880`073bc6b4 fffffa80`0a0a42c0 00000000`00000000 fffffa80`08c87010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03e47a10 fffff880`0816df13 : fffffa80`0a0a42c0 00000000`c00000b5 00000000`00000000 fffffa80`08c87010 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`03e47a40 fffff880`08197d50 : fffffa80`00000000 00000000`000e4bcf 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03e47b20 fffff880`08196437 : 00000000`00000102 00000000`00000000 00000000`000e4bcf 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`03e47b50 fffff880`081692d2 : ffffffff`ff676980 fffffa80`08c87010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03e47bf0 fffff880`08195ff6 : 00000000`00000000 fffffa80`08eea850 00000000`00000080 fffffa80`08c87010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03e47d00 fffff800`0335d2ea : 00000000`026ef447 fffffa80`08d29760 fffffa80`06d09040 fffffa80`08d29760 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03e47d40 fffff800`030b18e6 : fffff800`0323be80 fffffa80`08d29760 fffff800`03249cc0 fffff880`03e47e40 : nt!PspSystemThreadStartup+0x5a
fffff880`03e47d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+14d6b4
fffff880`073bc6b4 803d4e3e6a0000  cmp     byte ptr [nvlddmkm+0x7f1509 (fffff880`07a60509)],0

SYMBOL_NAME:  nvlddmkm+14d6b4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52314e10

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`0726f000 fffff880`07d66000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Sep 12 11:16:00 2013 (52314E10)
    CheckSum:         00AC9E83
    ImageSize:        00AF7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Arc said:

Lately we have experienced some issues with the latest driver. 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).
• Now follow Drivers - Clean Left over Files after Uninstalling
• 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:
  
  

Let us know the results.

Thanks koolkat77 I will let you know if it helps. :)