Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\050811-30232-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c40e50
Debug session time: Sun May 8 13:18:51.829 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:45.546
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880149b9159, fffff880049f4d08, fffff880049f4560}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveEntryList+25 )
Followup: MachineOwner
---------
3: 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: fffff880149b9159, The address that the exception occurred at
Arg3: fffff880049f4d08, Exception Record Address
Arg4: fffff880049f4560, 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!VidSchiInterlockedRemoveEntryList+25
fffff880`149b9159 4c8918 mov qword ptr [rax],r11
EXCEPTION_RECORD: fffff880049f4d08 -- (.exr 0xfffff880049f4d08)
ExceptionAddress: fffff880149b9159 (dxgmms1!VidSchiInterlockedRemoveEntryList+0x0000000000000025)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880049f4560 -- (.cxr 0xfffff880049f4560)
rax=ff00fa80088f1b80 rbx=fffff880049f4fb0 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8009809f08 rdi=0000000000000000
rip=fffff880149b9159 rsp=fffff880049f4f40 rbp=0000000000000001
r8=fffff880049f4f60 r9=0000000000000000 r10=0000000000000001
r11=fffffa80088f1b80 r12=fffff8a000f34e50 r13=0000000000000001
r14=fffff8a000f2f180 r15=0000000000000002
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010206
dxgmms1!VidSchiInterlockedRemoveEntryList+0x25:
fffff880`149b9159 4c8918 mov qword ptr [rax],r11 ds:002b:ff00fa80`088f1b80=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 2
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 fffff80002cab0e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VidSchiInterlockedRemoveEntryList+25
fffff880`149b9159 4c8918 mov qword ptr [rax],r11
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880149cc9a4 to fffff880149b9159
STACK_TEXT:
fffff880`049f4f40 fffff880`149cc9a4 : 00000000`00000001 00000000`00000001 00000000`00000001 fffff8a0`00f31870 : dxgmms1!VidSchiInterlockedRemoveEntryList+0x25
fffff880`049f4f90 fffff880`149c5677 : fffffa80`098af000 00000000`00000001 fffffa80`09809ef0 fffff8a0`00f42078 : dxgmms1!VIDMM_GLOBAL::xWaitOnDMAReferences+0xc4
fffff880`049f5060 fffff880`149ab260 : fffffa80`098af000 fffff960`000e4300 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0x7e3
fffff880`049f5130 fffff880`14914c63 : fffff880`049f52c0 fffffa80`09894000 fffff900`c0681ee0 fffff880`148b707b : dxgmms1!VidMmBeginCPUAccess+0x28
fffff880`049f5180 fffff880`148fa742 : fffff8a0`00dc24e0 fffff8a0`00dc24e0 fffff8a0`00f33000 fffff900`c0681ee0 : dxgkrnl!DXGDEVICE::Lock+0x287
fffff880`049f51e0 fffff960`00644bda : fffff900`c00c0020 00000000`00000000 00ff0000`00000120 fffff900`c2add2a0 : dxgkrnl!DxgkCddLock+0x236
fffff880`049f5270 fffff960`0064606c : ffffffff`fffd74f6 00000000`0104002b 00000000`00000001 00000000`00000000 : cdd!CddPresentBlt+0x262
fffff880`049f59b0 fffff800`02d18166 : 00000000`03fceaab fffffa80`088019f0 00000000`00000080 fffffa80`09794730 : cdd!PresentWorkerThread+0xd00
fffff880`049f5d40 fffff800`02a53486 : fffff880`02dd5180 fffffa80`088019f0 fffff880`02ddffc0 00000000`00000202 : nt!PspSystemThreadStartup+0x5a
fffff880`049f5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VidSchiInterlockedRemoveEntryList+25
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff880049f4560 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VidSchiInterlockedRemoveEntryList+25
BUCKET_ID: X64_0x7E_dxgmms1!VidSchiInterlockedRemoveEntryList+25
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\050811-30232-01 (2).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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c40e50
Debug session time: Sun May 8 13:18:51.829 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:45.546
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880149b9159, fffff880049f4d08, fffff880049f4560}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveEntryList+25 )
Followup: MachineOwner
---------
3: 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: fffff880149b9159, The address that the exception occurred at
Arg3: fffff880049f4d08, Exception Record Address
Arg4: fffff880049f4560, 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!VidSchiInterlockedRemoveEntryList+25
fffff880`149b9159 4c8918 mov qword ptr [rax],r11
EXCEPTION_RECORD: fffff880049f4d08 -- (.exr 0xfffff880049f4d08)
ExceptionAddress: fffff880149b9159 (dxgmms1!VidSchiInterlockedRemoveEntryList+0x0000000000000025)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880049f4560 -- (.cxr 0xfffff880049f4560)
rax=ff00fa80088f1b80 rbx=fffff880049f4fb0 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8009809f08 rdi=0000000000000000
rip=fffff880149b9159 rsp=fffff880049f4f40 rbp=0000000000000001
r8=fffff880049f4f60 r9=0000000000000000 r10=0000000000000001
r11=fffffa80088f1b80 r12=fffff8a000f34e50 r13=0000000000000001
r14=fffff8a000f2f180 r15=0000000000000002
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010206
dxgmms1!VidSchiInterlockedRemoveEntryList+0x25:
fffff880`149b9159 4c8918 mov qword ptr [rax],r11 ds:002b:ff00fa80`088f1b80=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 2
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 fffff80002cab0e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VidSchiInterlockedRemoveEntryList+25
fffff880`149b9159 4c8918 mov qword ptr [rax],r11
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880149cc9a4 to fffff880149b9159
STACK_TEXT:
fffff880`049f4f40 fffff880`149cc9a4 : 00000000`00000001 00000000`00000001 00000000`00000001 fffff8a0`00f31870 : dxgmms1!VidSchiInterlockedRemoveEntryList+0x25
fffff880`049f4f90 fffff880`149c5677 : fffffa80`098af000 00000000`00000001 fffffa80`09809ef0 fffff8a0`00f42078 : dxgmms1!VIDMM_GLOBAL::xWaitOnDMAReferences+0xc4
fffff880`049f5060 fffff880`149ab260 : fffffa80`098af000 fffff960`000e4300 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0x7e3
fffff880`049f5130 fffff880`14914c63 : fffff880`049f52c0 fffffa80`09894000 fffff900`c0681ee0 fffff880`148b707b : dxgmms1!VidMmBeginCPUAccess+0x28
fffff880`049f5180 fffff880`148fa742 : fffff8a0`00dc24e0 fffff8a0`00dc24e0 fffff8a0`00f33000 fffff900`c0681ee0 : dxgkrnl!DXGDEVICE::Lock+0x287
fffff880`049f51e0 fffff960`00644bda : fffff900`c00c0020 00000000`00000000 00ff0000`00000120 fffff900`c2add2a0 : dxgkrnl!DxgkCddLock+0x236
fffff880`049f5270 fffff960`0064606c : ffffffff`fffd74f6 00000000`0104002b 00000000`00000001 00000000`00000000 : cdd!CddPresentBlt+0x262
fffff880`049f59b0 fffff800`02d18166 : 00000000`03fceaab fffffa80`088019f0 00000000`00000080 fffffa80`09794730 : cdd!PresentWorkerThread+0xd00
fffff880`049f5d40 fffff800`02a53486 : fffff880`02dd5180 fffffa80`088019f0 fffff880`02ddffc0 00000000`00000202 : nt!PspSystemThreadStartup+0x5a
fffff880`049f5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VidSchiInterlockedRemoveEntryList+25
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff880049f4560 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VidSchiInterlockedRemoveEntryList+25
BUCKET_ID: X64_0x7E_dxgmms1!VidSchiInterlockedRemoveEntryList+25
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\050811-27222-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c49000 PsLoadedModuleList = 0xfffff800`02e86e50
Debug session time: Sun May 8 13:47:48.995 2011 (UTC - 4:00)
System Uptime: 0 days 0:20:43.712
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88013ee6e43, fffff88007712f60, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+211e43 )
Followup: MachineOwner
---------
1: 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: fffff88013ee6e43, Address of the instruction which caused the bugcheck
Arg3: fffff88007712f60, 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:
nvlddmkm+211e43
fffff880`13ee6e43 493b5008 cmp rdx,qword ptr [r8+8]
CONTEXT: fffff88007712f60 -- (.cxr 0xfffff88007712f60)
rax=ff00fa8007c5a1e8 rbx=0000000000000000 rcx=fffffa80082daba8
rdx=00000000caf00117 rsi=0000000000000000 rdi=fffffa80096bc298
rip=fffff88013ee6e43 rsp=fffff88007713940 rbp=fffffa80093dde20
r8=ff00fa8007c5a1e8 r9=fffffa80096bc348 r10=00000000caf00117
r11=fffff88007713940 r12=fffff88007713b88 r13=00000000c1d00610
r14=00000000ff010000 r15=00000000caf00117
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0x211e43:
fffff880`13ee6e43 493b5008 cmp rdx,qword ptr [r8+8] ds:002b:ff00fa80`07c5a1f0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: hon.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88013ee6e43
STACK_TEXT:
fffff880`07713940 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x211e43
FOLLOWUP_IP:
nvlddmkm+211e43
fffff880`13ee6e43 493b5008 cmp rdx,qword ptr [r8+8]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+211e43
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d27c6da
STACK_COMMAND: .cxr 0xfffff88007712f60 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nvlddmkm+211e43
BUCKET_ID: X64_0x3B_nvlddmkm+211e43
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\050811-27222-01 (2).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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c49000 PsLoadedModuleList = 0xfffff800`02e86e50
Debug session time: Sun May 8 13:47:48.995 2011 (UTC - 4:00)
System Uptime: 0 days 0:20:43.712
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88013ee6e43, fffff88007712f60, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+211e43 )
Followup: MachineOwner
---------
1: 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: fffff88013ee6e43, Address of the instruction which caused the bugcheck
Arg3: fffff88007712f60, 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:
nvlddmkm+211e43
fffff880`13ee6e43 493b5008 cmp rdx,qword ptr [r8+8]
CONTEXT: fffff88007712f60 -- (.cxr 0xfffff88007712f60)
rax=ff00fa8007c5a1e8 rbx=0000000000000000 rcx=fffffa80082daba8
rdx=00000000caf00117 rsi=0000000000000000 rdi=fffffa80096bc298
rip=fffff88013ee6e43 rsp=fffff88007713940 rbp=fffffa80093dde20
r8=ff00fa8007c5a1e8 r9=fffffa80096bc348 r10=00000000caf00117
r11=fffff88007713940 r12=fffff88007713b88 r13=00000000c1d00610
r14=00000000ff010000 r15=00000000caf00117
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0x211e43:
fffff880`13ee6e43 493b5008 cmp rdx,qword ptr [r8+8] ds:002b:ff00fa80`07c5a1f0=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: hon.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88013ee6e43
STACK_TEXT:
fffff880`07713940 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x211e43
FOLLOWUP_IP:
nvlddmkm+211e43
fffff880`13ee6e43 493b5008 cmp rdx,qword ptr [r8+8]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+211e43
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d27c6da
STACK_COMMAND: .cxr 0xfffff88007712f60 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nvlddmkm+211e43
BUCKET_ID: X64_0x3B_nvlddmkm+211e43
Followup: MachineOwner
---------