Hi Drax and welcome to the forums!
I have analyzed your Dump files and the 3 out of 4 have the dxgmms1.sys in the stack just before the crash occurred. Here is the complete analysis of your latest dump file :-
BUILD_VERSION_STRING: 9600.17041.amd64fre.winblue_gdr.140305-1710
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: P2.70
BASEBOARD_MANUFACTURER: ASRock
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
FAULTING_MODULE: fffff8008908e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUGCHECK_STR: 0x124_GenuineIntel
CPU_MICROCODE: 0,0,0,0 (F,M,S,R) SIG: 17'00000000 (cache) 0'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
CURRENT_IRQL: 0
ANALYSIS_SESSION_TIME: 05-28-2014 21:22:21.0854
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:
ffffd001`949c9cf8 fffff800`89055203 : 00000000`00000124 00000000`00000000 ffffe001`d53fe028 00000000`bf800000 : nt!KeBugCheckEx
ffffd001`949c9d00 fffff800`8924e825 : 00000000`00000001 ffffe001`d42a9bc0 ffffe001`d42a9bc0 ffffe001`d53fe028 : hal!HalBugCheckSystem+0xcf
ffffd001`949c9d40 fffff800`8905568c : 00000000`00000728 00000000`00000002 ffffd001`949ca130 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd001`949c9da0 fffff800`89055a11 : ffffe001`00000010 ffffe001`d42a9bc0 ffffd001`949c9f48 ffffe001`d42a9bc0 : hal!HalpMcaReportError+0x50
ffffd001`949c9ef0 fffff800`890558f4 : ffffe001`d42a9810 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd001`949c9f40 fffff800`89055b4e : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd001`949c9f80 fffff800`89055cd7 : ffffe001`d42a9810 ffffd001`949ca1b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd001`949c9fb0 fffff800`891ecabb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd001`949c9fe0 fffff800`891ec871 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x27bb
ffffd001`949ca120 fffff801`a8201e29 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x2571
ffffd001`9653f7b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!DXGFASTMUTEX::Acquire+0x19
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
IMAGE_VERSION:
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS
ANALYSIS_SESSION_ELAPSED_TIME: 74
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner
Furthermore, the issue seems to occur during some kind of activity related to the Video or the DirectX. You only seem to have
55 hotfixes installed. Please fetch them from the Windows Update.
Please follow these steps in case the problem is still not resolved :-
1. Update your graphics driver to the latest version. If you have the latest version then please try reverting back a few versions to see if the problem occurs only with the latest version?
2. Could you please see if the problem still persists if you remove your graphics card from the PCI slot and use the default integrated port for display?
3. If you have got more than one type of outputs on your graphics card, please try swapping the ports to check whether the problem exists only in one port?
4. There might be dust related issues as well, so if you could, please clean your system.
I would be glad to assist you further but in case the issue is resolved, please mark this as solved and post here what worked for you ^_^