BSOD with atikmdag.sys

Hello,
I got blue screen quite sometimes in the past.

But now i got it this blue screen of atikmdag.sys every time when starting the windows. Now I can only access windows through safe mode and in normal mode by disabled the graphic cards.


I don't know if its because of my hardware or it just the driver version is too old. I did try to uninstall the driver and downloaded a new version from AMD website but it didn't work for me. I even reinstalled windows but it also no good as well.

Is there anything I can do to fix this problem. Please give me some advice.

Thank you and sorry for my bad English since it's not my first language.

Hello and welcome Blaster mate first and foremost some systems specs please very hard to look for problems if we do not know what you have in place. System Info - See Your System Specs

Now I cannot open the BSOD files (the blue screen ones) so please try reloading them.

The one issue you mentioned atikmdag.sys is usually dealt with uninstalling the Catalyst Control Centre (CCC) and running the GPU with the driver direct from AMD. If you have tried it please try it gain bit again without knowing just what you have it is difficult to let you know what to try.

Sorry for late reply and thanks for the specs unfortunately I am having real issues with my broadband right now so I have to limit my reply in short form.

Now the dump files did you use these Dump Files - Configure Windows to Create on BSOD &
Blue Screen of Death (BSOD) Posting Instructions ??

The GPU is proving to be quite difficult to find so am going to keep trying tomorrow at home.

Sorry Blaster the problem was my end as my debugger was at fault.

Now the driver that I can find for the 6620 is this AMD Radeon(TM) HD 6620G and the driver for the AMD Radeon 6630M Graphic looks to me to be identical
Desktop try reinstalling this instead of the CCC and again sorry for the muck up with my own machine.

I am saying this because now I can see the dump file this is what would appear to be the problem

Code:

FAULTING_IP: 
atikmpag+cd78
fffff880`02c55d78 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`06f159c8 fffff880`02d4f000 : 00000000`00000116 fffffa80`05eda010 fffff880`02c55d78 00000000`00000000 : nt!KeBugCheckEx
fffff880`06f159d0 fffff880`02d4ed0a : fffff880`02c55d78 fffffa80`05eda010 fffffa80`08214ab0 fffffa80`05b24410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06f15a10 fffff880`125b5f07 : fffffa80`05eda010 00000000`00000000 fffffa80`08214ab0 fffffa80`05b24410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06f15a40 fffff880`125dfb75 : 00000000`ffffffff 00000000`00003167 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06f15b20 fffff880`125de2bb : 00000000`00000102 00000000`00000006 00000000`00003167 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06f15b50 fffff880`125b12c6 : ffffffff`ff676980 fffffa80`05b24410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06f15bf0 fffff880`125dde7a : 00000000`00000000 fffffa80`08368900 00000000`00000080 fffffa80`05b24410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06f15d00 fffff800`02f68cce : 00000000`fffffc32 fffffa80`07dfeb60 fffffa80`05aaa040 fffffa80`07dfeb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06f15d40 fffff800`02cbcfe6 : fffff800`02e3de80 fffffa80`07dfeb60 fffff800`02e4bcc0 fffff880`01223384 : nt!PspSystemThreadStartup+0x5a
fffff880`06f15d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+cd78
fffff880`02c55d78 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+cd78

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  564c20cc

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Now just as a by the by your RAM is not that large really for these days at least and if you are playing full on games. Can you try fitting say at least 8GB? RAM 12GB or 16GB would be much better but it does depend on the budget I know.

My other thought is whether the RAM is up to it and to see if it is ok then you need to run this RAM - Test with Memtest86+ but you must run it for at least 8 passes anything less is a waste of time. However if errors pop up fairly straight away you can stop the test. This is the only memtest we recommend the Windows feature isn't worth a breadcrumb.

It does take a fairly long time to run but it will eliminate bad RAM as an issue - overnight is good but as I said if the errors come quickly it can be stopped and then it is down to finding the offending stick - or slot as even they can go bad.

I suppose you have also tried reseating the sticks??