LiveKernelEvent Code 124 corresponds to the WHEA_UNCORRECTABLE_ERROR (bug check 0x124), which indicates a fatal hardware error reported through Windows Hardware Error Architecture (WHEA). In the bucket ID, the error is coming from the AMD processor cache.
From the documentation, this type of error is typically caused by:
- Physical hardware failures (CPU, memory, motherboard)
- Heat/thermal issues
- Overclocking or unstable CPU/SoC settings
- Less commonly, a driver that is triggering hardware to fail
Recommended steps based on the provided guidance:
- Remove overclocking and restore defaults
- If any CPU, RAM (XMP/EXPO), or GPU overclocking is enabled in BIOS/UEFI or via tuning software, disable it.
- Load BIOS/UEFI “Optimized Defaults” or “Setup Defaults” and save.
- Check cooling and thermals
- Ensure all case and CPU fans are working and not obstructed.
- Make sure heatsinks (especially CPU cooler) are properly seated.
- Clean dust filters and vents to improve airflow.
- Run hardware diagnostics
- Use the system or motherboard vendor’s built‑in diagnostics to test CPU, memory, and other components.
- Run the Windows Memory Diagnostics tool to check RAM:
- Open Control Panel, search for Memory, select Diagnose your computer's memory problems, and let it run. Then review results in Event Viewer under MemoryDiagnostics-Results.
- Check for other hardware issues and drivers
- Open Device Manager and look for devices with an exclamation mark (!). Update or temporarily disable/uninstall any problematic devices.
- Remove or disconnect any recently added hardware and test again.
- Review system logs around the error
- Open Event Viewer → Windows Logs → System and look for critical errors that occur at the same time as the LiveKernelEvent 124. This can help confirm if the issue is consistently CPU/processor‑related or if another device is involved.
- General bug check troubleshooting
- Check for viruses or disk corruption using your antivirus and disk tools, as corruption can also lead to bug checks.
- Ensure the hardware platform meets Windows requirements and that firmware/BIOS is compatible with the installed Windows build.
If the problem persists after restoring defaults, confirming cooling, and passing memory and vendor diagnostics, the documentation indicates a likely physical hardware fault (often CPU, memory, or motherboard) and the failing component may need to be repaired or replaced.
References: