BSOD MACHINE_CHECK_EXCEPTION during every game

I took out 1 RAM and ran memtest. It didnt show any errors. Also havent had any blue screens while playing with only this RAM. So I assume the one I took out is the faulty one. I´ll try testing it in the slot where the good one is

If the memtest86+ version 5.01 passes for each RAM module tested 1 time in the same DIMM after failing when tested simultaneously then move 1 RAM module to another DIMM and test for 8 or more passes.

If the memtest86+ version 5.01 fails for the 2nd RAM module tested in the same DIMM then you have completed the troubleshooting. If the motherboard is multichannel then the RAM should be replaced with RAM having the same model and SKU.

I am still getting regular freezes after alt tabing out of games even with just the 1 non faulty RAM inside.
After I minimize the game everything freezes and I have to push the power button. Could it be because of only the 1 RAM? maybe it cant handle the games. Or it might just be the game im playing (Total war warhammer 2).
It might be fixed with windowed borderless I imagine? I´ll look into it

Please check all RAM modules in the same DIMM for 8 or more passes.
If the RAM modules do not display any errors when tested in the same DIMM after displaying errors when tested together the DIMM / MB needs to be tested by testing 1 RAM module in another DIMM for 8 or more passes.

Please use a camera or smart phone camera to take pictures and post images into the thread.

I put the RAM I took out into the slot of the good one and ran the test

Still getting blue screens after tabbing out or exiting games, even with just the non faulty RAM inside

The physical RAM was reduced.
The event log displayed dumps that were 9c and 124.
The crash dumps have failed to generate mini dump or memory dump files that can be dubuged.
The last BSOD mini dump was on 9/25/2017.
The last crash was today 10/12/2017

In the left lower corner search type system > on the left pane click advanced system settings >
for performance click settings > click advanced tab > post an image into the thread
for virtual memory click change > post an image into the thread > click cancel then cancel again
for startup and recovery > click settings > post an image into the thread


For 0x124 it is sometimes necessary to perform a vanilla installation of windows to troubleshoot.
Can you perform a clean install and install no applications or drivers.
Only perform windows updates of Microsoft and non-Microsoft drivers.

I could reinstal it I just have no way of backing up all my files

And Im not sure about those errors? I think one of them happened when I restarted to enter BIOS to try memtest again, but did it wrong so I ended up back on the desktrop and restarted again. I got that error then for 1 second.

But the blue screens are definitely still there, but not as common after taking out the bad ram. It used to happen with the majority of demanding games consistently. Now it happens only with the most demanding games. And just as before its when I turn a game off or minimize it

In the bios please check the PSU voltages:
what are each 3.3v, 5v, and 12v values?
What are the CPU voltage and frequency?

The above post #59 displayed BSOD bugcheck Machine Check Exception.
This is BSOD bugcheck 9c and is equivalent to 0x124 WHEA.
This is the same BSOD bugcheck before the removal or the malfunctioning RAM.

To troubleshoot this error please backup all files.
Perform a vanilla type clean installation.
Use a bootable windows 10 iso to install Windows.
Disconnect ethernet and wifi an only install Windows.
Then monitor the computer for bsod.
After a period of time if there are no bsod then update Windows.
Then monitor the computer for bsod with Windows updates.
Then drivers are added slowly and the computer is monitored for bsod.
The aim is to slowly find out the cause and effect for the bsod.
At the same time stress testing can be performed without software applications and other confounding factors.

Code:

Event[9649]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-07-16T13:29:13.060  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-7EEKE55  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009c (0x0000000000000000, 0xffff8d8074ed1820, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6510d431-614e-4c65-b3d3-c22a4d7588a2.

Code:

Event[15856]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-08-20T21:36:41.272  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-7EEKE55  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff8609b2de0028, 0x00000000be000000, 0x000000000100110a). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a7143ef2-5195-47e0-b655-55ee03e2ffca.

Code:

Event[17027]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-08-27T19:29:42.289  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-7EEKE55  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009c (0x0000000000000000, 0xffff87803ead1820, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: aaa74377-6997-4b62-8cb1-6ea2cf12a9ce.

Code:

Event[17081]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-08-27T21:19:35.542  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-7EEKE55  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009c (0x0000000000000000, 0xfffff802adc4eba0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0c1b3a71-90f1-473c-b3fa-a46c974343d5.

Code:

Event[17274]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-08-27T23:07:54.228  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-7EEKE55  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009c (0x0000000000000000, 0xffffcd0180fcb820, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 58401807-6a2c-4d55-9ec3-d2c205f9831e.

Code:

Event[17318]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-08-27T23:18:29.383  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-7EEKE55  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009c (0x0000000000000000, 0xfffff80338c4eba0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: ffe80241-fc4c-4b4c-9ed3-770db442c831.

Code:

Event[20500]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-09-03T20:54:26.702  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-7EEKE55  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009c (0x0000000000000000, 0xffff8f00023c2820, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: da9c20a6-e3bf-4caa-8287-36d337d68c19.

Code:

Event[22823]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-09-25T23:18:01.438  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-7EEKE55  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009c (0x0000000000000000, 0xfffff80037091ba0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 195136dc-0ed3-420f-82d7-11008eebaaf2.