
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\081913-12183-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: C:\Windows\System32
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e5c6d0
Debug session time: Mon Aug 19 10:20:47.964 2013 (UTC + 2:00)
System Uptime: 0 days 0:28:12.136
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880056326be, fffff880027b5548, fffff880027b4da0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+14e )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880056326be, The address that the exception occurred at
Arg3: fffff880027b5548, Exception Record Address
Arg4: fffff880027b4da0, Context Record Address

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


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

FAULTING_IP: 
dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+14e
fffff880`056326be 48398d90000000  cmp     qword ptr [rbp+90h],rcx

EXCEPTION_RECORD:  fffff880027b5548 -- (.exr 0xfffff880027b5548)
ExceptionAddress: fffff880056326be (dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+0x000000000000014e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: ffffffffffffffff
   Parameter[1]: 0000000000000000
Attempt to unknown address 0000000000000000

CONTEXT:  fffff880027b4da0 -- (.cxr 0xfffff880027b4da0)
rax=fffffa80085e9000 rbx=000000000000000c rcx=000000000002c395
rdx=0000000000000000 rsi=fffffa8009d23c70 rdi=fffff8a0034db850
rip=fffff880056326be rsp=fffff880027b5780 rbp=6d4d695603090309
 r8=fffff880027b5758  r9=0000000000000000 r10=fffff8a00d8b7d70
r11=fffff88004906a08 r12=fffffa8007db7690 r13=0000000000000000
r14=fffff8a002dcaf70 r15=fffff8a0034db878
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+0x14e:
fffff880`056326be 48398d90000000  cmp     qword ptr [rbp+90h],rcx ss:0018:6d4d6956`03090399=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  ffffffffffffffff

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec6100
GetUlongFromAddress: unable to read from fffff80002ec61c0
 0000000000000000 Nonpaged pool

FOLLOWUP_IP: 
dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+14e
fffff880`056326be 48398d90000000  cmp     qword ptr [rbp+90h],rcx

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880056241dd to fffff880056326be

STACK_TEXT:  
fffff880`027b5780 fffff880`056241dd : fffffa80`07db7690 fffff880`0000000c 00000000`00000000 fffff880`027b5900 : dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+0x14e
fffff880`027b5850 fffff880`0561fba3 : fffff8a0`01291010 fffff8a0`01291010 fffffa80`085e9000 fffffa80`0991cbf0 : dxgmms1!VIDMM_GLOBAL::AllocateResourceForPinnedAllocation+0x55
fffff880`027b58d0 fffff880`0561f4b3 : fffff880`027b5c28 00000000`00000000 fffff880`027b5ba0 fffff880`027b5c38 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x19f
fffff880`027b59f0 fffff880`056393ad : 00000000`00000001 fffff880`0560b0e0 fffffa80`085dfd50 fffffa80`085dfd50 : dxgmms1!VidMmiProcessSystemCommand+0x23
fffff880`027b5a20 fffff880`05638538 : fffff880`027b5b80 00000000`00000000 fffffa80`085e1ec0 00000000`00000001 : dxgmms1!VidSchiSubmitSystemCommand+0x39
fffff880`027b5a50 fffff880`0560a786 : 00000000`00000000 fffffa80`085dfd50 fffffa80`085e1ec0 fffffa80`085e1ec0 : dxgmms1!VidSchiSubmitQueueCommand+0x74
fffff880`027b5a80 fffff880`0563aaa3 : fffffa80`085cfaf0 fffffa80`085d6000 fffffa80`085e1ec0 6d4d6956`027b5b60 : dxgmms1!VidSchiSubmitQueueCommandDirect+0x1e6
fffff880`027b5b10 fffff880`0561f5dd : fffffa80`00000001 fffffa80`07db0410 fffffa80`085e9000 fffffa80`085e9000 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x15f
fffff880`027b5b80 fffff880`0561f9f0 : fffff880`027b5ce0 fffff8a0`01291010 fffff880`027b5ce0 fffff8a0`01291010 : dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0xf9
fffff880`027b5bf0 fffff880`0561b0a7 : 00000000`00000000 00000000`00000000 fffffa80`0991cbf0 fffff8a0`05cdd290 : dxgmms1!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x4c
fffff880`027b5c60 fffff880`05601aa7 : fffff8a0`0dcf2a00 fffff8a0`05c6d570 fffff880`027b64d0 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+0x307
fffff880`027b5d50 fffff880`049294bd : 00000000`00000000 fffff880`027b6260 00000000`00000000 fffff8a0`000f8090 : dxgmms1!VidMmOpenAllocation+0xeb
fffff880`027b5da0 fffff880`04922a5a : fffff880`027b6048 fffff8a0`017a5f30 fffff880`027b6220 fffff880`027b6220 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x291
fffff880`027b5e30 fffff880`0492463b : fffff8a0`01273000 fffff880`027b64d0 00000000`00000000 fffff8a0`01273000 : dxgkrnl!DXGDEVICE::CreateAllocation+0x10ae
fffff880`027b6470 fffff880`0492aa34 : 00000000`ffffeea7 fffff900`c00fc79c 00000000`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::CreateStandardAllocation+0x367
fffff880`027b65d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkCddEnable+0x904


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+14e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

STACK_COMMAND:  .cxr 0xfffff880027b4da0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+14e

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+14e

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

