BSOD Problems when playing game

We either need the full dump which is located in the %systemroot% directory, you need a 3rd party uploader to upload this file due to the size, or need to wait for another crash to occur.

Code:

Event[1178]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2016-03-16T20:01:19.041
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-SV32KIJ
  Description: 
Unable to produce a minidump file from the full dump file.

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Code:

+++ WER2 +++:
Fault bucket 120349798582, type 4
Event Name: APPCRASH
Response: http://oca.microsoft.com/resredir.aspx?SID=95&iBucketTable=4&iBucket=120349798582&BucketHash=53d7eb388064e562b8f93fe58080c0c9
Cab Id: 0

Problem signature:
P1: dwm.exe // Desktop Window Manager, a system file
P2: 10.0.10586.0
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10:

The corruption is a file called opencl.dll, this is due to driver updates from Nvidia that replaced the opencl.dll from Windows.
This is something you don't have to worry about, because it doesn't affect performance, stability or something :)
If you however would like to resolve this, follow below instructions

The file {file} and the source are corrupted.

Please try following command in admin command prompt

Code:

DISM /Online /Cleanup-Image /RestoreHealth

If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial.

When restorehealth is succesful, run sfc again and let me know what the result is.

The memory dump is corrupted and thus useless unfortunately.
I would suggest to run a memory test to see if the memory could be a cause of corrupted dumps.

Code:

Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Download\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read KLDR_DATA_TABLE_ENTRY at 41074833`00084100 - NTSTATUS 0xC0000141

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x00000000`00000000 PsLoadedModuleList = 0xfffff803`63d64cd0
Debug session time: Wed Mar 16 19:59:57.438 2016 (UTC + 1:00)
System Uptime: 1 days 23:28:01.439
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read KLDR_DATA_TABLE_ENTRY at 41074833`00084100 - NTSTATUS 0xC0000141

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read KLDR_DATA_TABLE_ENTRY at 41074833`00084100 - NTSTATUS 0xC0000141

ReadControl failed - kernel symbols must be loaded first
WARNING: .reload failed, module list may be incomplete
No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Does it matter if the PC is being used while the "Verifier" is on?

Nope

For ~15min my temperature stayed around 90℃ and according to NVIDIA 97℃ is the max. So this also isn't the problem.

You better assume a max of 85C for safety even if Nvidia says the max is 97C, 90C is very high.