Windows 7: BSOD Whilst playing Browsing and Playing game's

Jim123 · 08 Dec 2012

Hi I'm new to this forum and was wondering if i could get some help or advice on what the problem might be the PC is only 3 months old and has had four recent blue screen errors over the time i have been using it and i was wondering if this is a hardware or system failure that i may need to replace. These are the dump files and system information attached to post thank you.

koolkat77 · 08 Dec 2012

Welcome

The BSOD seems to be caused by old ATI video card drivers:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007da8010, fffff8800774da1c, 0, 2}

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+7a1c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007da8010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800774da1c, 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: 
atikmpag+7a1c
fffff880`0774da1c 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`071ef308 fffff880`07311000 : 00000000`00000116 fffffa80`07da8010 fffff880`0774da1c 00000000`00000000 : nt!KeBugCheckEx
fffff880`071ef310 fffff880`07310d0a : fffff880`0774da1c fffffa80`07da8010 fffffa80`06c0bd50 fffffa80`07be0010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`071ef350 fffff880`073b7f07 : fffffa80`07da8010 00000000`00000000 fffffa80`06c0bd50 fffffa80`07be0010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`071ef380 fffff880`073e5d5a : fffffa80`ffffffff 00000000`00141feb fffff880`071ef4d0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`071ef460 fffff880`073cbbb1 : fffffa80`08b94000 ffffffff`feced300 00000000`00000002 fffff880`071ef7d8 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`071ef4a0 fffff880`073ceaaf : 00000000`00020182 00000000`00000000 fffffa80`08a33240 fffff8a0`0d99b510 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`071ef5a0 fffff880`073cd1a0 : fffff8a0`0d99b510 00000000`00000000 fffffa80`08b94000 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`071ef5e0 fffff880`073cd0f6 : 00000000`00000000 00000000`00000001 fffffa80`08b94000 fffff880`073cba1e : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34
fffff880`071ef770 fffff880`073d6642 : fffffa80`08ba3ea0 00000000`00000001 00000000`00000001 fffff800`02edba32 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
fffff880`071ef7e0 fffff880`073d63eb : fffff8a0`0d99b510 00000000`00001000 fffffa80`08ba3ea0 fffff8a0`0d99b510 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
fffff880`071ef830 fffff880`073d5d8f : fffff8a0`0d99b510 fffffa80`08b94c80 00000000`00000000 fffffa80`08b94c80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b
fffff880`071ef890 fffff880`073c976c : fffffa80`08b94000 fffffa80`08b94000 fffffa80`08b94c80 fffffa80`08b94000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf
fffff880`071ef8d0 fffff880`073c6133 : 00000000`00000000 00000000`00000000 00000000`0000001c fffffa80`08b94000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc
fffff880`071ef910 fffff880`073e065d : 00000000`00000000 fffff8a0`00f79220 fffffa80`00000000 fffffa80`071e0420 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f
fffff880`071efae0 fffff880`073e0398 : fffff800`04dcf080 fffff880`073dfd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`071efcd0 fffff880`073dfe96 : 00000000`00000000 fffffa80`07162010 00000000`00000080 fffffa80`07be0010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`071efd00 fffff800`0317ce5a : 00000000`fffffc32 fffffa80`0898e4c0 fffffa80`06419b30 fffffa80`0898e4c0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`071efd40 fffff800`02ed6d26 : fffff800`03058e80 fffffa80`0898e4c0 fffff800`03066cc0 00000039`78eb7000 : nt!PspSystemThreadStartup+0x5a
fffff880`071efd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7a1c
fffff880`0774da1c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7a1c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e0a89c9

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

2: kd> lmvm atikmpag
start             end                 module name
fffff880`07746000 fffff880`07797000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Jun 29 08:11:21 2011 (4E0A89C9)
    CheckSum:         00051127
    ImageSize:        00051000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Click on the Start

► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; ATI and restart the system. Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper
Download latest version from: AMD Driver Autodetect
Video Card - Stress Test with Furmark

Video Card - Stress Test with Furmark

Monitor your temps with Speccy during these tests:

Speccy - System Information - Free Download

AMD Driver Autodetect

Go through this thread for more information: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Problematic software:

Uninstall the following with Revo uninstaller in Advanced Mode. (Restart the system if prompted).

Code:

Start Menu\Programs\Avira	Public:Start Menu\Programs\Avira	Public
Start Menu\Programs\Avira\Avira Desktop	Public:Start Menu\Programs\Avira\Avira Desktop	Public
Start Menu\Programs\DAEMON Tools Pro	Public:Start Menu\Programs\DAEMON Tools Pro	Public
Start Menu\Programs\RegClean Pro	Public:Start Menu\Programs\RegClean Pro	Public
Start Menu\Programs\Spybot - Search & Destroy	Public:Start Menu\Programs\Spybot - Search & Destroy	Public

Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

MSE is recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software:-

1. Microsoft Security Essentials - Free Antivirus for Windows
2. Malwarebytes - Free
3. Good and Free system security combination.

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Run the System File Checker. It allows the user to scan for and restore corruptions in Windows system files.

1. Click on the
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Run Disk Check on your hard disk for file system errors and bad sectors on it:

Disk Check

Free up the start-up, nothing except the antivirus is usually needed.

____
Post back results

Jim123 · 08 Dec 2012

Thank you for the advice i have done everything in your post the burn test results where 40 degrees so barely above the usual system temp SFC scannow found errors which it repaired dskchk found problems with the file system but 0 bad sectors it also states that it was unable to obtain a handle to the event log. Also most of the security descriptors said missing or invalid there is no log for me to post

koolkat77 · 08 Dec 2012

Quote:

Also most of the security descriptors said missing or invalid there is no log for me to post

I'm not sure I understood. Can you elaborate?

Upload a screenshot of your hard disk using crystal disk info:

Make a hard drive test from the hard drive manufacturers website.

Hard Drive Diagnostic Procedure

Jim123 · 08 Dec 2012

That was my mistake sorry i forgot to run chkdsk/f after i did that it came back with no problems found, this is the screenshot of crystal disk.

koolkat77 · 08 Dec 2012

Looks good.
Any BSOD-s after making the changes?

Jim123 · 09 Dec 2012

No bsods for the moment but it wasn't frequent enough before it happened like every month or so, so i guess ill have to wait and see thank you for help and time :).

koolkat77 · 09 Dec 2012

Quote: Originally Posted by Jim123

No bsods for the moment but it wasn't frequent enough before it happened like every month or so, so i guess ill have to wait and see thank you for help and time :).

OK, update the thread if you get one or none during the weeks ahead. :)
Good luck.

koolkat77 · 17 Jan 2013

Tip

If your problem is solved please use the Mark this thread as solved link at the top of your thread or down on the left corner