BSOD Win 10 Enterprise - ntkrnlmp.exe and ntoskrnl.exe

Here are the specs

Operating System Windows 10 Enterprise 64-bit
CPU Intel Core i7 4790K @ 4.00GHz 55 °C Haswell 22nm Technology
RAM 16,0GB Dual-Channel DDR3 @ 666MHz (9-9-9-24)
Motherboard Gigabyte Technology Co. Ltd. Z97MX-Gaming 5 (SOCKET 0) 28 °C
Graphics EV2436W (1920x1200@59Hz) EA241WM (1920x1200@59Hz) Intel HD Graphics 4600 (Gigabyte) 4095MB NVIDIA GeForce GTX 960 (MSI) 35 °C ForceWare version: 385.28 SLI Disabled

Storage 232GB Samsung SSD 850 EVO 250GB (SSD) 35 °C 931GB SAMSUNG HD103SJ (SATA) 32 °C 698GB Crucial_CT750MX300SSD1 (SSD) 34 °C 232GB Generic External USB Device (SSD) 35 °C

I clean installed the graphics driver just recently, didnt help
WhoCrashed gives me this:

On Sat 26.08.2017 19:07:32 your computer crashedcrash dump file: C:\WINDOWS\Minidump\082617-8796-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x183B0C) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8030F410B0C, 0xFFFFAC8182B06528, 0xFFFFAC8182B05D70)Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_Mfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a system thread generated an exception which the error handler did not catch.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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 26.08.2017 19:07:32 your computer crashedcrash dump file: C:\WINDOWS\memory.dmpThis was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8030F410B0C, 0xFFFFAC8182B06528, 0xFFFFAC8182B05D70)Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDBug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. Any help? thanks in advance!

BSOD - Posting Instructions

sorry, my bad. here's the attachement.

i have to admit, i dont feel too secure about posting informations like this in the internet. what would you need this for? i am by far no professional, so i was just reading the pop up info and now i am wondering.