Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e12000 PsLoadedModuleList = 0x82f5a810
Debug session time: Fri Nov 26 11:11:34.799 2010 (GMT-5)
System Uptime: 0 days 2:24:57.376
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.......
0: kd> !Analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F7, {ac2e12c5, 312e12c5, ced1ed3a, 0}
Probably caused by : ntkrpamp.exe ( nt!__report_gsfailure+24 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: ac2e12c5, Actual security check cookie from the stack
Arg2: 312e12c5, Expected security check cookie
Arg3: ced1ed3a, Complement of the expected security check cookie
Arg4: 00000000, zero
Debugging Details:
------------------
DEFAULT_BUCKET_ID: GS_FALSE_POSITIVE_MISSING_GSFRAME
SECURITY_COOKIE: Expected 312e12c5 found ac2e12c5
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xF7
PROCESS_NAME: WinRAR.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: ace7faf0 -- (.exr 0xfffffffface7faf0)
ExceptionAddress: 8580222b (fltmgr!FltpPerformPostCallbacks+0x00000151)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00bf4184
Attempt to read from address 00bf4184
TRAP_FRAME: ace7fb44 -- (.trap 0xfffffffface7fb44)
ErrCode = 00000000
eax=00bf417c ebx=881d19e0 ecx=00000000 edx=00000020 esi=881d1a38 edi=881d1980
eip=8580222b esp=ace7fbb8 ebp=ace7fc08 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
fltmgr!FltpPerformPostCallbacks+0x151:
8580222b 8b4808 mov ecx,dword ptr [eax+8] ds:0023:00bf4184=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 82ee0999 to 82eeed10
STACK_TEXT:
ace7f59c 82ee0999 000000f7 ac2e12c5 312e12c5 nt!KeBugCheckEx+0x1e
ace7f5bc 82e4bcbd 00000000 00000000 00000000 nt!__report_gsfailure+0x24
ace7f5e4 82e7a822 ace7faf0 ace7fcf8 ace7f6d0 nt!_except_handler4+0x49
ace7f608 82e7a7f4 ace7faf0 ace7fcf8 ace7f6d0 nt!ExecuteHandler2+0x26
ace7f6c0 82ecf352 ace7faf0 ace7f6d0 00010017 nt!ExecuteHandler+0x24
ace7fad4 82e56036 ace7faf0 00000000 ace7fb44 nt!KiDispatchException+0x17c
ace7fb3c 82e55fea ace7fc08 8580222b badb0d00 nt!CommonDispatchException+0x4a
ace7fbc0 85804fec 8a0e7990 ace7fac0 003febc4 nt!Kei386EoiHelper+0x192
ace7fc08 858051e6 001d1980 000e7990 ace7fca4 fltmgr!FltpPerformFastIoCall+0x22e
ace7fc20 8a817dcf 00e7fc44 000e7990 85817c6c fltmgr!FltpPassThroughFastIo+0xa8
WARNING: Frame IP not in any known module. Following frames may be wrong.
ace7fc64 83050477 8a0e7990 ace7fcac 003febc4 0x8a817dcf
ace7fd08 82e5544a 8bbe79b0 00000000 00000000 nt!NtWriteFile+0x342
ace7fd08 002764f4 8bbe79b0 00000000 00000000 nt!KiFastCallEntry+0x12a
772cf004 00000000 00000000 00000000 00000000 0x2764f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!__report_gsfailure+24
82ee0999 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!__report_gsfailure+24
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
FAILURE_BUCKET_ID: 0xF7_MISSING_GSFRAME_nt!__report_gsfailure+24
BUCKET_ID: 0xF7_MISSING_GSFRAME_nt!__report_gsfailure+24
Followup: MachineOwner
---------
Debug session time: Fri Nov 26 08:12:34.504 2010 (GMT-5)
System Uptime: 0 days 3:18:48.081
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
......
1: kd> !Analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {1f, a91ee648, 0, 6d6afa}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+de )
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: 0000001f, The subtype of the bugcheck:
Arg2: a91ee648
Arg3: 00000000
Arg4: 006d6afa
Debugging Details:
------------------
BUGCHECK_STR: 0x10e_1f
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 85c01276 to 82eedd10
STACK_TEXT:
897d9a74 85c01276 0000010e 0000001f a91ee648 nt!KeBugCheckEx+0x1e
897d9a9c 8e587c6e 00000000 8b9d2c18 a50cd984 watchdog!WdLogEvent5+0xc6
897d9ab8 8e5899be 00000000 a7047298 00000c3a dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xde
897d9bb8 8e5a093e a98fa9f0 00000000 8a04bf60 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xa68
897d9d18 8e5a122f 825e5a78 8a145580 897d9d3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0
897d9d28 8e5a14cc 825e5a78 82e4d3f1 9e973008 dxgmms1!VidSchiSubmitQueueCommand+0x61
897d9d3c 8e5a1573 9e973008 00000000 9e971710 dxgmms1!VidSchiRun_PriorityTable+0x24
897d9d50 8301f6d3 9e973008 b853b4fd 00000000 dxgmms1!VidSchiWorkerThread+0x7f
897d9d90 82ed10f9 8e5a14f4 9e973008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+de
8e587c6e c74510c5f3ffff mov dword ptr [ebp+10h],0FFFFF3C5h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+de
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc265
FAILURE_BUCKET_ID: 0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+de
BUCKET_ID: 0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+de
Followup: MachineOwner
---------