WHEA_UNCORRECTABLE_ERROR help please

57IYSY2v4EDt

New Member
Hi all, I've just built a new computer and I've been getting BSOD's few times a day consistently every day.

Things I've done to try and fix it:
- Reinstalled windows
- Tested RAM using MemTest86 8 passes (4 passes when overclocked to 3200mhz and 4 passes when not overclocked at 2133) with 0 errors
- Ran stress tests using Prime95 (ran fine for like an hour, so stopped the tests)
- Ran Intel® Processor Diagnostic Tool (no errors detected)
- Tried running windows with and without installing drivers
- Update BIOS to latest version
- Reset BIOS (stock settings, no CPU overclock, etc...)

I ran out of ideas, therefore I'm asking for your help. Please let me know if you need any other information.

Latest dump from the W7F Diagnostic Tool is attached.

Thanks in advance!
 

Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffad876232c028, be000000, 800400}

Probably caused by : GenuineIntel

Followup:     MachineOwner
Hi,
124 usually relates to overheating often caused by overclocking as well as inadequate coolers so make sure your temps aren't getting too high by using something like HWiNFO64

Looking over your drivers I couldn't see any for the chipset which is super important. You need both drivers, the engine interface and the driver described as 'inf'. These basically tell the system how to run and are really important as i wrote earlier.
Z370 AORUS Gaming 3 (rev. 1.0) | Motherboard - GIGABYTE Global
(Look under chipset and it's the top two drivers)

I also notice your bios is now outdated as the current version stands 5d.

When you flash the bios, do you first set the motherboard to 'optimised defaults'? Something, I think, is worth doing before and after a bios flash.
If your currently overclocked please return to default values until we find the suspect.

Let us know if the drivers help or if your temps are very high.
 

57IYSY2v4EDt

New Member
Hi kemical,

None of the PC parts are overclocked at the moment. Checked the temps using HWiNFO64 and everything looks fine, IDLE CPU is about 25 degree celsius, at heavy load (when stress testing) max is about 55-60. I'm using Noctua's nh-d15 cooler so I'm pretty sure that is not the problem.

I've also installed both of the drivers that you have mentioned and updated BIOS to F5d (latest version).
Before and after update I have set mobo to optimised defaults.

I'm gonna let PC run overnight and see if it will BSOD or not.
Thanks for you help.
 
Last edited:

57IYSY2v4EDt

New Member
Your temps do sound fine as you say. Let's hope you have a crash free night.. :)
Hi kemical,

So far I haven't gotten any BSOD's today. Usually I would get at least 3 BSOD's per day. Thank you for all your assistance, kemical! :worship:

EDIT: 30mins after I wrote this I get a BSOD! :furious:
 

Attachments

Last edited:

kemical

Windows Forum Admin
Staff member
Premium Supporter
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffff810cb594d028, be000000, 800400}

Probably caused by : GenuineIntel

Followup:     MachineOwner
Hi,
sorry to hear your issues continue.

As you have just built the machine it might be worth checking that connections are nice and tight. Plus you could also try reseating the CPU, RAM and GPU if you have one.
I had a look over your dxdiag and noticed that Gigabyte applications like Easytune and Gigabyte easy saver were crashing quite a bit and it might be worth removing them and see if the issue stops

Lastly can you post your system spec including make and model of your PSU.
 

57IYSY2v4EDt

New Member
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffff810cb594d028, be000000, 800400}

Probably caused by : GenuineIntel

Followup:     MachineOwner
Hi,
sorry to hear your issues continue.

As you have just built the machine it might be worth checking that connections are nice and tight. Plus you could also try reseating the CPU, RAM and GPU if you have one.
I had a look over your dxdiag and noticed that Gigabyte applications like Easytune and Gigabyte easy saver were crashing quite a bit and it might be worth removing them and see if the issue stops

Lastly can you post your system spec including make and model of your PSU.
Hi kemical,

I'll reseat my PC parts and check all of the connections.
As for the Gigabyte apps, I have installed the APP Center so I could download the BIOS flasher tool. Anyway, I uninstalled them already.

System specs:
MOBO: Z370 AORUS Gaming 3
CPU: i7-8700K
RAM: 16GB (2x8GB) Corsair DDR4 Vengeance RGB, PC4-25600 (3200), Non-ECC Unbuffered, CAS 16-18-18-36, RGB LED, XMP 2.0, 1.35V
PSU: 750W - EVGA SuperNOVA G3 80+ Gold Full-Modular
GPU: I'm using Intel's integrated graphics, no dedicated graphics card.

Thanks again for you help!

EDIT 12:57 / 1/28/2018: I have checked all of the connections and reseated RAM & CPU. I'll post again if I get a BSOD!
 
Last edited:

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
Don't flash from windows, that way lays chaos, use the bios flash routine from within the bios. Bios on a usb key formatted to fat32 and then use @bios I think it's called from within the bios.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
As nmsuk says your better off formatting a usb drive ( a 4GB will do) as FAT32 and then pop the new bios on that.

Boot into your bios and on my board ( AX370 AORUS Gaming K7) I press F8 to get into Qflash .
you can access Q-Flash by either pressing <End> key during the POST or pressing the <F8> key in BIOS setup menu. No need to enter operating systems like MS-DOS or Windows first.

(@bios is the windows based utility and should be avoided, Windows can crash messing up the flash)

Your motherboard might have a slightly different key but if you watch the screen you should see it in one of the corners.

Once in Qflash you can save the current bios which is usually a good idea in case things go awry. Use a separate usb stick though with it formatted to FAT32.
To update the bios make sure your usb is plugged in and use Qflash to find it and the bios file within.

Any problems post back.
 
Last edited:

57IYSY2v4EDt

New Member
My computer just froze, didn't get a BSOD though. Couldn't even restart the computer, had to hold the power button to turn it off... :cry_smile:
Not sure if there is something in the dump from the W7F Diagnostic Tool but I'm gonna attach it anyway, just in case.
 

Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
My computer just froze, didn't get a BSOD though. Couldn't even restart the computer, had to hold the power button to turn it off... :cry_smile:
Not sure if there is something in the dump from the W7F Diagnostic Tool but I'm gonna attach it anyway, just in case.
Well no dump file was included so we could be getting somewhere. I've seen this kind of behaviour ( BSOD to freezing) before and often running these scans helps.:

File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
 

57IYSY2v4EDt

New Member
Well no dump file was included so we could be getting somewhere. I've seen this kind of behaviour ( BSOD to freezing) before and often running these scans helps.:

File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
I've ran the commands that you posted and there appears to be no errors. :(

 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Thanks for the update. See how you get on and if it does bsod please post the new dump file.
 

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
I was just thinking, when flashing did you load defaults before and after.
 

57IYSY2v4EDt

New Member
I was just thinking, when flashing did you load defaults before and after.
When I flashed it with QFLASH I actually forgot to load defaults. I'll flash it again and will load defaults before and after the install just to make sure that is not causing the problems that I'm having.

Thanks for the update. See how you get on and if it does bsod please post the new dump file.
Will do.

Thank you guys!
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
You shouldn't need to flash the bios again, as i said earlier in this thread just try to remember to do it before and after a flash.
 

57IYSY2v4EDt

New Member
I've got another BSOD (computer got stuck and after couple of minutes it BSOD'ed). As usual, I was just pretty much browsing & watching youtube.

I've attached logs & dump that were obtained using the W7F Diagnostic Tool.
 

Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Hi,
it was the same bugcheck as before.
Code:
===============================================================================
Common Platform Error Record @ ffffa40af8f2c028
-------------------------------------------------------------------------------
Record Id     : 01d3992ee7108197
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 1/29/2018 23:48:33 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffa40af8f2c0a8
Section       @ ffffa40af8f2c180
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   : 0x00000000000906ea
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffa40af8f2c0f0
Section       @ ffffa40af8f2c240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : ea 06 09 00 00 08 10 00 - ff 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  @ ffffa40af8f2c240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffa40af8f2c138
Section       @ ffffa40af8f2c2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 0 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x00000341c22de3a9
  Misc.       : 0x00000341c22de3a9
The above is a check I ran on your processor via the minidump and it looks like your processor may have a hardware issue. ( the other thing you could check is that the pins aren't bent on the cpu socket )
Is it possible to contact the vendor and arrange a replacement?
 

57IYSY2v4EDt

New Member
Hi,
it was the same bugcheck as before.
Code:
===============================================================================
Common Platform Error Record @ ffffa40af8f2c028
-------------------------------------------------------------------------------
Record Id     : 01d3992ee7108197
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 1/29/2018 23:48:33 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffa40af8f2c0a8
Section       @ ffffa40af8f2c180
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   : 0x00000000000906ea
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffa40af8f2c0f0
Section       @ ffffa40af8f2c240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : ea 06 09 00 00 08 10 00 - ff 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  @ ffffa40af8f2c240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffa40af8f2c138
Section       @ ffffa40af8f2c2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 0 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x00000341c22de3a9
  Misc.       : 0x00000341c22de3a9
The above is a check I ran on your processor via the minidump and it looks like your processor may have a hardware issue. ( the other thing you could check is that the pins aren't bent on the cpu socket )
Is it possible to contact the vendor and arrange a replacement?
Hi kemical,

I checked the pins on the board and couldn't see any bent pins when I was reseating the CPU. Guess I'll just have to contact vendor then.
Once again, thank you for helping me!
 
Top