cannot boot xp. ntfs.sys blue screen 0x00000024

the partition is NTFS. can't access from a windows 98 bootdisk.

Does this problem occur initially as xp begins to load? I have seen this hapen multiple times durring login as the system gets hung up attempting to connect to the network and then stalls. (I call it the blue screen virus" I've always been able to get past this by physically disconnecting any network/internet connections (Mine are using Novell Network). XP then prompts that the system cannot connect and finishes the login to windows.  After this I've updated the windows update, and have yet to have the problem re-occur on any machines. If this is similar to your problem, you might want to give that a shot, as it is a quick fix.

this problem appears before the boot screen logo... and if I connet the damaged disk in another computer with windows xp the same blue screen appears after the logo screen but before entering to windows. I don't see any logon screen.
I'm trying the boot disks prodedure now.

I did the windows 2000 boot disk procedure.. and I have recovered all the data !!! perfect !!!!!!
what a fright.... thank you !
:)

heda:
This old question needs to be finalized -- accept an answer, split points, or get a refund.  For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations!  No comment means you don't care.

Heda, who helped you the most?

Just a follow up for other folks, I had the same exact problem and this fixed my hard drive up too.  No lost data :)

~G~

I had the same problem. Actually it was windows sp 1 for xp c asuing the problem.

How you say? Well I installed XP pro and then installed every single update except sp1. After I installed sp1, the damn blue screen came up over and over.

SO now I did the same procedure but have not installed sp1. Still I get the odd bluescreen and have to fix that.

http://www.experts-exchange.com/Operating_Systems/WinXP/Q_20811532.html

i have the same 0x24 problem and when i make the boot disk (bootdisk.com) and try to use CHKDSK i get error AUTOCHK.EXE not found or something. I tried to copy the autochk.exe from my other computer to a disk but then i get bluescreen with STOP C0000139 about NTDLL.DLL
Help plz!

I had the same problem as Toope. For me worked copying AUTOCHK.EXE from another computer to a separate disk. After doing chkdisk /p my notebook booted again.
Are there already any ideas about the reason for that dammed NTFS - problem? Is SP1 the problem? Thx.

Hey there
I'm having sorta the same problem though the stop error is 0X50, NTFS.sys
I tried pretty much everything, got to this post, had already tried everything on here, problem isn't here :S
wutever i tried, i couldn't get to access the drive (which had been running XP Pro (later updated to SP1) for around a year) it would either display the BSOD or flash it and reboot the system.
I tried the drive as a single drive, BSOD. Tried it as slave to OS installations on NTFS and FAT32 partitions, BSOD. Tried it on the secondary IDE alone with either FAT32 or NTFS systems, again BSOD. Recovery console, nada. Safe mode(S), nada. Couldn't use the CD's repair option.

I'm running out of options... definitely won't consider a format.
Suggestions any1 ?

Thx,
Marc

My next suggestion was going to be format.  Then I read your last comment. :)

Do you have a second drive that you are willing to format?  If so, remove the other drives, leave the CD ROM, put the 'new' drive in as IDE1 (or 0 depending upon the MB).  Use the disk manufacturer utility to repartition and format the drive as FAT32.  Install WINXP on the new drive.  

After it is done, add the problem drive as a slave.
Make sure the boot order is correct in CMOS.
Boot onto the FAT32 drive, do a chkdsk /f /v on the 'problem' disk.

After that, boot up on the winxp cd again.  Go into recovery console and make sure it recognizes both windows installations.  Boot again on winxp cd but this time to repair a particular installation.  

After that (assuming to be successful on all of these), boot under safemode on the 'ex-problem' drive and do a 'sfc /scannow' to make sure protected files are intact.

I'm not sure if this is related, but the following happened to me last week.  I was rearranging cables on my computer and tripped over the power cable of my kids' computer while my son was playing an online game.

Got a BSOD every time on reboot.  It would pass POST and actually got into safe mode once.  Couldn't boot onto the CD, couldn't boot onto another windows installation on another drive.  Would always get the blue screen.

Got the latest memtest86 from March of 04.  Created a boot diskette on the broken computer and quickly discovered more memory errors than I could count.  Put the memory into my computer and verified the same thing.  However, I still wasn't sure if it was video card, mb or memory or all three.

Went to Fryes.  Turned out the MB, Memory and Video were all bad.  The fan stopped working on the nVidia video card - which btw can cause intermittent problems - memory bad and no amount of good memory and good video cards could make the MB work even though it POSTed fine.

Luckily the memory was Patriot and came with a lifetime warranty.  The other MB and video were two months out of warranty.  Spent $107 on MB/P4 combo - ECS and 2.4 P4 - not the best, but no problems now.  Bought a new video card for $75 and started all over with a reformat and installation.  Now the kids computer doesn't have a years worth of cr*p on it and it works great.

How do I carry out stage 2 of the solution:

 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.

When I insert Windows 98 Startup disk with CD-ROM support iI get "A:\> and it comes up with bad command or file name when I key in CD_ROM etc. How exactly do I change to the CD_ROM:\Support\Bootdisk folder?

Hey there,
just to make sure i understand u right
at a:\ u typed CD_ROM and u got that error ?

to switch to ur cdrom drive u need to find out wut letter it's set to D: - E: - F: depending on how many drives u got on ur system
u only need to type that drive letter followed by :
for example:
A:\E:

But here's a tip... www dot bootdisk dot com and download the files from there
HTH

Marc

Thank you very much: will use that website to download the file.

Hi All, I have the same ntfs.sys error message.  I followed the comments explained above.

At this moment I was about to use the Windows XP startup disks, 6 pieces, but these disks don't have a SATA driver in the floppy image files.  I can not edit the txsetup.si_ file, this is txsetup.si_ instead of txsetup.sif on the windows xp boot disks...  Whne opening this file with notepad or wordpad, you get to see a file that looks like a wordpad file that you open in notepad, you know with a lot of blocks and signs in it.

Also downloaded the Windows 2000 boot disks but these will not have a SATA driver in the image files as well.

Any idea how I can get the SATA driver in the disk image files?  What am I doing wrong with the txsetup.si_ file, is there a way that I can edit this file?

Thanks!

I followed the suggestions above, but like Troope, I got stuck at the STOP C0000139 screen. I tried everything to no avail. Finally, I arrived at a solution. If nothing else works for you:

1. On a working computer, download the Windows XP setup disks from http://support.microsoft.com/default.aspx?scid=kb;en-us;310994 .
2. After writing the six disks, go to the first disk. Delete TXTSETUP.SI_ .
3. Copy TXTSETUP.SIF from your Windows XP CD-ROM into the first disk; it's found in the I386 directory of the CD-ROM.
4. Edit TXTSETUP.SIF in WordPad, putting a semicolon before the "ntfs = ntfs.sys" line so it reads ";ntfs = ntfs.sys".
5. Copy AUTOCHK.EXE to a blank diskette; it's found in the I386 directory of the Windows XP CD-ROM.
6. Start the computer with the 0x00000024 errors using the six Windows XP Setup disks.
7. Enter the Recovery Console.
8. Run chkdsk.
9. If it can't find AUTOCHK.EXE, insert the disk you made with that file and tell it that the file can be found on A:\autochk.exe . CHKDSK should work successfully, which didn't happen for me when I used the comments above.
10. CHKDSK found problems for me. I also ran FIXBOOT and FIXMBR; I'm not sure if this was necessary. It didn't appear that the problem was solved, but when I restarted my computer (without the aid of any disks or CDs), Windows booted up successfully.

Hope this helps!

Hi Bet4a,

  I tried this but unfortunately the chkdsk always stopped after 35%.  Tried chkdsks with all parameters.  AFter that I downloaded Knoppix v3.6 and put that in my machine, this OS was also not able to access the bad ntfs system.  From on the Knoppix cd, I also tried the testdisk command to restore the disk but even this wasn't able to fix it.  
  Than I downloaded BartPE and tried a data recovery tool, GetDataBack, from http://www.runtime.org/datarecovery.htm.  This was also not working because once the BartPE Windows XP version found the disk it tried accessing the ntfs system which was not possible.  I contacted Runtime and asked what to do, they told me to use a Windows 98 system on a spare disk and run GetDAtaBack from on that system.  Because my broken disk is a 120Mb SATA disk, I thought that I should better give it a try with Windows 2000 so that it could access the entire disk, which I installed on a FAT32 partition and all other partitions on that spare disk were also FAT32.  When it booted it displayed that it would do a redundancy check on the broken disk, which I had to cancel else the system hanged again.  Once in Windows 2000, it made me able to access the broken ntfs system without the need of GetDAtaBack.  I was able to backup 80% of my data but some folders were still unaccessible and that data got lost.  I also tried to recover those folders using GetDataBack but when it started scanning the disk, it popped up errors continuously, so I gave up on those cause the data wasn't that important.

  This occassion made me learn a lot during the past two weeks, I didn't want to give up on my data and now I'm very happy that I got the most important stuff out  of it.  If this happens again I'll trow myself out of the window from on the sixth floor, cause I didn't made any backups the last year... ; )

Thanks for your help and for all the previous information in this toppic.

Perre.

help me i tried to installl the windows i tried al the ways but nothing work
i formated at fat23 but blue message was appers fastfat.sys file then i tried to formated NTFS
but the same screen but Ntfs.sys file
what i have to do
i have the windows xp sp2
*i check another harddisk or memory the same problem apperas
please help

i just recived a PC at work with this same problem and found a very simple remedy.

All i had to do was insert XP Pro cd-rom into the drive boot to recovery console and run chkdsk /p. i might have benn lucky but i didnt have to create any boot disk's or found any serious problem had no data loss.

P.S. Is the copy of windows XP PRO with the problems genuine licensed?