BSOD Crash when in Modern 2016 games such as Fallout 4, and more

I've gotten BSOD when playing games and they happen on Modern games 15 minutes into playing sometimes sooner. I thought it was the drivers and updated as much as possible but still it does it. I've run whocrash and it comes up with something to this effect below -

Fri 7/1/2016 2:41:51 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\063016-28015-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!GreUnlockVisRgn+0x48)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8036EA5CFE2, 0xFFFFD0008D9211F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
---------------------------------------------------------------------------------------------
There are more crashes but this is the most recent of the crashes. I've tried to close out of teamviewer as I've heard that effects games. I'm also using Steam for these games. I tried SFC scan now test and memory diagnostic test and didn't find anything.

This isn't a temp issue as I've ran the game along with speccy and gpu teak and neither show that they are only running from 38deg C to about 42-44 deg C.

I cannot think of anything else at this moment. I've tried reinstalling but it was to win7 as it did run with less crashing.. An when I updated back up to Win10 it didn't crash as much as it did previous Win 7 to Win10 which was almost random. So it has been fixed better than the previous installtion.

Thanks for any Help - Sean

Ztruker said:

The 6/30 9:05PM dump points to xusb22.sys dated 10/30/2015. This belongs to the Microsoft Xbox 360 Common Controller for Windows Driver.
There is an updated driver 6/26/2016 from MS in the upcoming Redstone release scheduled for August 4th I believe.

I don't know if this driver is the actual cause of a problem as normally MS files are not. Usually something else is the actual culprit. In this case I wonder since the XBOX support is still fairly new. Also I don't see anything in any of the dumps I've looked at that point to anything else.

Nothing else useful in the dumps I looked at. Give Driver Verifier a try, see if that flushes out any driver problems:

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

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 BSOD with a mini dump that will tell us what driver caused it.

Thank you for getting back with me Ztruker. OK, I did the Driver Verifier and added the Restore Point per requested. Luckly I did the restore point because once Restarted it hit a IO something BSOD but before I could write it down it restarted. To which it did about another crash as I was trying to get back into windows. Also cmd Prompt disable Driver Verifier didn't work and it crashed again with Service System Exception and Finally I had to do a System Restore point which worked and I'm back up and running. I've attached the new information below.

Thank you for your Help - Sean

Ztruker said:

Good dump, shows Verifier enabled. Indicates a problem with MBfilt64.sys which belongs to Audio Driver from Creative Technology Ltd. It's quite old and needs to be updated:

Code:

kd> lmvm MBfilt64
start             end                 module name
fffff800`485e0000 fffff800`485ee000   MBfilt64 T (no symbols)           
    Loaded symbol image file: MBfilt64.sys
    Image path: \SystemRoot\system32\drivers\MBfilt64.sys
    Image name: MBfilt64.sys
    Timestamp:        Thu Jul 30 23:40:32 2009 (4A7267B0)
    CheckSum:         00013EDE
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The only audio driver I see on the MSI web site is for Realtek: Support For 990FXA-GD80 | MSI USA | Motherboard - The world leader in motherboard design

Attachment 87979

Try it and see if it installs and fixes the problem.

I wanted to let you know that the problem was fixed Thank you. The problem was not only the memory which was 1866 mhz and was considered OC on the board. When replaced with 1600mhz memory and udated the motherboard bios. Windows was corrupt and reinstalled that. Watch Dogs and other graphics intense games work and no random BSOD's