Whea uncorrectable error & machine check exception

[h4x0r4g3]

I built my PC in August 2016, no problems since then. A few days ago i got a WHEA UNCORRECTABLE ERROR while using it, and when trying to restart it I got a MACHINE CHECK ERROR. Since then everytime i've tried to turn it on it either gives me a WHEA UNCORRECTABLE ERROR after windows 10 launches, or after about 2 minutes of usage.

I've gotten into the BIOS and it seems stable there, was able to stay there for about 15 min before attempting to launch windows only for another whea error immediately upon the windows splash screen. CPU temp was below 40 when that happened, voltage ranges from 0.720 to ~1.2 depending on usage.

I've also tried opening and cleaning up the fans & coolers, but the problem still persists.

CPU - i6700
Mobo- Asus H170-PRO
RAM- 2X 8GB Corsair Vengeance DDR4 2133Hz
PSU- Cooler Master 500W v2


Downloaded BlueScreenView, here's some info (All the variables are the same each time except Parameter 2, I've included all 4 inside.)
==================================================
Dump File : 021117-5015-01.dmp
Crash Time : 11/02/2017 10:20:57
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2(1) : ffffc00b`e0874028
Parameter 2(2) : ffffc58b`8caba028
Parameter 2(3) : ffffc08a`ff070028
Parameter 2(4) : ffffe30b`d055b028
Parameter 3 : 00000000`be000000
Parameter 4 : 00000000`00800400
Caused By Driver : hal.dll
Caused By Address : hal.dll+3627f
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.206 (rs1_release.160915-0644)
Processor : x64
Crash Address : ntoskrnl.exe+14a6f0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\021117-5015-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 14393
Dump File Size : 428,076
Dump File Time : 11/02/2017 14:40:30
==================================================

 

[Colif]

If PC stayed on for more than 2 minutes I would suggest updating BIOS but not going to do that, just brick motherboard going there...

Have you checked the CPU and seen if any bent pins between it and motherboard

WHEA (Windows Hardware Error Architecture) errors are normally CPU errors but sometimes can be USB devices or PCI cards.

I would suggest you try this: http://www.tcsscreening.com/files/users/IPDT_LiveUSB/index.html

 

[h4x0r4g3]

If PC stayed on for more than 2 minutes I would suggest updating BIOS but not going to do that, just brick motherboard going there...

Have you checked the CPU and seen if any bent pins between it and motherboard

WHEA (Windows Hardware Error Architecture) errors are normally CPU errors but sometimes can be USB devices or PCI cards.

I would suggest you try this: http://www.tcsscreening.com/files/users/IPDT_LiveUSB/index.html

Thanks for your suggestion, I read on a seperate thread that some users found success with disabling Intel Turbo Boost. I've tried that, and I've not experienced any crashes since then. Would running this test still be useful?

 

[Colif]

It will show you if CPU is fine or not. I would test it just to see if reason you can't run turbo is a fault of the CPU itself.

 

[h4x0r4g3]

It will show you if CPU is fine or not. I would test it just to see if reason you can't run turbo is a fault of the CPU itself.

--- IPDT64 - Revision: 4.0.0.29
--- IPDT64 - Start Time: 14/02/2017 20:40:43

--------------------------------------------------------------------
-- Testing
--------------------------------------------------------------------
CPU 1 - SPBC - Pass.
CPU 1 - Genuine Intel - Pass.
CPU 1 - BrandString - Pass.
CPU 1 - Floating Point - Pass.
CPU 1 - Prime Number - Pass.
CPU 1 - Cache - Pass.
CPU 1 - MMXSSE - Pass.
CPU 1 - FMA - Pass.
CPU 1 - AVX - Pass.
CPU 1 - IMC - Pass.
CPU 1 - PCH - Pass.
CPU 1 - IGD - Pass.
CPU 1 - GFX - Pass.
CPU 1 - CPULoad - Pass.
CPU 1 - CPU Frequency - Pass.

IPDT64 Passed
--- IPDT64 - Revision: 4.0.0.29
--- IPDT64 - End Time: 14/02/2017 20:45:42

--------------------------------------------------------------------
PASS

Expected CPU Frequency is -- 3.40
Detected CPU Frequency is -- 3.3898

Expected Base Clock -- 100 MHz
Detected Base Clock -- 102.721 MHz

Everything seems fine according to the test, is there anything else I could do to further diagnose the issue? I suppose I could try enabling Turbo Boost again to check if it still gives errors, but that doesn't seem to provide much information.

 

[Colif]

Check you have the latest BIOS for PC, Version 3016 is the latest on Asus web site dated 29 Dec 2016, its possible an update would fix the problem without you needing to disable turbo boost - I only suggest this since PC seems to work for you now?

If you need to upgrade BIOS, download the zip files, extract its contents to a USB. Boot into bios and go to the advanced view, there should be a tools menu which has the bios update utility. put USB with cap file into PC and choose it. PC will update BIOS and restart, you will need to go into BIOS to set defaults again after the upgrade.

I would see if you get BSOD with default settings before turning turbo off again.

 

[h4x0r4g3]

Check you have the latest BIOS for PC, Version 3016 is the latest on Asus web site dated 29 Dec 2016, its possible an update would fix the problem without you needing to disable turbo boost - I only suggest this since PC seems to work for you now?

If you need to upgrade BIOS, download the zip files, extract its contents to a USB. Boot into bios and go to the advanced view, there should be a tools menu which has the bios update utility. put USB with cap file into PC and choose it. PC will update BIOS and restart, you will need to go into BIOS to set defaults again after the upgrade.

I would see if you get BSOD with default settings before turning turbo off again.

Oh mine's actually the H170 PRO, updated it in the additional post.
https://www.asus.com/sg/Motherboards/H170-PRO/HelpDesk_Download/

The current BIOS version is 0903, so it's pretty outdated from Dec 2015. There were no issues from Aug 2016 till now though, is it still likely/possible to be the motherboard? I would prefer to avoid flashing the BIOS in case anything goes wrong somewhere.

Thanks for your guidance so far, it's been extremely useful

 

[Colif]

I should have asked since i saw it under the gamer model.

Two of the bios updates since the version you have say they improve stability, the last two just allow usage of the latest CPU so not as essential. I can't force you to upgrade BIOS, if you happy not using turbo boost you could continue how you are now. All turbo does is increases the CPU speed under certain circumstances.

It seems odd it only started happening this week, did you update any drivers recently?

Check you have latest chipset drivers for Motherboard as well, they might effect it somehow. Latest are from December. They might help.

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

I don't normally ask for dumps on a WHEA error but it might give us a clue.

 

[h4x0r4g3]

I should have asked since i saw it under the gamer model.

Two of the bios updates since the version you have say they improve stability, the last two just allow usage of the latest CPU so not as essential. I can't force you to upgrade BIOS, if you happy not using turbo boost you could continue how you are now. All turbo does is increases the CPU speed under certain circumstances.

It seems odd it only started happening this week, did you update any drivers recently?

Check you have latest chipset drivers for Motherboard as well, they might effect it somehow. Latest are from December. They might help.

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it
I don't normally ask for dumps on a WHEA error but it might give us a clue.

Yup it's pretty odd, I didn't install/update any drivers anytime this year. Something I noticed was that about 5 seconds before the BSOD my mouse, keyboard and headphones would stop working but I just assumed that was just the system dying. Is this relevant?

I haven't updated the chipset drivers since building the PC either, should I proceed first or check the dumps first?

Dumps (hope this is correct): https://www.dropbox.com/sh/v2sr2acd7tywiwq/AADSSGfvlbfkywjhYqfAvhrAa?dl=0

 

[Colif]

its possible windows 10 has updated drivers and started the ball rolling. You could look in settings/update & security/windows update - update history and see if you got anything new around time problem started.. not that the updates tell you what they did. Last one I got was my GPU and I don't even remember getting it...

It could be the chipset driver update would need the new BIOS to run with, as its likely BIOS has new features now to support the Series 7 chips, and chipset would activate them on those CPU's. MIght not help you but it could be a matching set

I can't read the dumps but others around here can so see if anyone looks in today.