J'ai réussi a ouvrir le fichier mais cela s'affiche:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [H:\Documents and Settings\Utilisateur\Mes documents\hj\Mini020408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
- ***********************************************
- ***********************
- Symbol loading may be unreliable without a symbol search path. *
- Use .symfix to have the debugger choose a symbol path. *
- After setting your symbol path, use .reload to refresh symbol locations. *
- ***********************************************
- ***********************
Executable search path is:
- ***********************************************
- ****************
- Symbols can not be loaded because symbol path is not initialized. *
- *
- The Symbol Path can be set by: *
- using the _NT_SYMBOL_PATH environment variable. *
- using the -y <symbol_path> argument when starting the debugger. *
- using .sympath and .sympath+ *
- ***********************************************
- ****************
Unable to load image ntoskrnl.exe, Win32 error 0n2
- WARNING: Unable to verify timestamp for ntoskrnl.exe
- ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Mon Feb 4 21:51:24.656 2008 (GMT+1)
System Uptime: 0 days 2:58:18.335
- ***********************************************
- ****************
- Symbols can not be loaded because symbol path is not initialized. *
- *
- The Symbol Path can be set by: *
- using the _NT_SYMBOL_PATH environment variable. *
- using the -y <symbol_path> argument when starting the debugger. *
- using .sympath and .sympath+ *
- ***********************************************
- ****************
Unable to load image ntoskrnl.exe, Win32 error 0n2
- WARNING: Unable to verify timestamp for ntoskrnl.exe
- ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..................................................
..................................................
..................................................
.
Loading User Symbols
Loading unloaded module list
........................................
- ***********************************************
- **************************
- *
- Bugcheck Analysis *
- *
- ***********************************************
- **************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {7, 2, 0, 804f4671}
- ** Kernel symbols are WRONG. Please fix symbols to do analysis.
- WARNING: Unable to verify timestamp for Ntfs.sys
- ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
- ***********************************************
- ********************
- ***
- ***
- Your debugger is not using the correct symbols ***
- ***
- In order for this command to work properly, your symbol path ***
- must point to .pdb files that have full type information. ***
- ***
- Certain .pdb files (such as the public OS symbols) do not ***
- contain the required information. Contact the group that ***
- provided you with these symbols if you need this command to ***
- work. ***
- ***
- Type referenced: nt!_KPRCB ***
- ***
- ***********************************************
- ********************
- ***********************************************
- ********************
- ***
- ***
- Your debugger is not using the correct symbols ***
- ***
- In order for this command to work properly, your symbol path ***
- must point to .pdb files that have full type information. ***
- ***
- Certain .pdb files (such as the public OS symbols) do not ***
- contain the required information. Contact the group that ***
- provided you with these symbols if you need this command to ***
- work. ***
- ***
- Type referenced: nt!KPRCB ***
- ***
- ***********************************************
- ********************
- ***********************************************
- ********************
- ***
- ***
- Your debugger is not using the correct symbols ***
- ***
- In order for this command to work properly, your symbol path ***
- must point to .pdb files that have full type information. ***
- ***
- Certain .pdb files (such as the public OS symbols) do not ***
- contain the required information. Contact the group that ***
- provided you with these symbols if you need this command to ***
- work. ***
- ***
- Type referenced: nt!_KPRCB ***
- ***
- ***********************************************
- ********************
- ***********************************************
- ********************
- ***
- ***
- Your debugger is not using the correct symbols ***
- ***
- In order for this command to work properly, your symbol path ***
- must point to .pdb files that have full type information. ***
- ***
- Certain .pdb files (such as the public OS symbols) do not ***
- contain the required information. Contact the group that ***
- provided you with these symbols if you need this command to ***
- work. ***
- ***
- Type referenced: nt!KPRCB ***
- ***
- ***********************************************
- ********************
- ***********************************************
- ********************
- ***
- ***
- Your debugger is not using the correct symbols ***
- ***
- In order for this command to work properly, your symbol path ***
- must point to .pdb files that have full type information. ***
- ***
- Certain .pdb files (such as the public OS symbols) do not ***
- contain the required information. Contact the group that ***
- provided you with these symbols if you need this command to ***
- work. ***
- ***
- Type referenced: nt!_KPRCB ***
- ***
- ***********************************************
- ********************
- WARNING: Unable to verify timestamp for aswMon2.SYS
- ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
- ***********************************************
- ********************
- ***
- ***
- Your debugger is not using the correct symbols ***
- ***
- In order for this command to work properly, your symbol path ***
- must point to .pdb files that have full type information. ***
- ***
- Certain .pdb files (such as the public OS symbols) do not ***
- contain the required information. Contact the group that ***
- provided you with these symbols if you need this command to ***
- work. ***
- ***
- Type referenced: nt!_KPRCB ***
- ***
- ***********************************************
- ********************
- ***********************************************
- ********************
- ***
- ***
- Your debugger is not using the correct symbols ***
- ***
- In order for this command to work properly, your symbol path ***
- must point to .pdb files that have full type information. ***
- ***
- Certain .pdb files (such as the public OS symbols) do not ***
- contain the required information. Contact the group that ***
- provided you with these symbols if you need this command to ***
- work. ***
- ***
- Type referenced: nt!_KPRCB ***
- ***
- ***********************************************
- ********************
- ***********************************************
- ****************
- Symbols can not be loaded because symbol path is not initialized. *
- *
- The Symbol Path can be set by: *
- using the _NT_SYMBOL_PATH environment variable. *
- using the -y <symbol_path> argument when starting the debugger. *
- using .sympath and .sympath+ *
- ***********************************************
- ****************
- ***********************************************
- ****************
- Symbols can not be loaded because symbol path is not initialized. *
- *
- The Symbol Path can be set by: *
- using the _NT_SYMBOL_PATH environment variable. *
- using the -y <symbol_path> argument when starting the debugger. *
- using .sympath and .sympath+ *
- ***********************************************
- ****************
Probably caused by : aswMon2.SYS ( aswMon2+83c )
Followup: MachineOwner
---------
