|
|
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\tawny01.20081226-2343\桌面\Mini032609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055b820
Debug session time: Thu Mar 26 16:52:35.000 2009 (GMT+8)
System Uptime: 0 days 6:18:55.560
Loading Kernel Symbols
...............................................................................................
.............
Loading User Symbols
Loading unloaded module list
............................
*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {ed91cc7c, 0, bf8011b3, 0}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k+11b3 )
Followup: MachineOwner
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: ed91cc7c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf8011b3, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: ed91cc7c
FAULTING_IP:
win32k+11b3
bf8011b3 8b11 mov edx,dword ptr [ecx]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x50
PROCESS_NAME: IEXPLORE.EXE
LAST_CONTROL_TRANSFER: from bf803646 to bf8011b3
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
edd3cccc bf803646 bc650198 0000000f 00000000 win32k+0x11b3
edd3cd0c bf80ee49 7e2789e4 edd3cd64 0012eb18 win32k+0x3646
edd3cd58 804df7ec 0012eb90 0012eb50 7c92eb94 win32k!EngFreeUserMem+0x52f5
edd3cd58 7c92eb94 0012eb90 0012eb50 7c92eb94 nt!KiFastCallEntry+0xf8
0012eb50 00000000 00000000 00000000 00000000 0x7c92eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+11b3
bf8011b3 8b11 mov edx,dword ptr [ecx]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47e0df7d
SYMBOL_NAME: win32k+11b3
FAILURE_BUCKET_ID: 0x50_win32k+11b3
BUCKET_ID: 0x50_win32k+11b3
Followup: MachineOwner
---------
kd> !analvze -v
No export analvze found
找不到是什么原因导致win32k.sys这个驱动出错，希望大家帮忙分析下 |
|
发表于 2009-3-26 22:43:58
楼主
）
