Newsgroup: it.comp.os.win.win2000
Titolo: Crash2

Vi aggiorno in quelli che sono i "dolori": ho inviato un post precedente
dicendo che il crash era dovuto alla RAM, in effetti ho avuto un altro crash
ma con scritta differente:
NTFS_FILE_SYSTEM
Sa qualcuno per caso che diavolo sia e da cosa possa dipendere?
Grazie
Max

SYMPTOMS
When you run Windows 2000 or Windows XP, you may receive either of the
following error messages:
  Stop 0x00000024
  -or-
  NTFS_FILE_SYSTEM
CAUSE
This issue can occur if a problem occurred within the Ntfs.sys file. The
Ntfs.sys file is the driver file that enables your computer to read and
write to NTFS partitions. Damage in the NTFS file system, damaged portions
of your hard disk, or damaged SCSI or IDE drivers can also cause this issue.
RESOLUTION
To resolve this issue:
  1.. Interpret the error message. The stop error is followed by four
parameters defined in order of appearance:
    a.. Source file and line number.
    b.. Optionally contains the address of the exception record.
    c.. Optionally contains the address of the context record.
    d.. Optionally contains the address where the original exception
occurred.
  All stop errors due to problems with NTFS or FAT have encoded in their
first parameter the source file and the line number within the source file
that generated the stop error. The high 16 bits (the first four hexadecimal
digits after 0x) identify the source file number, and the lower 16 bits (the
last four hexadecimal digits of the parameter) identify the source line in
the file where the stop occurred.
  2.. Check Event Viewer for error messages from SCSI, FASTFAT (the System
Log), or Autochk (the Application Log) that might help determine the device
or driver that is causing the error.
  3.. Try disabling any virus scanning programs, backup programs, or disk
defragmenter tools that constantly monitor your computer, and if possible,
run hardware diagnostics tools supplied by your computer manufacturer.
  4.. Run chkdsk /f /r to detect and resolve any file system structural
damage.
  5.. Depletion of non-paged pool memory can cause this issue. If you create
a Services for Macintosh (SFM) volume on a large partition (7 gigabytes or
larger) with a large number of files (at least 100,000) while the AppleTalk
driver Apf.sys is running, the indexing routine consumes a large amount of
non-paged pool memory. If the non-paged pool memory is completely depleted,
this error can cause your computer to stop responding (hang). However, if
the amount of available non-paged pool memory is very low during the
indexing process, another kernel-mode driver requiring non-paged pool memory
can also cause this issue. To resolve this issue, increase the amount of
installed RAM to increase the quantity of non-paged pool memory available to
the kernel, or reduce the number of files on the SFM volume.
Any corrupted system or data volume that is using NTFS can cause this error
message. If you receive a "stop 0x24" error message when you restart the
computer or when you try to run Setup or Recovery Console, you may not be
able to determine the cause of the problem by using the steps outlined
above. Instead, use one of the following methods to resolve the corrupted
NTFS volume.
FAT or FAT32 File System
If your system partition is using the FAT or FAT32 file system, disconnect
or turn off any data disks that contain NTFS volumes. This allows you to
start back into the operating system to perform troubleshooting steps. If
you can determine which NTFS volume is causing the boot problem, use the
following steps:
  1.. Make sure the drive that contains the corrupted NTFS volume is
disconnected, and then start Windows by using Safe mode.
  2.. Rename the %SystemRoot%\System32\Drivers\Ntfs.sys file to Ntfs.old,
and then shut down the computer (this action prevents the Ntfs.sys driver
from loading).
  3.. Reconnect the drive that contains the corrupted NTFS volume.
  4.. Restart the computer, and then run the following command on the
corrupted NTFS volume:
    chkdsk driveletter: /f
  NOTE: The Chkdsk tool has built-in support for NTFS and does not require
the Ntfs.sys driver to make repairs.
  5.. After you use the Chkdsk tool to repair the corrupted NTFS volume,
rename %SystemRoot%\System32\Drivers\Ntfs.old to Ntfs.sys, and then shut
down and restart the computer.
The computer should be operational again, and you can try to determine what
caused the original problem.
NTFS File System
If your system partition is using the NTFS file system, it is possible that
the system partition is corrupted and is causing the "stop 0x24" error
message.
To determine if this is the case, disconnect or turn off all other data
disks that contain NTFS volumes. After you determine which disk contains the
corrupted NTFS volume, move the disk to another Windows 2000-based computer
that is running on the FAT or FAT32 file system, or install Windows 2000 on
a disk that contains the FAT or FAT32 file system. After you do this, use
the steps that are outlined in the "FAT or FAT32 File System" section.
Using Recovery Console on a Single Drive Computer
If your computer contains only a single NTFS volume and no additional
Windows 2000-based computers or hard disks are available to use for the
previously described methods, you can boot from the four Setup disks to run
the Chkdsk tool with the Ntfs.sys driver disabled. To repair a NTFS volume
by using Recovery Console, use the following steps:
  1.. Start the computer by using a Microsoft Windows 95/98 startup disk
with CD-ROM support (or from another computer with a CD-ROM drive, insert
the Windows 2000 installation CD-ROM).
  2.. Change to the CD_ROM:\Support\Bootdisk folder, and then run
Makeboot.exe or Makebt32.exe to create the four Windows 2000 Setup disks.
  3.. Using Notepad, modify the Txtsetup.sif file on the first Setup disk
you created in step 2:
    1.. In the [FileSystems.Load] section, locate the line that begins with
"ntfs."
    2.. Insert a semicolon (;) at the beginning of the line, as shown in the
following example:
[FileSystems.Load]
fat      = fastfat.sys
;ntfs     = ntfs.sys
    3.. Save your changes.
  4.. Start the computer that is experiencing the "stop 0x24" error message
by using the four Setup disks. When the Welcome to Setup dialog box is
displayed, press F10 to start Recovery Console.
  5.. Run the following command to repair the corrupted NTFS partition:
    chkdsk driveletter: /p
  6.. Type exit to quit Recovery Console, and then restart the computer.
If none of these methods work, you may have to delete, re-create, and format
the corrupted NTFS partition, and restore the partition from your last good
backup of the volume. The fdisk command in MS-DOS 5.x, MS-DOS 6.x, or
Windows 95/98 lets you to delete NTFS partitions by selecting and deleting
the NON-DOS partition.

 Sa qualcuno per caso che diavolo sia e da cosa possa dipendere?
Hai gia tolto l'overclock e la ram incriminata?
-- 
     __         ____           | Eм 'Aanммgтт 'Ahoot'й
 __ / /__  ___ / __/__ __ __   |
/ // / _ \/ -_) _// _ \\ \ /   | 
http://www.macrossmm.com
\___/\___/\__/_/  \___/_\_\    | ICQ UIN: 61571298

La RAM l'ho tolta ma il problema è rimasto.
Devo solo rimettere a 750 il proc, ma per ora dopo vari scandisk, Norton
Utility.....per ora regge!
grazie per i tuoi consigli e disponibilità
Buona domenica
Max

 Norton Utility.....per ora regge!
Norton Utility? Ops!
A proposito... con più di 512 MB di RAM va messo il sp2...
-- 
     __         ____           | Eì 'Aanììgòò 'Ahoot'é


Gią installato a suo tempo il SP2.
Capisco il tuo OPS alle Norton utility, ma visto che la versione 2001 puo'
girare senza bisogno di essere installata...č un bel sollievo.
Comunque non dico niente.................................
Grazie per i tuoi consigli.
Max