BSOD when playing games

Hello,

I seem to be regulary getting the BSOD when playing games and it's getting very annoying.

Here are some dump files https://mega.nz/#F!JSBmBZSA!-c-i6FwlYsadfbmZ2n9I8Q although I have crashed far more times than this I cant seem to find their dump files.

Any help would be greatly appreciated, let me know of more information I can give and if I have done the dump files wrong. I am running Windows 7 SP1, have an AMD Radeon R9 290 Tri-x and Intel Core i5 4670k.

Thanks.

EDIT: After looking at other topics, I have found WhoCrashed. Below is the Crash Dump Analysis

--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 04/07/2017 13:28:58 your computer crashed
crash dump file: C:\Windows\Minidump\070417-4914-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x5039)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880016FF039, 0xFFFFF8800AD87670, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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.



On Tue 04/07/2017 13:28:58 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltGetStreamHandleContext+0x3C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880016FF039, 0xFFFFF8800AD87670, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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.



On Fri 28/04/2017 18:55:37 your computer crashed
crash dump file: C:\Windows\Minidump\042817-8299-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFF8800426B800, 0xFFFFFA800AA8D340)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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.



On Tue 06/12/2016 12:44:13 your computer crashed
crash dump file: C:\Windows\Minidump\120616-19032-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8800182D20E)
Bugcheck code: 0x50 (0xFFFFFA810DF3B020, 0x0, 0xFFFFF8800182D20E, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
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.