atikmdag.sys BSOD

**mscrivo** · 05-02-2013

Ever since upgrading my AMD 6950 to an AMD 7970 card, I've been having two very annoying issues: 1) a BSOD with atikmdag.sys randomly, but most often within a few mins of resuming from monitor sleep 2) Monitor just not waking up from sleep at all.

This is happening daily, and is driving me nuts. Here are the results from analyzing the crash dump in the hopes that you guys can help:

thanks,

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
Machine Name:
Kernel base = 0xfffff800`32804000 PsLoadedModuleList = 0xfffff800`32ad0b00
Debug session time: Thu May 2 11:23:14.415 2013 (UTC - 4:00)
System Uptime: 0 days 0:10:21.057
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
..................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007f6`03edf018). Type ".hh dbgerr001" for details
Loading unloaded module list
..........
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880051aad95, fffff8801a49f0b0, 0}

*** 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+14bd95 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880051aad95, Address of the instruction which caused the bugcheck
Arg3: fffff8801a49f0b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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+14bd95
fffff880`051aad95 8b4108 mov eax,dword ptr [rcx+8]

CONTEXT: fffff8801a49f0b0 -- (.cxr 0xfffff8801a49f0b0)
rax=0000000600000003 rbx=0000000600000003 rcx=0000000600000003
rdx=0000000000000010 rsi=fffffa800da2e5c0 rdi=fffffa8012a47040
rip=fffff880051aad95 rsp=fffff8801a49fab0 rbp=fffff8801a49fab0
r8=0000000000000015 r9=0000000000000000 r10=0000000000000801
r11=fffff8801a4a03f0 r12=0000000040001fc0 r13=fffff8a00f32c200
r14=fffffa8012a47040 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
atikmdag+0x14bd95:
fffff880`051aad95 8b4108 mov eax,dword ptr [rcx+8] ds:002b:00000006`0000000b=????????
Resetting default scope

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8800510c45a to fffff880051aad95

STACK_TEXT:
fffff880`1a49fab0 fffff880`0510c45a : 00000000`00000000 fffff880`1a49fae0 fffffa80`0da2e5c0 0000041a`00000690 : atikmdag+0x14bd95
fffff880`1a49fac0 fffff880`050fd0b3 : fffffa80`12a47040 fffffa80`12a47040 ffff0b96`d51c7ac7 fffffa80`12a45b01 : atikmdag+0xad45a
fffff880`1a49faf0 fffff880`05115d10 : fffff880`1a49fb60 fffff880`0510c45a 00000000`00000000 fffff880`1a49fb60 : atikmdag+0x9e0b3
fffff880`1a49fb30 fffff880`0510ebab : 00000000`00000000 fffff880`050fd0b3 fffffa80`0cc1f048 fffffa80`11d4d040 : atikmdag+0xb6d10
fffff880`1a49fb60 fffff880`05114cb5 : fffffa80`0da2e5c0 fffff880`1a49fce0 00000000`00000001 000000f4`00000000 : atikmdag+0xafbab
fffff880`1a49fbb0 fffff880`04ae56ab : fffffa80`12a47060 fffff880`00000000 fffffa80`00000000 00000000`000003d0 : atikmdag+0xb5cb5
fffff880`1a49fc70 fffff880`04190c2c : fffffa80`11d4d040 fffff880`1a4a0750 00000000`00000000 fffff8a0`028b5000 : atikmpag+0xc6ab
fffff880`1a49ff50 fffff880`0413ef6e : fffff880`1a4a0750 fffff880`1a4a07a1 00000000`00000001 00000000`00000000 : dxgkrnl!ADAPTER_RENDER:

diOpenAllocation+0x7c
fffff880`1a49ffa0 fffff880`0413e1d3 : fffff8a0`028b5000 fffff880`1a4a0750 fffff880`1a4a0490 fffff8a0`0c8be160 : dxgkrnl!DXGDEVICE::OpenAllocations+0x11e
fffff880`1a4a0050 fffff880`0414df25 : fffff880`00000799 fffff880`1a4a07a1 00000000`00000000 00000000`00000701 : dxgkrnl!DXGDEVICE::CreateAllocation+0x4c3
fffff880`1a4a06c0 fffff880`041483e9 : fffff8a0`00000238 fffff8a0`031024e0 fffff8a0`0c906490 00000000`00000000 : dxgkrnl!DXGDEVICE::OpenResource<_D3DKMT_OPENRESOUR CEFROMNTHANDLE>+0x325
fffff880`1a4a07e0 fffff880`04148057 : 00000084`235ae3d0 00000000`887a0005 fffff8a0`00000001 fffff8a0`0c906400 : dxgkrnl!OpenResourceFromGlobalHandleOrNtObject<_D3 DKMT_OPENRESOURCEFROMNTHANDLE>+0x349
fffff880`1a4a09d0 fffff800`3285d253 : 00000084`235ae3d0 00000000`00000020 00000084`235ae830 00000000`00000001 : dxgkrnl!DxgkOpenResourceFromNtHandle+0x193
fffff880`1a4a0b00 000007fd`102b233a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000084`235ae378 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fd`102b233a

FOLLOWUP_IP:
atikmdag+14bd95
fffff880`051aad95 8b4108 mov eax,dword ptr [rcx+8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+14bd95

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5154fbf8

STACK_COMMAND: .cxr 0xfffff8801a49f0b0 ; kb

FAILURE_BUCKET_ID: 0x3B_atikmdag+14bd95

BUCKET_ID: 0x3B_atikmdag+14bd95

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

**usasma** · 05-03-2013

The crash dump blames the video drivers, but we'll need the memory dumps to extract any more out of them.
Also, Please provide this information so we can provide a complete analysis: How To Ask For Help With BSOD

Update the video drivers and see if that helps.
Reseat the video card and make sure it's getting plenty of cool air and that the fan is working
Make sure the power connectors are firmly seated and that there's no hairballs, etc in the cooler.

Try the video stress tests at this page: Additional Hardware Diagnostics

**mscrivo** · 05-03-2013

Thanks! I can definitely get that info later today. The memory dump is 700MB, how would you like to receive that?

**mscrivo** · 05-03-2013

windows choose to delete the memory.dmp file .. I'll have to wait until it happens again, and i'll upload all the items requested.

**usasma** · 05-04-2013

Make sure the system is set to generate minidumps: Set MiniDump
If uploading a full memory dump, you'll have to pick a free file-hosting service to upload it to - then post a link to it here.

**mscrivo** · 05-08-2013

Here's the package from the W7F Diagnostic Tool W7F_08-05-2013.zip
Here's the full memory dump: https://www.dropbox.com/s/q2civw3u0dvqlap/MEMORY.zip

Also, every single driver and firmware for my system is up to date. As is all software.

Thanks again!

**usasma** · 05-08-2013

Only 50 Windows Updates installed. Most systems have 66 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:

1) That the SSD firmware is the latest available for the SSD
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to.

The memory dump blames your video drivers. Please follow the instructions here for installing ONLY DRIVERS: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

dsNcAdpt.sys Mon Mar 30 22:33:33 2009 (49D180FD)
Network Connect VPN software by Juniper Networks
http://www.carrona.org/drivers/driver.php?id=dsNcAdpt.sys

LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
Logitech Keyboard
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys

LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
Logitech Gamepanel Virtual HID Device Driver
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys

ladfGSCamd64.sys Mon Apr 11 14:41:01 2011 (4DA34B3D)
Driver for the Logitech GSeries Headset
http://www.carrona.org/drivers/driver.php?id=ladfGSCamd64.sys

ladfGSRamd64.sys Mon Apr 11 14:41:07 2011 (4DA34B43)
Driver for the Logitech GSeries Headset
http://www.carrona.org/drivers/driver.php?id=ladfGSRamd64.sys

Analysis:
The following is for informational purposes only.

Code:

**************************Wed May  8 09:14:05.827 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\050813-5671-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
System Uptime:2 days 18:48:34.468
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :atikmdag.sys ( atikmdag+d575 )
BugCheck 3B, {c0000005, fffff88005c3a575, fffff8801bdbe0b0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88005c3a575, Address of the instruction which caused the bugcheck
Arg3: fffff8801bdbe0b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID: 0x3B_atikmdag+d575
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

**************************Wed May  8 09:14:05.827 2013 (UTC - 4:00)**************************
dsNcAdpt.sys                Mon Mar 30 22:33:33 2009 (49D180FD)
LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
LGVirHid.sys                Mon Nov 23 20:36:48 2009 (4B0B38B0)
ladfGSCamd64.sys            Mon Apr 11 14:41:01 2011 (4DA34B3D)
ladfGSRamd64.sys            Mon Apr 11 14:41:07 2011 (4DA34B43)
cmudaxp.sys                 Wed Sep 26 04:29:02 2012 (5062BCCE)
lvrs64.sys                  Mon Oct 22 22:11:24 2012 (5085FCCC)
lvuvc64.sys                 Mon Oct 22 22:12:08 2012 (5085FCF8)
intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
e1q63x64.sys                Fri Nov 30 20:00:17 2012 (50B956A1)
HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
AtihdW86.sys                Thu Feb 14 17:11:12 2013 (511D6100)
rzendpt.sys                 Mon Mar  4 01:48:30 2013 (513443BE)
igdkmd64.sys                Fri Mar  8 21:10:00 2013 (513A99F8)
iaStorA.sys                 Mon Mar 18 19:36:36 2013 (5147A504)
dump_iaStorA.sys            Mon Mar 18 19:36:36 2013 (5147A504)
atikmpag.sys                Tue Apr 16 09:35:21 2013 (516D5399)
atikmdag.sys                Tue Apr 16 10:45:48 2013 (516D641C)
rzudd.sys                   Thu Apr 18 22:00:07 2013 (5170A527)
rzvkeyboard.sys             Thu Apr 18 22:00:15 2013 (5170A52F)
rzdaendpt.sys               Thu Apr 18 22:00:17 2013 (5170A531)
cbfs4.sys                   Wed Apr 24 14:10:52 2013 (5178202C)

Thread: atikmdag.sys BSOD

LinkBack

Thread Tools

Search Thread

atikmdag.sys BSOD

Re: atikmdag.sys BSOD

Re: atikmdag.sys BSOD

Re: atikmdag.sys BSOD

Re: atikmdag.sys BSOD

Re: atikmdag.sys BSOD

Re: atikmdag.sys BSOD

LinkBacks (?)

atikmdag.sys BSOD

Similar Threads

amounts of BSOD's

BSOD in Black Osp 2

How To Ask For Help With BSOD

What is causing my BSOD?

BSOD...

Tags for this Thread

Posting Permissions