WHEA_UNCORRECTABLE_ERROR
A 0x124 is one of the worst STOP codes to encounter for the sole reason that the dump files usually give nothing away as to the cause of the problem. WHEA (Windows Hardware Error Architecture) errors signify a problem with hardware but very rarely pinpoint the culprit. In these scenarios it is advised to run a series of hardware stress and diagnostic tests to try and pinpoint the problem. A template is offered below which covers the four main components (GPU, CPU, RAM, HDD) and gives you a fighting chance of narrowing down the problematic device.
Code:
0x00000124: [SPECIAL] WHEA_UNCORRECTABLE_ERROR (2018-08-15 13:16:17) [Windows 10]
CAUSED BY: GenuineIntel_PROCESSOR_CACHE
WHEA Notify: Machine Check Exception
Type: Cache error
Error: GCACHEL2_DWR_ERR (Proc 6 Bank 6)
PROCESS: ts3client_win64.exe
Code:
2018-07-20 18:27:12 Error: Unable to produce a minidump file from the full dump file.
2018-07-20 18:27:12 Error: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffad89d1af0028, 0x00000000fe000000, 0x000000000040014a). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.
2018-07-21 13:32:54 Error: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffcb8dc0cf6028, 0x00000000fa000000, 0x0000000000400405). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7b4d558a-48a2-4a49-a845-8e3491396fd0.
2018-07-22 14:19:00 Error: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: df0a650b-c8e9-47b3-9715-fe90d52a3d13.
2018-07-28 22:59:39 Error: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff98890a917028, 0x00000000be000000, 0x0000000000400152). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 57b78d17-bda5-452b-a560-07ca793038b7.
2018-07-30 12:03:12 Error: Unable to produce a minidump file from the full dump file.
2018-07-30 12:03:12 Error: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe305bbb11028, 0x00000000fe200040, 0x000000000060114a). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.
2018-08-01 22:08:36 Error: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff00cd643a2e2, 0x0000000000000000, 0xfffff80102add866, 0x000000000000000c). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 43b500f7-a440-40d8-be8a-640b1010dc22.
2018-08-03 14:23:41 Error: Unable to produce a minidump file from the full dump file.
2018-08-03 14:23:41 Error: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff820503af0028, 0x00000000fa000000, 0x0000000000400405). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.
2018-08-15 12:18:27 Error: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff8e08972f6028, 0x00000000fe000000, 0x000000000040014a). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 86cf7001-056d-4f2e-b6ef-340665d258d3.
"Cache Error": Could be caused by hardware problems, but also by overclocking, faulty drivers or BIOS problems.
Generic "Stop 0x124" Troubleshooting Steps:
1) Ensure that none of the hardware components are overclocked. Overclocking means pushing the components beyond what they were designed for. If you do not know what that is you probably are not overclocking so go to the next step
2) Ensure that the machine is adequately cooled. If this is a laptop use compressed air to carefully blow out the heat pipe and fan when the computer is turned off. If a desktop take the side cover off and blow a fan on the components
3) Update all hardware-related drivers: video, sound, RAID (if any), etc. Do not rely on windows when it says the most recent driver is installed. It may be the most recent but it may also be corrupt.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS. Check with the computer maker for directions on this procedure and as usual it is always a good idea to back up your data.
5) Update ALL OS Windows updates
6) Stress test the major components. Start with RAM, CPU, HD, etc.
For RAM, use Memtest. Instructions for which can be found here.
Computers are extremely sensitive to problematic ram so any errors on memtest should be considered an issue and even a clear report for less than 8 passes can give a false negative.
For CPU use Prime95
For hard drives, use CHKDSK /F finds any problems on the drive(s), notably "bad sectors". You should also go to the HD maker and download and run their HD checking utility
7) Perform a "vanilla" (clean) re-installation of Windows: Install nothing that is not from the OS (not even Malware) until you have seen that the computer is not crashing in this state.
When the vanilla installation has run long enough that you are convinced it is OK, start installing updates and applications a few at a time, and wait until you are again convinced it is OK. If the crashes resume it is obviously the last group of installations that is the issue and remove them.
8) Re-seat all connectors, ram modules, etc. You can use the same can of compressed air to clean out the RAM DIMM sockets as much as possible.
Only attempt this if you are FULLY knowledgeable about the procedures.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Quote