Bonjour,
Je cale sur un crash dump sous windows 7 pro dont voici le minidump :
Quelqu'un a-t-il une idée dans quelle direction je dois porter mes recherches ?
[#0000ff]Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [R:\Windows\Minidump\052112-11871-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*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.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82e51000 PsLoadedModuleList = 0x82f9a4d0
Debug session time: Mon May 21 11:46:37.732 2012 (GMT+2)
System Uptime: 0 days 2:54:30.141
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 0, 9edc7cb8, 0}
Probably caused by : ntkrpamp.exe ( nt!KiFastCallEntry+12a )
Followup: MachineOwner
---------
1: 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: 00000000, The address that the exception occurred at
Arg3: 9edc7cb8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction "0x%08lx" emploie l'adresse m moire "0x%08lx". La m moire ne peut pas tre "%s".
FAULTING_IP:
+12a
00000000 ?? ???
TRAP_FRAME: 9edc7cb8 -- (.trap 0xffffffff9edc7cb8)
ErrCode = 00000010
eax=00000031 ebx=00000000 ecx=84db4030 edx=00000000 esi=0567fdc4 edi=0000056c
eip=00000000 esp=9edc7d2c ebp=9edc7d34 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: wfica32.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82e8f21a to 00000000
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
9edc7d28 82e8f21a 0000056c 0567fdc4 76f27094 0x0
9edc7d28 76f27094 0000056c 0567fdc4 76f27094 nt!KiFastCallEntry+0x12a
0567fdc4 00000000 00000000 00000000 00000000 0x76f27094
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiFastCallEntry+12a
82e8f21a f6456c01 test byte ptr [ebp+6Ch],1
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiFastCallEntry+12a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76eb4
FAILURE_BUCKET_ID: 0x8E_nt!KiFastCallEntry+12a
BUCKET_ID: 0x8E_nt!KiFastCallEntry+12a
Followup: MachineOwner---------[/#0000ff]
