Hi,
We have four dump files, with the first three being of the
WHEA_UNCORRECTABLE_ERROR (124) bugcheck.
A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).
If we run an !errrec on the 2nd parameter of the bugcheck (address of the WER structure) we get the following:
Code:
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa80066b70a8
Section @ fffffa80066b7180
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 : 0x0000000000000006
Code:
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa80066b7138
Section @ fffffa80066b72c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : GCACHEL2_ERR_ERR (Proc 3 Bank 5)
Status : 0xbe0000000100110a
Address : 0x0000000054d09980
Misc. : 0x0000011082000086
Cache error + GCACHEL2_ERR_ERR - Looks like faulty L2 Cache on Processor 3 and Cache Bank 5.In the other two dumps we switch between Processor 3, 0 (first and primary core), 2, and Cache Bank 6 and 5.
MODULE_NAME: hardware
IMAGE_NAME: hardware
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
-----------------------------------------------------------------
The other dump is of the following bug check:
KMODE_EXCEPTION_NOT_HANDLED (1e)
This indicates that a kernel-mode program generated an exception which the error handler did not catch.
Debug session time: Sat Oct 12 14:18:58.674 2013
^^ It's not 'recent', but I'll show you as to why it still may be relevant.
BugCheck 1E, {
ffffffffc0000005, fffff880038bac9a, fffff88002f7fbb8, fffff88002f7f3f0}
The 1st parameter of the bug check is 0xc0000005 which indicates an access violation occurs. If we take a look here -
FAILURE_BUCKET_ID: X64_0x1E_c0000005_e1d63x64+4fc9a
We can see that it was caused by
e1d63x64.sys which is the Intel Gigabit Adapter NDIS 6.x driver
OR Intel Ethernet Connection I217-V.
Now why I said it may still be relevant is I ran an lmvm on the driver to check the date:
Code:
2: kd> lmvm e1d63x64
start end module name
fffff880`0386b000 fffff880`038df000 e1d63x64 T (no symbols)
Loaded symbol image file: e1d63x64.sys
Image path: \SystemRoot\system32\DRIVERS\e1d63x64.sys
Image name: e1d63x64.sys
Timestamp: Tue Feb 26 19:23:53 2013 (512D5219)
And in the very latest dump, if you run an lmvm to check the date, it's the same date. With this said, originally I was under the impression looking at the dumps that you may have had some networking driver issues and updating them solved that, however, I can see that they were not updated therefore this may still be an issue.
-----------------------------------------------------------------
Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it may be causing NETBIOS conflicts in your case:
avast! removal tool - avast! Uninstall Utility | Download aswClear for avast! Removal
-----------------------------------------------------------------
If after removing and replacing avast! you're still crashing:
1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps -
Speccy - System Information - Free Download
2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting -
How To Clear CMOS (Reset BIOS)
3. Ensure your BIOS is up to date.
4. The
only software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite or their PC Probe utility. Checking your loaded modules list I do see you have that installed, so uninstall the software ASAP.
AsIO.sys - Wed Aug 22 05:54:47 2012
<------ Asus PCProbe Utility
5. If all of the above fail, the only left to do is replace your processor as it is faulty.
Regards,
Patrick
