BSOD playing Archeage, Error 4101?

[Bay]

Computer freezes every second until I close the program. It happens while:
Browsing the some sites, especially facebook - with any browser
using WMP to watch movies - from any source
Playing Games like Archeage
__________________________________

This is what i've done so far to try to fix:
___________________________________
1: Reinstalled Driver with the following steps:
Delete existing drivers from your computer:
In computer control panel select 'uninstall a program'
For computers with AMD processors:
Select AMD install manager and 'custom uninstall' the graphics drivers and CCC only.
Reboot into 'safe mode'
In safe mode run Guru 3D's DDU
Reboot
Install the new driver suite.
____________________________________________
2: Physically reset the graphics card on MB.
____________________________________________
3: Tried using previous driver versions
_____________________________________________
This is the error log from event viewer:
- System
- Provider
[ Name] Display

- EventID 4101
[ Qualifiers] 0

Level 3

Task 0

Keywords 0x80000000000000

- TimeCreated
[ SystemTime] 2014-10-10T20:08:11.000000000Z

EventRecordID 21135

Channel System

Computer PC

Security
- EventData
amdkmdap


(I've also attacked the BSOD .dmp file)

___________________________


Other things to note:
AMD FX-8320 @ 3.5
Ram: 8 gb
AMD Radeon R7 280 (i think its 280, i know its 200 series)
windows 7 ultimate 64bit


My computer system is new, not overclocked, all default settings, all windows updates done before driver installed, there is plenty of power (650w PS), not overheating (usually 40c - 45c)


Any help is greatly appreciated.

 

[Arc]

Hi Bay.

A stray crash dump is not enough. 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
________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8009804010, fffff88003c0b038, 0, d}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+b038 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009804010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003c0b038, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+b038
fffff880`03c0b038 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.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`045fd618 fffff880`1211a134 : 00000000`00000116 fffffa80`09804010 fffff880`03c0b038 00000000`00000000 : nt!KeBugCheckEx
fffff880`045fd620 fffff880`12119ebb : fffff880`03c0b038 fffffa80`09804010 fffffa80`09cbc010 fffffa80`094da010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`045fd660 fffff880`121c1f13 : fffffa80`09804010 00000000`00000000 fffffa80`09cbc010 fffffa80`094da010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`045fd690 fffff880`121efed6 : 00000000`ffffffff 00000000`000078a6 fffff880`045fd7f0 fffffa80`094da010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`045fd770 fffff880`121ebe21 : fffffa80`097a0000 ffffffff`ff676980 fffffa80`07aac570 fffff880`121d09d3 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`045fd7b0 fffff880`121ebfd9 : fffffa80`097a0000 fffffa80`094da010 fffffa80`097a1900 00000000`00000000 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
fffff880`045fd8a0 fffff880`121eaeb8 : 00000000`0000001b 00000000`00008849 fffffa80`07aac570 fffffa80`094da010 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x171
fffff880`045fd9a0 fffff880`121ea514 : fffff800`00b96000 fffff880`121e9f00 fffffa80`00000000 fffffa80`00000120 : dxgmms1!VidSchiSubmitRenderCommand+0x920
fffff880`045fdb90 fffff880`121ea012 : 00000000`00000000 fffffa80`09cbc010 00000000`00000080 fffffa80`094da010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`045fdbc0 fffff800`02f6c73a : 00000000`fffffc32 fffffa80`094d3b50 fffffa80`06cde5f0 fffffa80`094d3b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`045fdc00 fffff800`02cc18e6 : fffff800`02e4be80 fffffa80`094d3b50 fffff800`02e59cc0 fffffa80`06d46410 : nt!PspSystemThreadStartup+0x5a
fffff880`045fdc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+b038
fffff880`03c0b038 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+b038

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5417612a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}

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

1: kd> lmvm atikmpag
start             end                 module name
fffff880`03c00000 fffff880`03c92000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Tue Sep 16 03:29:06 2014 (5417612A)
    CheckSum:         000964D0
    ImageSize:        00092000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Bay]

thank you much. Here is the .zip

 

[Arc]

That is a display/graphics related BSOD, not having any connection (other than a coincidence) with the game as you said. It is overall display failure. And it happened over a time, irrespective of the display driver version installed.

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.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. 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.
http://www.extreme.outervision.com/psucalculatorlite.jsp
Also let us know the wattage of the PSU.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.

 

[Bay]

My computer system is new, not overclocked, all default settings, all windows updates done before driver installed, there is plenty of power (650w PS), not overheating (usually 40c - 45c)

as previously posted.

 

[Arc]

My computer system is new, not overclocked, all default settings, all windows updates done before driver installed, there is plenty of power (650w PS), not overheating (usually 40c - 45c)

as previously posted.

Well, I am not saying that you are saying it wrong, but I would prefer to see documentation.

There must be something that is causing the BSOD. Our goal is to find out the source of the issue. And so documentation is needed.

 

[Bay]

Info as requested. The PSU is giving plenty of power to the computer. I have 650w and the site said 411 was efficient.

 

[Arc]

If ....

• the PSU supplies plenty of power
• the computer is not hot
• stress test goes good
• the computer is not overclocked

and still it BSODs with bugcheck 0x116 irrespective of the display driver version installed, then one more thing can be said (though no such evidence is there in the crash dump) ... some games are causing graphics misbehavior.

Try to identify which game/games are causing the issue. Consult with the game developer .... they might have custom settings or patches which may work good with your computer.