EDIT: does it crash in games when you don't have the software that came with the monitor installed?
if it still crash's then have you tried everything at stock then game?
monitors itself can't cause BSOD's
if you get another 4k monitor your pc will still do the still BSOD..
for example, at 1080p on my tv i had no issues gaming, since i upgraded to a 4k monitor and game at 4k res, i get freezes, crash's and it turned out to be a faulty graphic card.
yes a few hours ago it crashed without the monitor drivers and whocrashed came up with this ...
On Sat 28/03/2015 21:54:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032815-10328-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x16C116)
Bugcheck code: 0xF7 (0xFFFFD00205025CE0, 0x850E423636D1, 0xFFFFD466D2205DCD, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 347.88
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 347.88
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 347.88 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_OVERRAN_STACK_BUFFER
These were before the graphics driver BSOD .
On Sat 28/03/2015 20:14:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032815-8781-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x31EEC)
Bugcheck code: 0x24 (0xB500190645, 0xFFFFD001437158E8, 0xFFFFD001437150F0, 0xFFFFF801A26277AB)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Sat 28/03/2015 19:53:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032815-9125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Watchdog was due to the SSD in IDE mode or just the magician software
On Sat 28/03/2015 19:42:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032815-9078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x124 (0x0, 0xFFFFE001FFB8E028, 0xFF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.