How do I fix BSOD,give advice

Hi adnanarif.

Download and install AMD Catalyst 14.9 from here: Mobile

Report us for any further BSOD after doing it.

So the driver update did not work. That means it is not only the driver that is causing the display failure. The issue is a deeper one.

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.

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: Speccy - Publish Snapshot of your System Specs .

About fixing, I cannot fix an issue, but I can assist you to fix it, as far as I can.
__________________________________________________

Code:

BugCheck 119, {1, 138c, 1e5d, 1e5c}

*** 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+383d0 )

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

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

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 000000000000138c
Arg3: 0000000000001e5d
Arg4: 0000000000001e5c

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  6

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

DPC_STACK_BASE:  FFFFF88002F92FB0

LAST_CONTROL_TRANSFER:  from fffff880015e822f to fffff80002ed8640

STACK_TEXT:  
fffff880`02f8b558 fffff880`015e822f : 00000000`00000119 00000000`00000001 00000000`0000138c 00000000`00001e5d : nt!KeBugCheckEx
fffff880`02f8b560 fffff880`0693aeb9 : 00000000`00000000 00000000`0000138c 00000000`00000000 00000000`00001e5d : watchdog!WdLogEvent5+0x11b
fffff880`02f8b5b0 fffff880`0693b125 : fffffa80`03a54000 fffff880`02f8b6c0 fffff880`000011ac fffffa80`0399d620 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff880`02f8b5e0 fffff880`0693af76 : 00000000`0000138c ffffe85d`5905c17f fffffa80`03a2d000 fffffa80`02cb5400 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x19d
fffff880`02f8b630 fffff880`0684213f : fffffa80`02d6f480 fffff880`01907432 fffffa80`02827190 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`02f8b660 fffff880`06ebc3d0 : fffff800`0304ae80 00000000`00000180 fffff880`02f8b710 fffffa80`0281f000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`02f8b690 fffff800`0304ae80 : 00000000`00000180 fffff880`02f8b710 fffffa80`0281f000 fffffa80`01c97500 : atikmpag+0x383d0
fffff880`02f8b698 00000000`00000180 : fffff880`02f8b710 fffffa80`0281f000 fffffa80`01c97500 00000000`00000001 : nt!KiInitialPCR+0x180
fffff880`02f8b6a0 fffff880`02f8b710 : fffffa80`0281f000 fffffa80`01c97500 00000000`00000001 00000000`00000001 : 0x180
fffff880`02f8b6a8 fffffa80`0281f000 : fffffa80`01c97500 00000000`00000001 00000000`00000001 00000001`0000138c : 0xfffff880`02f8b710
fffff880`02f8b6b0 fffffa80`01c97500 : 00000000`00000001 00000000`00000001 00000001`0000138c 00000000`00000000 : 0xfffffa80`0281f000
fffff880`02f8b6b8 00000000`00000001 : 00000000`00000001 00000001`0000138c 00000000`00000000 fffff880`01601816 : 0xfffffa80`01c97500
fffff880`02f8b6c0 00000000`00000001 : 00000001`0000138c 00000000`00000000 fffff880`01601816 00000000`00000001 : 0x1
fffff880`02f8b6c8 00000001`0000138c : 00000000`00000000 fffff880`01601816 00000000`00000001 00000000`00000000 : 0x1
fffff880`02f8b6d0 00000000`00000000 : fffff880`01601816 00000000`00000001 00000000`00000000 00000000`00000000 : 0x00000001`0000138c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmpag+383d0
fffff880`06ebc3d0 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  atikmpag+383d0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5417612a

FAILURE_BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+383d0

BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+383d0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x119_1_driver_reported_invalid_fence_id_atikmpag+383d0

FAILURE_ID_HASH:  {90d2aea6-4390-0293-f7e7-f2c2514653f4}

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

2: kd> lmvm atikmpag
start             end                 module name
fffff880`06e84000 fffff880`06f16000   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

I must barge in.

Either you temp reading are wrong or you are running very very hot.
A motherboard at 87C is very hot. I would suggest you check all cooling fans and vents to make sure they are working properly.
If those temps are correct you will destroy your mother board and more while testing.