The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
WHEA_UNCORRECTABLE_ERROR Parameters
Parameter 1
Parameter 2
Parameter 3
Parameter 4
Cause of error
Address of WHEA_ERROR_RECORD structure.
High 32 bits of MCi_STATUS MSR for the MCA bank that had the error.
Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error.
A machine check exception occurred.
These parameter descriptions apply if the processor is based on the x64 architecture, or the x86 architecture that has the MCA feature available (for example, Intel Pentium Pro, Pentium IV, or Xeon).
Address of WHEA_ERROR_RECORD structure.
A corrected machine check exception occurred.
Address of WHEA_ERROR_RECORD structure.
A corrected platform error occurred.
Address of WHEA_ERROR_RECORD structure.
A nonmaskable Interrupt (NMI) error occurred.
Address of WHEA_ERROR_RECORD structure.
An uncorrectable PCI Express error occurred.
Address of WHEA_ERROR_RECORD structure.
A generic hardware error occurred.
Address of WHEA_ERROR_RECORD structure
An initialization error occurred.
Address of WHEA_ERROR_RECORD structure.
A BOOT error occurred.
Address of WHEA_ERROR_RECORD structure
A Scalable Coherent Interface (SCI) generic error occurred.
Address of WHEA_ERROR_RECORD structure.
Length, in bytes, of the SAL log.
Address of the SAL log.
An uncorrectable Itanium-based machine check abort error occurred.
Address of WHEA_ERROR_RECORD structure
A corrected Itanium-based machine check error occurred.
Address of WHEA_ERROR_RECORD structure.
A corrected Itanium platform error occurred.
Cause
This bug check is typically related to physical hardware failures. It can be heat related, defective hardware, memory or even a processor that is beginning to fail or has failed. If over-clocking has been enabled, try disabling it. Confirm that any cooling systems such as fans are functional. Run system diagnostics to confirm that the system memory is not defective. It is less likely, but possible that a driver is causing the hardware to fail with this bug check.
For additional general bug check troubleshooting information, see Blue Screen Data.
Remarks
The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.
Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error condition.
When a hardware error occurs, WHEA creates an error record to store the error information associated with the hardware error condition. Each error record is described by a WHEA_ERROR_RECORD structure. The Windows kernel includes the error record with the Event Tracing for Windows (ETW) hardware error event that it raises in response to the error so that the error record is saved in the system event log. The format of the error records that are used by WHEA are based on the Common Platform Error Record as described in Appendix N of version 2.2 of the Unified Extensible Firmware Interface (UEFI) Specification. For more information, see WHEA_ERROR_RECORD and Windows Hardware Error Architecture (WHEA).
For more information see the following topics:
This bug check is not supported in Windows versions prior to Windows Vista. Instead, machine check exceptions are reported through bug check 0x9C.
Bug Check 0xC000021A: WINLOGON_FATAL_ERROR
The WINLOGON_FATAL_ERROR bug check has a value of 0xC000021A. This means that that the Winlogon process terminated unexpectedly.
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
WINLOGON_FATAL_ERROR Parameters
A string that identifies the problem
Cause
This error occurs when a user-mode subsystem, such as WinLogon or the Client Server Run-Time Subsystem (CSRSS), has been fatally compromised and security can no longer be guaranteed. In response, the operating system switches to kernel mode. Microsoft Windows cannot run without WinLogon or CSRSS. Therefore, this is one of the few cases where the failure of a user-mode service can shut down the system.
Mismatched system files can also cause this error. This mismatch can occur if you have restored your hard disk from a backup. Some backup programs might skip restoring system files that they determine are in use.
Resolution
Running the kernel debugger may not be useful in this situation because the actual error occurred in a user-mode process.
Resolving an error in a user-mode device driver, system service, or third-party application
Because bug check 0xC000021A occurs in a user-mode process, the most common culprits are third-party applications. If the error occurred after the installation of a new or updated device driver, system service, or third-party application, the new software should be removed or disabled to isolate the cause. Contact the manufacturer of the software about a possible update.
Resolving a mismatched system file problem
If you have recently restored your hard disk from a backup, check if there is an updated version of the backup/restore program available from the manufacturer.
Look at the most recently installed applications. To do this navigate to «Uninstall or change a program» in control panel and sort the installed applications by install date.
Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.
Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Look for critical errors in the system log that occurred in the same time window as the blue screen.
Remarks
Use the System File Checker tool to repair missing or corrupted system files. The System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. Use the following command to run the System File Checker tool (SFC.exe).
Run a virus detection program. Viruses can infect all types of hard disks that are formatted for Windows, and the resulting disk corruption can generate system bug check codes. Make sure the virus detection program checks the Master Boot Record for infections.
Verify that the system has the latest updates installed. To detect which version is installed on your system, select Start, select Run, type winver, and then press ENTER. The About Windows dialog box displays the Windows version number (and the version number of the service pack, if one is installed).
Using Safe Mode
Consider using Safe Mode to isolate elements for troubleshooting and, if necessary, to use Windows. Using Safe Mode loads only the minimum required drivers and system services during the Windows startup.
To enter Safe Mode, use Update and Security in Settings. Select RecoveryВ > Advanced startup to boot to maintenance mode. At the resulting menu, choose TroubleshootВ > Advanced OptionsВ > Startup SettingsВ > Restart. After Windows restarts and displays the Startup Settings screen, select option 4, 5, or 6 to boot to Safe Mode.
Safe Mode may also be available by pressing a function key on boot, for example F8. Refer to information from the computer’s manufacturer for specific startup options.
Interpreting a Bug Check Code
When Microsoft Windows encounters a condition that compromises safe system operation, the system halts. This condition is called a bug check. It is also commonly referred to as a system crash, a kernel error, a Stop error, or BSOD. A hardware device, its driver, or related software might have caused this error.
If crash dumps are enabled on the system, a crash dump file is created.
If a kernel debugger is attached and active, the system causes a break so the debugger can be used to investigate the crash.
If no debugger is attached, a blue text screen appears with information about the error. This screen is called a blue screen, a bug check screen, a Stop screen, or BSOD.
Interpreting bug check code tools
The exact appearance of the bug check screen depends on the cause of the error. The following is an example of one possible bug check screen:
On the other hand, some blue screens look like this:
Data tools
The hexadecimal number following the word «STOP» is called the bug check code or Stop code. This is the most important item on the screen.
Each bug check code has four associated parameters. In the first blue screen shown here, all four parameters are displayed after the bug check code. However, in the second kind of blue screen, these parameters have been rearranged within the explanatory text. Regardless of the amount of rearrangement, they will always appear sequentially. If fewer than four parameters appear, the remaining parameters can be assumed to be zero.
The remainder of the text on the blue screen gives additional information. For some bug checks, this may be an explanation of what happened or suggestions for how you can deal with the problem. If a kernel-mode dump file has been written, this will usually be indicated as well.
Under some conditions, Windows will display only the first line of the blue screen. This can occur if the vital services needed for the display have been affected by the error.
Bug Check Symbolic Names
Each bug check code also has an associated symbolic name. These names usually do not appear on the blue screen. In these examples, the first screen shows bug check 0x79 (MISMATCHED_HAL), while the second shows bug check 0xC000021A (STATUS_SYSTEM_PROCESS_TERMINATED).
You can deliberately cause a bug check from a kernel-mode driver by passing the bug check’s symbolic name to KeBugCheck or KeBugCheckEx. This should only be done in circumstances where no other option is available.
Reading Bug Check Information from the Debugger
If a debugger is attached, a bug check will cause the target computer to break into the debugger. In this case, the blue screen may not appear, or may appear with less text; the full details on this crash will be sent to the debugger and appear in the debugger window. For more information, see Using a Debugger.
This reference section for the bug check codes can be found as part of Windows Debugging. See Bug Check Code Reference for descriptions of the bug checks and parameters. Each reference page lists the bug check code, the text string, and the four additional parameters which are displayed with each bug check. It also describes how you can diagnose the fault that led to the bug check, and possible ways to deal with the error.
For a full list of bug check codes, see the Bugcodes.h file. This file can be found in the inc directory of the Microsoft Windows Driver Kit (WDK).
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffdd8824f1b8f8, 0x0000000000000000, 0x0000000000000000).
Hello, I’ve had this bugcheck error twice now and a Kernel-Power restart once over the past week. I am getting very worried, as I haven’t changed any hardware. After the first time (on the 3rd of December), I dusted the PC with compressed air because I read this issue could occur due to overheating and it was OK until the 8th of December when it happened again, and I realised that the problem may be much more severe than an overheating issue. It happened again yesterday (11th of December) and I knew I had to ask for help here.
This PC is a year old (built in April of 2016) and I built it. I can only find 1 of the minidumps from yesterday. I don’t know where the other 2 have gone but they’re not in the minidump folder.
Thank you so much.
Edit: I haven’t overclocked.
Replies (2)
BCC124 is usually due to a faulty hardware which I can see from the dump too, but the details are really scarce:
This means something of the AMD crash-which can be your PCs GPU or CPU.
Drilling it more finds this:
BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
This points to a BUS error.
A general guide to resolve BCC124:
I would first suggest doing a CPU test and subsequently over to GPU test:
Sumit Volunteer Moderator- Microsoft Community
Mark the reply as helpful or answered to help others if your query is resolved
1 person found this reply helpful
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Could be heat related — try using a small fan to blow into the air intakes to see if that helps. Does it just act like it loses power or does it shutdown in a normal manner? Heat related does not always mean too much heat as it is very possible that something is too sensitive to even normal levels of heat.
Remove ALL power and reseat all cards, memory, and cables (both ends when possible) — actually remove and replace — do not just snug. Remove the dust bunnies and clean the vents. Check that the fans work (before and after opening the case). If a laptop about all you can do is reseat the memory and clean the vents (still can try adding a small fan as a test).
This sounds like hardware so if the above does not help then you probably need the help of a real computer shop (one that does its own in-shop service) or the S ystem Maker’s Support.
Probably caused by : AuthenticAMD
Processor report: Notice the Fatal
============================================ Common Platform Error Record @ ffffdd8824f1b8f8 ——————————————————————————- Record Id : 01d37255533d9423 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 12/11/2017 7:55:01 (UTC) Flags : 0x00000002 PreviousError
Proc. Type : x86/x64 Instr. Set : x64 Error Type : BUS error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000600f20 Processor ID : 0x0000000000000000
Error : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4) Status : 0xf2000010000b0c0f
BCCode: 124 0x00000124
This is usually heat related, defective hardware, memory or even processor though it is «possible» that it is driver related (rare). Remove ALL power and reseat all cards, memory and cables (on both ends) — actually remove and replace — do not just snug. Make sure the system has adequate ventilation — add a small fan blowing into intakes. Carefully inspect the motherboard and other cards for damage. Pay attention to the fatal hardware error implication. You may need a real computer shop (not leeks and peeks at a BestBuy or other BigBox stores) or the System maker’s Support.
Check the processor seating, heat sink, and the compound between the processor and the heat sink which are common causes.
There have been a few instances where Norton/Symantec and other antivirus/security programs have caused this error.
BCCode: 124 0x00000124
The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
Hope this helps. ——————————————————————————— Rob Brown — Microsoft MVP Rob Brown — past Microsoft MVP — Windows Insider MVP 2016 — 2021 Microsoft MVP Windows and Devices for IT 2009 — 2020
