Buscar

BOSD error stop 0x00000a (lean el minidump!!)


 
 Old 08 ene 2009, 19:54   #1 (permalink)  
Miembro
 
Avatar de Ryosuke Takahashi
 
Registrado: mayo 2007
Mensajes: 79

Predeterminado BOSD error stop 0x00000a (lean el minidump!!)

Hola ps me sale un pantallazo azul cuando aveces quiero descargar algo me sale un pantallazo azul y ya estoy cansado porque me tira el mismo error, tambien me pasa con el jdownloader, aca dejo los detalles del minidump, espero me puedan ayudar y que la solucion no sea formatear .

Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Sebastian\Desktop\Mini010709-03.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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x8361c000 PsLoadedModuleList = 0x83733c70
Debug session time: Wed Jan 7 18:07:34.407 2009 (GMT-5)
System Uptime: 0 days 1:43:24.429
************************************************** *******************
* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** 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 A, {b75e0834, 2, 1, 836d1693}

*** WARNING: Unable to verify timestamp for NETIO.SYS
*** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
*** WARNING: Unable to verify timestamp for tdx.sys
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*** WARNING: Unable to verify timestamp for nvmfdx32.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmfdx32.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** *******************
* 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 : NETIO.SYS ( NETIO+769a )

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

Y no digan que me pase a xp porque no lo voy hacer : , me duro año y medio sin problemas pero hasta ahora paso nose que sera :S
Ryosuke Takahashi is offline   Citar y responder
 
 Old 08 ene 2009, 20:20   #2 (permalink)  
Miembro activo
 
Avatar de conan_blasi
 
Registrado: noviembre 2006
Mensajes: 10.021

Predeterminado Re: BOSD error stop 0x00000a (lean el minidump!!)

http://www.techsupportforum.com/micr...vista-sp1.html
conan_blasi is offline   Citar y responder
 
 Old 08 ene 2009, 20:55   #3 (permalink)  
Miembro activo
 
Avatar de ferinancat
 
Registrado: enero 2008
Mensajes: 1.761

Predeterminado Re: BOSD error stop 0x00000a (lean el minidump!!)

has hecho alguna actualizacion de software o de hardware ultimamente??

Procesador: Intel Core 2 CPU 4300 @ 1.80Ghz
Memoria: 2 Gb RAM
T. Gráfica: NVIDIA 8500 GT
HD1: 40Gb - HD2: 250Gb
S.O.: Ubuntu 10.04 LTS Lucid Lynx
Nº registro linux user: 475.977

NOT POLITIC, NOT STUPID JUST S.H. //// I'm not a nazi, I'm not a red \\\\
ferinancat is offline   Citar y responder

« como quito nero del inicio? | Problemas con Pc? »

Herramientas
Estilo




Buscar