Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\windows\minidump\101210-16130-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: f:\Symbols\
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a4f000 PsLoadedModuleList = 0xfffff800`02c8ce50
Debug session time: Tue Oct 12 15:20:00.852 2010 (UTC + 2:00)
System Uptime: 0 days 0:32:42.585
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10E, {b, fffff880045c7620, ffffffffc0000001, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+2a9 )

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

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

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000000b, Driver returned an invalid error code from BuildPagingBuffer.
Arg2: fffff880045c7620
Arg3: ffffffffc0000001
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x10e_b

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800199022f to fffff80002abf740

STACK_TEXT:
fffff880`045c7518 fffff880`0199022f : 00000000`0000010e 00000000`0000000b fffff880`045c7620 ffffffff`c0000001 : nt!KeBugCheckEx
fffff880`045c7520 fffff880`05306f41 : fffffa80`06391000 fffffa80`06391000 ffffffff`ffffffff ffffffff`c0000001 : watchdog!WdLogEvent5+0x11b
fffff880`045c7570 fffff880`05304f80 : fffff8a0`0786a010 fffff8a0`0786a010 00000000`00000000 fffff880`045c7620 : dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0x2a9
fffff880`045c75f0 fffff880`05304d97 : 00000000`00000000 fffffa80`06391000 00000000`00000100 fffff880`00001f40 : dxgmms1!VIDMM_GLOBAL::MapVideoApertureSegmentInternal+0x15c
fffff880`045c7780 fffff880`0530e54e : 00000000`00000100 00000000`00000000 fffff8a0`0786a010 fffff880`00000000 : dxgmms1!VIDMM_GLOBAL::MapVideoApertureSegment+0x16b
fffff880`045c7800 fffff880`0530d5f9 : fffff8a0`0786a010 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_APERTURE_SEGMENT::MapApertureRange+0x62
fffff880`045c7860 fffff880`05301af3 : fffffa80`0430bed0 fffffa80`06391000 fffffa80`06391000 fffff880`053016e8 : dxgmms1!VIDMM_APERTURE_SEGMENT::CommitResource+0x11d
fffff880`045c78b0 fffff880`052fe763 : 00000000`00000000 fffffa80`04202000 00000000`00000000 fffffa80`03fec380 : dxgmms1!VIDMM_GLOBAL::PageInAllocations+0xbb
fffff880`045c7910 fffff880`0531865d : 00000000`00000000 fffff8a0`02ad7780 fffffa80`00000000 fffffa80`03fe83f0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xccf
fffff880`045c7ae0 fffff880`05318398 : fffff880`02f04f40 fffff880`05317d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`045c7cd0 fffff880`05317e96 : 00000000`00000000 fffffa80`03f16010 00000000`00000080 fffffa80`06354010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`045c7d00 fffff800`02d63c06 : 00000000`030b5a32 fffffa80`06355060 fffffa80`03b54040 fffffa80`06355060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`045c7d40 fffff800`02a9dc26 : fffff880`02f00180 fffffa80`06355060 fffff880`02f0afc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`045c7d80 00000000`00000000 : fffff880`045c8000 fffff880`045c2000 fffff880`045c7690 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+2a9
fffff880`05306f41 c78424a00000009bbdffff mov dword ptr [rsp+0A0h],0FFFFBD9Bh

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+2a9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x10e_b_dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+2a9

BUCKET_ID:  X64_0x10e_b_dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+2a9

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