====== Minidump ======

Après un crash, windows crée un fichier minidump illisible. Voici comment le décrypter.

  * Télécharger et installer [[http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.4.7.2.exe|WinDbg]]
  * Lancer **WinDbg**
  * Dans le menu **File/Symbol File Path** Copier/coller cette ligne : 

  srv*c:\symbols*http://msdl.microsoft.com/download/symbols

  * Dans le menu **File/Open Crash Dump...** chercher votre fichier dans **c:\windows\minidump**
  * Après traitement, voici un exemple de résultat

<code>
Microsoft (R) Windows Debugger  Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071313-02.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) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.130503-0418
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Jul 13 07:45:39.799 2013 (GMT+2)
System Uptime: 0 days 0:01:29.196
Loading Kernel Symbols
........................................................................................................................................................
Loading unloaded module list
............
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {90c8f14c, 0, 805b7501, 0}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiGetPageProtection+119 )

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

</code>

A la fin le message **Probably caused by : memory_corruption ** nous indique que le problème vient probablement de la RAM.