Jump to content

Pantallazo azul :(

Cri_Lancelot
 Share

Recommended Posts

Cri_Lancelot Newbie

Cri_Lancelot

Posted
Posted (edited)

Hola amigos de chilecomparte... mi problema viene sucediendo hace poco tiempo me a pasado ya como 3 veces adjunto lo que saque del Debugging tools for windows

 

--------------------------------------------------------------------------------

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a b(Si bloquean la publicidad, el sitio NO tendrá recursos para mantenerse) in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c0464780, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: 8ad95860, current process (virtual address for lock type 3, or PTE)
Arg4: 8c8f0d89, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*********************************************************************
* 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+ *
*********************************************************************
*************************************************************************
*** ***
*** ***
*** 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+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: 82e05000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09
ERROR_CODE: (NTSTATUS) 0xc000000e - Se ha especificado un dispositivo inexistente.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ea8e45 to 82ee3f20
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a615196c 82ea8e45 0000007a c0464780 c000000e nt+0xdef20
a61519dc 82eac726 a6151a30 82f3b5c0 a6151a50 nt+0xa3e45
a6151a6c 82e95977 82f3b5c0 8c8f0d89 87daf410 nt+0xa7726
a6151af0 82e463d8 00000008 8c8f0d89 00000000 nt+0x90977
a6151b08 8c8f0d89 badb0d00 86136d18 00000727 nt+0x413d8
a6151bdc 8c82b0cf 86136c50 8911d808 c000000e Ntfs+0xded89
a6151c1c 82e847ba 896e865c 00000000 ffffffff Ntfs+0x190cf
a6151c34 7576621a badb0d00 0000000c 00000000 nt+0x7f7ba
a6151c38 badb0d00 0000000c 00000000 00000000 0x7576621a
a6151c3c 00000000 00000000 00000000 00000000 0xbadb0d00
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+def20
82ee3f20 cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+def20
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlpa.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner

------------------------------------------------------------------------

 

Espero me puedan ayudar

 

Saludos

Edited by Cri_Lancelot
Link to comment
Share on other sites
Nagash Newbie

Nagash

Posted
Posted

Analizaste el informe .dmp abierto con debugging tools con el comando !analyze -v?
Al hacer eso, te da el resultado de que es lo que te esta dando bluescreen

 

en softzone hay un manual del debugging tools, pero solo pondré una imagen de referencia para que veas como da el análisis con el comando:

!analyze -v

imagen8.png

 

Como puedes ver el mismo programa te indica la posible causa.

 

Analiza y nos cuentas.
Saludos

Link to comment
Share on other sites
Cri_Lancelot Newbie

Cri_Lancelot

Posted
  • Author
Posted (edited)

Datos del debbuging tools for windows completo usando el comando !analyze -v

 

------------------------------------------

 

 

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\051913-20701-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 \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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82e05000 PsLoadedModuleList = 0x82f4f850
Debug session time: Sun May 19 00:00:15.234 2013 (GMT-4)
System Uptime: 0 days 1:59:43.124
*********************************************************************
* 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
.....
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a b(Si bloquean la publicidad, el sitio NO tendrá recursos para mantenerse) in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c0464780, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: 8ad95860, current process (virtual address for lock type 3, or PTE)
Arg4: 8c8f0d89, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*********************************************************************
* 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+ *
*********************************************************************
*************************************************************************
*** ***
*** ***
*** 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+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: 82e05000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09
ERROR_CODE: (NTSTATUS) 0xc000000e - Se ha especificado un dispositivo inexistente.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ea8e45 to 82ee3f20
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a615196c 82ea8e45 0000007a c0464780 c000000e nt+0xdef20
a61519dc 82eac726 a6151a30 82f3b5c0 a6151a50 nt+0xa3e45
a6151a6c 82e95977 82f3b5c0 8c8f0d89 87daf410 nt+0xa7726
a6151af0 82e463d8 00000008 8c8f0d89 00000000 nt+0x90977
a6151b08 8c8f0d89 badb0d00 86136d18 00000727 nt+0x413d8
a6151bdc 8c82b0cf 86136c50 8911d808 c000000e Ntfs+0xded89
a6151c1c 82e847ba 896e865c 00000000 ffffffff Ntfs+0x190cf
a6151c34 7576621a badb0d00 0000000c 00000000 nt+0x7f7ba
a6151c38 badb0d00 0000000c 00000000 00000000 0x7576621a
a6151c3c 00000000 00000000 00000000 00000000 0xbadb0d00
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+def20
82ee3f20 cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+def20
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlpa.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------

 

 

 

Datos que saque del BlueScreenView

 

 

==================================================
Dump File : 051913-20701-01.dmp
Crash Time : 19/05/2013 0:01:22
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xc0464780
Parameter 2 : 0xc000000e
Parameter 3 : 0x8ad95860
Parameter 4 : 0x8c8f0d89
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+ded89
File Description : Controlador del sistema de archivos NTFS
Product Name : Sistema operativo Microsoft® Windows®
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+def20
Stack Address 1 : ntkrnlpa.exe+a3e45
Stack Address 2 : ntkrnlpa.exe+a7726
Stack Address 3 : ntkrnlpa.exe+90977
Computer Name :
Full Path : C:\Windows\Minidump\051913-20701-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 131.072
==================================================

 

 

 

 

Edited by Cri_Lancelot
Link to comment
Share on other sites
Nagash Newbie

Nagash

Posted
Posted (edited)

Por lo que estuve investigando y acorde a lo de bluescreenview (debugging tools se encabrono XD) debes reemplazar ntfs.sys, el cual posee un error y debe ser reemplazado utilizando el disco de instalación de windows.

 

Microsoft tiene un articulo de como reparar susodicho archivo

http://support.microsoft.com/kb/822800/es

Espero no estar mal, ya que nunca me he tenido que topar con un error en ese archivo y por ende mi inexperiencia en tal error.

Disculpa lo poco que he podido ayudar.

Edited by nagash_negro
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...