Multiple BSODs while playing Hearthstone, error 0xa0000001

[Bassintag]

Hello,
I've experienced multiple BSODs while playing hearthstone, I was first thinking that updating all my drivers should fix it but it keep crashing.
I've linked the 3 latest minidump along with the dxdiag file.
Tell me if you need any other info.
Thanks a lot for the help.

Edit: Sorry, I'm new to the forums, forgot to upload the SF Diag file

 

[Bassintag]

Bump

 

[Arc]

[COLOR=Red]BugCheck A0000001[/COLOR], {5, 0, 0, 0}

Probably caused by : atikmdag.sys ( atikmdag+28ece )

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

It is a bugcheck inherent in AMD/ATI display environment.

At first we need to see the situation with another version of the display driver applied.

Uninstall your installed latest version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

Then install version 13.9 WHQL only (it is a good stable one).

• Previous AMD Catalyst? Display Drivers

Let us know the situation.

 

[Bassintag]

Thanks for the reply, just finished doing what you told me, I'll try to play the game for a bit and I'll come back to you with the results. Anyway thanks for the help!

 

[Arc]

Yes, you need to try to recreate the BSOD by doing the identical jobs.

 

[Bassintag]

I have been playing for 2 hours without any problem, I can't tell if it is fixed since the crashes happens randomly but it's looking good
Thanks a lot!

 

[Arc]

Wait and observe for some more time, say two or three days. Then let us know the situation.

 

[Bassintag]

Hello, it's me again, sorry to bother you but after playing for almost 2 weeks without any issues the crash happened again, I'm linking the SF Diag report.
The crash happened at the exact same time I played a minion and I was also listening to music on youtube, not sure if that matters but better tell you everything I know.

 

[Arc]

..........
*** 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 A0000001, {5, 0, 0, 0}

Probably caused by : atikmdag.sys ( atikmdag+258de )

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

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

Unknown bugcheck code (a0000001)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000005
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA0000001

PROCESS_NAME:  System

CURRENT_IRQL:  9

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF88003322FB0

LAST_CONTROL_TRANSFER:  from fffff8800f4ee8de to fffff8000347abc0

STACK_TEXT:  
fffff880`0331b808 fffff880`0f4ee8de : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0331b810 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x258de
fffff880`0331b818 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xa0000001
fffff880`0331b820 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+258de
fffff880`0f4ee8de ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  atikmdag+258de

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52540dc7

FAILURE_BUCKET_ID:  X64_0xA0000001_atikmdag+258de

BUCKET_ID:  X64_0xA0000001_atikmdag+258de

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa0000001_atikmdag+258de

FAILURE_ID_HASH:  {c8bc73bc-9f7f-7e8b-8b23-87c76577ca7a}

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

1: kd> lmvm atikmdag
start             end                 module name
fffff880`0f4c9000 fffff880`10112000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Tue Oct 08 19:21:03 2013 (52540DC7)
    CheckSum:         00BFB253
    ImageSize:        00C49000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The same issue, even with the most stable version of AMD display driver that I am aware of.

This issue is inherent with AMD display environment; the driver or the GPU.

When the issue continues irrespective of the driver version installed, it is the GPU that is throwing the issue. And it is better to replace the GPU.

But if you want, you may consult with AMD about this issue, too.

Lately I am seeing that a great number of AMD users are suffering from this very issue.

 

[Bassintag]

Ok thanks for the quick reply, one last question, could it be linked with the fact that I have two monitors which don't have the same size (one is 1920*1080 and the other one is 1440*900) ?

 

[Arc]

Apparently not.

 

[Bassintag]

So I contacted the AMD support and they told me that it was an issue with the game because it wasn't optimized for amd GPU or something like that (basically they didn't know and said it was because of the game devs). Does that mean I'll have to buy a new GPU ? (which really sucks since I'm 14 and I don't have that much money) Or is there another solution ?

 

[Arc]

Trust on them for the time being, till the BSOD happens again outside of the game.

You need to not play the game in the mean time. Apparently there is no other solution.

What do you think, is it bad as a plan?

 

[Bassintag]

I guess I have no other choice, too sad I can't play that game anymore I was getting pretty good ranking and wanted to start doing tournaments. Also I never got a BSOD in any other game so I don't think the GPU has a problem.
Anyway I'd like to thank you a lot for all the help you provided, I really appreciate it!

I'll probably get money for my birthday in november, I'll try to see If I can buy a decent Nvidia GPU then.

 

[Arc]

I'll probably get money for my birthday in november, I'll try to see If I can buy a decent Nvidia GPU then.

All the best.

 

[Bassintag]

The only thing that I don't get is why does that crash only happens to some people and not everyone who owns a amd GPU? For example my little brother has the same PC and an amd GPU but he can play the game just fine.
(Sorry for asking that many questions, I know it's anoying but I'd really like to understand how that stuff works)

 

[Arc]

The 0xA0000001 BSOD happens only to AMD users; but not necessarily to everybody of them.

Even some essentially identical computers work differently, and response differently. The way of usage and a bit of luck, that makes the difference.

 

[Bassintag]

Ok thanks for answering, I guess I just wasn't lucky enough then :/

 

[Bassintag]

Sorry, it's me again, after looking up on the internet about that bsod I found out that a lot of people are having the same issue with different games (and non-gaming related softwares) and I found that post on guru3d: FIX BSOD ATI Blue screen on atikmdag.sys solved fix - Guru3D.com Forums
Do you think that could fix the issue? I didn't want to try it right away because I don't want to break anything.

 

[Arc]

It may not fix your issue, but it should not break anything.

The maximum loss it may cause is to corrupt the installed display driver. If so, you may download the driver again and install it.