Windows 10: New pc build , BSOD ntoskrnl.exe

Greetings! Recently I built my new pc. Have been having some BSOD issues (ntoskrnl.exe). I thought i had it resolved but i tried to play a new game(BlackDesert) and it popped up again. The minidump is attached. So far i have tried old nvidia drivers(359.06) after removing the newest ones with DDU and updating all of the other drivers. I ran the ASUS stress test on the cpu, gpu and memory for two hours and had no errors. All of the hardware is new except for the video card. Have tried reinstalling direct x. This is also the 2nd clean install of windows 10 i have used

At this point i am out of ideas, hopefully someone here will have suggestions.

windows 10 education version
asus z170a motherboard
asus gtx670 gpu [
Trident Z] F4-3200C16Q-16GTZB
corsair rm850i psu
Intel Skylake i5-6600k
Samsung 950 m.2
Samsung 850 EVO x2

:)

 

Blue screen crashes with new pc

It has been about 2 hours since doing a clean boot and I received a new BSOD:

This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802E8DF8834, 0x0, 0xFFFFFFFFFFFFFFFF)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\WINDOWS\system32\ntoskrnl.exe

BlueScreenView highlights ntoskrnl.exe and partmgr.sys as the cause.

Here is the new Dump file Dump.zip

 

Windows 10 Creators Update BSOD kernel crash - UNEXPECTED_KERNEL_MODE_TRAP

Hi,

we're facing same BSOD on all PC's with Creators Update in our Company (to be honest up to today there's 3 Machines in production use right now, we stopped rollout).

Since last update last week (15063.413) crash address changed from "ntoskrnl.exe+16c310" to "ntoskrnl.exe+16c3f0".

May be you can check this, too?

For testing purpose I did a clean VM-Install from MSDN media (Build 1703) and got same BSOD.

I also tested with Inside PreView / FastBuild 2 weeks ago, there I couldn't reproduce BSOD so far (although I didn't check latest release / just upgrading this moment).

You can check my minidumps here:
Minidump

Regards,

Michael