Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\WINDOWS\Minidump\Mini112611-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Nov 26 14:56:20.531 2011 (GMT+1)
System Uptime: 0 days 0:38:49.332
Loading Kernel Symbols
...............................................................
.......................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {bbd10c8d, 0, bf83c6b8, 2}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!xxxCallHook2+214 )
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: bbd10c8d, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf83c6b8, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: bbd10c8d
FAULTING_IP:
win32k!xxxCallHook2+214
bf83c6b8 f644810901 test byte ptr [ecx+eax*4+9],1
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: gg.exe
LAST_CONTROL_TRANSFER: from bf8f631a to bf83c6b8
STACK_TEXT:
acc70790 bf8f631a 03e4a348 00000000 00000001 win32k!xxxCallHook2+0x214
acc707ac bf8e3174 00000000 00000001 00000000 win32k!xxxCallNextHookEx+0x2d
acc70800 bf8f6297 00000003 00000000 00000001 win32k!NtUserfnHkINLPMSG+0x3a
acc7081c 8054161c 00000000 00000001 01a8dee4 win32k!NtUserCallNextHookEx+0xa5
acc7081c 7c90e4f4 00000000 00000001 01a8dee4 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
01a8de10 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!xxxCallHook2+214
bf83c6b8 f644810901 test byte ptr [ecx+eax*4+9],1
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!xxxCallHook2+214
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a
FAILURE_BUCKET_ID: 0x50_win32k!xxxCallHook2+214
BUCKET_ID: 0x50_win32k!xxxCallHook2+214
Followup: MachineOwner
---------
