Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\030811-18423-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`030a1e90
Debug session time: Tue Mar 8 17:52:57.804 2011 (UTC - 5:00)
System Uptime: 0 days 2:08:59.396
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800ffcdd90, fffff88002fe86a8, fffff88002fe7f00}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )
Followup: MachineOwner
---------
0: 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: fffff8800ffcdd90, The address that the exception occurred at
Arg3: fffff88002fe86a8, Exception Record Address
Arg4: fffff88002fe7f00, Context Record Address
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!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`0ffcdd90 8b4810 mov ecx,dword ptr [rax+10h]
EXCEPTION_RECORD: fffff88002fe86a8 -- (.exr 0xfffff88002fe86a8)
ExceptionAddress: fffff8800ffcdd90 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000000c4)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88002fe7f00 -- (.cxr 0xfffff88002fe7f00)
rax=0200000000000000 rbx=fffff8a00a3fa980 rcx=fffffa800622d000
rdx=fffffa8005352a00 rsi=fffffa800622d000 rdi=fffffa800622d000
rip=fffff8800ffcdd90 rsp=fffff88002fe88e0 rbp=fffffa8004d30ec0
r8=fffffa800454b701 r9=0000000000000000 r10=0000000000000000
r11=0000000000000174 r12=fffffa8005352a00 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4:
fffff880`0ffcdd90 8b4810 mov ecx,dword ptr [rax+10h] ds:002b:02000000`00000010=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310d0e8
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`0ffcdd90 8b4810 mov ecx,dword ptr [rax+10h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800ffcaed3 to fffff8800ffcdd90
STACK_TEXT:
fffff880`02fe88e0 fffff880`0ffcaed3 : 00000000`00000000 fffffa80`04ae54e8 00000000`000000d7 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4
fffff880`02fe8910 fffff880`0ffe565d : 00000000`00000000 fffff8a0`0a8b3830 fffffa80`00000000 fffffa80`0454b7c0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`02fe8ae0 fffff880`0ffe5398 : fffff880`009eaec0 fffff880`0ffe4d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02fe8cd0 fffff880`0ffe4e96 : 00000000`00000000 fffffa80`04358c90 00000000`00000080 fffffa80`0620e010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02fe8d00 fffff800`03179cce : 00000000`166f4759 fffffa80`0622c620 fffffa80`03ccf040 fffffa80`0622c620 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02fe8d40 fffff800`02ecdfe6 : fffff880`009e6180 fffffa80`0622c620 fffff880`009f0f40 fffff880`01242384 : nt!PspSystemThreadStartup+0x5a
fffff880`02fe8d80 00000000`00000000 : fffff880`02fe9000 fffff880`02fe3000 fffff880`02fe8680 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
STACK_COMMAND: .cxr 0xfffff88002fe7f00 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\031111-22339-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03063e90
Debug session time: Fri Mar 11 00:53:04.360 2011 (UTC - 5:00)
System Uptime: 2 days 2:30:44.936
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff901054f7814, 0, fffff960007e0061, 5}
Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!memcpy+41 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff901054f7814, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960007e0061, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030cf0e8
fffff901054f7814
FAULTING_IP:
cdd!memcpy+41
fffff960`007e0061 8b040a mov eax,dword ptr [rdx+rcx]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88002f06090 -- (.trap 0xfffff88002f06090)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000040001e00 rbx=0000000000000000 rcx=00000000008d7814
rdx=fffff90104c20000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960007e0061 rsp=fffff88002f06228 rbp=0000000000000396
r8=0000000000001ddc r9=0000000000000000 r10=ff1c2324ff2a322f
r11=00000000008d7814 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
cdd!memcpy+0x41:
fffff960`007e0061 8b040a mov eax,dword ptr [rdx+rcx] ds:62c0:fffff901`054f7814=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e48c6f to fffff80002e9e640
STACK_TEXT:
fffff880`02f05f28 fffff800`02e48c6f : 00000000`00000050 fffff901`054f7814 00000000`00000000 fffff880`02f06090 : nt!KeBugCheckEx
fffff880`02f05f30 fffff800`02e9c76e : 00000000`00000000 fffff901`054f7814 fffff8a0`09340900 fffff901`054f7814 : nt! ?? ::FNODOBFM::`string'+0x44891
fffff880`02f06090 fffff960`007e0061 : fffff960`007c4281 00000000`00000000 fffff8a0`021ae000 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`02f06228 fffff960`007c4281 : 00000000`00000000 fffff8a0`021ae000 00000000`00000001 00000000`00000000 : cdd!memcpy+0x41
fffff880`02f06230 fffff960`007c4c26 : fffff900`c00c0020 00000000`00000040 fffff900`c206aa10 fffff900`c1f38a10 : cdd!CopyBits+0xed
fffff880`02f06270 fffff960`007c606c : ffffffff`fffd743e 00000000`0104002b 00000000`00000001 00000000`00000000 : cdd!CddPresentBlt+0x2ae
fffff880`02f069b0 fffff800`0313bcce : 00000000`2dd4431d fffffa80`061ab060 00000000`00000080 fffffa80`0665ab30 : cdd!PresentWorkerThread+0xd00
fffff880`02f06d40 fffff800`02e8ffe6 : fffff880`009e6180 fffffa80`061ab060 fffffa80`03d00b60 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f06d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
cdd!memcpy+41
fffff960`007e0061 8b040a mov eax,dword ptr [rdx+rcx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: cdd!memcpy+41
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7c546
FAILURE_BUCKET_ID: X64_0x50_cdd!memcpy+41
BUCKET_ID: X64_0x50_cdd!memcpy+41
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\031111-22885-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e1f000 PsLoadedModuleList = 0xfffff800`0305ce50
Debug session time: Fri Mar 11 23:22:48.791 2011 (UTC - 5:00)
System Uptime: 0 days 0:10:49.585
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41284, 20000006facc001, 427b, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 020000006facc001
Arg3: 000000000000427b
Arg4: fffff70001080000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41284
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: mbamservice.ex
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ee43b3 to fffff80002e8f740
STACK_TEXT:
fffff880`084967e8 fffff800`02ee43b3 : 00000000`0000001a 00000000`00041284 02000000`6facc001 00000000`0000427b : nt!KeBugCheckEx
fffff880`084967f0 fffff800`02ec0445 : fffff700`01080000 a7b00000`be8cd025 00000000`6facc000 a7b00000`be8cd025 : nt! ?? ::FNODOBFM::`string'+0x4a83
fffff880`08496830 fffff800`02ec2df9 : 00000000`00000000 00000000`6facffff fffffa80`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0x4cc
fffff880`084969f0 fffff800`031a6010 : fffffa80`07484e40 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`08496b10 fffff800`031a641b : 00000980`00000000 00000000`6f9e0000 fffffa80`00000001 fffffa80`03eb2de0 : nt!MiUnmapViewOfSection+0x1b0
fffff880`08496bd0 fffff800`02e8e993 : 00000000`00000000 00000000`00000001 fffffa80`03e9c060 00000000`7ef9e000 : nt!NtUnmapViewOfSection+0x5f
fffff880`08496c20 00000000`7715f95a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0442e718 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7715f95a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4a83
fffff800`02ee43b3 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4a83
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83
BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83
Followup: MachineOwner
---------