• Find an incredible deal for Black Friday or Cyber Monday? Share those epic bargains with the community by posting them in this forum thread!

[SOLVED] BSOD caused by MACHINE_CHECK_EXCEPTION

Aug 27, 2019
9
2
15
0
I built a new pc about a month ago now and it has crashed about 8 or 9 times all with the error code MACHINE_CHECK_EXCEPTION. These crashes occur randomly (idle, in game, browsing the web) and I can not seem to figure out exactly is going on in my case, despite looking at countless threads online.

More info about the crash:
Bug check code: 0x0000009c
Parameter 1: 0000000000000000
Parameter 2: ffff9a81
a554ccd0
Parameter 3: 0000000000000000
Parameter 4: 00000000
00000000
Caused by driver: hal.dll
Caused by address: hal.dll+491e1
Crash address: ntoskrnl.exe+1bfcc0
Event ID: 1001

My PC:
Intel Core i5-9600k
Corsair H100i CPU cooler
ASUS Prime Z390-A
Corsair Vengeance 16GB (2x8) 3000Hz
WD NVMe SSD 500GB
Samsung QVO SSD 1TB
MSI GeForce RTX 2070
Corsair RMx 750 W 80+ Gold
Windows 10 64-bit
BIOS Vers. 1105

I have already tried these things to fix this issue but they have not worked:
  • Windows 10 reset
  • Update GPU drivers
  • Update BIOS utilities, chipset, LAN, audio drivers
  • Enable/disable XMP settings for my memory, trying both auto BIOS settings and manual at 3000Hz (its possible I just still don't have some of these setting correct. and yes the voltage is at 1.35)
  • Disabled conflicting audio drivers
  • Update windows and all other system drivers I could find in device manager
  • Ran memtest86+ through multiple passes on both sticks together and separately without error
  • Disabled fast startup
Any opinions, suggestions, or solutions would be greatly appreciated. This is getting quite annoying at this point, thanks.
 

PC Tailor

Distinguished
Herald
I have run the dump files and you can view the full reports here:
Dump 1: https://pste.eu/p/131C.html
Dump 2: https://pste.eu/p/e4z5.html
Dump 3: https://pste.eu/p/WKFM.html
Dump 4: https://pste.eu/p/i1jw.html

Summary of findings:
BugCheck 9C
Probably caused by : intelppm.sys ( intelppm!MWaitIdle+1f )

Bugcheck Description:
MACHINE_CHECK_EXCEPTION
"This bug check indicates that a fatal machine check exception has occurred. In Windows Vista and later operating systems, this bug check occurs only in the following circumstances:
  • WHEA is not fully initialized.
  • All processors that rendezvous have no errors in their registers.
For other circumstances, this bug check has been replaced with bug Check 0x124: WHEA_UNCORRECTABLE_ERROR in Windows Vista and later operating systems.
For more information about Machine Check Architecture (MCA), see the Intel or AMD Web sites."
About your bugcheck:
"A machine check exception is almost solely hardware based. It is possible in rare circumstances for this to be a driver, however it is very unlikely. It is often caused by:
  • Component overheating
  • Unstable overclocking or XMP profile
  • Faulty hardware"
Some things to consider:
I would highly advise you to view the full report above, as this will contain much more detail as to the bugcheck and modules running at the time.
  • It may be worth disabling your XMP to see if the issue persists.
  • Does the issue occur every day? If so, run with a clean boot and see if the issue persists. This will disable all third party drivers so you won't be able to do much.
  • If you have latest BIOS installed, you may want to see if there is an update for your Intel Management Engine as this and your BIOS should be aligned
  • Antivirus can cause all manner of problems too, are you on a paid or free version? It may be worth uninstalling and running on defender temporarily to see if issue persists.
  • All of your stop errors care calling the CPU - which doesn't mean the CPU is to fault necessarily, but that the CPU is calling the error at least.
Whilst I understand it is highly likely this is hardware, we tend to prefer eliminating all software first to prevent you from buying hardware before we'd properly confirmed it. You have a LOT of drivers running so it could be any theoretically.
 
Solution 2 – Run the BSOD Troubleshooter

The next thing we’re going to try here is running Windows 10‘s built-in troubleshooting tool. This tool can be used for dealing with all sorts of issues, including the BSOD problems. So, it could be useful when dealing with the MACHINE CHECK EXCEPTION error, as well.

Here’s how to run Windows 10‘s troubleshooting tool:
  1. Open the Settings app and go to Update & Security section.
  2. Select Troubleshoot from the menu on the left.
  3. Select BSOD from the right pane and click Run the troubleshooter.
  4. Follow the instructions on the screen to complete the troubleshooter.

 
Aug 27, 2019
9
2
15
0
Solution 2 – Run the BSOD Troubleshooter

The next thing we’re going to try here is running Windows 10‘s built-in troubleshooting tool. This tool can be used for dealing with all sorts of issues, including the BSOD problems. So, it could be useful when dealing with the MACHINE CHECK EXCEPTION error, as well.

Here’s how to run Windows 10‘s troubleshooting tool:
  1. Open the Settings app and go to Update & Security section.
  2. Select Troubleshoot from the menu on the left.
  3. Select BSOD from the right pane and click Run the troubleshooter.
  4. Follow the instructions on the screen to complete the troubleshooter.
Its telling me "Windows Online Troubleshooting service is not available for this version of windows." although I have an activated version of Windows 10 Home.
 
Aug 28, 2019
43
0
40
0
I built a new pc about a month ago now and it has crashed about 8 or 9 times all with the error code MACHINE_CHECK_EXCEPTION. These crashes occur randomly (idle, in game, browsing the web) and I can not seem to figure out exactly is going on in my case, despite looking at countless threads online.

More info about the crash:
Bug check code: 0x0000009c
Parameter 1: 0000000000000000
Parameter 2: ffff9a81
a554ccd0
Parameter 3: 0000000000000000
Parameter 4: 00000000
00000000
Caused by driver: hal.dll
Caused by address: hal.dll+491e1
Crash address: ntoskrnl.exe+1bfcc0
Event ID: 1001

My PC:
Intel Core i5-9600k
Corsair H100i CPU cooler
ASUS Prime Z390-A
Corsair Vengeance 16GB (2x8) 3000Hz
WD NVMe SSD 500GB
Samsung QVO SSD 1TB
MSI GeForce RTX 2070
Corsair RMx 750 W 80+ Gold
Windows 10 64-bit
BIOS Vers. 1105

I have already tried these things to fix this issue but they have not worked:
  • Windows 10 reset
  • Update GPU drivers
  • Update BIOS utilities, chipset, LAN, audio drivers
  • Enable/disable XMP settings for my memory, trying both auto BIOS settings and manual at 3000Hz (its possible I just still don't have some of these setting correct. and yes the voltage is at 1.35)
  • Disabled conflicting audio drivers
  • Update windows and all other system drivers I could find in device manager
  • Ran memtest86+ through multiple passes on both sticks together and separately without error
  • Disabled fast startup
Any opinions, suggestions, or solutions would be greatly appreciated. This is getting quite annoying at this point, thanks.
Machine checks are a hardware problem, not a software problem.
https://en.wikipedia.org/wiki/Machine-check_exception#Possible_causes
 
Aug 28, 2019
43
0
40
0
Which hardware do you think it would be? I've already ran memtest with no errors. Would it be a bad CPU? Ive also hear it could be a bad motherboard that not very likely.
Im not sure but might be the type of memorys rams . Whats versión of ram you got.
CORSAIR VENGEANCE RGB
Corsair Vengeance LPX
Try Installing Windows 10 x64 mini might fix the error
 

PC Tailor

Distinguished
Herald
Welcome to the forums my friend!

Please see this guide for enabling minidumps so that you can share the minidumps with us and we can help debug further: https://forums.tomshardware.com/threads/handy-details-to-include-in-blue-screen-of-death-posts.3468965/

Machine Checks are called by the CPU, but aren't ALWAYS hardware. They can often be firmware conflicts with hardware, temperatures, and in the rare case, drivers. So they CAN be a software problem, just rarer. But hardware problem doesn't immediately mean hardware is faulty, but can mean the hardware is conflicting or throttling.

With the dump file we may be able to advise more, but jumping onto random hardware won't help.

  • The most common cause of Machine Checks and WHEA errors are excess temperatures, have you monitored GPU and CPU temps under load?
  • Do you have latest BIOS installed?
  • Do you have latest drivers isntalled direct from the manufacturers website?
  • Are you running any overclock or XMP anywhere at all?
 
Aug 27, 2019
9
2
15
0
Who knows you need to try nother then memory ram first or you might may be able to bypass machine check with lite Windows lite versión has alot of checks exceptions removed
Windows.10.Lite.Edition.v6.x64.2018
Here is the minidump files and system info:
https://1drv.ms/f/s!Alofdnbcga8iuh_3z4ibZSCQlrQu

My system temps are:
CPU: 32C idle / 45-50C under moderate load / 75C under heavy load test
GPU: 50C idle / ~60C under load
RAM: 40C

Yes I do have the latest BIOS installed and the drivers downloaded from the ASUS website. I'm not overclocking my CPU but do have XMP enabled so that I'm able to reach the 3000hz it is capable of.
 

PC Tailor

Distinguished
Herald
I have run the dump files and you can view the full reports here:
Dump 1: https://pste.eu/p/131C.html
Dump 2: https://pste.eu/p/e4z5.html
Dump 3: https://pste.eu/p/WKFM.html
Dump 4: https://pste.eu/p/i1jw.html

Summary of findings:
BugCheck 9C
Probably caused by : intelppm.sys ( intelppm!MWaitIdle+1f )

Bugcheck Description:
MACHINE_CHECK_EXCEPTION
"This bug check indicates that a fatal machine check exception has occurred. In Windows Vista and later operating systems, this bug check occurs only in the following circumstances:
  • WHEA is not fully initialized.
  • All processors that rendezvous have no errors in their registers.
For other circumstances, this bug check has been replaced with bug Check 0x124: WHEA_UNCORRECTABLE_ERROR in Windows Vista and later operating systems.
For more information about Machine Check Architecture (MCA), see the Intel or AMD Web sites."
About your bugcheck:
"A machine check exception is almost solely hardware based. It is possible in rare circumstances for this to be a driver, however it is very unlikely. It is often caused by:
  • Component overheating
  • Unstable overclocking or XMP profile
  • Faulty hardware"
Some things to consider:
I would highly advise you to view the full report above, as this will contain much more detail as to the bugcheck and modules running at the time.
  • It may be worth disabling your XMP to see if the issue persists.
  • Does the issue occur every day? If so, run with a clean boot and see if the issue persists. This will disable all third party drivers so you won't be able to do much.
  • If you have latest BIOS installed, you may want to see if there is an update for your Intel Management Engine as this and your BIOS should be aligned
  • Antivirus can cause all manner of problems too, are you on a paid or free version? It may be worth uninstalling and running on defender temporarily to see if issue persists.
  • All of your stop errors care calling the CPU - which doesn't mean the CPU is to fault necessarily, but that the CPU is calling the error at least.
Whilst I understand it is highly likely this is hardware, we tend to prefer eliminating all software first to prevent you from buying hardware before we'd properly confirmed it. You have a LOT of drivers running so it could be any theoretically.
 
Aug 27, 2019
9
2
15
0
I have run the dump files and you can view the full reports here:
Dump 1: https://pste.eu/p/131C.html
Dump 2: https://pste.eu/p/e4z5.html
Dump 3: https://pste.eu/p/WKFM.html
Dump 4: https://pste.eu/p/i1jw.html

Summary of findings:


About your bugcheck:

"A machine check exception is almost solely hardware based. It is possible in rare circumstances for this to be a driver, however it is very unlikely. It is often caused by:
  • Component overheating
  • Unstable overclocking or XMP profile
  • Faulty hardware"
Some things to consider:
I would highly advise you to view the full report above, as this will contain much more detail as to the bugcheck and modules running at the time.
  • It may be worth disabling your XMP to see if the issue persists.
  • Does the issue occur every day? If so, run with a clean boot and see if the issue persists. This will disable all third party drivers so you won't be able to do much.
  • If you have latest BIOS installed, you may want to see if there is an update for your Intel Management Engine as this and your BIOS should be aligned
  • Antivirus can cause all manner of problems too, are you on a paid or free version? It may be worth uninstalling and running on defender temporarily to see if issue persists.
  • All of your stop errors care calling the CPU - which doesn't mean the CPU is to fault necessarily, but that the CPU is calling the error at least.
Whilst I understand it is highly likely this is hardware, we tend to prefer eliminating all software first to prevent you from buying hardware before we'd properly confirmed it. You have a LOT of drivers running so it could be any theoretically.
Thank you for looking into this. I originally did not have XMP enabled for the first few crashes and then enabled it to see if it fixed the issue, which it didn't. Good thing is it does NOT occur everyday but maybe once or twice a week, which keeps it just at the edge of being annoying and being a serious issue. I'll try updating the Intel Management Engine as you said, and I have a free version of Norton running so I'll also just uninstall that. If the error persists after all this I'll report back with the dumps and hopefully you can assist me further. Thank you.
 
Reactions: PC Tailor

ASK THE COMMUNITY