"Your PC encountered a problem and needs to restart."

This error is usually caused by a hardware problem.

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred.

There is rarely enough information in the crash dumps to help so basically the procedure is to test all aspects of your hardware until you find the component that is causing the problem. Look for any obvious problems inside your case such as excessive dust leading to overheating, fans not working, loose connections. Re-seat all memory modules and graphics cards as this tends to help remake any connections that might have become bad.

Some guidelines follow:

Diagnostic Tests

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

 GPU TEST

Run Furmark to test your GPU. Furmark tutorial

   Note

Run Furmark for around 30 minutes

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high

 HDD TEST

Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

philc43 said:

This error is usually caused by a hardware problem.

Do the tests you mentioned have to be run in any particular order? Also, can I use CHKDSK and/or Western Digital Data Lifeguard instead of HDTune to test my hard drives?

Also, is it possibly relevant that I recently (only three days before this error happened) hooked my computer up to a new Uninterruptible Power Supply that includes a USB cable that hooks it to the computer and a software program (called PowerChute) that allows the user to monitor the UPS through the program and the UPS to tell the computer to shut off if power has been out for too long? That's the only recent hardware change I've made.

The only other relevant thing I can think of is that I was using programs that used a lot of RAM about half an hour before the error happened (although not at the precise time it happened, as far as I can tell).

You can run the tests in any order. Chkdsk is a good one to run and if you have the manufacturer diagnostic tests that is good too.

The UPS may just be coincidence but try running with the UPS software uninstalled and see if it makes a difference.

philc43 said:

You can run the tests in any order. Chkdsk is a good one to run and if you have the manufacturer diagnostic tests that is good too.

I ran MemTest86 for over 24 hours (11 passes) and never got any errors.

I then ran Prime95, and also got no errors.

Furmark, ditto.

I ran the long test of the Western Digital Data Lifeguard program, and likewise got no errors. I could run CHKDSK, but I doubt I'd get any errors (I ran it not long ago, and my hard drive is very new).

I don't think it's a problem with my hardware.

The UPS may just be coincidence but try running with the UPS software uninstalled and see if it makes a difference.

I'm not sure how tell tell whether a difference has been made, as I don't know if the issue was a one-off or evidence of a continuing problem. I haven't gotten again it since it first happened.

However, I think I'll use Macrium Reflect to perform a system image restoration of my system as it was when I made the last backup before installing PowerChute, and see what happens.

By the way, do you think it's relevant that when I installed Powerchute, the installer said that it was disabling part of Windows' native power management?

Sorry to break in but I see a problem with the processor in the dmp.

Code:

0x00000124:    WHEA_UNCORRECTABLE_ERROR (10.02.2017 21:47:33) [Windows 10] 
 
CAUSED BY:     AuthenticAMD [16.07.2016]   
               hal.dll  (Hardware Abstraction Layer DLL. NO Driver)  
 
WHEA Notify:   Machine Check Exception 
     Type:     Cache error 
     Error:    ICACHEL1_IRD_ERR (Proc 0 Bank 1) 
 
PROCESS:       opera.exe  
 
Usual causes:  Hardware, Incompatibility, May be driver corruption

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. (see other wikis for how to)
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.
Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.

Its always worth to do filesystem check:

Repair Windows Filesystem:

1. Open an elevated command prompt.
2. In the elevated command prompt, type these commands below, and press Enter:

dism /Online /NoRestart /Cleanup-Image /CheckHealth

dism /Online /NoRestart /Cleanup-Image /ScanHealth

dism /Online /NoRestart /Cleanup-Image /RestoreHealth

sfc /scannow

chkdsk %systemdrive% /F /R /X

fsutil dirty set %systemdrive%

SFC:
The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
DISM:
If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
For example, you would use DISM to fix Windows component store corruption when a sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted. SFC should be able to repair the files afterwards.
CHKDSK:
Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...

Please run it seperatly one after another.

I would do that BIOS update.

In the postet sevenforums thread u posted it was the CPU at the end.

After that i would do all that hardware diagnosis beginning with memtest and prime95 posted in the thread from philc43.

Please have a look at the temps when stress testing your CPU. U can do that with SpeedFan:

SpeedFan
SpeedFan automatically searches your computer for informative chips: the hardware monitor chips. SpeedFan can display voltages, fan speeds and temperatures.

BSODHunter said:

Please run it seperatly one after another.

I have now run all of the following:

dism /Online /NoRestart /Cleanup-Image /CheckHealth

dism /Online /NoRestart /Cleanup-Image /ScanHealth

dism /Online /NoRestart /Cleanup-Image /RestoreHealth

sfc /scannow

chkdsk %systemdrive% /F /R /X

They all came up clean, including CHKSDSK.

However, I was uncertain whether the following is just one command split over two lines, or two commands that should be run separately. I only ran "chkdsk %systemdrive% /F /R /X", and not "fsutil dirty set %systemdrive%". Should I now run "fsutil dirty set %systemdrive%", or is it unnecessary?

chkdsk %systemdrive% /F /R /X
fsutil dirty set %systemdrive%

I would do that BIOS update.

Is there any safety information I need to know before proceeding (precautions to take)?

Also, is it indeed necessary to clear the CMOS afterward, and is there anything I need to know before clearing the CMOS (such as whether I will have to manually set which hard drive to boot from, any risks, etc).

After that i would do all that hardware diagnosis beginning with memtest and prime95 posted in the thread from philc43.

I already ran those a couple of days ago (after philc43 recommended them). I ran MemTest86 for over 24 hours (11 passes) to test my RAM, and never got any errors. I then ran Prime95 to check my CPU, and also got no errors. I ran Furmark (to test my GPU), and likewise found no problems. I also ran Western Digital Data Lifeguard to test my hard drive, and got no errors.

Please have a look at the temps when stress testing your CPU. U can do that with SpeedFan:

I used Speccy to monitor the heat. The hottest it got was around 74 Celsius.

However, I think I'll use Macrium Reflect to perform a system image restoration of my system as it was when I made the last backup before installing PowerChute, and see what happens.

Just interested to know if you did the above? If you have not had any further problems I would just continue using your system. The checks and tests you have done all indicate your file system is correct and the hardware tests so far have passed. If you get another BSOD post a new set of logfiles and we can look again.