xinlit
新手上路
积分 6
发帖 6
注册 2014-5-12
|
#1 win7x86平台微点8E蓝屏,求解决
以下是Minidump文件分析结果
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Loading Dump File [H:\Minidump\091714-48609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\MyLocalSymbols-7-x86*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.x86fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0x84614000 PsLoadedModuleList = 0x8475d4d0
Debug session time: Wed Sep 17 08:35:35.564 2014 (GMT+8)
System Uptime: 0 days 0:00:28.579
Loading Kernel Symbols
...............................................................
Loading User Symbols
Loading unloaded module list
........
**********************************************
* *
* Bugcheck Analysis *
* *
**********************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 84734008, 92337bc0, 0}
Probably caused by : ntkrpamp.exe ( nt!ExAllocatePoolWithTag+3 )
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: 84734008, The address that the exception occurred at
Arg3: 92337bc0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
nt!ExAllocatePoolWithTag+3
84734008 8bec mov ebp,esp
TRAP_FRAME: 92337bc0 -- (.trap 0xffffffff92337bc0)
ErrCode = 00000000
eax=00000220 ebx=0000000c ecx=8d0acc04 edx=00000000 esi=00000000 edi=0000000c
eip=84734008 esp=92337c34 ebp=92337c68 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!ExAllocatePoolWithTag+0x3:
84734008 8bec mov ebp,esp
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: MPSVC2.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 84699495 to 84734008
STACK_TEXT:
92337c34 84699495 00000000 00000220 20707249 nt!ExAllocatePoolWithTag+0x3
92337c68 846a78d8 0000000c 00000000 8488477e nt!IopAllocateIrpPrivate+0x148
92337c7c 8488477e 0000000c 00000000 b15e3d86 nt!IoAllocateIrp+0x14
92337d08 846518ba 87cd8020 00000000 00000000 nt!NtWriteFile+0x4d6
92337d08 77b67094 87cd8020 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0245eb88 00000000 00000000 00000000 00000000 0x77b67094
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExAllocatePoolWithTag+3
84734008 8bec mov ebp,esp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExAllocatePoolWithTag+3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5147d331
FAILURE_BUCKET_ID: 0x8E_nt!ExAllocatePoolWithTag+3
BUCKET_ID: 0x8E_nt!ExAllocatePoolWithTag+3
Followup: MachineOwner
------------------------------------------------------------------------
========================
以下是MEMORY.DMP文件分析结果
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [H:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\MyLocalSymbols-7-x86*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.x86fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0x84614000 PsLoadedModuleList = 0x8475d4d0
Debug session time: Wed Sep 17 08:35:35.564 2014 (GMT+8)
System Uptime: 0 days 0:00:28.579
Loading Kernel Symbols
...............................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd900c). Type ".hh dbgerr001" for details
Loading unloaded module list
........
0: kd> !analyze -v
**********************************************
* *
* Bugcheck Analysis *
* *
**********************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: 84734008, The address that the exception occurred at
Arg3: 92337bc0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 7ffd900c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd900c). Type ".hh dbgerr001" for details
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
nt!ExAllocatePoolWithTag+3
84734008 8bec mov ebp,esp
TRAP_FRAME: 92337bc0 -- (.trap 0xffffffff92337bc0)
ErrCode = 00000000
eax=00000220 ebx=0000000c ecx=8d0acc04 edx=00000000 esi=00000000 edi=0000000c
eip=84734008 esp=92337c34 ebp=92337c68 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!ExAllocatePoolWithTag+0x3:
84734008 8bec mov ebp,esp
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: MPSVC2.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 846c83be to 846f2c2c
STACK_TEXT:
92337734 846c83be 0000008e c0000005 84734008 nt!KeBugCheckEx+0x1e
92337b50 846524a6 92337b6c 00000000 92337bc0 nt!KiDispatchException+0x1ac
92337bb8 8465245a 92337c68 84734008 badb0d00 nt!CommonDispatchException+0x4a
92337c34 84699495 00000000 00000220 20707249 nt!Kei386EoiHelper+0x192
92337c68 846a78d8 0000000c 00000000 8488477e nt!IopAllocateIrpPrivate+0x148
92337c7c 8488477e 0000000c 00000000 b15e3d86 nt!IoAllocateIrp+0x14
92337d08 846518ba 87cd8020 00000000 00000000 nt!NtWriteFile+0x4d6
92337d08 77b67094 87cd8020 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0245eb88 00000000 00000000 00000000 00000000 0x77b67094
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExAllocatePoolWithTag+3
84734008 8bec mov ebp,esp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExAllocatePoolWithTag+3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5147d331
FAILURE_BUCKET_ID: 0x8E_nt!ExAllocatePoolWithTag+3
BUCKET_ID: 0x8E_nt!ExAllocatePoolWithTag+3
Followup: MachineOwner
----------------
|
※ ※ ※ 本文纯属【xinlit】个人意见,与【 微点交流论坛 】立场无关※ ※ ※
|
|
|