Definitely the graphic card, Let's try different graphic card then Same stop code as the previous one with dxgmms1.sys (Directx) as well as your graphic card driver were blamed.
BUGCHECK SUMMARY:
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff88004578ce5, fffff880021306a8, fffff8800212ff10}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff88004bef70e, fffff88006c9f7e0, 0}
Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+35e70e )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff80002cb8863, fffff8800824b0b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!EtwpFindGuidEntryByGuid+73 )
Followup: MachineOwner
---------
BugCheck C2, {b, fffffa80085f9070, c, fffffa80085f9e00}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264 )
Followup: MachineOwner
---------
BugCheck 1E, {0, 0, 0, 0}
Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d )
Followup: MachineOwner
---------