.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8005777b30, fffffa8005777e10, fffff80002f881e0}

Probably caused by : csrss.exe

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8005777b30, Terminating object
Arg3: fffffa8005777e10, Process image file name
Arg4: fffff80002f881e0, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa8005777b30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

BUGCHECK_STR:  0xF4_C0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`029efb08 fffff800`0300ad02 : 00000000`000000f4 00000000`00000003 fffffa80`05777b30 fffffa80`05777e10 : nt!KeBugCheckEx
fffff880`029efb10 fffff800`02fb3e23 : ffffffff`ffffffff fffffa80`05a0e660 fffffa80`05777b30 fffffa80`05777b30 : nt!PspCatchCriticalBreak+0x92
fffff880`029efb50 fffff800`02f3b77c : ffffffff`ffffffff 00000000`00000001 fffffa80`05777b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17566
fffff880`029efba0 fffff800`02c7d953 : fffffa80`05777b30 fffff880`c0000005 00000000`0194f5d0 fffffa80`05a0e660 : nt!NtTerminateProcess+0x20c
fffff880`029efc20 00000000`7723f97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0194d8c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7723f97a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

Followup: MachineOwner
---------


......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa7fced72dd8, 2, 1, fffff88010bbd55f}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiExecuteMmIoFlip+33 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa7fced72dd8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88010bbd55f, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efb0e0
 fffffa7fced72dd8 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiExecuteMmIoFlip+33
fffff880`10bbd55f 418bd8          mov     ebx,r8d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f8b450 -- (.trap 0xfffff88002f8b450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80056d3010
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88010bbd55f rsp=fffff88002f8b5e0 rbp=0000000000000000
 r8=000000000000003e  r9=000000000000003e r10=0000000000000000
r11=fffff88002f8b8f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgmms1!VidSchiExecuteMmIoFlip+0x33:
fffff880`10bbd55f 418bd8          mov     ebx,r8d
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc2c69 to fffff80002cc3700

STACK_TEXT:  
fffff880`02f8b308 fffff800`02cc2c69 : 00000000`0000000a fffffa7f`ced72dd8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f8b310 fffff800`02cc18e0 : fffff880`02f8b550 fffffa80`056de000 fffffa80`04ea7000 00000000`00020000 : nt!KiBugCheckDispatch+0x69
fffff880`02f8b450 fffff880`10bbd55f : 00000000`00000000 00000000`00000000 fffffa80`056e2bf0 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02f8b5e0 fffff880`10bbda0e : fffffa80`056de000 00000000`00000000 00000000`0000003e 00000000`00000000 : dxgmms1!VidSchiExecuteMmIoFlip+0x33
fffff880`02f8b900 fffff880`10bba638 : fffffa80`056e2bf0 fffffa80`05feba90 fffffa80`05feb550 00000000`00000000 : dxgmms1!VidSchUnwaitFlipQueue+0x146
fffff880`02f8b950 fffff880`10bb9e00 : fffffa80`00000000 fffff880`0fe3ff98 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x214
fffff880`02f8b9f0 fffff880`10bb9c4c : 00000000`00000000 fffffa80`056d3010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`02f8ba40 fffff880`10ac01cf : fffffa80`04c3f480 fffff880`0ff21d3d 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02f8ba90 fffff880`0fecc4ed : fffffa80`04ea7000 fffffa80`04ea7000 00000000`00000000 fffff880`0ffb057d : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02f8bac0 fffffa80`04ea7000 : fffffa80`04ea7000 00000000`00000000 fffff880`0ffb057d fffffa80`04ea7000 : nvlddmkm+0xa34ed
fffff880`02f8bac8 fffffa80`04ea7000 : 00000000`00000000 fffff880`0ffb057d fffffa80`04ea7000 00000000`00000000 : 0xfffffa80`04ea7000
fffff880`02f8bad0 00000000`00000000 : fffff880`0ffb057d fffffa80`04ea7000 00000000`00000000 00000000`00000000 : 0xfffffa80`04ea7000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiExecuteMmIoFlip+33
fffff880`10bbd55f 418bd8          mov     ebx,r8d

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiExecuteMmIoFlip+33

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiExecuteMmIoFlip+33

BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiExecuteMmIoFlip+33

Followup: MachineOwner