once haunted BSOD pc again haunted :(

It looks like you are having problems with the ati driver.

Let's wipe the current installation with this tool.
Phyxion.net - Driver Sweeper

and reinstall the latest version of your driver from a fresh download.
AMD Graphics Drivers & Software

Code:

KMODE_EXCEPTION_NOT_HANDLED (1e)
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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3837356334626561
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002ffd428 -- (.exr 0xfffff88002ffd428)
ExceptionAddress: fffff8800410cb3d (dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x000000000000007d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002ffd4d0 -- (.trap 0xfffff88002ffd4d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=f7fffa8004e6a700 rbx=0000000000000000 rcx=fffffa8004bec010
rdx=fffffa8004c19480 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800410cb3d rsp=fffff88002ffd660 rbp=fffffa8004bdf540
 r8=0000000000000002  r9=fffffa8005345038 r10=fffffa8004b817d0
r11=fffff88002ffda10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d:
fffff880`0410cb3d f0834018ff      lock add dword ptr [rax+18h],0FFFFFFFFh ds:9b58:f7fffa80`04e6a718=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a946be to fffff80002a9ccd0

STACK_TEXT:  
fffff880`02ffc508 fffff800`02a946be : 00000200`00020000 00010000`01000002 fffff880`02ffcc80 fffff800`02ac8890 : nt!KeBugCheck
fffff880`02ffc510 fffff800`02ac855d : fffff800`02ca3968 fffff800`02be0cbc fffff800`02a1d000 fffff880`02ffd428 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffc540 fffff800`02ac7335 : fffff800`02be40fc fffff880`02ffc5b8 fffff880`02ffd428 fffff800`02a1d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffc570 fffff800`02ad83b1 : fffff880`02ffd428 fffff880`02ffcc80 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x415
fffff880`02ffcc50 fffff800`02a9c382 : fffff880`02ffd428 fffffa80`04b859c0 fffff880`02ffd4d0 fffffa80`04c19480 : nt!KiDispatchException+0x135
fffff880`02ffd2f0 fffff800`02a9ac8a : 00000000`00000000 fffff800`02aa303a fffffa80`043c7f00 fffff880`03f690c6 : nt!KiExceptionDispatch+0xc2
fffff880`02ffd4d0 fffff880`0410cb3d : 00000000`00000000 fffffa80`04900000 fffffa80`04b81010 fffffa80`04bdf540 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffd660 fffff880`04110677 : fffffa80`04900000 fffffa80`04b81010 fffffa80`04b84000 fffff880`04905730 : dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d
fffff880`02ffd690 fffff880`0410fe00 : 00000000`00000000 fffffa80`04b81010 fffffa80`04b85ab0 fffffa80`04b81010 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x253
fffff880`02ffd730 fffff880`0410fc4c : 00029105`60000400 fffffa80`04b81010 00000000`00000000 fffffa80`04900000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`02ffd780 fffff880`040161cf : fffffa80`043c6040 00000000`00000000 00000000`00000001 fffffa80`049120d0 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02ffd7d0 fffff880`048f4d31 : fffffa80`03a00000 fffffa80`03a00000 fffffa80`04900000 00000000`00000001 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02ffd800 fffffa80`03a00000 : fffffa80`03a00000 fffffa80`04900000 00000000`00000001 fffffa80`04922ef0 : atikmdag+0x4dd31
fffff880`02ffd808 fffffa80`03a00000 : fffffa80`04900000 00000000`00000001 fffffa80`04922ef0 fffff880`04905730 : 0xfffffa80`03a00000
fffff880`02ffd810 fffffa80`04900000 : 00000000`00000001 fffffa80`04922ef0 fffff880`04905730 00000000`00000000 : 0xfffffa80`03a00000
fffff880`02ffd818 00000000`00000001 : fffffa80`04922ef0 fffff880`04905730 00000000`00000000 00000000`00000000 : 0xfffffa80`04900000
fffff880`02ffd820 fffffa80`04922ef0 : fffff880`04905730 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff880`02ffd828 fffff880`04905730 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`049955c7 : 0xfffffa80`04922ef0
fffff880`02ffd830 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`049955c7 fffffa80`04922e70 : atikmdag+0x5e730


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d
fffff880`0410cb3d f0834018ff      lock add dword ptr [rax+18h],0FFFFFFFFh

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x1E_0_dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

BUCKET_ID:  X64_0x1E_0_dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

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

normally it would take longer but I've seen this specific debug result quite a few times now.

Just so long as we wiped everything, the computer probably reinstalled the default driver for the device when you rebooted, just go ahead and update from the amd/ati link I gave above.

yeah, it's a wait and see thing now.
If it does happen again just post the newest minidump along with the update post.

You don't have anything overclocked at all do you?
Using driver sweeper should have cleaned out the problem we shouldn't still be seeing the same error here.

hmmm... here's something to test, create a new user account (possibly a temporary measure)
Boot into the new account try playing the same video and see if you experience the crash again.

...just checking that we do still in fact have a video driver issue and not a user account setting issue.