deepthought67
Technical User
I recently booted my system running Windows XP Pro and received this error on a BSOD:
A problem has been detected and windows has been shutdown to prevent damage to your computer. If this is…
*** STOP: 0x00000024(….)
*** Ntfs.sys – Address…
This error is documented on Microsoft.com for windows 2000 and many tech websites have people posting solutions. None have worked so far.
What I have done:
1. Booted from win xp cd and tried to use the recovery console – R option “to repair” so that I could run chkdsk /f from the command line. Failed with the same error before getting to the command promt.
Then I tried to install a new installation of windows in a new directory. It failed with the same stop error.
2. Installed second hd with a windows partition formatted to FAT32 and slaved the non-booting drive to it. This failed with the same error. (I also tried formatting the second hd as NTFS and trying it – same error).
The computer boots and runs fine using the new windows installation as long as the non-booting drive is physically disconnected.
3. Tried using the windows 2000 boot disk remedy (it can read NTFS partition) to boot to DOS to run chkdsk. It got past the first error and started to run chkdsk but then failed with a “could not find entry point” error. This error was undocumented on the net under many types of Google searches.
What I am currently doing.
I downloaded the ntfsreader.exe from ntfs.com and it was able to read directory and file information and write it to a new hd with a FAT32 partition. However, the free version does not recover longfile names. You can read them, but DOS does not let you write with long file names. It worked, but recovering the files without the long filename information was troublesome.
So I paid $50 for the full version, called unerase.exe, and it does recover long filename recovery.
I am currently imaging the hd partitions to a new drive. It is working fine except I’m into a 6 hour recovery process just to image the first partition that is 36 GB large.
I also downloaded the knoppix and I hope to use it to speed the process up once I know that the hd has been imaged.
I see a lot of posts where others have been advising some that their hd is just gone. But, it might be a case like mine where the data in the ntfs partition is unreadable using windows methods. So a DOS or a Linnux method must be used.
A problem has been detected and windows has been shutdown to prevent damage to your computer. If this is…
*** STOP: 0x00000024(….)
*** Ntfs.sys – Address…
This error is documented on Microsoft.com for windows 2000 and many tech websites have people posting solutions. None have worked so far.
What I have done:
1. Booted from win xp cd and tried to use the recovery console – R option “to repair” so that I could run chkdsk /f from the command line. Failed with the same error before getting to the command promt.
Then I tried to install a new installation of windows in a new directory. It failed with the same stop error.
2. Installed second hd with a windows partition formatted to FAT32 and slaved the non-booting drive to it. This failed with the same error. (I also tried formatting the second hd as NTFS and trying it – same error).
The computer boots and runs fine using the new windows installation as long as the non-booting drive is physically disconnected.
3. Tried using the windows 2000 boot disk remedy (it can read NTFS partition) to boot to DOS to run chkdsk. It got past the first error and started to run chkdsk but then failed with a “could not find entry point” error. This error was undocumented on the net under many types of Google searches.
What I am currently doing.
I downloaded the ntfsreader.exe from ntfs.com and it was able to read directory and file information and write it to a new hd with a FAT32 partition. However, the free version does not recover longfile names. You can read them, but DOS does not let you write with long file names. It worked, but recovering the files without the long filename information was troublesome.
So I paid $50 for the full version, called unerase.exe, and it does recover long filename recovery.
I am currently imaging the hd partitions to a new drive. It is working fine except I’m into a 6 hour recovery process just to image the first partition that is 36 GB large.
I also downloaded the knoppix and I hope to use it to speed the process up once I know that the hd has been imaged.
I see a lot of posts where others have been advising some that their hd is just gone. But, it might be a case like mine where the data in the ntfs partition is unreadable using windows methods. So a DOS or a Linnux method must be used.