stop 0x00000024

27/11/2003 - 20:25 por david | Informe spam
hola

al iniciar el pc, poco despues que empieza la carga de XP,
me sale una pantalla azul de error con las informaciones
tecnicas:
***stop: 0x00000024 (ox001902F8, 0xF8966B68, 0xF8966868,
0xF83E08E9)
***Ntfs.sys - Address F83E08E9 base at F83D1000, Datestamp
3b7dc5d0

hace tres dias tuve el Blaster porque no tenia ni el
firewall ni el patch de windows. Se me lo baje, lo
instale y todo parecia areglado. Ahora acabo de leer que
hubiera tenido que formatear el disco duro y instalar en
limpia.
Luego, hace dos noches hubo un apagon mientrras el pc
estaba encendido. Eske no tengo suerte!

soy principante en informatica asi ke no entiendo muy bien
las explicaciones de windows

¿Hay algo facil ke hacer o tengo ke devolverlo a la tienda
para ke me lo areglan?
gracias de antemano por la ayuda

david
 

Leer las respuestas

#1 david
27/11/2003 - 20:45 | Informe spam
hola jess

gracias por la ayuda. Lo habia encontrado tambien, pero
mi problema eske no llego hasta ahi. Cuando estoy en la
pantalla de error no me deja hacer nada, solo puedo apagar
el ordenador.
¿Mas ideas?
un saludo
Stop 0x00000024 or NTFS_FILE_SYSTEM
The Stop 0x24 message indicates that a problem occurred


within Ntfs.sys, the driver file that allows the system to
read and write to NTFS file system drives. A similar Stop
message, 0x23, exists for the file allocation table (FAT16
or FAT32) file systems.

Interpreting the Message
This Stop message has four parameters:

1.. Source file and line number.
2.. A non-zero value that contains the address of the


exception record (optional).
3.. A non-zero value that contains the address of the


context record (optional).
4.. A non-zero value that contains the address where


the original exception occurred (optional).
Parameters for this Stop message are useful only to


Microsoft technical support with access to Windows XP
Professional source code. Stop messages due to file system
issues have the source file and the line number within the
source file that generated the error encoded in their
first parameter. The first four hexadecimal digits (also
known as the high 16 bits) after the "0x" identify the
source file number, and the last four hexadecimal digits
(the low 16 bits) identify the source line in the file
where the stop occurred.

Resolving the Problem
The following suggestions are specific to Stop 0x24


errors. For additional troubleshooting suggestions that
apply to all Stop errors, see "Stop Message Checklist"
later in this appendix.

a.. Malfunctioning SCSI and Advanced Technology


Attachment (ATA) hardware or drivers can also adversely
affect the system's ability to read and write to disk,
causing errors. If using SCSI hard disks, check for
cabling and termination problems between the SCSI
controller and the disks. Periodically check Event Viewer
for error messages related to SCSI or FASTFAT in the
System log or Autochk in the Application log. For more
information about troubleshooting SCSI adapters and disks,
see "Troubleshooting Startup," "Troubleshooting Disks and
File Systems," and "Disk Management" in this book.
b.. Verify that the tools you use to continually


monitor your system, such as virus scanners, backup
programs, or disk defragmenters are compatible with
Windows XP Professional. Some disks and adapters come
packaged with diagnostic software that you can use to run
hardware tests. For more information, see the owner's
manual for your computer, hard disk, or controller. For
more information about Autochk, see "Troubleshooting Disks
and File Systems" in this book.
To test hard disk or volume integrity

Method 1:

1.. In the Run dialog box, in the Open box type:
cmd

2.. Start the Chkdsk tool, which detects and attempts


to resolve file system structural corruption. At the
command prompt type:
chkdsk drive: /f

Method 2:

1.. Double-click My Computer, and then select the


hard disk you want to check.
2.. On the File menu, click Properties.
3.. Click the Tools tab.
4.. In the Error-checking box, click Check Now.
5.. In Check disk options, select the Scan for and


attempt recovery of bad sectors check box. You can also
select the Automatically fix file system errors check box.
If the volume you are checking is in use, a message


asks whether you want to delay disk error checking until
the next time you restart your computer. After you
restart, disk error checking runs and the volume chosen is
not available to run other tasks during this process. If
you cannot restart the computer due to the error, use safe
mode or Recovery Console.

If you are not using the NTFS file system, and the


system partition is formatted with the file allocation
table (FAT16 or FAT32) file system, long file name (LFN)
information can be lost if hard disk tools are started
from an MS-DOS command prompt. A command prompt appears
when using a startup floppy disk or when using the command
prompt startup option on multiple boot systems that use
FAT16 or FAT32 partitions with Microsoft Windows 95 OEM
Service Release 2 (OSR2), Microsoft Windows 98, or
Microsoft Windows Millennium Edition (Me) installed. Do
not use tools meant for other operating systems on Windows
XP Professional partitions.

For more information about disks and file systems,


see "Disk Management," "File Systems,"
and "Troubleshooting Disks and File Systems" in this book.

c.. Nonpaged pool memory might be depleted, which can


cause the system to stop. You can resolve this situation
by adding more RAM, which increases the quantity of
nonpaged pool memory available to the kernel. You can also
reduce the number of files on the Services for Macintosh
volume, if applicable.

Saludos

Jessica Fisherman Lee

jessfi at mtv dot com
"david" wrote in


message news:006901c3b51c$445cf3c0$
hola

al iniciar el pc, poco despues que empieza la carga de


XP,
me sale una pantalla azul de error con las


informaciones
tecnicas:
***stop: 0x00000024 (ox001902F8, 0xF8966B68,


0xF8966868,
0xF83E08E9)
***Ntfs.sys - Address F83E08E9 base at F83D1000,


Datestamp
3b7dc5d0

hace tres dias tuve el Blaster porque no tenia ni el
firewall ni el patch de windows. Se me lo baje, lo
instale y todo parecia areglado. Ahora acabo de leer


que
hubiera tenido que formatear el disco duro y instalar


en
limpia.
Luego, hace dos noches hubo un apagon mientrras el pc
estaba encendido. Eske no tengo suerte!

soy principante en informatica asi ke no entiendo muy


bien
las explicaciones de windows

¿Hay algo facil ke hacer o tengo ke devolverlo a la


tienda
para ke me lo areglan?
gracias de antemano por la ayuda

david

Preguntas similares