Hey all, I'm going to keep this short and simple until someone can point me to the proper information to send your way to help out.

I've had intermittent issues with my PC since purchase, beginning with an occasional BSOD when playing games.  It wasn't often so I didn't pay it any mind.  But as time went on, it's become more and more common to the point where any benchmark game is causing problems. I'm now running 10 instead of 8.1. I understand this is the 8.1 forum, but the errorr were similar (not exact same descriptions but same chain of events) in 8.1 as it is now in 10. 

I've tried clean installs, installing and removing drivers, safe mode.

The issue:  Whenever changing settings for a game, or entering into fullscreen mode I get a BSOD.  I've done the basics: clean install, safe mode, ect. 

Light info:  In event log I get this (same order every time when I get a crash/shutdown

Error ATIeREcord 16396

A number of devicesetupmanager warnings

Followed by error Devicesetupmanager 131

and culminating in a critical Kernel-Power 41

I know this is basic info, but once we can head in the right direction, I can provide details or a dmp file if necessary.  Just need to know how many dmp files or what details are needed

Thanks!

• Edited by EternalElements Thursday, July 30, 2015 7:43 PM

Your DMP file coincides with what your event log indicated. The crashes are caused by atikmdag.sys, which is an ATI driver. Please follow Jim-xu's instructions to update, reinstall, or revert to an older more stable version of the driver.

P.S. Your reference to Star Wars earns you a +1

DMP information below.

.

.

.

.

.

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff801654a29aa, ffffd0002337d778, ffffd0002337cf90}

*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmdag.sys ( atikmdag+329aa )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801654a29aa, The address that the exception occurred at
Arg3: ffffd0002337d778, Exception Record Address
Arg4: ffffd0002337cf90, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
atikmdag+329aa
fffff801`654a29aa 488b5cc310      mov     rbx,qword ptr [rbx+rax*8+10h]

EXCEPTION_RECORD:  ffffd0002337d778 -- (.exr 0xffffd0002337d778)
ExceptionAddress: fffff801654a29aa (atikmdag+0x00000000000329aa)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000010
Attempt to read from address 0000000000000010

CONTEXT:  ffffd0002337cf90 -- (.cxr 0xffffd0002337cf90)
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe0009258e000
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffd0002337da70
rip=fffff801654a29aa rsp=ffffd0002337d9b0 rbp=0000000000000001
 r8=0000000000000000  r9=ffffd0002337da70 r10=ffffe000917d8020
r11=ffffd0002337da88 r12=0000000000000001 r13=ffffd0002337e0a0
r14=0000000000000001 r15=0000000000000002
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+0x329aa:
fffff801`654a29aa 488b5cc310      mov     rbx,qword ptr [rbx+rax*8+10h] ds:002b:00000000`00000010=????????????????
Resetting default scope

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000010

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000010

FOLLOWUP_IP:
atikmdag+329aa
fffff801`654a29aa 488b5cc310      mov     rbx,qword ptr [rbx+rax*8+10h]

BUGCHECK_STR:  AV

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff801654a28a1 to fffff801654a29aa

STACK_TEXT:  
ffffd000`2337d9b0 fffff801`654a28a1 : ffffe000`917d8020 fffff801`65531b93 00000000`00000000 00000000`00000000 : atikmdag+0x329aa
ffffd000`2337d9e0 fffff801`65563a5c : ffffe000`978af300 ffffd000`2337db30 ffffd000`2337da70 fffff801`6559cb43 : atikmdag+0x328a1
ffffd000`2337da20 fffff801`65563908 : 00000000`00000000 ffffc000`b7dd2900 ffffe000`978af300 00000000`00000000 : atikmdag+0xf3a5c
ffffd000`2337da50 fffff801`655633fe : 00000000`00000003 ffffe000`978af300 00000000`00000000 fffff801`65484534 : atikmdag+0xf3908
ffffd000`2337da90 fffff801`65564393 : ffffd000`2337e0a0 ffffd000`2337e050 00000000`00000000 00000000`00000001 : atikmdag+0xf33fe
ffffd000`2337db00 fffff801`655a88bd : ffffe000`96f97010 ffffd000`2337e050 00000000`00000000 ffffe000`96f97010 : atikmdag+0xf4393
ffffd000`2337df90 fffff801`654843cf : ffffe000`917d8020 ffffd000`2337e0c0 ffffe000`975de060 00000000`21180000 : atikmdag+0x1388bd
ffffd000`2337dfc0 fffff801`66e2c80b : ffffd000`2337e270 fffff801`620e35c0 ffffd000`2337e270 fffff801`66e2c867 : atikmdag+0x143cf
ffffd000`2337e170 fffff801`6214d02a : ffffe000`9790e2c0 ffffd000`2337e270 00000000`00000000 00000000`00000001 : atikmpag+0xc80b
ffffd000`2337e1c0 fffff801`62e9529b : ffffd000`2337e300 ffffc000`ae12bba0 ffffe000`973ca000 ffffd000`2337e310 : dxgkrnl!ADAPTER_RENDER::DdiBuildPagingBuffer+0x8a
ffffd000`2337e200 fffff801`62ea40e7 : ffffc000`aeb75c70 ffffc000`af6d6a00 ffffc000`b7bb3700 00000000`00000098 : dxgmms2!VIDMM_GLOBAL::UpdatePageTable+0x29f
ffffd000`2337e420 fffff801`62e9e7df : ffffc000`b7bb3700 fffff803`00000002 ffffc000`b33d0620 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTable+0x14b
ffffd000`2337e4f0 fffff801`62e9dfcb : 00000000`00000006 ffffc000`b33d0620 ffffe000`977e87a0 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x453
ffffd000`2337e5a0 fffff801`62e9d9e9 : 00000000`00000002 ffffc000`b33d0620 ffffd000`2337e7d0 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x51b
ffffd000`2337e720 fffff801`62e8c436 : 00000000`00000000 00000000`00000000 00000000`00000004 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x5e9
ffffd000`2337e870 fffff801`62e6fe7d : 00000000`00000071 ffffd000`2337e9f0 ffffe000`95ff1e70 ffffe000`9790e3c0 : dxgmms2!VIDMM_GLOBAL::CommitVirtualAddressRangeSystemCommand+0x152
ffffd000`2337e8f0 fffff801`62e89478 : ffffc000`ae964d30 00000000`003128d4 ffffc000`aeb6b5d0 ffffc000`ae964d30 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0xa7d
ffffd000`2337ea90 fffff801`62e78867 : ffffc000`ae964d30 ffffd000`2337eb99 00000000`003128d4 ffffc000`aeb6b5d0 : dxgmms2!VIDMM_WORKER_THREAD::SubmitPacket+0x10430
ffffd000`2337eaf0 fffff803`6ecf7698 : 00000000`000ebb00 00000000`000ebb00 00000000`000ebb00 00000000`000ebb00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x36b
ffffd000`2337ec00 fffff803`6ed64306 : ffffd000`dfbda180 ffffe000`9790e2c0 ffffd000`dfbe6dc0 00000000`000ebb8f : nt!PspSystemThreadStartup+0x58
ffffd000`2337ec60 00000000`00000000 : ffffd000`2337f000 ffffd000`23379000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+329aa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55a70ac5

STACK_COMMAND:  .cxr 0xffffd0002337cf90 ; kb

FAILURE_BUCKET_ID:  AV_atikmdag+329aa

BUCKET_ID:  AV_atikmdag+329aa

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

• Proposed as answer by Kate LiMicrosoft contingent staff, Moderator Monday, August 10, 2015 11:16 AM
• Edited by Acreed02 Monday, August 10, 2015 6:56 PM
• Marked as answer by Bruce WoodingModerator Sunday, August 16, 2015 3:19 AM

I'll be looking into it more this week (I'm out of town till Monday). I do want to point out I've already rolled back my drivers to two previous versions already and I'm still having the same issue. The other thing is that this type of issue would occasionally pop up in the past. The new drivers might have exsaberated the issue but it did not originate with the most recent update. I'll take a step back one more and see where I am, then follow the provided link.

• Edited by EternalElements Sunday, August 02, 2015 2:51 AM

It seems I am experiencing the same symptoms as you and would like to know your system configuration. Are you perhaps running CrossFire with two AMD graphics cards?

I've gotten the exact error memory code atikmdag+329aa consistantly with 15.7.1 (1002). Note that there are two hotfix drivers for 15.7.1 that update the driver version to 1003 and then 1004. It is the same driver and link from AMD's website and the only clue to the hotfix updates are found is the change list notes. You might want to download the driver again to obtain the latest version.

With the newer 1004 driver the memory location that triggers the BSOD changes to atikmdag+329af for me.

I have also posted my experiences on the AMD forums at community.amd.com/thread/175389. Read through it to see if you identify with any of my symptoms. I'm uncertain if its my unique combination of hardware since I do not see many reports of this problem and yours is one of the first I've found online.

This issue has been present for me for every driver after 13.1, through Windows 7, 8, 8.1 and has gotten much more frequent in 10.

I would suggest trying the older 13.1 drivers hopefully your card is supported as it only supports cards up to the HD 7000 series. If you still experience the issue then it might be a totally unrelated problem to mines but its worth a try.

I am unable to post links as my account is still new or I would have provided the link to the 13.1 drivers. Guru3D.com should have it.