MACHINE_CHECK_EXCEPTION (BSOD) with new PC

[Cedders21]

Dear community,


I have self-built a new PC in January and I struggle for 2 months now to make it work properly due to permanent BSOD which are mostly "MACHINE_CHECK_EXCEPTION".


I am playing various games from Epic Games Steam or Origin platforms but also some standalone games like League of Legends.


When does the BSOD occured ?

• When I run steam to play a game or simply download a game
• When I run Epic
• When I tried to install League of Legends (BSOD during UAC to allow setup only)

But, it never occurred while running Origin. For instance, I have played many days 2-3 hours in row with Need for Spead : Heat without any issue.



My configuration

1. be quiet! Dark Power Pro 11 (750 W)
2. Corsair Carbide 270R (Midi Tower)
3. MSI GeForce GTX 1660 Ti GAMING X (6Go)
4. MSI MPG Z390 Gaming Pro Carbon AC (LGA 1151, Intel Z390, ATX)
5. WD Blue (2To, 3.5")
6. Samsung 970 EVO Plus (500Go, M.2 2280)
7. 2x Corsair Vengeance LPX (2x, 8Go, DDR4-3200, DIMM 288)
8. Intel Core I7-9700K (LGA 1151, 3.6Ghz, 8-Core)
9. 3x be quiet! Pure Wings 2 (120mm, 1x)
10. Cooler Master MasterLiquid 240 (2.70cm)

For information :

• The OS is installed on the SDD (point 6)
• The softwares are installed on the SDD (point 6) but the games library (Origin, Steam, Epics) is installed on the HD (point 5)
• The CPU (point 8) is cooled by the water cooling (point 10) which got 2 fans oriented in the front of my midi tower
• The original fan of the midi tower is on the back
• I have added 2 additional fans (point 9) on the top and 1 in front
• RAM is set on slot 2 and 4

What I have tried so far ?


In two months, I had time to try many and many solutions provided on various forums without success. Even worst, 95% of the BSOD does not generate minidump or memorydump files so it was quiet thought to identify the origin of the problem.


Here is things that I've tried :

• Fresh install of windows 10 using only the drivers provided by windows update
• Fresh install of windows 10 using manufacturer drivers
• Removed RAM (point 7) from slot 4; removed RAM from slot 2 replaced by the one from slot 4; reset both ram
• Removed the HD (point 5)
• Removed the GPU (point 3)
• Flashed the BIOS with most recent version (beta)
• Ran sfc /scannow -> no errors
• Ran CHKDSK -> no errors
• Ran memtest86+ -> no errors
• Ran Intel diagnostic tool -> Tests passed with CPU going to 80° Celsius during stress test and back to 33° Celsius straight after
• Support from Miscrosoft which said it comes from heating problem but according to the point above and the fact I've been able to play NFS : Heat without issue it seems weird it is a CPU problem
• Trying to fix problems from Event Viewer (DistributedCom warning remains only)

After many crash, I've finally been able to get some minidump and memorydump that I would be glad to share. What is the best way ?


It is possible I forgot to mention something so just let me know if you need any more information or else.


Thank you in advance for your help.



Meanwhile, here is an output from WhoCrashed :

[COLOR=000000]On Tue 10.03.2020 01:11:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031020-6687-01.dmp
This was probably caused by the following module: [COLOR=000000]hal.dll[/COLOR] (hal+0x49A01)
Bugcheck code: 0x9C (0x0, 0xFFFFF80114634B30, 0x0, 0x0)
Error: [COLOR=000000]MACHINE_CHECK_EXCEPTION[/COLOR]
file path: C:\Windows\system32\hal.dll
product: [COLOR=000000]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=000000]Microsoft Corporation[/COLOR]
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[/COLOR]

[COLOR=000000]On Tue 10.03.2020 01:11:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: [COLOR=000000]ntfs.sys[/COLOR] (Ntfs+0x1****)
Bugcheck code: 0x9C (0x0, 0xFFFFF80114634B30, 0x0, 0x0)
Error: [COLOR=000000]MACHINE_CHECK_EXCEPTION[/COLOR]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [COLOR=000000]Système d’exploitation Microsoft® Windows®[/COLOR]
company: [COLOR=000000]Microsoft Corporation[/COLOR]
description: Pilote du système de fichiers NT
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

[/COLOR]

[COLOR=000000]On Mon 09.03.2020 23:55:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\030920-6171-01.dmp
This was probably caused by the following module: [COLOR=000000]ntoskrnl.exe[/COLOR] (nt+0x1C2380)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801373A188B, 0xFFFFCB0F653511D0, 0x0)
Error: [COLOR=000000]SYSTEM_SERVICE_EXCEPTION[/COLOR]
file path: C:\Windows\system32\ntoskrnl.exe
product: [COLOR=000000]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=000000]Microsoft Corporation[/COLOR]
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.[/COLOR]

Continue reading...