BSOD appears often on various times

[Cervix]

Windows 7 Ultimate - x64
Not the original installed OS on the system
Full retail version
What is the age of system (hardware)? A few days.
What is the age of OS installation? A few days.

So I have been upgrading my computer with new parts (motherboard, cpu, psu, gpu, memory) and having some problems with the stability. The HDD is about a year old.

Check my profile for full info about my hardware.

Would be very grateful if anyone could help me out with this one

 

[writhziden]

Problem Devices:

Ethernet Controller	PCI\VEN_8086&DEV_150C&SUBSYS_84571043&REV_00\4&312AFB2E&0&0028	The drivers for this device are not installed.

Antivirus Software? Recommend either

Microsoft Security Essentials - Free Antivirus for Windows​

or the

http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627​

Possible out of date drivers:

rt2870	fffff880`02690000	fffff880`0277e000	Wed Apr 15 00:32:59 2009 (49e57f9b)	000ee640		rt2870.sys

rt2870.sys -> Drivers

Loading Dump File [D:\Kingston\BSODDmpFiles\Cervix\Windows_NT6_BSOD_jcgriff2\030612-20170-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 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a5d000 PsLoadedModuleList = 0xfffff800`02c9ae50
Debug session time: Mon Mar  5 23:21:52.412 2012 (UTC - 7:00)
System Uptime: 0 days 7:02:17.988
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800c4fe4e0, fffff880043a79e0, 0, d}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** 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
---------

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800c4fe4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880043a79e0, 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`043a79e0 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  &ûÌ


CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`061d99c8 fffff880`05338cbc : 00000000`00000116 fffffa80`0c4fe4e0 fffff880`043a79e0 00000000`00000000 : nt!KeBugCheckEx
fffff880`061d99d0 fffff880`05338a43 : fffff880`043a79e0 fffffa80`0c4fe4e0 fffffa80`0be3fab0 fffffa80`0be41010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`061d9a10 fffff880`0420ff07 : fffffa80`0c4fe4e0 00000000`00000000 fffffa80`0be3fab0 fffffa80`0be41010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`061d9a40 fffff880`04239b75 : 00000000`ffffffff 00000000`0018c816 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`061d9b20 fffff880`042382bb : 00000000`00000102 00000000`00000003 00000000`0018c816 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`061d9b50 fffff880`0420b2c6 : ffffffff`ff676980 fffffa80`0be41010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`061d9bf0 fffff880`04237e7a : 00000000`00000000 fffffa80`0cbc4600 00000000`00000080 fffffa80`0be41010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`061d9d00 fffff800`02d72166 : 00000000`fffffc32 fffffa80`0be588c0 fffffa80`09a23740 fffffa80`0be588c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`061d9d40 fffff800`02aad486 : fffff800`02c47e80 fffffa80`0be588c0 fffff800`02c55c40 fffff880`0124abf0 : nt!PspSystemThreadStartup+0x5a
fffff880`061d9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+79e0
fffff880`043a79e0 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
---------

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 http://www.sevenforums.com/crashes-debugging/25912-bsod.html#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html and proceed through each step. Let us know if you need further help.

AODDriver2	fffff880`02a70000	fffff880`02aa1000	Mon Dec 19 00:30:03 2011 (4eeee7fb)	00018588		AODDriver2.sys

The above driver can cause problems on some systems. This driver is usually part of AMD Overdrive; also in EasyTune6 for Gigabyte motherboard; also in AMD Vision Engine Control Center. Remove the appropriate software.