|
|
越来越频繁的蓝屏，机箱内也重新擦过，吸尘器吸过等等。每次蓝屏代码都不太一样。请各位大侠帮我分析一下原因，万分感谢！！！！
Microsoft (R) Windows Debugger Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini052809-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d8000 PsLoadedModuleList = 0x80554fc0
Debug session time: Thu May 28 23:03:05.843 2009 (GMT+8)
System Uptime: 0 days 2:00:22.438
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
....................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..........................
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, e35dcd6c, b55d6764, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : win32k.sys ( win32k+fd0f )
Followup: MachineOwner
---------
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: e35dcd6c, The address that the exception occurred at
Arg3: b55d6764, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: win32k
FAULTING_MODULE: 804d8000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"
FAULTING_IP:
+ffffffffe35dcd6c
e35dcd6c 0000 add byte ptr [eax],al
TRAP_FRAME: b55d6764 -- (.trap 0xffffffffb55d6764)
ErrCode = 00000002
eax=00000000 ebx=00000000 ecx=e47077b8 edx=40000000 esi=b55d67dc edi=e35dcd6c
eip=e35dcd6c esp=b55d67d8 ebp=bf80fb66 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
e35dcd6c 0000 add byte ptr [eax],al ds:0023:00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from bf80fd0f to e35dcd6c
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b55d67dc bf80fd0f b55d6854 10018000 00000000 0xe35dcd6c
b55d6818 bf808023 b55d6854 10018000 00000000 win32k+0xfd0f
b55d68a4 bf80810b e5b2e198 00000000 00000002 win32k+0x8023
b55d68bc bf94178a b55d68e0 00000000 00000002 win32k+0x810b
b55d68d8 bf949fbc e47076d0 b55d68f4 b55d6934 win32k+0x14178a
b55d6920 8053e638 2d01174d 144c8fc4 00000000 win32k+0x149fbc
b55d6934 7c92e4f4 badb0d00 144c8fac b55d695c nt+0x66638
b55d6938 badb0d00 144c8fac b55d695c 00000005 0x7c92e4f4
b55d693c 144c8fac b55d695c 00000005 b55d6968 0xbadb0d00
b55d6940 b55d695c 00000005 b55d6968 8062ba21 0x144c8fac
b55d6944 00000000 b55d6968 8062ba21 e34eb968 0xb55d695c
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+fd0f
bf80fd0f 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
SYMBOL_NAME: win32k+fd0f
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
--------- |
|
发表于 2009-5-28 23:38:48
楼主
