Share via

atikmdag.sys BSOD issues!

Anonymous
2011-03-20T17:52:48+00:00

Hello, as of late I have begun to have some crashing issues involving my PC...

It started when I would do a Full-System Scan with my PC with Trend Micro Antivirus, once I started the scan, I walked away from my PC todo other tasks thus causing my monitor to go into power save mode after a short while. Once I returned, I noticed that my PC was at the login screen and once after logging on to my account I realized that my computer recovered from a BSOD and logged the event as a dump file. Naturally, I tried booting into safe mode and did a full system scan through trend and found nothing.... A couple of days later I did a full scan with Malwarebytes' Antimalware and again, walked away from my PC todo other tasks and returned to the same fate of a restarted PC at the login screen only to get the "Windows has recovered from an error" box after logging on, again I booted the PC into safe mode and did a full scan with Malwarebytes' and again found nothing. Once that was completed, I decided to investigate the two dump files created from the BSODs using Microsoft's Debugging application from the Windows SDK package to find out that in both files, the file "atikmdag.sys" was the culprit of the error and it was ultimately caused by the desktop windows manager "dwm.exe" here are the dump files from each...

(From the Trend Antivirus scan crash)

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88004899817, fffff8800c05d900, 0}

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

Followup: MachineOwner


3: 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: fffff88004899817, Address of the instruction which caused the bugcheck

Arg3: fffff8800c05d900, 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+90817

fffff880`04899817 8b4820          mov     ecx,dword ptr [rax+20h]

CONTEXT:  fffff8800c05d900 -- (.cxr 0xfffff8800c05d900)

rax=0000000000000000 rbx=fffffa8006d47330 rcx=fffffa80087501f0

rdx=0000000000000000 rsi=0000000000000015 rdi=fffffa8009124010

rip=fffff88004899817 rsp=fffff8800c05e2d0 rbp=fffffa80087501f0

 r8=0000000000000015  r9=fffff88004c5b970 r10=0000000000000000

r11=fffff8800c05e420 r12=0000000000000000 r13=fffffa80087db860

r14=0000000000000001 r15=0000000000000000

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+0x90817:

fffff88004899817 8b4820          mov     ecx,dword ptr [rax+20h] ds:002b:0000000000000020=????????

Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88004899817

STACK_TEXT: 

fffff8800c05e2d0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : atikmdag+0x90817

FOLLOWUP_IP:

atikmdag+90817

fffff880`04899817 8b4820          mov     ecx,dword ptr [rax+20h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+90817

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cef1f94

STACK_COMMAND:  .cxr 0xfffff8800c05d900 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+90817

BUCKET_ID:  X64_0x3B_atikmdag+90817

Followup: MachineOwner


(and this is from the Malwarebytes' scan crash)

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88004988817, fffff8800cf9b900, 0}

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

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: fffff88004988817, Address of the instruction which caused the bugcheck

Arg3: fffff8800cf9b900, 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+90817

fffff880`04988817 8b4820          mov     ecx,dword ptr [rax+20h]

CONTEXT:  fffff8800cf9b900 -- (.cxr 0xfffff8800cf9b900)

rax=0000000000000000 rbx=fffffa8006e254c0 rcx=fffffa80086aa1f0

rdx=0000000000000000 rsi=0000000000000015 rdi=fffffa80086ba340

rip=fffff88004988817 rsp=fffff8800cf9c2d0 rbp=fffffa80086aa1f0

 r8=0000000000000015  r9=fffff88004d4a970 r10=0000000000000000

r11=fffff8800cf9c420 r12=0000000000000000 r13=fffffa8005c33d00

r14=0000000000000001 r15=0000000000000000

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+0x90817:

fffff88004988817 8b4820          mov     ecx,dword ptr [rax+20h] ds:002b:0000000000000020=????????

Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88004988817

STACK_TEXT: 

fffff8800cf9c2d0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : atikmdag+0x90817

FOLLOWUP_IP:

atikmdag+90817

fffff880`04988817 8b4820          mov     ecx,dword ptr [rax+20h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+90817

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cef1f94

STACK_COMMAND:  .cxr 0xfffff8800cf9b900 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+90817

BUCKET_ID:  X64_0x3B_atikmdag+90817

Followup: MachineOwner


What can I do to try to avoid this problem in the future? Please help!

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2011-03-20T18:11:50+00:00

Hi,

atikmdag.sys is the ATI driver. The 0xc0000005 as 1st parameter also means that the

MEMORY might be involved.

Update the ATI drivers or reinstall the present ones. Check with ATI Support, their on-line

documentation and drivers, and ask in the forums for known issues.

Check with ATI Drivers (manually), Support and their forums as their could be known issues.

Get the Catalyst Drivers herehttp://game.amd.com/us-en/drivers_catalyst.aspx

ATI - Forums

http://forums.amd.com/game/categories.cfm?catid=260&forumid=11

ATI - Support and Drivers

http://support.amd.com/us/Pages/AMDSupportHub.aspx

=================================================================

Try removing and reseating all cards, memory, and cables (both ends when possible) - actually

remove and replace - do not just snug (on a PC) and clean out the dust bunnies and vents. On

a laptop about all that can be done is reseat the memory and clean the vents.

3b is usually a graphic's driver (display adapter/video driver), other possibilities includebut are not limited to antivirus/antispyware/security programs and even memory (mapping).BCCode: 3b    0x0000003bCause

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

BCCode: 3b    0x0000003b  <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/SYSTEM-SERVICE-EXCEPTION-0x0000003B-\*1074.html

============================================================

Vista and Windows 7 love updated drivers so here is how to update the major ones.

**References to Vista also apply to Windows 7.**This is my generic how to for proper driver updates : (update video/display driver and BIOS)

This utility makes it easy to see which versions are loaded :

DriverView - Free - utility displays the list of all device drivers currently loaded on your system.

For each driver in the list, additional useful information is displayed: load address of the driver,

description, version, product name, company that created the driver, and more.

http://www.nirsoft.net/utils/driverview.html

For Drivers check System Maker as fallbacks and Device Maker's which are the most current.

Control Panel - Device Manager - Display Adapter - write down the make and complete model

of your video adapter - double click - Driver's tab - write down the version info. Now click UPdate

Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click -

Uninstall - REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party

with their own software and drivers and any other major device drivers you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device

Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for

BIOS, Chipset and software updates at System Maker's site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after

each installation.

Always check in Device Manager - Drivers tab to be sure the version you are installing actually

shows up. This is because some drivers rollback before the latest is installed (sound drivers

particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as

needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check

manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.

http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

Installing and updating drivers in Windows 7 (updating drivers manually using the methods above

is preferred to ensure the latest drivers from System maker and Device makers are found)

http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

If you update drivers manually then it is a good idea to disable Driver Installations in Windows

Updates, this leaves Windows Updates ON however it will not install drivers which will usually be

older and cause issues. If Updates suggests a new driver then HIDE it (Right Click on it) and then

go look for new ones manually if you wish.

How To Disable Automatic Driver Installation In Windows Vista - Drivers

http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/

http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx


Memory tests do not catch all errors such as mismatched memory (possible even for sticks

that appear to be identical) and when faster memory is placed in system behind slower memory.

So it is best to also swap sticks in and out to check for those even if all memory tests fail to show

a problem.

To test RAM check here - let it run 4+ hours or so.  <-- best methodwww.memtest.org

For the Windows Memory Diagnostic Tool.

Start - type in Search box ->  Memory - find Memory Diagnostics tool at top of list - Right Click -

RUN AS ADMIN follow the instructions

Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista Memory Diagnostic

Tool

http://www.shivaranjan.com/2007/11/01/windows-vista-how-to-scan-test-your-ram-or-memory-with-windows-vista-memory-diagnostic-tool/

How to Run the Memory Diagnostics Tool in Windows 7

http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

Test Your Computer’s Memory Using Windows Vista Memory Diagnostic Tool

http://www.howtogeek.com/howto/windows-vista/test-your-computers-memory-using-windows-vista-memory-diagnostic-tool/

Hope this helps.

Was this answer helpful?

0 comments No comments

0 additional answers

Sort by: Most helpful