Windows 10: BSOD when playing certain games

I can't fine Trigger 1 + graphics ca. Where is it located?

 

I attempted to play Deus Ex and I got as far as when asked to pick lethal or non-lethal for the first mission and when I clicked on my choice the computer froze. I had to do a had reset. Uploading a new log. Didn't get a BSOD this time.

 

Any USB graphics device?

 

No. I don't have any USB graphics devices. That's what's puzzling. The only USB devices I have is an Eclipse Keyboard and a Rosewill RGM-300 Gaming Mouse. Could it be a driver error? I read that I should run Memtest, Furmark as well as Prime95. Should I go ahead and do that?

 

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.[/quote] 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[/quote] This is almost certainly a CPU error. Definitely run Prime95 and see if it shows anything.

 

Ran Prime95 for two hours. It didn't show anything.

 

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.

 

No. The system isn't overclocked. I have a fresh install of windows 10 home and the only game installed right now is Deus Ex. Before the re-install of Windows I had Cyrsis & Witcher 3 installed. I could play Cyrsis, but not Witcher 3 or Deus Ex. The latest Civiliations doesn't play also. They all start but then I get a BSOD. I sometimes get a BSOD when watching a video also.

 

Tried to run Deus Ex again. Latest BSOD file.

 

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.[/quote] 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[/quote] 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.

 

Ran Verifier. Got BSOD as soon as the computer restarted. See latest log.

 

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 )[/quote] 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.

 

Ran verifier again and nothing really popped up. Tried to play Deus Ex again and got a BSOD after starting to play. See upload.

 

Did you do anything with MBfilt64.sys.?

 

Windows used it's generic HD driver instead.