BSOD help

silentbravo · 30 Aug 2010

This pc is running Win 7 x64 Pro, this is the only install I have done, and it was with OEM disk.

This pc has been rock solid for close to a year since I built it, a few days ago I came into the office to a loud squeel, and It seemed as though the gpu had lost power and the machine was unresponsive. (may be irrelevant to this bsod)

Came in today pc had restarted itself and showed a BSOD message. I'm thinking it might have overheated some time yesterday and shut itself down. I run folding @ home apps which stress the pc full load and I think the heater may have been on yesterday and overheated it. My best guess anyways.

Just about 1 year old for this pc

Specs:

Phenom 2 945 stock clocked, stock hsf
2 x 2gb corsair + 1 x 1 corsair
8800 ultra card
corsair hx520 psu

report attached

**Capt.Jack Sparrow** · 30 Aug 2010

Hello and Welcome to SF !

Seems like it's your Video card that is causing the problem. Follow this article STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Follow this guide for Driver Removal nVidia Driver Cleanup Guide !! « Captain Debugger

Update the Following Drivers

Code:

RTCore64.sys Wed May 25 12:09:12 2005
BrUsbSer.sys Wed Aug 09 17:41:02 2006
Brserid.sys  Mon Aug 07 07:21:11 2006
lmimirr.sys  Wed Apr 11 04:02:45 2007
RaInfo.sys   Sat Jan 05 00:27:14 2008
Rt64win7.sys Thu Aug 20 21:35:06 2009

Check this article Driver Troubleshooting !! « Captain Debugger for updating drivers

Bugcheck:

Code:

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006b0f4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88013d76d50, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+11bd50
fffff880`13d76d50 803d815cb70000  cmp     byte ptr [nvlddmkm+0xc919d8 (fffff880`148ec9d8)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`04bdd9c8 fffff880`040f6ef8 : 00000000`00000116 fffffa80`06b0f4e0 fffff880`13d76d50 00000000`00000000 : nt!KeBugCheckEx
fffff880`04bdd9d0 fffff880`040f6c02 : fffff880`13d76d50 fffffa80`06b0f4e0 fffffa80`06db3d50 fffffa80`06d8f010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04bdda10 fffff880`0419df07 : fffffa80`06b0f4e0 00000000`00000000 fffffa80`06db3d50 fffffa80`06d8f010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`04bdda40 fffff880`041c7b75 : 00000000`ffffffff 00000000`000901d4 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`04bddb20 fffff880`041c62bb : 00000000`00000102 00000000`00000000 00000000`000901d4 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`04bddb50 fffff880`041992c6 : ffffffff`ff676980 fffffa80`06d8f010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`04bddbf0 fffff880`041c5e7a : 00000000`00000000 fffffa80`06e19c70 00000000`00000080 fffffa80`06d8f010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`04bddd00 fffff800`03520a86 : 00000000`fffffc32 fffffa80`06d7c060 fffffa80`039739e0 fffffa80`06d7c060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`04bddd40 fffff800`03259b06 : fffff880`02d63180 fffffa80`06d7c060 fffff880`02d6dfc0 fffff880`0106ebf0 : nt!PspSystemThreadStartup+0x5a
fffff880`04bddd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+11bd50
fffff880`13d76d50 803d815cb70000  cmp     byte ptr [nvlddmkm+0xc919d8 (fffff880`148ec9d8)],0

SYMBOL_NAME:  nvlddmkm+11bd50

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bb7d7fd

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner

Hope this helps,
Captain

silentbravo · 30 Aug 2010

Great thanks, I will look into these suggestions. It may have overheated and caused this, but I think I might have had some driver issues before, so would probably do good to reinstall them.