[Win10ProV1607b14393 x64] BugCheck 124 Random Restarting

eeaga

New member
Joined
May 21, 2017
Posts
2
Hello,

I am having problems for two weeks now with WHEA_UNCORRECTABLE_ERROR bugcheck 0x00000124. I tried posting on other forums but nothing helped yet.

I am attaching the files according to the BSOD posting instructions. Few things I have to mention here. First,
Windows decided to do an update today without me confirming. It wiped out all my dumps so they are not a part of the file collection app report. I am attaching latest minidumps in a separate file (dumps.zip). Second, the PERFMON output is in Russian :banghead:. Since Windows was purchased in Russian Microsoft Store the language of installation is Russian. Even though ALL region and language settings are set to English, it still runs some apps in Russian language. I am very sorry for this. Hope it would be a big problem.


My configuration (brand new hardware, Desktop PC):


  • Windows 10 Pro x64, 10.0.14393 (retail version, originally installed two weeks ago)
  • i7-7700K 4.2GHz processor
  • Asus z270g mainboard with the latest BIOS 0906
  • Corsair RM750x PSU
  • Noctua NH D9L cooler
  • G.Skill F4 DDR4 2133MHz RAM (2x8GB)
  • 250 GB Samsung 850EVO SSD
  • No GPU


What did I try so far:
  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.

I would really appreciate your help, thank you!
 

Attachments

Re: BugCheck 124 Random Restarting

Temperatures are a bit high, but that's common for Prime95. You're not reaching throttling temperatures, so I doubt temperature is a real concern. Despite no major findings with Memtest86+ and Prime95, it could be an issue with your memory, CPU, motherboard, or PSU. See if running with only one 8GB module at a time helps. If you crash, switch to your other 8GB.

What are your voltage readings in your BIOS? HWMonitor is good at reading temperatures, but HWMonitor and other hardware readings within Windows are not 100% reliable at reading the true voltages.
 
Re: BugCheck 124 Random Restarting

Temperatures are a bit high, but that's common for Prime95. You're not reaching throttling temperatures, so I doubt temperature is a real concern. Despite no major findings with Memtest86+ and Prime95, it could be an issue with your memory, CPU, motherboard, or PSU. See if running with only one 8GB module at a time helps. If you crash, switch to your other 8GB.

What are your voltage readings in your BIOS? HWMonitor is good at reading temperatures, but HWMonitor and other hardware readings within Windows are not 100% reliable at reading the true voltages.

Thanks for the feedback! Unfortunately, I was kindly asked not to post my problem on other forums before my post is closed there. They say that suggestions might collide. Could I return back here if the other forum will not help? I apologize for this. Thought that I might have better understanding of the problem if I ask different people.
 
Hi eeaga. :welcome:

After the bios update, your manual says: Ensure to load the bios settings to ensure system compatibility and stability. Select the 'Load optimized defaults' item under the exit menu.
Did you make it?

I also can see a huge pagefile.sys (17GB?).
I'm not sure if a little pagefile could help, but I'd set it from 1GB to 4GB, same initial size and maximum size (1024-1024 or 2048-2048 or 3072-3072 or 4096-4096).
If there's a recommended size, you could use that.

These two things shouldn't interfere with your actual helpers and their recommendations, but feel free to ask them about those two things.
 
Just to Note: Despite SF's diagnosis of a definite faulty CPU, 0x124 BSOD can mean any piece of hardware has failed. The exact piece is unknown. 0x124 WHEA BSOD is just a fancy name for a machine check exception.

Machine-check exception - Wikipedia

There is a serious hardware issue at hand.

Regards. . .

jcgriff2
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top