BSOD while streaming movies, playing games. Error: 0x0000007f

Please read and follow the instructions here: Blue Screen of Death (BSOD) Posting Instructions

The 2/1 9:59PM dump shows the following:

Code:

BugCheck C4, {2000, fffff802b6904b94, 0, 774e6350}

*** 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+4b94 )

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff802b6904b94, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 00000000774e6350, Pool Tag (if provided).

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

The obne you have is very old, 7/30/2009 11:40:32 PM C:\WINDOWS\system32\drivers\MBfilt64.sys.

There is a fairly new driver available:

Code:

64bits Vista, 
Windows7, 
Windows8,
Windows8.1, 
Windows10 Driver only (Executable file)	R2.81	2017/1/13	217554k	Global

Please update the Realtek driver again.

Several other dumps indicate memory_corruption:

Code:

BugCheck 7F, {8, ffff9a01701a6b30, 4000, fffff80322ac66f3}

Probably caused by : memory_corruption

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffff9a01701a6b30
Arg3: 0000000000004000
Arg4: fffff80322ac66f3

Time to test your RAM. You have 16GB or RAM so it will take 14+ hours to run the memtets86+ for 8 passes which is the recommended number:

===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

   Warning

MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

   Note

MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

The large MEMORY.DMP you uploaded to Mediafire shows this:

Code:

BugCheck 139, {3, ffffcd01647b3170, ffffcd01647b30c8, 0}

Probably caused by : usbaudio.sys ( usbaudio!USBType1CompleteCallback+223 )

Driver Description: C-Media USB Audio Class 1.0 and 2.0 DAC Device Driver
Driver Update Site: USB Audio,PCIe audio,USB audio ic,USB sound chip--C-Media Electronics, Inc.

The driver you have for this is pretty new: Fri Jul 15 22:26:48 2016 but check for a newer one. If none available, you could try rolling back to the previous version in Device Manager.

Did you look for a new USBAUDIO driver?