BSOD After AMD Driver Crashes and Recovers

Rum2Rum · 10 Feb 2015

Hello,

My computer will have a BSOD randomly while I am browsing on the internet, maybe while I'm on Facebook. The screen will freeze and then turn black. Then It will restore and it will tell me my AMD Driver has stopped working and successfully recovered. The computer will work for 10 seconds or so after and then crash to a BSOD. I had a failing hard drive a couple months ago and have switched it out with a WD 750 GB Black HDD. The new one is working fine but I am not sure if it may have anything to do with it. I have also done a chkdsk and a sfc scan. I usually get this BSOD randomly and I feel like it happens while I am on Facebook. I put my laptop on sleep a lot and keep the Facebook website open as one of my tabs on Chrome so maybe a memory issue?

Rum2Rum · 10 Feb 2015

My computer just crashed again while I was watching a youtube video. I paused the video and put the computer to sleep. I then used my computer and everything was fine until I started watching the video from where it left off. The computer then gave me the AMD driver has stopped working and has recovered message again and then crashed about 15 seconds after it recovered to the BSOD. I get this message from microsoft when I reboot:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800A8B64E0
BCP2: FFFFF8800440B038
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\021015-34788-01.dmp
C:\Users\Rum\AppData\Local\Temp\WER-97625-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I have attached a new log collector file.

Rum2Rum · 17 Feb 2015

Bump

SGT Oddball · 17 Feb 2015

The dump is blaming your ATI graphics driver, try finding a new driver from your laptop's vendor site or ATI then uninstall the old one and install the new one without the Catalyst control center and see how you get on.

Driver Reference Table - atikmpag.sys

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800a8b64e0, fffff8800440b038, 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+b038 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800a8b64e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800440b038, 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+b038
fffff880`0440b038 4883ec28        sub     rsp,28h
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`03ca2888 fffff880`10116134 : 00000000`00000116 fffffa80`0a8b64e0 fffff880`0440b038 00000000`00000000 : nt!KeBugCheckEx
fffff880`03ca2890 fffff880`10115e3e : fffff880`0440b038 fffffa80`0a8b64e0 fffffa80`085d4b40 fffffa80`06503010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03ca28d0 fffff880`101bdf13 : fffffa80`0a8b64e0 00000000`00000000 fffffa80`085d4b40 fffffa80`06503010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03ca2900 fffff880`101e7cf1 : 00000000`ffffffff 00000000`003ebc92 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03ca29e0 fffff880`101e6437 : 00000000`00000102 00000000`00000006 00000000`003ebc92 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03ca2a10 fffff880`101b92d2 : ffffffff`ff676980 fffffa80`06503010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03ca2ab0 fffff880`101e5ff6 : 00000000`00000000 fffffa80`0575cb30 00000000`00000080 fffffa80`06503010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03ca2bc0 fffff800`03d5f0ca : 00000000`fffffc32 fffffa80`065c7060 fffffa80`04ed3040 fffffa80`065c7060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03ca2c00 fffff800`03ab3be6 : fffff800`03c3ce80 fffffa80`065c7060 fffff800`03c4acc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03ca2c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+b038
fffff880`0440b038 4883ec28        sub     rsp,28h
SYMBOL_NAME:  atikmpag+b038
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  5417612a
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys
FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}
Followup: MachineOwner
---------