BSOD 1000007E caused by atikmdag.sys while playing games

[Mac2115]

Hi,
The BSOD only occurs while playing specific games(Battlefield 3,Path of Exile), I can play a few others without any problems(empire total war, binding of isaac). I tried to solve this problem by making clean reinstall of the drivers, reinstalling windows and after that checking if BSOD still occurs on default drivers provided by the Acer or Latest AMD Drivers, nothing changed.

P.S I'm really sorry for my terrible English

 

[Arc]

Try the 14.11.2 Beta from Mobile rather than the Omega one?

Uninstall your installed latest version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

Then install the driver.

Also Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Let us know the results.

 

[Mac2115]

Had another BSOD after installing the mobility beta drivers so I uploaded the crash dump file too

 

[Arc]

When multiple versions of the display driver causing the same BSOD, the indication goes to the graphics card. But furmark ran for enough time, you did not mention about any mishap during the test.

In this situation, it is difficult to say that either the driver or the card is responsible for the BSODs. I would suggest you to contract the game developers. Ask them if your device is ready for those games and if you need any custom settings or patches to play those games successfully on your computer.
_______________________________________

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000094, fffff8800f368d15, fffff88005878e38, fffff88005878690}

Probably caused by : atikmdag.sys ( atikmdag+79d15 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff8800f368d15, The address that the exception occurred at
Arg3: fffff88005878e38, Exception Record Address
Arg4: fffff88005878690, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
atikmdag+79d15
fffff880`0f368d15 41f7f1          div     eax,r9d

EXCEPTION_RECORD:  fffff88005878e38 -- (.exr 0xfffff88005878e38)
ExceptionAddress: fffff8800f368d15 (atikmdag+0x0000000000079d15)
   ExceptionCode: c0000094 (Integer divide-by-zero)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff88005878690 -- (.cxr 0xfffff88005878690;r)
rax=00000000000afc80 rbx=fffff880058790c0 rcx=fffff88005879100
rdx=0000000000000000 rsi=fffffa800ade0400 rdi=fffff8800f2ef000
rip=fffff8800f368d15 rsp=fffff88005879070 rbp=fffff88005879120
 r8=00000000000afc80  r9=0000000000000000 r10=0000000000000186
r11=fffff8800f618ac0 r12=00000000000009dd r13=00000000000009de
r14=0000000000000026 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
atikmdag+0x79d15:
fffff880`0f368d15 41f7f1          div     eax,r9d
Last set context:
rax=00000000000afc80 rbx=fffff880058790c0 rcx=fffff88005879100
rdx=0000000000000000 rsi=fffffa800ade0400 rdi=fffff8800f2ef000
rip=fffff8800f368d15 rsp=fffff88005879070 rbp=fffff88005879120
 r8=00000000000afc80  r9=0000000000000000 r10=0000000000000186
r11=fffff8800f618ac0 r12=00000000000009dd r13=00000000000009de
r14=0000000000000026 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
atikmdag+0x79d15:
fffff880`0f368d15 41f7f1          div     eax,r9d
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffff880058790c0 to fffff8800f368d15

STACK_TEXT:  
fffff880`05879070 fffff880`058790c0 : fffff880`05879120 fffffa80`0ade0000 fffffa80`0acae878 fffff880`05879160 : atikmdag+0x79d15
fffff880`05879078 fffff880`05879120 : fffffa80`0ade0000 fffffa80`0acae878 fffff880`05879160 fffff880`0f3683c2 : 0xfffff880`058790c0
fffff880`05879080 fffffa80`0ade0000 : fffffa80`0acae878 fffff880`05879160 fffff880`0f3683c2 00000000`00000027 : 0xfffff880`05879120
fffff880`05879088 fffffa80`0acae878 : fffff880`05879160 fffff880`0f3683c2 00000000`00000027 00000000`00000000 : 0xfffffa80`0ade0000
fffff880`05879090 fffff880`05879160 : fffff880`0f3683c2 00000000`00000027 00000000`00000000 00000013`00000040 : 0xfffffa80`0acae878
fffff880`05879098 fffff880`0f3683c2 : 00000000`00000027 00000000`00000000 00000013`00000040 00000081`00000002 : 0xfffff880`05879160
fffff880`058790a0 00000000`00000027 : 00000000`00000000 00000013`00000040 00000081`00000002 fffff880`05879160 : atikmdag+0x793c2
fffff880`058790a8 00000000`00000000 : 00000013`00000040 00000081`00000002 fffff880`05879160 fffffa80`0ade0400 : 0x27


FOLLOWUP_IP: 
atikmdag+79d15
fffff880`0f368d15 41f7f1          div     eax,r9d

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+79d15

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  546a4601

STACK_COMMAND:  .cxr 0xfffff88005878690 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+79d15

BUCKET_ID:  X64_0x7E_atikmdag+79d15

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+79d15

FAILURE_ID_HASH:  {1018387c-e526-9518-97f0-b50368a4b26a}

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

2: kd> lmvm atikmdag
start             end                 module name
fffff880`0f2ef000 fffff880`1035b000   atikmdag   (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Tue Nov 18 00:31:21 2014 (546A4601)
    CheckSum:         01007EA1
    ImageSize:        0106C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Mac2115]

I dont think this is a problem with the games, I could play them just fine a few months ago and I think that the last patch to BF3 came before I even bought the game. Thanks for trying to help though.

 

[Arc]

I dont think this is a problem with the games, I could play them just fine a few months ago and I think that the last patch to BF3 came before I even bought the game. Thanks for trying to help though.

So what do you think about the problem?

 

[Mac2115]

Today I had another crash with different game and after searching the web for some time it turned out that my particular spec(Acer Aspire 7750G) has quite a history with this BSOD. A lot of people gets it randomly while using different applications. I thought about what you said and I still don't think it's problem with the applications. Crashes started occuring around 1/2 year ago out of nowhere(without any patches to the applications that could break anything). You said that those might be just problems with graphic card, official amd guide about troubleshooting this particular BSOD (How to troubleshoot) also suggests that those crashes might be caused by "inadequate or defective power supply". I think that would be a pretty easy explanation why those crashes still occur after reinstalling system and checking all possible driver versions.