Hi Zeales & Welcome to the forums ^_^,
I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred.
Code:
1: kd> !errrec ffffe00172751028
===============================================================================
Common Platform Error Record @ ffffe00172751028
-------------------------------------------------------------------------------
Record Id : 01d02c1d21ee7ad2
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 1/11/2015 3:59:38 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffe001727510a8
Section @ ffffe00172751180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Generic
Flags : 0x00
Level : 2
CPU Version : 0x00000000000306c3
Processor ID : 0x0000000000000001
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffe001727510f0
Section @ ffffe00172751240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000001
CPU Id : c3 06 03 00 00 08 10 01 - bf fb fa 7f ff fb eb bf
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0 @ ffffe00172751240
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffe00172751138
Section @ ffffe001727512c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
[COLOR=#ff0000][B][U]Error : GCACHEL2_ERR_ERR (Proc 1 Bank 8)[/U][/B][/COLOR]
Status : 0xbe0000000100110a
Address : 0x0000000048d6b380
Misc. : 0x0000001080000086
So, according to the dump files, the system experienced a crash due to hardware fault. On scrolling below in the above code part, you will see that I have highlighted the error. It seems that there was an error in L2 Cache of the Processor. The cache at fault is consistent in the dump files having 0x124.
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
Code:
2: kd> .bugcheck
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 [COLOR=#0000ff]fffff800`3a041c38[/COLOR]
Code:
2: kd> !address [COLOR=#0000ff]fffff800`3a041c38[/COLOR]
Mapping user range ...
Mapping system range ...
Mapping non addressable range ...
Mapping page tables...
Mapping hyperspace...
Mapping HAL reserved range...
Mapping User Probe Area...
Mapping system shared page...
Mapping system cache working set...
Mapping loader mappings...
Mapping system PTEs...
Mapping system paged pool...
Mapping session space...
Mapping dynamic system space...
Mapping PFN database...
Mapping non paged pool...
Mapping VAD regions...
Mapping module regions...
Mapping process, thread, and stack regions...
Mapping system cache regions...
Usage:
Base Address: fffff800`00000000
End Address: fffff800`3a35b0ff
Region Size: 00000000`3a35b0ff
[B][U][COLOR=#ff8c00]VA Type: BootLoaded[/COLOR][/U][/B]
VAD Address: 0x27676e69727473
Commit Charge: 0x100000003
Protection: 0x7ffc55aba2f0 []
Memory Usage: Private
No Change: yes
More info: !vad 0xfffff80000000000
There was another bugcheck which was due to accessing invalid memory. Furthermore, the address which referred to the invalid memory, it was Bootloaded which means that it was a part of the Operating System. This is generally seen in the case of bad hardware.
Kindly perform the Free hardware diagnostics (Prime95 first) at the link -
Hardware Diagnostics
Also remove ASUS Bloatware and physically disconnect RAZER devices present on the system as it is known to cause problems.
Let me know how it goes ^_^
-Pranav