Windows 7: Recent BSOD's NO Gaming, No Overclocking

lstephenscpa · 25 Feb 2012

I've had two recent BSOD's this month. My HP Pavillion Elite Core i7, 750GB, 8
GB, is 2 1/2 years old. Windows 7 Home Premium 64bit.

Prior to the BSOD's, I have recently installed Office 365, and am using Lync and Sharepoint. I've also recently hooked up a new Western Digital External 2TB, USB 2.0/3.0 to back up my data using Windows Backup. I have not left the external drive connected.

I've attached the dump file zip. Can you tell me what these dump files are saying is my problem?
Thank you.

ePeen · 25 Feb 2012

Hello, welcome to SevenForums!

Both dump files provided are the 116 Graphics Driver TDR Fault bugcheck. Common causes are:

Quote: Originally Posted by usasma

More info from the AMD link above - the suggestions in red are mine. This was extracted from this post - ( http://www.sevenforums.com/crashes-d...tml#post782801 )

Quote:

From this link ( http://forums.amd.com/game/messagevi...&enterthread=y ):

Quote:

The following hardware issues are examples that can cause a TDR event:
- Failing overclock on CPU or GPU (stop overclocking)
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: |MG| Video Memory Stress Test 1.7.116 Download )
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( HD Diagnostic ), reset your pagefile and run the System File Checker )
- Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!)
- GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)

Quote:

The following software issues are examples that can cause a TDR event:
-Incompatible drivers of any sort (either GPU, sound, etc) ( Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads )
-Messy registry (I doubt this and don't approve of registry cleaners)
-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for this OS)
-Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for this OS)
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version and that it's compatible with Windows 7)

First thing I'd recommend you do is fully uninstall and reinstall the latest version of your AMD video card drivers, especially since I've noticed that yours are dated from 2010. If doing this does not work, please follow the suggestions above.

Drivers that need to be updated:

Quote:

lmimirr.sys - lmimirr Tue Apr 10 18:32:45 2007 (LogMeIn Remote Access driver). Update here.

RaInfo.sys - RaInfo Fri Jan 04 13:57:14 2008 (LogMeIn/RemotelyAnywhere Kernel Information Provider). Update here.

LMIRfsDriver.sys - LMIRfsDriver Mon Jul 14 12:26:56 2008 (RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver). Update here.

purendis.sys - purendis Tue Oct 28 00:31:28 2008 (Pure Networks, Inc. Network Magic NDIS Relay Driver). Update here.

pnarp.sys - pnarp Tue Oct 28 01:57:00 2008 (Pure Networks, Inc. Network Magic Address Resolution Protocol Driver). Update here.

Code:

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800e5a0380, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880017a5f5c, 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+6f5c
fffff880`017a5f5c 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`068fa9c8 fffff880`03ef1000 : 00000000`00000116 fffffa80`0e5a0380 fffff880`017a5f5c 00000000`00000000 : nt!KeBugCheckEx
fffff880`068fa9d0 fffff880`03ef0d87 : fffff880`017a5f5c fffffa80`0e5a0380 00000000`00000000 fffffa80`0b0c2410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`068faa10 fffff880`03f97f07 : fffffa80`0e5a0380 00000000`00000000 00000000`00000000 fffffa80`0b0c2410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`068faa40 fffff880`03fc1bd4 : fffffa80`00000000 00000000`030fbeb6 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`068fab20 fffff880`03fc02bb : 00000000`00000102 00000000`00000000 00000000`030fbeb6 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`068fab50 fffff880`03f932c6 : ffffffff`ff676980 fffffa80`0b0c2410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`068fabf0 fffff880`03fbfe7a : 00000000`00000000 fffffa80`107f4160 00000000`00000080 fffffa80`0b0c2410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`068fad00 fffff800`03378fee : 00000000`fffffc32 fffffa80`09f54b60 fffffa80`06a06040 fffffa80`09f54b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`068fad40 fffff800`030cf5e6 : fffff880`009ed180 fffffa80`09f54b60 fffff880`009f80c0 fffff880`01421384 : nt!PspSystemThreadStartup+0x5a
fffff880`068fad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6f5c
fffff880`017a5f5c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+6f5c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c86e399

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800741b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002e1cf5c, 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+6f5c
fffff880`02e1cf5c 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`02356898 fffff880`04261000 : 00000000`00000116 fffffa80`0741b4e0 fffff880`02e1cf5c 00000000`00000000 : nt!KeBugCheckEx
fffff880`023568a0 fffff880`04260d87 : fffff880`02e1cf5c fffffa80`0741b4e0 00000000`00000000 fffffa80`09f07410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`023568e0 fffff880`04307f07 : fffffa80`0741b4e0 00000000`00000000 00000000`00000000 fffffa80`09f07410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`02356910 fffff880`04335d5a : 00000000`00000001 00000000`00444249 fffff880`02356a70 fffffa80`09f07410 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`023569f0 fffff880`0433179e : fffffa80`09f07410 ffffffff`feced300 00000000`00000000 fffff880`043042f2 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`02356a30 fffff880`04330034 : fffffa80`09f07410 00000000`00000002 00000000`01312d00 fffff880`042ff27b : dxgmms1!VidSchiWaitForDrainFlipQueue+0x92
fffff880`02356b20 fffff880`043302fe : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`09f07ba0 : dxgmms1!VidSchiHandleControlEvent+0x4c
fffff880`02356b50 fffff880`043032c6 : ffffffff`ff676980 fffffa80`09f07410 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`02356bf0 fffff880`0432fe7a : fffffa80`0b72ea20 fffffa80`0b72ea20 00000000`00000080 fffffa80`09f07410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02356d00 fffff800`03325fee : 00000000`fffffc32 fffffa80`0b170b60 fffffa80`06a06040 fffffa80`0b170b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02356d40 fffff800`0307c5e6 : fffff800`03200e80 fffffa80`0b170b60 fffff800`0320ecc0 2c4d4145`52545356 : nt!PspSystemThreadStartup+0x5a
fffff880`02356d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6f5c
fffff880`02e1cf5c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+6f5c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c86e399

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner

Windows 7: Recent BSOD's NO Gaming, No Overclocking

Recent BSOD's NO Gaming, No Overclocking problems?