Hi,
We have a few different bug checks, with
WHEA_UNCORRECTABLE_ERROR (124) bug check.
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:
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa800f7bd0a8
Section @ fffffa800f7bd180
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 : 0x00000000000306a9
Processor ID : 0x0000000000000000
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800f7bd138
Section @ fffffa800f7bd2c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : GCACHEL2_ERR_ERR (Proc 0 Bank 7)
Status : 0xbe2000000005110a
Address : 0x000000019a5f4b40
Misc. : 0x0000011082000086
^^ Right, so GCACHEL2_ERR_ERR implies there was a problem with your L2 Cache. This specifically occurred on Processor 0 and Cache Bank 7. In other *124 dumps, we have Processor 4 and 0, but remaining consistent regarding Cache Bank 7.
PROCESS_HAS_LOCKED_PAGES (76)
This bug check indicates that a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked.
The driver either failed to unlock pages that it locked (parameter 1 value is 0x0), or the driver is attempting to unlock pages that have not been locked or that have already been unlocked (parameter 1 value is 0x1).
BugCheck 76, {
0, fffffa8010751b30, 9, 0}
Cannot seem to locate the image name of the driver that is leaking the pages with !search, it may need to be a Kernel dump.
BAD_POOL_HEADER (19)
This indicates that a pool header is corrupt.
Code:
3: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffff880`02ba1368 fffff800`0380bcae : 00000000`00000019 00000000`00000020 fffff8a0`0226a130 fffff8a0`0226a190 : nt!KeBugCheckEx
fffff880`02ba1370 fffff880`0f514cda : 00000000`00000001 00000000`000007ff 00000000`494e494d 00000000`00000000 : nt!ExDeferredFreePool+0x12da
fffff880`02ba1420 00000000`00000001 : 00000000`000007ff 00000000`494e494d 00000000`00000000 fffff8a0`0231c8c0 : [COLOR=#ff0000][I][B]atikmdag+0x39cda[/B][/I][/COLOR]
fffff880`02ba1428 00000000`000007ff : 00000000`494e494d 00000000`00000000 fffff8a0`0231c8c0 fffff880`0f4e9d62 : 0x1
fffff880`02ba1430 00000000`494e494d : 00000000`00000000 fffff8a0`0231c8c0 fffff880`0f4e9d62 fffff8a0`0226a140 : 0x7ff
fffff880`02ba1438 00000000`00000000 : fffff8a0`0231c8c0 fffff880`0f4e9d62 fffff8a0`0226a140 fffff880`02ba1620 : 0x494e494d
Unable to load image \SystemRoot\system32\DRIVERS\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+39cda )
^^ AMD/ATI video driver.
------------------
1. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.
2. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:
avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal
MSE - Microsoft Security Essentials - Microsoft Windows
3. Remove GPU-z.
------------------
If the above does not help, there is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:
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. If you have something like this software-wise, remove it ASAP.
5. If all of the above fail, the only left to do is replace your processor as it is faulty.
Regards,
Patrick
