bsod because of atikmdag and other gfx driver things

[qoosghoune]

Hi all,

I was having BSODs a few times in a week (sometimes a few times in a day), I was aware that they were because of my graphics card drivers, I searched for a solution on the internet for some time, but nothing worked. (Using old gfx drivers etc.)

Interestingly, I had realised they were always happening when Firefox was open, so I started using Chrome; and they had ceased to happen.

Later I had to change my motherboard and cpu; clean Windows installation... And started using Firefox again, hoping for it won't happen again...

But it did when I was playing game and Firefox was also open... Again...

So here are my info files...

 

[Arc]

Uninstall the installed display driver using Display Driver Uninstaller. Then install the CCC 14.4 WHQL only.

When done, stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.
___________________________________________________

BugCheck 7F, {8, 80050033, 406f8, fffff8800f7ef94a}

*** 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+17594a )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff8800f7ef94a

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  DragonAge2.exe

CURRENT_IRQL:  0

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

LAST_CONTROL_TRANSFER:  from fffff800030d8e69 to fffff800030d98c0

STACK_TEXT:  
fffff800`00ba2d28 fffff800`030d8e69 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff800`00ba2d30 fffff800`030d7332 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2e70 fffff880`0f7ef94a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`060eed18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x17594a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+17594a
fffff880`0f7ef94a 488b6c2458      mov     rbp,qword ptr [rsp+58h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+17594a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  546ea3c3

FAILURE_BUCKET_ID:  X64_0x7f_8_atikmdag+17594a

BUCKET_ID:  X64_0x7f_8_atikmdag+17594a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7f_8_atikmdag+17594a

FAILURE_ID_HASH:  {139f76c7-b39c-e830-616c-c144da8f8aeb}

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

0: kd> lmvm atikmdag
start             end                 module name
fffff880`0f67a000 fffff880`108fe000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Nov 21 08:00:27 2014 (546EA3C3)
    CheckSum:         0121F198
    ImageSize:        01284000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[qoosghoune]

I uninstalled the gfx drivers and installed 14.4 one as described.

So far no other bsod occured, but I'm not using firefox. (I don't know, it doesn't make sense, but it's a weird coincidence maybe.)

Ran furmark but couldn't manage to take a screenshot while fullscreen (it results a black screen), so I ran it windowed. By the way, as you see, there was no information at topside; am I missing a setting?

Didn't ran it for too long, closed when temp went to 70 degrees.

I'd done furmark tests before; there were no crashes or bsod's...

 

[Arc]

You should have tried furmark for a bit longer .... either for 15 minutes or till it temps to high like 90°C.

But OK, let us know for any further BSOD.

 

[qoosghoune]

Another BSOD happened last night. I was playing Civilization 5 and Firefox was open.

This time I saw dxgmms1.sys

 

[Arc]

It is still the display failure.

fffff880`043aa5a8  fffff880`0f650c1fUnable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys[/COLOR]
 atikmdag+0x16c1f

And it is another version of the display driver that which was originally installed there.

    Image name: atikmpag.sys
[COLOR=Red]    Timestamp:        Fri Apr 18 06:37:07 2014[/COLOR] (53507ABB)

At this point we can say that the display caused BSOD is occurring irrespective of the display driver installed. We have seen that 14.12 and 14.4, both the drivers are victim of it. So, the issue is not driver caused, and its root is somewhere deeper.

Now check three things and let us know.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.

How To Clear CMOS (Reset BIOS)
​

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage and/or gaming. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.

eXtreme Power Supply Calculator - The only power supply calculator trusted by PSU manufacturers and computer enthusiasts
​

Also let us know the wattage of the installed PSU.

A lot will depend on the results.

 

[qoosghoune]

I don't overclock... Never did...

I had checked for heat before, didn't see any problems, but I will keep track of it again while playing games...

I have a 650 w psu... (High Power Absolute 650W 80+ Plus)

 

[Arc]

Temps are OK, and 650 watts should be enough for a PSU, apparently.

If you are sure that everything stated in post #6 is not relevant for you (I stated it earlier that things will depend on it a lot), then you need to do one more thing, as we are minimizing the possible causes one by one.

Borrow another card from friends or family. Apply it there. See how it goes with another card.