AMD MSI HD7950 BSOD when streaming videos

I have been getting BSOD's when streaming videos wheter it be sivlerlgiht or flash, however it never happens with amazon instant video or netflix it only ever happens with streaming sites like xfinity or youtube. I have been searching the forums on various sites for a fix for months and havent fixed it. When it happens it usually only happens once and then doesnt happen for weeks or even months. I have tried updated and rolling back the videocard driver numerous times.

I have attached a dump file that I anaylzed with windows debug, although not really sure if it will help.

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*http://msdl.microsoft.com/download/symbols

Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`2fc72000 PsLoadedModuleList = 0xfffff802`2ff3c2d0
Debug session time: Mon Jun 23 20:30:42.412 2014 (UTC - 5:00)
System Uptime: 0 days 14:47:56.477
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols

Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff801f1199dbb, ffffd000a019e128, ffffd000a019d930}

*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmdag.sys ( atikmdag+c7dbb )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801f1199dbb, The address that the exception occurred at
Arg3: ffffd000a019e128, Exception Record Address
Arg4: ffffd000a019d930, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
atikmdag+c7dbb
fffff801`f1199dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h]

EXCEPTION_RECORD: ffffd000a019e128 -- (.exr 0xffffd000a019e128)
ExceptionAddress: fffff801f1199dbb (atikmdag+0x00000000000c7dbb)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000006a8
Attempt to read from address 00000000000006a8

CONTEXT: ffffd000a019d930 -- (.cxr 0xffffd000a019d930;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=00000000001e0000 rdi=0000000000000002
rip=fffff801f1199dbb rsp=ffffd000a019e360 rbp=ffffe000179ed060
r8=0000000000000002 r9=000000f423330000 r10=0000000000000000
r11=fffff801f0825587 r12=ffffe0001b969800 r13=ffffe0001af2d580
r14=ffffe0001e4d7740 r15=fffff801f10d2000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmdag+0xc7dbb:
fffff801`f1199dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=00000000001e0000 rdi=0000000000000002
rip=fffff801f1199dbb rsp=ffffd000a019e360 rbp=ffffe000179ed060
r8=0000000000000002 r9=000000f423330000 r10=0000000000000000
r11=fffff801f0825587 r12=ffffe0001b969800 r13=ffffe0001af2d580
r14=ffffe0001e4d7740 r15=fffff801f10d2000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmdag+0xc7dbb:
fffff801`f1199dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Resetting default scope

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000000006a8

READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
00000000000006a8

FOLLOWUP_IP:
atikmdag+c7dbb
fffff801`f1199dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h]

BUGCHECK_STR: AV

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER: from fffff801f11faf6f to fffff801f1199dbb

STACK_TEXT:
ffffd000`a019e360 fffff801`f11faf6f : 00000000`00000001 ffffe000`1828ae40 000000ff`03cc5000 00000000`00000120 : atikmdag+0xc7dbb
ffffd000`a019e390 fffff801`f10e5703 : 00000000`00000001 ffffe000`179ed060 fffff801`f10d2000 000000f4`23330000 : atikmdag+0x128f6f
ffffd000`a019e3e0 fffff801`f0ef85b5 : ffffffff`ffffffff 00000000`00000003 ffffd000`a019e650 ffffd000`a019e7c9 : atikmdag+0x13703
ffffd000`a019e540 fffff801`f0cb9b91 : 00000000`00000000 ffffc001`668fc330 00000000`c0000001 00000000`00000001 : atikmpag+0xb5b5
ffffd000`a019e5d0 fffff801`f0842ebe : ffffc001`668fc330 ffffd000`a019e700 00000000`00000000 ffffe000`17afa000 : dxgkrnl!ADAPTER_RENDER:diBuildPagingBuffer+0x4d
ffffd000`a019e600 fffff801`f0842fbf : 00000000`00000000 ffffc001`668fc330 ffffe000`17afa000 00000000`00000001 : dxgmms1!VIDMM_GLOBAL:iscardAllocationInternal+0xbe
ffffd000`a019e7a0 fffff801`f0843158 : 00000000`00000000 ffffc001`668fc330 ffffe000`1b984800 ffffe000`183ac300 : dxgmms1!VIDMM_GLOBAL:iscardAllocation+0x37
ffffd000`a019e7d0 fffff801`f084d942 : 00000000`00000001 00000000`00000001 ffffe000`1cf7c9a0 ffffc001`668fc330 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x118
ffffd000`a019e990 fffff801`f0846920 : ffffe000`1c695640 00000000`00000000 ffffd000`9e300180 00000000`00000000 : dxgmms1!VIDMM_GLOBAL:rocessDeferredCommand+0xda
ffffd000`a019eaf0 fffff801`f0846884 : ffffe000`1ae5b000 ffffe000`00000000 00000000`0000000f 00000000`00000000 : dxgmms1!VIDMM_GLOBAL:rocessTerminationCommand+0x44
ffffd000`a019eb40 fffff801`f0857f85 : ffffe000`2091f6c0 ffffe000`1ae5b000 ffffe000`2091f6c0 ffffe000`00000000 : dxgmms1!VidSchiSubmitDeviceCommand+0x34
ffffd000`a019eb70 fffff801`f0857d1d : ffffe000`1ae5b000 00000000`00000080 ffffe000`1b984800 ffffe000`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x265
ffffd000`a019ebc0 fffff802`2fd41794 : ffffd000`a2c0c2c0 ffffe000`1b984800 ffffd000`a019ec90 fffff802`2fdc937d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd000`a019ec00 fffff802`2fdcc5c6 : ffffd000`a2c00180 ffffe000`1b984800 ffffd000`a2c0c2c0 ffffc001`573f9b90 : nt!PspSystemThreadStartup+0x58
ffffd000`a019ec60 00000000`00000000 : ffffd000`a019f000 ffffd000`a0199000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+c7dbb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53508a3c

STACK_COMMAND: .cxr 0xffffd000a019d930 ; kb

FAILURE_BUCKET_ID: AV_atikmdag+c7dbb

BUCKET_ID: AV_atikmdag+c7dbb

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_atikmdag+c7dbb

FAILURE_ID_HASH: {0471d6b8-06e1-47c6-22ba-995dd0010efa}

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