BSOD when playing certain games

Is this system overclocked? Ive seen overclocking generate some really strange issues. I had an AMD system I overclocked at one time. The only time it would BSOD was when playing Unreal Tournament 2004, and nothing else. As soon as I reverted the overclock it was fine. It was strange because only the game would cause it, but Prime95 could run all day without an issue.

Same error as before, hardware machine check:

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffbb0e4b41e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000052000402, Low order 32-bits of the MCi_STATUS value.

Code:

3: kd> !errrec ffffbb0e4b41e028
===============================================================================
Common Platform Error Record @ ffffbb0e4b41e028
-------------------------------------------------------------------------------
Record Id     : 01d2a5d4f3b7429e
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/2/2017 12:28:17 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffbb0e4b41e0a8
Section       @ ffffbb0e4b41e180
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   : 0x00000000000306c3
Processor ID  : 0x0000000000000006

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

Local APIC Id : 0x0000000000000006
CPU Id        : c3 06 03 00 00 08 10 06 - 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  @ ffffbb0e4b41e240

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

Error         : Internal unclassified (Proc 3 Bank 4)
  Status      : 0xba00000052000402

It's beginning to look to me like a defective CPU.

Have you tried running Driver Verifier yet? If not, do:

===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to PART TWO and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file.

7 Dumps from 4/2. Only the first at 11:48AM has any data and has verifier active. The next 5 are empty and the last at 2:44PM has vrifier disabled.

The 11:48AM dump shows a problem with MBfilt64.sys.

Code:

BugCheck A, {1100000004, 2, 0, fffff80358a48678}
*** WARNING: Unable to verify timestamp for MBfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
Probably caused by : MBfilt64.sys ( MBfilt64+1817 )

Driver Description: Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver) - Was found in the latest Win8 version available from Realtek on 07Sep2013

It's dated 7/30/2009 11:40:32 PM which is very old. I don't know what driver it's part since it looks like you have the latest Realtek driver installed from here: GA-Z97X-Gaming 3 (rev. 1.0) | Motherboard | GIGABYTE

Needs to be removed I believe. You should be able to rename it in Safe Mode then boot normally and see if everything is ok. If yes then delete the renamed file.

Try Driver Verifier again once that's done.

Did you do anything with MBfilt64.sys.?