Windows 10: BSOD random restarts on new hardware, error 0x00000124

What cause this problem? BSOD 0x124 - Graphics Cards

Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR - Windows 10 hardware dev

axe0 - There was one website that showed that a guy replaced his 6700K from getting this error, but the site is down and I can't pull it up. I can't verify the credibility of the website, but it appears credible since it said Microsoft MVP Professional.

And yes you are right. Hardware doesn't always cause hardware errors. Bad drivers can also cause hardware errors, but also in my experience with failed hardware, it's very difficult to rule out the CPU or Motherboard that is the cause.

Eeaga - have you tried going into safe mode and seeing if the error occurs there?

As anyway, here are some links of people having this same error.

0x124 BSOD - Windows 7 Help Forums

BSOD Stop 0x124 Solved - Windows 7 Help Forums

 

I am not able to pull up the website as the site is down. They had a post about a 7700k and 6700k that had this issue, user replaced it, and all was normal. Yet since it is down, it makes me question the credibility of the site, so if it's bad credibility, I do apologize.

I'm saying, that looking at the dumps, and looking at all the forums online, that this BSOD is either caused by a failed CPU overclock, bad graphics card, RAM, and hard disk. Some have reported that bad voltages to the CPU and RAM caused these issues.

I am only trying to help on this issue. I could be completely wrong on the cause, but there is obviously a problem here.

 

There are many things that could cause hardware issues,
- Hardware failure, improper seating, loose cabling, overheating, overclocking, drivers, software, BIOS

There are enough threads on this site with the same BSOD but somehow different, Windows 10 Forums
Also this one Windows 7 Forums is the largest help and support community, providing friendly help and advice for Microsoft Windows 7 Computers such as Dell, HP, Acer, Asus or a custom build. - Search Results for 0x124
And this one, Windows 8 Forums - Search Results


And a few other sites that are currently under maintenance

@eeaga, a full dump won't be necessary. Often multiple minidumps is enough to get a pattern which is what we need with this particular BSOD *Smile
Please provide the other logs too, they can be quite useful from time to time, see my previous post.

 

Axe - You are correct. Looks like many problems can cause this issue. Yet I still have a lot to learn, as I've had 2 machines that I owned personally that had this exact BSOD, and one machine was a bad motherboard, and the other was a bad RAM stick and Hard drive.

 

Thanks for helping guys. Log Collector output is attached.

I will go through the things I've tried once again:
1) MemTest86+ 15 passes - no errors
2) Prime95 different tests 4-5 hours in total - no errors
3) System File Checker - no corrupt files detected
4) Intel Processor Diagnostic - all tests passed
5) Updated all drivers
6) Updated SSD firmware
7) Updated Windows just now before generating Log Collector report
8) Tried different OS; Linux also crashes but does not report errors in the logs

I am also attaching a screenshot of HWMonitor so you can see min/max temperatures and voltages under load (during Prime95 tests). Maybe this will help.

Now, after having some experience with 0x124 BSODs, I've noticed that it usually happens during some graphics load e.g. playing a movie with VLC, Games, fancy flash web sites... Not sure though, this is just an observation.

 

You reinstalled the OS or did an upgrade, because the event logs and dumps have been wiped.

Each test should be run for a couple of hours minimum, or do you mean each test 4-5h?

 

I wondering if you couldn't turn the turbo core technology off on the CPU, which can be shut off in the BIOS. The max turbo core is 4.5 GHz, and it's going about 30 MHz above that.

Not saying the turbo core technology is the problem, but it's a good thing to test.

 

Yes, that's right. My PC went to sleep mode and woke up updated. I have no idea how did that happen. Didn't know that it wipes out the dump files... I managed to restore 4 minidumps that were saved here and there (attached). In the previous post I mentioned that the Log Collector gathered information after the system was updated.

I did In/place large FFT (on the screenshot in the previous post) for three hours and blend test for around two hours.

Isn't 30 MHz just a normal deviation? I could try disabling turbo though.

 

Yes it's normal, but disabling the turbo would only allow the CPU to go to 4.2 GHz Max. It's worth a try.

I know AMD and Intel Architectures are way different, but AMD had issues with the Turbo Core Technology on FX CPUs, causing BSODs and hard freezing. Not sure if Intel works the same in terms of "Boost" frequencies, but it's always worth a try. Any troubleshooting will be helpful at this point

 

Don't start a new thread on different forums, chance that suggestions collide is high.

@eeaga

We await your reponse.........

 

@axe0 Sorry, I did not think it might be a problem. I will not touch that forum and apply their suggestions until we are done here. Already replied there accordingly.

Can we proceed?

 

Different people think in different ways, with some bad luck it results in your system becoming more unstable.

We await the results of @lmaneke suggestion to disable the turbo for your CPU *Smile

 

Okay, I see. Sure it makes sense.

I was not at home these two days. Will disable turbo today evening and report results asap.

 

UPDATE:

Disabled turbo. Immediately after booting into the system I ran Prime95 blend test and opened Youtube. After like 40 min of browsing with the test running Windows terminated with CLOCK_WHATCHDOG_TIMEOUT BSOD.

Unfortunately, Windows stuck while trying to collect the information about this error during BSOD. No mini dump files were generated and the full dump is corrupt... I will try to repeat this scenario to generate dumps.

Could this post be relevant for my case?

 

I've never seen that BSOD before. I've seen the Watchdog_Violation but not this one.

It's a big possibility, but looking at Toms Hardware forums, you definitely aren't alone. Without having the dumps from that BSOD, I can't tell if it's a CPU internal clock issue as stated on the other site.

Looks like many others are having these issues on ASUS motherboards, with the 2500k, 4770, 6700k, so the problem is across many platforms.

Some indicated that the AI suite software was the cause. I think you said you got all of that uninstalled. Plus some said updating the BIOS helps, but yours is up to date.

RAM isn't throwing any errors, no errors with SSD.

You get the WHEA_Uncorrectable_error with Turbo on and Clock_watchdog_timeout with turbo off. Hmmm

I'm suspecting PSU, CPU, or Motherboard to be the cause at this moment. But not sure which one