Re: 求助这种状况怎么办？

WinDbg

求助这种状况怎么办？

菜鸟奥 2013-07-22, 09:43 上午

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: 804de9a5, The address that the exception occurred at
Arg3: abd85cec, Trap Frame
Arg4: 00000000

Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"

FAULTING_IP:
nt!KiSystemServiceAccessTeb+45
804de9a5 0000 add byte ptr [eax],al

TRAP_FRAME: abd85cec -- (.trap 0xffffffffabd85cec)
ErrCode = 00000002
eax=00000000 ebx=a8fe95d2 ecx=a8fe9a94 edx=00100001 esi=0007f848 edi=abd85d3c
eip=804de9a5 esp=abd85d60 ebp=abd85d64 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!KiSystemServiceAccessTeb+0x45:
804de9a5 0000            add     byte ptr [eax],al          ds:0023:00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E

PROCESS_NAME: svchost.exe

MISALIGNED_IP:
nt!KiSystemServiceAccessTeb+45
804de9a5 0000 add byte ptr [eax],al

LAST_CONTROL_TRANSFER: from 7c92e514 to 804de9a5

STACK_TEXT:
abd85d64 7c92e514 badb0d00 0007f83c 00000000 nt!KiSystemServiceAccessTeb+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
0007f830 7c92daea 77e5c672 000000c0 0009ffa0 0x7c92e514
0007f880 77e5a80e 0009ffd8 0007f8a0 77e5a83f 0x7c92daea
0007f88c 77e5a83f 0007f8bc 77db1f70 0007fca0 0x77e5a80e
0007f8a0 77ed5675 0007f8e8 000a0014 000a00a8 0x77e5a83f
0007fc84 77db706c 77db1f70 77db654c 0007fca0 0x77ed5675
0007fc98 77db7023 000a00a8 0007fd90 00008000 0x77db706c
0007fce0 77dc33b6 000a00a8 0007fd90 00008000 0x77db7023
0007fd50 77dc3628 000000bc 0007fd7c 00000216 0x77dc33b6
0007ffd0 805522fa 0007ffc8 88e07930 ffffffff 0x77dc3628
0007fff0 00000000 01002509 00000000 00000000 nt!ExFreePoolWithTag+0x664

STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
804de983-804de987 5 bytes - nt!KiSystemServiceAccessTeb+23
[ 8b 3f 8b 1c 87:e8 c8 23 b1 28 ]
5 errors : !nt (804de983-804de987)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

BUCKET_ID: MEMORY_CORRUPTION_LARGE

Followup: memory_corruption