BSOD randomly, sometimes while playing games, sometimes just idle.

Hey, its a great gaming rig, but just recently started getting these BSOD. While playing Stronghold 3, I've been getting them none stop making it impossible to play, as well as with many other games. Tried reinstalling drivers but not sure exactly which ones are causing the problem, if it even is drivers. Here's some info from the files:

Here are reports from BLUESCREEVIEW:

1.
021812-28563-01.dmp 2/18/2012 9:19:22 PM 0x00000116 fffffa80`05db2010 fffff880`10cf7ae4 ffffffff`c000009a 00000000`00000004 dxgkrnl.sys dxgkrnl.sys+5d000 x64 ntoskrnl.exe+705c0 C:\Windows\Minidump\021812-28563-01.dmp 8 15 7600 928,992

2.
021812-50419-01.dmp 2/18/2012 9:05:44 PM 0x00000116 fffffa80`065ad010 fffff880`10d0cae4 ffffffff`c000009a 00000000`00000004 dxgkrnl.sys dxgkrnl.sys+5d000 x64 ntoskrnl.exe+705c0 C:\Windows\Minidump\021812-50419-01.dmp 8 15 7600 456,368

3.
021812-28548-01.dmp 2/18/2012 7:30:08 PM 0x00000116 fffffa80`0622f010 fffff880`10c91ae4 ffffffff`c000009a 00000000`00000004 dxgkrnl.sys dxgkrnl.sys+5d000 x64 ntoskrnl.exe+705c0 C:\Windows\Minidump\021812-28548-01.dmp 8 15 7600 487,712
.

etc etc. Anyone can shine some light on this I'd greatly appreciate.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\Kingston\BSODDmpFiles\romanteni\Windows_NT6_BSOD_jcgriff2\021812-35521-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0305d000 PsLoadedModuleList = 0xfffff800`0329ae70
Debug session time: Sat Feb 18 23:23:13.574 2012 (GMT-7)
System Uptime: 0 days 0:00:43.948
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {7, fffff8800a70ba10, fffff9800bb9aee0, 0}

Unable to load image \??\C:\Program Files\PeerBlock\pbfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for pbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for pbfilter.sys
Probably caused by : pbfilter.sys ( pbfilter+2a10 )

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

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000007, IRP passed to IoCompleteRequest still has cancel routine set
Arg2: fffff8800a70ba10, the cancel routine pointer
Arg3: fffff9800bb9aee0, the IRP
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_7

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  7

IRP_CANCEL_ROUTINE: 
pbfilter+2a10
fffff880`0a70ba10 48895c2408      mov     qword ptr [rsp+8],rbx

FAULTING_IP: 
pbfilter+2a10
fffff880`0a70ba10 48895c2408      mov     qword ptr [rsp+8],rbx

FOLLOWUP_IP: 
pbfilter+2a10
fffff880`0a70ba10 48895c2408      mov     qword ptr [rsp+8],rbx

IRP_ADDRESS:  fffff9800bb9aee0

DEVICE_OBJECT: fffffa800b6f9cc0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000356d072 to fffff800030cd5c0

STACK_TEXT:  
fffff880`073aa098 fffff800`0356d072 : 00000000`000000c9 00000000`00000007 fffff880`0a70ba10 fffff980`0bb9aee0 : nt!KeBugCheckEx
fffff880`073aa0a0 fffff880`0a70b9ea : 00000000`00004400 00000000`00000000 fffffa80`0b6f9e10 fffff980`0bb9aee0 : nt!IovCompleteRequest+0x72
fffff880`073aa170 00000000`00004400 : 00000000`00000000 fffffa80`0b6f9e10 fffff980`0bb9aee0 00000000`00000011 : pbfilter+0x29ea
fffff880`073aa178 00000000`00000000 : fffffa80`0b6f9e10 fffff980`0bb9aee0 00000000`00000011 00000000`ffffffff : 0x4400


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  pbfilter+2a10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: pbfilter

IMAGE_NAME:  pbfilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cd60dba

FAILURE_BUCKET_ID:  X64_0xc9_7_VRF_pbfilter+2a10

BUCKET_ID:  X64_0xc9_7_VRF_pbfilter+2a10

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

Loading Dump File [F:\Kingston\BSODDmpFiles\romanteni\Windows_NT6_BSOD_jcgriff2\021812-28563-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0304a000 PsLoadedModuleList = 0xfffff800`03287e70
Debug session time: Sat Feb 18 22:17:47.946 2012 (GMT-7)
System Uptime: 0 days 0:03:49.304
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005db2010, fffff88010cf7ae4, 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+c3bae4 )

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: fffffa8005db2010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88010cf7ae4, 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+c3bae4
fffff880`10cf7ae4 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`09ed2b88 fffff880`070e7000 : 00000000`00000116 fffffa80`05db2010 fffff880`10cf7ae4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`09ed2b90 fffff880`070ba867 : fffff880`10cf7ae4 fffffa80`0ab0b000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`09ed2bd0 fffff880`070e6e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`05db2010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`09ed2c80 fffff880`071b5ec1 : fffffa80`0ade7970 00000000`00000080 00000000`00000000 fffffa80`0ab03010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`09ed2d00 fffff800`0335a6fa : 00000000`04590ff6 fffffa80`0ab26770 fffffa80`05af2040 fffffa80`0ab26770 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`09ed2d40 fffff800`03098b46 : fffff800`03234e80 fffffa80`0ab26770 fffff800`03242c40 fffff880`01449534 : nt!PspSystemThreadStartup+0x5a
fffff880`09ed2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+c3bae4
fffff880`10cf7ae4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+c3bae4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

1. Caused by Verifier. The driver causing the Verifier based crash is part of Peerblock.
2. This is a stop 0x116, which means that your display card driver or display card failed to respond in a timely manner to a system command asking it to respond.

Remove Peerblock. Disable Driver Verifier.

For stop 0x116:

H2SO4 said:

These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.

The above quote was taken from https://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.



Update to Service Pack 1 (SP1)

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site

Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH