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\030711-18015-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`03297e90
Debug session time: Mon Mar 7 16:45:27.025 2011 (UTC - 5:00)
System Uptime: 0 days 6:56:20.103
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d89aba75c1, 0, ac2bf067706777e8, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89aba75c1, Reserved
Arg2: 0000000000000000, Reserved
Arg3: ac2bf067706777e8, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
Debugging Details:
------------------
BUGCHECK_STR: 0x109
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800030d2640
STACK_TEXT:
fffff880`033625d8 00000000`00000000 : 00000000`00000109 a3a039d8`9aba75c1 00000000`00000000 ac2bf067`706777e8 : nt!KeBugCheckEx
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: BAD_STACK
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\030411-21625-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0301f000 PsLoadedModuleList = 0xfffff800`0325ce50
Debug session time: Fri Mar 4 20:39:29.173 2011 (UTC - 5:00)
System Uptime: 0 days 11:21:34.330
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck BE, {fffff88010bb5849, 1b3464121, fffff8800759a660, b}
Probably caused by : hardware ( dxgmms1!VidMmIsAllocationTerminated+4 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff88010bb5849, Virtual address for the attempted write.
Arg2: 00000001b3464121, PTE contents.
Arg3: fffff8800759a660, (reserved)
Arg4: 000000000000000b, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xBE
PROCESS_NAME: ShippingPC-Sto
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800759a660 -- (.trap 0xfffff8800759a660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88010bb58c0 rbx=0000000000000000 rcx=fffffa800749d000
rdx=fffff8a008d17500 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88010ba5e20 rsp=fffff8800759a7f8 rbp=fffff8a007cef300
r8=fffffa8006459820 r9=0000000000000000 r10=fffff8a001ec6901
r11=fffff8a008983000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
dxgmms1!VidMmIsAllocationTerminated+0x4:
fffff880`10ba5e20 084889 or byte ptr [rax-77h],cl ds:0001:fffff880`10bb5849=25
Resetting default scope
MISALIGNED_IP:
dxgmms1!VidMmIsAllocationTerminated+4
fffff880`10ba5e20 084889 or byte ptr [rax-77h],cl
LAST_CONTROL_TRANSFER: from fffff8000310fae2 to fffff8000308f740
STACK_TEXT:
fffff880`0759a4f8 fffff800`0310fae2 : 00000000`000000be fffff880`10bb5849 00000001`b3464121 fffff880`0759a660 : nt!KeBugCheckEx
fffff880`0759a500 fffff800`0308d82e : 00000000`00000001 fffff8a0`07cee000 fffffa80`0749d000 fffff800`031c34d3 : nt! ?? ::FNODOBFM::`string'+0x4237e
fffff880`0759a660 fffff880`10ba5e20 : fffff880`10ae7630 fffff8a0`07cee000 00000000`00000000 fffffa80`07620ba0 : nt!KiPageFault+0x16e
fffff880`0759a7f8 fffff880`10ae7630 : fffff8a0`07cee000 00000000`00000000 fffffa80`07620ba0 00000000`00000000 : dxgmms1!VidMmIsAllocationTerminated+0x4
fffff880`0759a800 fffff880`10ae78e1 : fffff8a0`07cee000 fffff8a0`07cee000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x74
fffff880`0759a850 fffff880`10aeb79c : fffff8a0`09145a00 fffff880`0759aca0 fffffa80`07627000 fffff880`10ab23af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`0759a8a0 fffff880`10aede57 : fffff8a0`07cee000 fffff880`0759a9b0 00000000`fff02001 fffff800`030d9101 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`0759a930 fffff960`001ec6e6 : 00000000`00000000 fffffa80`05fe8600 00000000`00000020 00000000`74365f08 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`0759abf0 fffff800`0308e993 : fffffa80`05fe8600 00000000`00001468 00000000`00000000 fffffa80`07138440 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0759ac20 00000000`7438120a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0d4be7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7438120a
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidMmIsAllocationTerminated+4
fffff880`10ba5e20 084889 or byte ptr [rax-77h],cl
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VidMmIsAllocationTerminated+4
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_dxgmms1.sys
BUCKET_ID: X64_IP_MISALIGNED_dxgmms1.sys
Followup: MachineOwner
---------