pantalla azul frecuente

busca en la siguiente url el error que dices:
http://www.microsoft.com/resources/...p_ottj.asp
te saldra lo siguiente:
Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
The Stop 0x7A message indicates that a page of kernel data was not found
in the paging (virtual memory) file and could not be read into memory.
This might be due to incompatible disk or controller drivers, firmware,
or hardware.

Interpreting the Message
This Stop message has four parameters:

1.. Lock type value (0x00000001, 0x00000002, 0x00000003, or page table
entry (PTE) address).
2.. I/O status code.
3.. If the lock type is 0x00000001, this parameter represents the
current process. If the lock type is 0x00000003, this parameter
represents the virtual address.
4.. The virtual address that could not be read into memory.
Frequently, the cause of this error can be determined from the second
parameter, the I/O status code. Some common status codes are:

a.. 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of
nonpaged pool resources.
b.. 0xC000009C, or STATUS_DEVICE_DATA_ERROR, indicates bad blocks
(sectors) on the hard disk.
c.. 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or
loose data or power cables, a problem with SCSI termination, or improper
controller or disk configuration.
d.. 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks
(sectors) on the hard disk.
e.. 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper
termination, defective storage controller hardware, or defective disk
cabling, or two devices attempting to use the same resources.
For information about other possible status codes that might be
returned, see the file Ntstatus.h of the Windows XP Professional Driver
Development Kit (DDK). For more information about the DDK, see the
Driver Development Kits link on the Web Resources page at
http://www.microsoft.com/windows/re...resources.

Resolving the Problem
The following suggestions are specific to Stop 0x7A errors. For
additional troubleshooting suggestions that apply to all Stop errors,
see "Stop Message Checklist" later in this appendix.

a.. Stop 0x7A can be caused by bad sectors in the virtual memory
paging file, disk controller error, virus infection, or memory hardware
problems. In extremely rare cases, depleted nonpaged pool resources can
cause this error. If the first and third parameters are zero, the stack
signature in the kernel stack is missing, an error typically caused by
defective hardware. If the I/O status is 0xC0000185 and the paging file
is on a SCSI disk, check for cabling and termination issues. An I/O
status code of 0xC000009C or 0xC000016A indicates that the requested
data could not be found. You can try to correct this by restarting the
computer. If a problem with disk integrity exists, Autochk, a program
that attempts to mark bad disk sectors as defective so that they are not
used in the future, starts automatically. If Autochk fails to run, you
can manually perform the integrity check yourself by following the
instructions to run Chkdsk provided in "Stop 0x00000024 or
NTFS_FILE_SYSTEM" earlier in this appendix. For more information about
Autochk and Chkdsk, see "Troubleshooting Disks and File Systems" in this
book.
b.. Another cause of Stop 0x7A messages is defective, malfunctioning,
or failed memory hardware, such as memory modules, Level 2 (L2) SRAM
cache, or video adapter RAM. If you added new hardware recently, remove
and replace it to determine if it is causing or contributing to the
problem. Run diagnostics software supplied by the system manufacturer to
determine if the component has failed.
c.. Check the hardware manufacturer's Web site for updates to disk
adapter firmware or drivers that improve compatibility. Verify that your
disks and controller support the same set of advanced features, such as
higher transfer rates. If necessary, select a slower transfer rate if an
update is not yet available. Consult your hardware or device
documentation for more information.
Important

a.. You can install disk controller drivers not present on the
Windows XP Professional operating system CD by responding to the
following prompt shortly after starting Setup:
b.. Press F6 if you need to install a third party SCSI or RAID
driver.
c.. Press F6, and when prompted, provide the appropriate storage
controller driver (ATA or SCSI) supplied by the manufacturer.
d.. The problem might also be due to cracks, scratched traces, or
defective components on the motherboard. If all else fails, take the
system motherboard to a repair facility for diagnostic testing.
e.. Problems that cause Stop 0x7A messages can also cause Stop 0x77
messages. For more information about Stop 0x77 messages, see "Stop
0x00000077 or KERNEL_STACK_INPAGE_ERROR" earlier in this appendix.
For more information about Stop 0x7A messages, see the Microsoft
Knowledge Base link on the Web Resources page at
http://www.microsoft.com/windows/re...resources. Search using
keywords winnt, 0x0000007A, and 0x7A.


Luis J.

"Ignacio García" escribió en el mensaje
news:
| Hace poco que tengo un nuevo ordenador. Mucho más potente que el que
venía
| usando y, además, con ánimo de mejora, de marca...
| Pues bien, con una frecuencia de dos o tres días por semana, me
aparecen las
| famosas pantallas azules. Supongo que se debe a algún conflicto de
hard pero
| no he sabido identificarlo. Os posteo el texto que me aparece en
pantalla:
|
| KERNEL_DATA_INPAGE_ERROR
| STOP: 0x0000007A(0XC03DDDF4, 0XC000000E, 0XF777D384, 0X12D48860)
|
| atapi.sys - Adress F777D384 base at F7770000, Datestamp 41107b4d
|
| Empezando el volcado de la memoria física
|
| A partir de ahí, a veces se queda colgado y otras veces, al cabo de un
rato
| se reinicia solo.
| El equipo venía con el SO instalado (WINXP SP2) y está actualizado a
fecha
| de hoy. El único cambio que le he hecho es añadirle una segunda unidad
de
| DVD RW, de la misma marca (HP) pero el problema de la pantalla azul
comenzó
| anteriormente a este añadido.
| Os agradeceré si me podéis echar una mano
| Gracias
|
| Ignacio
|
|
|