chema03 | |
| 2008-05-01 21:40 - Respuestas: 0 - Tema nº: 2515795
Características: Windows XP Profesional AMD Athlon 3000+ 1,80 Gh, 512 Ram.
Hola, me pasa lo mismo que en el hilo este
****************************
Si alguien puede ayudarme. Estoy harto de los reinicios.
He hecho lo que dice el moderador y mi volcado del dump es el siguiente:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\\WINDOWS\\Minidump\\Mini050108-02.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 tosymbol 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image \\WINDOWS\\system32\\ntkrnlpa.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu May 1 18:07:09.812 2008 (GMT+2)
System Uptime: 0 days 0:20:35.408
************************************************** *******************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image \\WINDOWS\\system32\\ntkrnlpa.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
....................... ....................... .....................
Loading User Symbols
Loading unloaded module list
..............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {8, 2, 0, f83dbb1d}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Unable to load image NDIS.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
Probably caused by : NDIS.sys ( NDIS+17b1d )
Followup: MachineOwner
Comentarios adicionales: El problema surgió justo despues de agregar o quitar hardware en el PC.
-
[Mensaje editado por tordanxa con fecha: 01-05-2008 21:44:57]. | |
|
|