Windows 10: BSOD playing BF 1, WHEA_UNCORRECTABLE_ERROR (124)

Hi,

I'm getting this error on heavy load, like when i'm playing Battefield 1.
Sometimes the system just freezes for several minutes, and the only way to use the computer is to cut the power / long press power button.

I have tried to analyze the crash report, but I can't tell if it's the motherboard or the CPU, or maybe something else. The crash report is attached.

I have also tried to update BIOS, but here it seems to be an issue with my motherboard (Asus maximus vii hero) because it won't accept the file with the updated BIOS that i downloaded from Asus (and yes I renamed the file according to the motherboard instructions).

I really would appreciate your help, since i'm pretty much lost.

Thanks in advance! *Smile

:)

 

BSOD Help whea_uncorrectable_error (124)

Hi thanks for replying. To answer your questions, this issue occurs very rarely but has now happened twice within a short period. This is a computer I built myself. I initially thought my ram was causing the issue because the documentation from Asus (motherboard
manufacture) didn't show the ram I was using as supported models. So I replaced them with new Adata sticks that are supported, and I got another crash after about 5 minutes of running the computer on idle. Also my motherboard likes to automatically "optimize"
settings in the UEFI bios which includes a slight overclocking of the cpu and possibly the ram as well. I have forced all settings in bios to run at hardware defaults (or standard) settings, and so far have had no issues.

Here's a link to my public onedrive folder with two zipped dump files (it's all i have)

Public

 

BSOD Help whea_uncorrectable_error (124)

Hi,

I will certainly help you regarding the blue screen issue.

Kindly let us know a few more details on the below questions:

• Since when are you facing this issue?
• Did you make any changes prior to the issue?

Kindly refer the suggestions from the link below:

Windows 10 BSOD WHEA_UNCORRECTABLE_ERROR

Also, refer the link regarding the blue screen error:

https://support.microsoft.com/en-us/help/14238/windows-10-troubleshoot-blue-screen-errors

Please get back to us for further assistance. We will be happy to help.

Thank you

 

Very sorry you got overlooked. I don't know what happened or why.

Please follow the directions shown in the notice at the top of the forum and of all threads:

Attachment 119071

 

Hi, and thanks for the heads up. I should have seen it before I posted *Rolleyes

I have now attached the zip file from the DM log collector.

 

Sorry, it looks like you are using pirated software. Please correct this by removing the illegal software. If you then get any more BSODs, run DM_Log_collector and upload the zip file and I'll be happy to take a look at it.

 

I did not see that coming. Thought I had put those day's behind me *Smile
Well, I have done a cleanup and have ran the DM_log_collector again.

 

hmmm... I also disconnected the old HDD and I have not had any problems when playing today (for about 3 hours). So now I'm running only the SSD's.

 

Still seeing activation bypasses for Adobe and you have Adobe CS5 Design Premium installed. It sure looks like you have illegal software still installed, sorry.

 

The Adobe CS5 Design premium is valid and activated. I noticed some url's to adobe that where routed back to localhost in the hosts file. I have removed them now. And updated all adobe products included in the CS5 Design premium. I can assure you that this Abode package is not illegal. My girlfriend bought this when she took a degree in graphic design for about 3 years ago.

I don't know how i can prove this, but attached is an image of the deactivation screen. Cause I'm not giving out the key.
I also did a new run with DM_Log_Collector.

 

Good enough for me, thanks.

The newest dumps I see is dated 1/2/2017 and 1/4/2017.
Code: WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. 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 conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffff9e8704540028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.[/quote] Code: 2: kd> !errrec ffff9e8704540028 =============================================================================== Common Platform Error Record @ ffff9e8704540028 ------------------------------------------------------------------------------- Record Id : 01d266b169ba01ee Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 1/4/2017 21:35:07 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff9e87045400a8 Section @ ffff9e8704540180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Micro-Architectural Error Flags : 0x00 CPU Version : 0x00000000000306c3 Processor ID : 0x0000000000000002 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff9e87045400f0 Section @ ffff9e8704540240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000002 CPU Id : c3 06 03 00 00 08 10 02 - bf fb fa 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffff9e8704540240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff9e8704540138 Section @ ffff9e87045402c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 2 Bank 4) Status : 0xbe00000000800400 Address : 0x00007ff8b7248d14 Misc. : 0x00007ff8b7248d14[/quote] The above can be caused by defective hardware or a faulty device driver.

See if a full memory dump is available: The dump file is located at "C:\Windows\Memory.dmp" . It would be a large file so please make sure that you ZIP it up before uploading to a file hosting service like OneDrive. Then post a link to it here.

 

Thanks for checking the logs.
I can't seem to find the memory.dmp file in c:\windows path.
I have checked in the "startup and recovery" settings and it's set to write debug information from "kernel memory dump" to the dump file: %SystemRoot%\MEMORY.DMP (see picture)

It could be that it's been deleted since the diskspace on C: is only 16GB (but I don't know the limit for deleting the memory.dmp file)

Could it be the driver to the HDD I disconnected or the HDD itself that has caused these issues?
- Cause I haven't had any issues since i disconnected it, but it could also just be a coincident..

Thank you in advance for all your help. *Smile

 

Lets wait awhile and see if another BSOD occurs. If not then we can look at the HDD you disconnected.