BSOD Playing online games

[Kimirron]

Hi there.
First sorry for my bad English is not my native language.
I wear a long suffering blue screens while playing a very specific game, Dota 2.
Doing a little research I discovered that the BSOD is produced by the atikmdag.sys file.
I searched a lot but I have not found any kind of solution, I updated the graphics drivers and I've tried everything I've been seeing, but I have not managed to solve.
The BSOD occurs only playing Dota 2, any other game is fine.
I hope someone can help me.
Thank you very much for your attention.

 

[Arc]

Click on the button below ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[Kimirron]

Here you have it, I think I have gone well.

 

[Arc]

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

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

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

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

Uninstall your installed 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.

• Previous AMD Catalyst? Display Drivers

Let us know how the computer is running.

 

[Kimirron]

Bad news.

I followed the steps indicated and thanks to that I was able to play for several hours without any problem, even thought it was already solved, but a few minutes ago is back out the screenshot

 

[Arc]

but a few minutes ago is back out the screenshot

What does it mean?

 

[Kimirron]

I mean I have to jump back to the blue screen with the same error code as before.

 

[Arc]

Follow post #2 again.

 

[Kimirron]

Here you have it

 

[Arc]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

[COLOR=Red]Probably caused by : atikmdag.sys[/COLOR] ( atikmdag+258de )

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

0: 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:  dota.exe

CURRENT_IRQL:  b

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

LAST_CONTROL_TRANSFER:  from fffff8800f07c8de to fffff80002ed2bc0

STACK_TEXT:  
fffff880`08ef36f8 fffff880`0f07c8de : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`08ef3700 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x258de
fffff880`08ef3708 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02edc6f7 : 0xa0000001
fffff880`08ef3710 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff800`02edc6f7 00000000`00000000 : 0x5


STACK_COMMAND:  kb

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

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
---------

0: kd> lmvm atikmdag
start             end                 module name
fffff880`0f057000 fffff880`0fca0000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
[COLOR=Red]    Image name: atikmdag.sys
    Timestamp:        Tue Oct 08 19:21:03 2013[/COLOR] (52540DC7)
    CheckSum:         00BFB253
    ImageSize:        00C49000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

When it occurs with multiple versions of the display driver, then it is the GPU that is throwing the issue.

You need to replace it; at least as a test basis.