Why are you telling people to update their BIOS all the time as a first response? That's silly. BIOS updates really aren't necessary unless they fix something that is broken or if the user wants a feature that may have been added in an update.
Code:
3: kd> .cxr ffff800d06bac3a0
rax=0000000000003b89 rbx=0000000000000001 rcx=ffff868ab87a1010
rdx=0000000000000001 rsi=000000002a4cb2c7 rdi=0000000000000001
rip=fffff80138abc846 rsp=ffff800d06bacd90 rbp=0000000000000003
r8=0000000000003b89 r9=ffff868ab87a1010 r10=fffff801200a0f20
r11=0000000000000001 r12=0000000000000001 r13=ffff868a90842870
r14=fffffb287903e310 r15=0000000000000003
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
dxgkrnl!CFlipToken::TraceStateChanged+0x86:
fffff801`38abc846 498bcd mov rcx,r13
There was an exception, specifically an access violation that occurred in the DirectX function while it was doing some graphics-related work. There was an attempt to move r13 to the rcx register, but that's where the access violation hit.
Code:
3: kd> !pte ffff868ab87a1010
VA ffff868ab87a1010
PXE at FFFFE371B8DC6868 PPE at FFFFE371B8D0D150 PDE at FFFFE371A1A2AE18 PTE at FFFFE343455C3D08
Unable to get PXE FFFFE371B8DC6868
We can't get the status of the rcx register's contents because it's only a minidump, so not much to go on. I presume it's invalid memory though and that's why the exception occurred.
I'd first try a complete uninstall of your nvidia drivers, restarting, and then a reinstall of the latest nvidia video card drivers for your system so we can either see if it fixes it or at the very least rule out video drivers.
