本帖最后由 扬帆起航 于 2014-7-22 18:24 编辑
这是你的蓝屏分析文件:
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\Mini072114-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*D:\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
Built by: 2600.xpsp_sp3_gdr.120504-1619
Kernel base = 0x804d8000 PsLoadedModuleList = 0x805644c0
Debug session time: Fri Jul 18 20:09:56.656 2014 (GMT+8)
System Uptime: 0 days 0:05:07.199
Loading Kernel Symbols
...........................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bf85fc9e, a770eae4, 0}
Probably caused by : win32k.sys ( win32k!PFEOBJ::vFreepfdg+45 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf85fc9e, The address that the exception occurred at
Arg3: a770eae4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"
FAULTING_IP:
win32k!PFEOBJ::vFreepfdg+45
bf85fc9e f6412180 test byte ptr [ecx+21h],80h
TRAP_FRAME: a770eae4 -- (.trap 0xffffffffa770eae4)
Unable to read trap frame at a770eae4
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from bf85fd72 to bf85fc9e
STACK_TEXT:
a770eb68 bf85fd72 e137ba08 00000000 a770ebdc win32k!PFEOBJ::vFreepfdg+0x45
a770eb88 bf8e0a88 00000000 00000000 00000000 win32k!RFONTOBJ::bDeleteRFONT+0x1d
a770ebac bf8e0f80 a770ebdc 00000000 e12283f8 win32k!PUBLIC_PFTOBJ::bLoadAFont+0x21f
a770ebd4 bf8beb9b e378d730 e12283f8 00000000 win32k!PFTOBJ::bUnloadWorkhorse+0x112
a770ec00 bf8be82e e3811978 00000000 00000000 win32k!vCleanupPrivateFonts+0x4d
a770ec18 bf8bcede e3811978 00000000 00000000 win32k!NtGdiCloseProcess+0xb9
a770ec30 bf8ba08f e3811978 00000000 8784d020 win32k!GdiProcessCallout+0x102
a770ec4c 8058f42f 8791b020 00000000 87941770 win32k!W32pProcessCallout+0x5c
a770ecf0 8058fb61 00000000 a770ed4c 804e84c8 nt!PspExitThread+0x409
a770ecfc 804e84c8 87941770 a770ed48 a770ed3c nt!PsExitSpecialApc+0x22
a770ed4c 804dea0a 00000001 00000000 a770ed64 nt!KiDeliverApc+0x1af
a770ed4c 7c92e514 00000001 00000000 a770ed64 nt!KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following frames may be wrong.
03e7fedc 00000000 00000000 00000000 00000000 0x7c92e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!PFEOBJ::vFreepfdg+45
bf85fc9e f6412180 test byte ptr [ecx+21h],80h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!PFEOBJ::vFreepfdg+45
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52f43e77
FAILURE_BUCKET_ID: 0x8E_win32k!PFEOBJ::vFreepfdg+45
BUCKET_ID: 0x8E_win32k!PFEOBJ::vFreepfdg+45
Followup: MachineOwner
---------
0: kd> !process
Unable to get current process pointer.
0: kd> lmvm win32k
start end module name
bf800000 bf9caa80 win32k # (pdb symbols) D:\Symbols\win32k.pdb\FF84AE9473A94DC3944B18A3366DB0672\win32k.pdb
Loaded symbol image file: win32k.sys
Mapped memory image file: D:\Symbols\win32k.sys\52F43E771caa80\win32k.sys
Image path: \SystemRoot\System32\win32k.sys
Image name: win32k.sys
Timestamp: Fri Feb 07 10:01:27 2014 (52F43E77)
CheckSum: 001CF584
ImageSize: 001CAA80
File version: 5.1.2600.6514
Product version: 5.1.2600.6514
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0404.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft(R) Windows(R) Operating System
InternalName: win32k.sys
OriginalFilename: win32k.sys
ProductVersion: 5.1.2600.6514
FileVersion: 5.1.2600.6514 (xpsp_sp3_qfe.140207-0419)
FileDescription: Multi-User Win32 Driver
LegalCopyright: (C) Microsoft Corporation. All rights reserved.
win32K.sys这个驱动出了问题 |
楼主: Robin1991
楼主
发表于 2014-7-22 18:18:24