BSOD when playing certain games

Page 3 of 4 FirstFirst 1234 LastLast
  1. ArazelEternal's Avatar
    Posts : 318
    Windows 10 Pro x64
       01 Apr 2017 #21

    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.
      My ComputersSystem Spec

  2.    02 Apr 2017 #22

    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.
      My ComputerSystem Spec

  3.    02 Apr 2017 #23

    BSOD again

    Tried to run Deus Ex again. Latest BSOD file.
      My ComputerSystem Spec

  4. Ztruker's Avatar
    Posts : 6,612
    Windows 10 Pro X64 1809 17763.134
       02 Apr 2017 #24

    Same error as before, hardware machine check:
    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.
    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.
    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.

    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.
      My ComputersSystem Spec

  5.    02 Apr 2017 #25


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

  6. Ztruker's Avatar
    Posts : 6,612
    Windows 10 Pro X64 1809 17763.134
       03 Apr 2017 #26

    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.
    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.
      My ComputersSystem Spec

  7.    04 Apr 2017 #27

    Verifier BSOD

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

  8. Ztruker's Avatar
    Posts : 6,612
    Windows 10 Pro X64 1809 17763.134
       05 Apr 2017 #28

    Did you do anything with MBfilt64.sys.?
      My ComputersSystem Spec

  9.    05 Apr 2017 #29

    Yes. I renamed it.
      My ComputerSystem Spec

  10.    05 Apr 2017 #30

    Windows used it's generic HD driver instead.
      My ComputerSystem Spec

Page 3 of 4 FirstFirst 1234 LastLast

Related Threads
Hello, So first of all, I am not a computer wizard. Some terms I might not understand as i've never had a problem like this before, but i'll try to enlist as much information as possible. Since last friday or so, i've suddenly encountered a...
A friend of mine is having bsod issues when playing certain games, example: Rainbox six siege, Battlefield One (BETA) and a few others. Wondering if anyone can give us a clue as to the cause. Windows Format is done, but to no avail,...
BSOD when playing games in BSOD Crashes and Debugging
Hi, I'm getting a DPC Watchdog Violation error when playing DOTA 2, as well as this it also crashes and BSODs on Kerbal Space Program, I used to get infrequent BSODs related to nvlddmkm.sys error but now this happens at the beginning of every game...
Hi, i got this computer about 3~ Weeks ago, and have gotten random BSOD's after that. System Information Bellow Intel Core i5-6600K 3.5Ghz @ 3.5 GeForce GTX960 2gb GDDR5, Physx CUDA 1TB Harddisk 7200RPM 8Gb DDR4 2133Mhz Dual Channel, 2x4gb...
BSOD when playing certain games in BSOD Crashes and Debugging
My laptop been having this problem for this many times. While gaming everyday, have BSOD almost everyday. Screen went blue and won't restart at all. have to manually restart the laptop. The DM Log Collector file is attached. From: Kevin
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 00:50.
Find Us