Forum Home
Press F1
Thread ID: 68159	2006-04-19 22:32:00	Stop 0X24 error NTFS.sys in XP. Is it best to repair or reload?	Oggy (5399)	Press F1

Post ID	Timestamp	Content	User
447757	2006-04-19 22:32:00	Got the dreaded Blue Screen Of Death yesterday with the error message Stop0x00000024 blahdy blahdy blah NTFS.sys I've found out what it is and have looked at various forum posts about it. My question to those who have experienced this error is ... "am I best to try to repair XP or just to recover my data if possible and then reload XP?" I've seen people who have done both and a common comment on people who just took the repair option was that XP was a bit slower and/or flakier following just a repair. I'm not going to do the work myself but I do want to get the techy who does it to do the most appropriate fix. Other question is ... I have all my data on D: while XP resides on C: Will it be possible for D: to come through this unscathed and therefore not need to recover my data? I do have a backup of it from a couple of months back but it would be nice to have the whole data folder saved.	Oggy (5399)
447758	2006-04-19 23:43:00	From what I have read here (support.microsoft.com). It seems best that you get the techie to backup everything for you. A lot faster than trying to repair it too espcially if the NTFS partition table is corrupted. If a partition table is corrupted beyond repair then all the data on that hard drive will be lost as a new partition table will need to be created by formating the drive. The only reason this error could and most probably will affect your D: drive would be if you have only one physical hard drive but it is divided into two logical drives, C: and D:. Meaning in your computer, you have something like a 40GB Hard drive. (HDD) (This is very common nowadays) If you had two 40GB HDD's then C: would be a separate 40GB physical drive and D: would be a separate physical drive. In this case the ntfs.sys error on the C: would not impact the D: And making a backup of D: (if all data is ok on it) in this case would not be needed.	Mamaz (10231)
447759	2006-04-20 00:45:00	Yeah, it's a 250GB drive separated into a 20GB C: for the system files and the rest is D: for everything else. I split it that way for just this sort of problem but if it's not going to make a difference then perhaps i'm just better off having everything on one huge C:	Oggy (5399)
447760	2006-04-20 01:02:00	Yeah, it's a 250GB drive separated into a 20GB C: for the system files and the rest is D: for everything else. I split it that way for just this sort of problem but if it's not going to make a difference then perhaps i'm just better off having everything on one huge C: Well, depends I suppose. I would have done the same as you have if I had a monster HDD like that. You are absolutely correct in doing the partitions that way to prevent what has happened to you. Infact it may have saved you. IF the techie does a disk scan (scandisk or chkdsk using recovery console) on D: and finds partition table (be it NTFS or FAT) intact then all he would really need to do would be reformat C: (assuming NTFS partition table is corrupt) and then reload XP onto it. Wouldn't harm your data in D: if he knows what he's doing. Do you know how you got the error? Like anything you changed / installed on comp that resulted in it? As for my comment earlier regarding all data on HDD will be lost if partition table is corrupt that is incorrect. Sorry about that - every logical drive has its own partition table.	Mamaz (10231)
447761	2006-04-20 02:07:00	How it happened is a mystery. I've updated nothing recently and the only software installed was a couple of games about 3 weeks ago. Admittedly one of the games has had some issues over the last week with the sound going stuttery although the sound was fine with other games. I also noticed when that game was running the PC was having to deal with quite a bit of heat so perhaps it's all connected. Who knows? My techie will figure it out hopefully. Thanks for your advice. I'll be sure to tell the techie not to just charge in and reformat the whole disc straight away.	Oggy (5399)
1