Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Occasional BSOD atikmdag

16 Feb 2015   #1
agentsmith24

Windows 7 Ultimate 64 Bit
 
 
Occasional BSOD atikmdag

Haven't had any BSODs in a long time until the last month or so, maybe 1 every other day, always related to atikmdag.sys which I believe is the video driver? What would cause it to suddenly start crapping out on me like this?
Dump files attached for reference. Thanks for any assistance!


My System SpecsSystem Spec
.
17 Feb 2015   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Update the display driver to the latest WHQL. Download Drivers

See how it goes. Let us know.

Further actions may be needed depending on the resulting situation.
__________________________________________
Code:
.............
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** 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, {ffffffffc0000005, fffff8800f4e283b, fffff88005da6228, fffff88005da5a80}

Probably caused by : atikmdag.sys ( atikmdag+c483b )

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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800f4e283b, The address that the exception occurred at
Arg3: fffff88005da6228, Exception Record Address
Arg4: fffff88005da5a80, 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+c483b
fffff880`0f4e283b 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]

EXCEPTION_RECORD:  fffff88005da6228 -- (.exr 0xfffff88005da6228)
ExceptionAddress: fffff8800f4e283b (atikmdag+0x00000000000c483b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000006a8
Attempt to read from address 00000000000006a8

CONTEXT:  fffff88005da5a80 -- (.cxr 0xfffff88005da5a80;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=00000000000a8000 rdi=0000000000000002
rip=fffff8800f4e283b rsp=fffff88005da6460 rbp=fffffa801097d9a0
 r8=0000000000000002  r9=000000f41e1d0000 r10=0000000000000000
r11=fffff88005da6690 r12=fffffa801097d880 r13=fffffa800d48fbc0
r14=fffffa80143d0010 r15=fffff8800f41e000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
atikmdag+0xc483b:
fffff880`0f4e283b 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=00000000000a8000 rdi=0000000000000002
rip=fffff8800f4e283b rsp=fffff88005da6460 rbp=fffffa801097d9a0
 r8=0000000000000002  r9=000000f41e1d0000 r10=0000000000000000
r11=fffff88005da6690 r12=fffffa801097d880 r13=fffffa800d48fbc0
r14=fffffa80143d0010 r15=fffff8800f41e000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
atikmdag+0xc483b:
fffff880`0f4e283b 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

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:  00000000000006a8

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f8100
GetUlongFromAddress: unable to read from fffff800032f81c0
 00000000000006a8 Nonpaged pool

FOLLOWUP_IP: 
atikmdag+c483b
fffff880`0f4e283b 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]

BUGCHECK_STR:  0x7E

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

LAST_CONTROL_TRANSFER:  from 00000000000c0000 to fffff8800f4e283b

STACK_TEXT:  
fffff880`05da6460 00000000`000c0000 : 00000000`00000000 fffffa80`1097d880 00000000`00000003 fffffa80`143d0010 : atikmdag+0xc483b
fffff880`05da6468 00000000`00000000 : fffffa80`1097d880 00000000`00000003 fffffa80`143d0010 fffff880`0f54148f : 0xc0000


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+c483b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52ec068c

STACK_COMMAND:  .cxr 0xfffff88005da5a80 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+c483b

BUCKET_ID:  X64_0x7E_atikmdag+c483b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+c483b

FAILURE_ID_HASH:  {dc9cc0b9-993f-663d-42f6-2cf123a43aab}

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

2: kd> lmvm atikmdag
start             end                 module name
fffff880`0f41e000 fffff880`101bf000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Sat Feb 01 01:54:44 2014 (52EC068C)
    CheckSum:         00D501B6
    ImageSize:        00DA1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
17 Feb 2015   #3
agentsmith24

Windows 7 Ultimate 64 Bit
 
 

Ok I will. Thanks!
My System SpecsSystem Spec
.

27 Feb 2015   #4
agentsmith24

Windows 7 Ultimate 64 Bit
 
 
Crashed Again

So I ran AMD's auto-detect and download program, which I think may have installed a beta driver instead of WHQL? I didn't see options for older versions on their site, am I looking in the wrong place?

Anyways, I got a new crash today, the dump files are attached. Thanks for the help!
My System SpecsSystem Spec
27 Feb 2015   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

You should not use a BETA, get the 14.4 WHQL.
You may get it from here: AMD Catalyst 14.4 WHQL (14.100.0.0 April 17)

Follow this method to install it.
Quote:
Uninstall your installed latest version of the display driver.
Then clean up any possible leftover.
Then install version 114.4 WHQL only.
Done see how it goes.
Report us for any further BSOD.
My System SpecsSystem Spec
Reply

 Occasional BSOD atikmdag




Thread Tools




Similar help and support threads
Thread Forum
BSOD caused by the following module: atikmdag.sys (atikmdag+0x19C6D)
I hope anybody can help me....i already have the latest drivers but i still get BSOD's
BSOD Help and Support
Occasional BSOD
So far it seems to happen close to when I click Play on a game in my Steam library. Should this be a GPU driver issue, I am uninstalling them anyways to install a new card tomorrow along with making sure my RAM is seated properly, etc. I built this computer about 2 or 3 weeks ago and have had about...
BSOD Help and Support
Occasional BSOD
I built my computer about 6 months ago and have had occasional Blue Screens (1 a month or so), and am curious to find out what is causing them.
BSOD Help and Support
Occasional BSOD
I did a clean upgrade from Vista Home Premium to Windows 7 Professional 64bit and twice now I've gotten a BSOD with the same reason. These were weeks apart. I ran WhoCrashed and it puts out this: This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x9F (0x3,...
BSOD Help and Support
Occasional BSOD
Can somebody check this out for me? I recently built a new computer and finally installed Windows 7. After about 2 weeks of Vista, I had gone back to XP because my old P4 couldn't handle Vista too well. Well, got a new computer and decided to install Windows 7 Ultimate x64 after hearing many...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:17.
Twitter Facebook Google+