BSOD when playing certain games

Details would help BSOD Posting Instructions

Run dm_log_collector again and post the new zip file.

The 3/18 5:18PM dump indicates a problem with t1pusb.sys and mctkmd.sys.

Code:

*** WARNING: Unable to verify timestamp for t1pusb.sys
*** ERROR: Module load completed but symbols could not be loaded for t1pusb.sys

*** WARNING: Unable to verify timestamp for mctkmd.sys
*** ERROR: Module load completed but symbols could not be loaded for mctkmd.sys

Code:

File details of most used file with name t1pusb.sys
Product:  USB Graphics Device (1P)
Company: Magic Control Technology Corp.
Description: USB Graphics Device (1P) Driver

File details of most used file with name mctkmd.sys
Product:     LDDM Kernel Mode Driver for Magic Control Technology Corporation
Company:     Magic Control Technology Corporation
Description:     LDDM Kernel Mode Driver for Magic Control Technology Corporation

The drivers.txt file from the zip says: Trigger 1+ Graphics Ca. If you have such a beast look for new drivers or uninstall if not using.

Any USB graphics device?

Hmmm, I have a feeling I got my dumps mixed up. Just looked again and the only dump I have from you is from 3/17 at 9:59PM, not 3/18 at 5:18PM as I listed before. In this dump, I see:

Code:

BugCheck 124, {0, ffff8d03363ef028, ba000000, 52000402}
Probably caused by : GenuineIntel

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: ffff8d03363ef028, 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 ffff8d03363ef028
===============================================================================
Common Platform Error Record @ ffff8d03363ef028
-------------------------------------------------------------------------------
Record Id     : 01d29e9792221ea6
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/18/2017 1:58:02 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff8d03363ef0a8
Section       @ ffff8d03363ef180
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    @ ffff8d03363ef0f0
Section       @ ffff8d03363ef240
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  @ ffff8d03363ef240

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

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

This is almost certainly a CPU error. Definitely run Prime95 and see if it shows anything.