bsod when idle or little useage

Problem Devices:

Code:

Broadcom 802.11g Network Adapter	PCI\VEN_14E4&DEV_4320&SUBSYS_70011799&REV_03\4&2B4059EA&0&30A4	This device is disabled.

This was probably intentional and nothing to worry about...


Security Software: ??? Recommend that you install one of the following two security systems, update it, and then run a full scan of your system for viruses/malware:

• Microsoft Security Essentials - Free Antivirus for Windows
  
  
• Good and Free system security combination.

Possible out of date driver:

Code:

pcouffin	fffff880`04256000	fffff880`0426a080	Fri Jun 30 07:40:29 2006 (44a529cd)	00019543		pcouffin.sys

pcouffin.sys

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\fastslvblkcar\Windows_NT6_BSOD_jcgriff2\033012-9999-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 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02a13000 PsLoadedModuleList = 0xfffff800`02c57650
Debug session time: Fri Mar 30 22:22:08.142 2012 (UTC - 6:00)
System Uptime: 0 days 0:48:43.797
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007db94e0, fffff880040bb9e0, 0, d}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+79e0 )

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

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

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

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


FAULTING_IP: 
atikmpag+79e0
fffff880`040bb9e0 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`06bed9c8 fffff880`04166000 : 00000000`00000116 fffffa80`07db94e0 fffff880`040bb9e0 00000000`00000000 : nt!KeBugCheckEx
fffff880`06bed9d0 fffff880`04165d87 : fffff880`040bb9e0 fffffa80`07db94e0 fffffa80`08455950 fffffa80`06a11010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06beda10 fffff880`061b9f07 : fffffa80`07db94e0 00000000`00000000 fffffa80`08455950 fffffa80`06a11010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`06beda40 fffff880`061e3b75 : 00000000`ffffffff 00000000`0002db98 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06bedb20 fffff880`061e22bb : 00000000`00000102 00000000`00000001 00000000`0002db98 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06bedb50 fffff880`061b52c6 : ffffffff`ff676980 fffffa80`06a11010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06bedbf0 fffff880`061e1e7a : 00000000`00000000 fffffa80`08a5cd50 00000000`00000080 fffffa80`06a11010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06bedd00 fffff800`02d29f7a : 00000000`fffffc32 fffffa80`08627b60 fffffa80`069ab9e0 fffffa80`08627b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06bedd40 fffff800`02a809c6 : fffff880`030a4180 fffffa80`08627b60 fffff880`030af040 fffff880`0101ccb0 : nt!PspSystemThreadStartup+0x5a
fffff880`06bedd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+79e0
fffff880`040bb9e0 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+79e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f3b14b8

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

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.

Security Software:

Code:

msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	2396	8	200	1380	4/1/2012 9:04 PM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	1172	8	200	1380	4/1/2012 9:05 PM	3.0.8402.0	281.52 KB (288,272 bytes)	4/27/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	3900	8	200	1380	4/1/2012 9:04 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 2:35 PM

Looks good. If you have any more crashes, let us know, upload the crash report, and then follow the link provided in my previous post.