BSOD issue

No problem. My English is poor too, I am an Indian.

You are right that the BSODs were caused by some display malfunction. But all them took place with 14.12 Omega driver installed, which is problematic to cards below R7/R9 etc (as far as I have seen in a number of threads). So let us see the situation with another version of the display driver installed?

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.

• Drivers - Clean Left over Files after Uninstalling

Then install version 14.9 WHQL only.

• Download AMD Catalyst 14.9 WHQL Driver

Let us know how it goes. We may need to do some further troubleshooting depending on the situation.
____________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800532f130, fffff88003e42848, 0, 2}

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+b848 )

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

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

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

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


FAULTING_IP: 
atikmpag+b848
fffff880`03e42848 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`023d4888 fffff880`10333134 : 00000000`00000116 fffffa80`0532f130 fffff880`03e42848 00000000`00000000 : nt!KeBugCheckEx
fffff880`023d4890 fffff880`10332e3e : fffff880`03e42848 fffffa80`0532f130 fffffa80`04a915f0 fffffa80`04670010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`023d48d0 fffff880`0f00ff13 : fffffa80`0532f130 00000000`00000000 fffffa80`04a915f0 fffffa80`04670010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`023d4900 fffff880`0f039cf1 : 00000000`ffffffff 00000000`00000581 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`023d49e0 fffff880`0f038437 : 00000000`00000102 00000000`00000001 00000000`00000581 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`023d4a10 fffff880`0f00b2d2 : ffffffff`ff676980 fffffa80`04670010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`023d4ab0 fffff880`0f037ff6 : 00000000`00000000 fffffa80`04d87860 00000000`00000080 fffffa80`04670010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`023d4bc0 fffff800`031270ca : 00000000`fffffc32 fffffa80`04b6a410 fffffa80`03ce29e0 fffffa80`04b6a410 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`023d4c00 fffff800`02e7bbe6 : fffff880`009e9180 fffffa80`04b6a410 fffff880`009f3fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`023d4c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+b848
fffff880`03e42848 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+b848

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  546e9eb6

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

2: kd> lmvm atikmpag
start             end                 module name
fffff880`03e37000 fffff880`03ecd000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Nov 21 07:38:54 2014 (546E9EB6)
    CheckSum:         00093077
    ImageSize:        00096000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Pierrax said:

Hmmm, that's better but I still get a BSOD after an error message "AMD driver not responding...".

Not a healthy situation at all. If this issue continues with multiple versions of the display driver, then it is not a driver issue, but the hardware is gradually failing to work.

Try one other driver version, as a test basis. I would suggest you an old one, 13.9 WHQL, because it was very stable at its own.

• Previous AMD Catalyst? Display Drivers

See how it goes. If the issue recurs, nothing, no guide will help you for long. Only a new card will be able to solve the issue in that case.