Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Wednesday, January 19, 2011

Stop error 0x00000024


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:
      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 fdiskcommand in MS-DOS 5.x, MS-DOS 6.x, or Windows 95 and Windows 98 lets you to delete NTFS partitions by selecting and deleting the NON-DOS partition.

Check the BIOS AHCI or SATA 
Run UBCD and run the diagnostic on the drives.

You might want to run Memtest86+ overnight to confirm your RAM is stable, if you haven't done so already. If it's fancy RAM intended for above-normal voltages, make sure to go into your BIOS and manually set the voltage to the intended spec.
Another problem solved by proper application of the voltagez:

You need the Intel INF Update Utility, probably the latest version:

Windows Vista and 7
Fixed it by (if OS starts):
Right click on C:, Properties, Disk Cleanup, Files from all users, More
Options, Clean-up (System Restore and Shadow Copies). Repeated for all
partitions and System Restore is now working.

Look with a Linux Live CD for  an event file (*.evt). Copy it.
If you are able to get to SAFE MODE then you could find more detail in the EVENT VIEWER

Eventually: Clear all the EVENT VIEWER logs and then reboot to crash. Now back to SAFE MODE. And look for the events

1. If  the antivirus has failed. Uninstall it.
2. You can ignore DCOM entries.

3. In safe mode head to the services control panel and set SERVER to Automatic.
4. All entries with "not a valid Win32 application." are deep trouble. Let's gloss over those for the moment.
5. "The WebDav Client Redirector Driver service" is rarely used. While in the Services, set it to disabled for now.
6. Same for the The WebClient service.
7. Researching further events turned up

It's either a heavily damaged Vista OS or BAD RAM.

The BSOD isn't saying ntfs.sys just the stop number, but I ran MS's minidump analyzer and it's the file behind it. I ran chkdsk on all my partitions and it found problems on a partition, but it's not the one Vista is on, might even have been on my external drive.
any ways, I installed Vista x64 today, I had XP telling me last weekend my E: NFTS was corrupt and needed to be fixed, I ran chkdsk it did it's thing and everything seemed okay. I've had this BSOD 2x on my new Vista install already. Google is turning up too many suggestions on what to do, MS's offical page about this seems weird (don't know how else to explain it) They make it sound like the ntfs.sys file needs to be replaced but they're talking about xfering the drive to a new system and doing all sorts of stuff.
I'm going to run Spinrite tonight on the drive to make sure it's not bad, I'll try to dig up another IDE cable. System is new, was built a few months ago and has ran pretty well. I'm not taking this lightly as it might be a bad HD or hardware problems, but none of the links I'm finding on google seem to break down how serious this is. I'm going to do a full backup tomorrow but if it's a software issue causing it, or the ntfs.sys file is bad a backup-restore won't help things.
Is it not possible to simply to boot to a UBCD and delete the ntfs.sys and copy the file off my Vista DVD?

The analysis of the dump (!analyze -v) showed what? (Please turn on verifier, please force another BSOD, then please analyze the dumpfile.)
Re: Only Vista -> no third party drivers? No driver CDs used? You literally put the Vista CD in, installed Vista, and you can repro this crash? If that is the case, you have a hardware problem. That's not normal for a STOP 19.

Windows XP
boot the machine with your startup CD,
select "Repair", then select "Command Console".
Now rename
c:\winnt\system32\config\system to "system.bad", and
c:\winnt\system32\config\system.alt to "system".
You must suspect a hardware problem.
If this was an ordinary disk then I would do either of these:
a) Temporarily install the disk as a slave disk in some other WinXP PC, and run chkdsk /f on it; or
b) Temporarily install a spare disk in this machine (while the main disk is disconnected), install a vanilla version
of WinXP on this disk, then reconnect the problem disk so that I could check it.
In either case you could rename a suspected driver file after checking the disk.
You need to decide if either of these methods is feasible for your RAID set.
I use the recovery disk and I deleted and rebuilt the array, installed XP in striped set again and ran 
chkdsk /v, and there seem to be no problem with the disks.


No comments: