[LOGICIEL] Analyse fichier .dmp

[zstef]

Bonjour,

après plantage au démarage windows écran bleu ... et ne trouvant pas l'origine, j'ai été chercher le fichiers . dmp dans le répertoire Minidump

N'ayant pas les outils pour le lire si qqun veut bien de donner un coup de main,

http://www.yousendit.com/download/Y1Rxak85UnFqV0IzZUE9PQ

merci !

[Drak]

Pourquoi ne pas aller directement lire l'observateur d'événements ? moins compliqué que d'essayer de décrypter le fichier .dmp

[XZombi]

Après analyse, tu as XP SP3 avec probablement une carte nVidia. Désinstalle les drivers de ta carte graphique et réinstalle les.

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [F:\Autre\Mini080109-05.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 XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Sat Aug  1 12:39:49.703 2009 (GMT-4)
System Uptime: 0 days 0:00:57.609
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
....
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 80527ef8, f77ba360, 0}

Probably caused by : nv4_mini.sys ( nv4_mini+4ad24 )

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: 80527ef8, The address that the exception occurred at
Arg3: f77ba360, Trap Frame
Arg4: 00000000

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


OVERLAPPED_MODULE: Address regions for 'rdbss' and 'serial.sys' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction   0x%08lx emploie l'adresse m moire 0x%08lx. La m moire ne peut pas  tre en  tat

FAULTING_IP: 
nt!READ_REGISTER_ULONG+4
80527ef8 8b02            mov     eax,dword ptr [edx]

TRAP_FRAME:  f77ba360 -- (.trap 0xfffffffff77ba360)
ErrCode = 00000000
eax=040041c0 ebx=10010701 ecx=f557d000 edx=0558d700 esi=0558d700 edi=00000000
eip=80527ef8 esp=f77ba3d4 ebp=86e7c008 iopl=0     vif nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00090206
nt!READ_REGISTER_ULONG+0x4:
80527ef8 8b02            mov     eax,dword ptr [edx]  ds:0023:0558d700=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  5

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  csrss.exe

LAST_CONTROL_TRANSFER:  from f6f1cd24 to 80527ef8

STACK_TEXT:  
f77ba3d0 f6f1cd24 0558d700 86e7b368 f6f3b63f nt!READ_REGISTER_ULONG+0x4
WARNING: Stack unwind information not available. Following frames may be wrong.
f77ba3d8 86e7b368 f6f3b63f 86e7c008 86e7b368 nv4_mini+0x4ad24
f77ba3dc f6f3b63f 86e7c008 86e7b368 10010701 0x86e7b368
f77ba3e0 86e7c008 86e7b368 10010701 86e7b368 nv4_mini+0x6963f
f77ba3e4 86e7b368 10010701 86e7b368 86e6f000 0x86e7c008
f77ba3e8 10010701 86e7b368 86e6f000 00000000 0x86e7b368
f77ba3ec 86e7b368 86e6f000 00000000 f77ba4a4 0x10010701
f77ba3f0 86e6f000 00000000 f77ba4a4 f6f7190b 0x86e7b368
f77ba3f4 00000000 f77ba4a4 f6f7190b 00000000 0x86e6f000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nv4_mini+4ad24
f6f1cd24 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nv4_mini+4ad24

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME:  nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  42cca321

FAILURE_BUCKET_ID:  0x8E_nv4_mini+4ad24

BUCKET_ID:  0x8E_nv4_mini+4ad24

Followup: MachineOwner
---------