BSOD youtube or chrome use, error 0x00000116, atikmpag.sys

The zip you uploaded does not contain any crash dump.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

Display failure. The system is not detecting the ATI graphics and runs on Standard VGA Graphics Adapter. I think the GPU shuld be ATI Mobility Radeon HD 5730?

Code:

---------------
Display Devices
---------------
          Card name: Standard VGA Graphics Adapter
       Manufacturer: (Standard display types)
          Chip type: ATI ATOMBIOS
           DAC type: 8 bit
         Device Key: Enum\PCI\VEN_1002&DEV_68C0&SUBSYS_397817AA&REV_00

Code:

Name    Standard VGA Graphics Adapter
Driver    c:\windows\system32\drivers\vgapnp.sys (6.1.7600.16385, 28.50 KB (29,184 bytes), 7/13/2009 7:38 PM)

As the crash dupms are reporting to be 14.12 Omega display driver installed and it is known to be problematic with a good lot of cards, better you try another previous driver.

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

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

Though it is not supposed to be a memory issue (as per the bugcheck code), the memtest screen is not very known to me. I will request essenbe to comment on it.
______________________________________

Code:

....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80070a64e0, fffff88004234848, 0, 2}

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80070a64e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004234848, 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`04234848 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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:  
fffff880`061ea888 fffff880`0431c134 : 00000000`00000116 fffffa80`070a64e0 fffff880`04234848 00000000`00000000 : nt!KeBugCheckEx
fffff880`061ea890 fffff880`0431be3e : fffff880`04234848 fffffa80`070a64e0 fffffa80`07074010 fffffa80`09673410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`061ea8d0 fffff880`10371f13 : fffffa80`070a64e0 00000000`00000000 fffffa80`07074010 fffffa80`09673410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`061ea900 fffff880`1039bcf1 : 00000000`ffffffff 00000000`00004758 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`061ea9e0 fffff880`1039a437 : 00000000`00000102 00000000`00000000 00000000`00004758 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`061eaa10 fffff880`1036d2d2 : ffffffff`ff676980 fffffa80`09673410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`061eaab0 fffff880`10399ff6 : 00000000`00000000 fffffa80`07074010 00000000`00000080 fffffa80`09673410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`061eabc0 fffff800`02f130ca : 00000000`fffffc32 fffffa80`09ad2b50 fffffa80`06b80890 fffffa80`09ad2b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`061eac00 fffff800`02c67be6 : fffff800`02df0e80 fffffa80`09ad2b50 fffff800`02dfecc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`061eac40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+b848
fffff880`04234848 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
---------

6: kd> lmvm atikmpag
start             end                 module name
fffff880`04229000 fffff880`042bf000   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

Please run it this way. You are running memtest86 not memtest86+ ( yes, I know, but they chose the names) The download links are in the middle of the page. Please use V4.20

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

Following are observation,
While running FurMark first time system withing second bumped into BSOD.(DM Log Attached)

after reboot did ran FurMark until display driver did gave up.

I would suggest you to replace the graphics card. It is failing to do its job and hence the BSODs are.

Arc is correct, that's what Furmark is for. Your card is at least 4 generations old, if not older. Graphics cards are either the driver, the card, the Motherboard or the PSU. In your case it appears to be the card or the board. Almost all evidence points to the card.