SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code. Your display drivers are a little aged but they weren't flagged in the dump. You might check for an update. Also consider what was already mentioned.
Drivers:
Code:
fffff880`05e71000 fffff880`05e8c000 AtihdW76 AtihdW76.sys Tue Sep 24 19:23:49 2013 (52422D15)
fffff880`0481d000 fffff880`04fd9000 atikmdag atikmdag.sys Wed Sep 29 21:55:51 2010 (4CA3FC37)
fffff880`02d0a000 fffff880`02d54000 atikmpag atikmpag.sys Wed Sep 29 21:13:37 2010 (4CA3F251)
fffff880`019d5000 fffff880`019dd000 AtiPcie64 AtiPcie64.sys Wed Mar 10 08:33:45 2010 (4B97ADC9)
I have some virtual drives mounted
Yes, that's often a cause of errors due to how the Daemons fudge the DVD drive.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88003731e30, fffff8800a1f6060, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmIsAllocationTerminated+14 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88003731e30, Address of the instruction which caused the bugcheck
Arg3: fffff8800a1f6060, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
dxgmms1!VidMmIsAllocationTerminated+14
fffff880`03731e30 488b1a mov rbx,qword ptr [rdx]
CONTEXT: fffff8800a1f6060 -- (.cxr 0xfffff8800a1f6060)
rax=fffff880037418c0 rbx=fffff8a017355000 rcx=fffffa8006044000
rdx=0000000000000000 rsi=fffff8a0118064f0 rdi=fffff8a01240c580
rip=fffff88003731e30 rsp=fffff8800a1f6a40 rbp=fffff8a017356300
r8=fffffa8004c6db50 r9=0000000000000050 r10=fffff88002f64780
r11=fffff8a0163d8330 r12=0000000000000001 r13=fffff8a00d252600
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgmms1!VidMmIsAllocationTerminated+0x14:
fffff880`03731e30 488b1a mov rbx,qword ptr [rdx] ds:002b:00000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: Crysis.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88003673630 to fffff88003731e30
STACK_TEXT:
fffff880`0a1f6a40 fffff880`03673630 : fffff8a0`17355000 fffff8a0`17356300 fffff8a0`118064f0 00000000`00000799 : dxgmms1!VidMmIsAllocationTerminated+0x14
fffff880`0a1f6a70 fffff880`0367959b : 00000000`00000799 00000000`00000001 fffff880`0a1f6ca0 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x74
fffff880`0a1f6ac0 fffff960`002711ee : 00000000`0008e2e0 00000000`40000b40 00000000`4dcec020 00000000`000007d3 : dxgkrnl!DxgkCreateAllocation+0x40b
fffff880`0a1f6bf0 fffff800`032c8e53 : 00000000`00000001 00000000`4dcec020 fffffa80`040bb101 00000000`00000004 : win32k!NtGdiDdDDICreateAllocation+0x12
fffff880`0a1f6c20 00000000`750c13aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x750c13aa
FOLLOWUP_IP:
dxgmms1!VidMmIsAllocationTerminated+14
fffff880`03731e30 488b1a mov rbx,qword ptr [rdx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VidMmIsAllocationTerminated+14
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13
STACK_COMMAND: .cxr 0xfffff8800a1f6060 ; kb
FAILURE_BUCKET_ID: X64_0x3B_dxgmms1!VidMmIsAllocationTerminated+14
BUCKET_ID: X64_0x3B_dxgmms1!VidMmIsAllocationTerminated+14
Followup: MachineOwner