Thank you for taking the time to mark my reply as the answer. Howerver, I would ask you to un-mark the reply and wait until your issue is resolved. Thanks.. :-)
NTLDR:FATAL ERROR 57344 READING BOOT.INI
XP Home Edition will not boot anymore. I get the XPWindows Logo when I boot
then shuts down to a blank screen with the following Error posted at the top of
the blank screen.
Error:
NTLDR: FATAL ERROR 57344 READING BOOT.INI
Question: What is this error and how do I correct it so I can get my XP Windows back.
XPWindows Home Edition
Windows for home | Previous Windows versions | Devices and drivers
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
75 answers
Sort by: Oldest
-
Anonymous
2012-11-21T15:36:25+00:00 -
Anonymous
2012-11-21T16:59:34+00:00 when chkdsk /r is run it will check the entire disk ,and it can take a looong time depending on
the size of the disk it is checking ..
Sure is taking a looong time like you mentioned. Thought maybe
hours, but this processing has been going on since late Tuesday
when it was started and I'm only at 26 percent complete. At this
rate it will be a few days. Have you personally run chkdsk /r and
how long. What can I expect when it's 100 percent complete.
Will the computer automatically reboot. Did this work for you to
resolve your problem.
-
Anonymous
2012-11-21T17:16:12+00:00 I can appreciate your anxiety. The process can often take a very long time. As I previously stated there are several factors that come into play in respect to the amount of time it takes.
It is unclear from your post whether you booted from the disc or allowed check disk to run as a result of receiving a prompt when trying to load Windows. If the later is the case the computer will automatically reboot.
There is no way for us to know to any degree of certainty whether or not this will resolve your issue. There are times it does and times it doesn't. Regardless, it is the best place to begin. I would suspect your chances of success are fairly good considering Windows is prompting you to run check disk on startup.
-
Anonymous
2012-11-23T06:08:51+00:00 Update:
The computer has been running since late afternoon 11-20-12
with chkdsk processing and completed whatever it was processing 100%
but is now doing something new. What is it doing now that is back to
1% complete. Will explain as I go along with this response.
Sample of what I saw on the blue screen while it was processing in the
during the chkdsk: The whole screen was filled with all kinds of code
checking what looked to be all the files on the hard drive.
Windows Replaced Bad Clusters In File\Program Files\
IMSI\FormToolv5\Forms\u6502.FTF
Note: Upper Case Letters L were always in reverse in the codes
which I'm not shown in the above sample code.
Windows Replaced Bad Clusters In File\Windows System32\Config\
SystemProFile\Local Settings\Temp\Heat.Log
Of Name (null)
File And Folder Verification Is Complete.
Convert Lost Chains To Files (Y/N)? Yes
Insufficient Disk Space To Recover Lost Data.
4438944 kb In 31279 Recovered Files.
Windows Is Verifying Free Space...
1 Percent Completed...
Note: I was not at the computer when the question:
Convert Lost Chains To Files (Y/N)?
Need help with what the computer is doing now based on
the above info and should I continue with the chkdsk
-
Anonymous
2012-11-23T07:12:11+00:00 yes let it run as it has not finished, there are 5 stages and I believe that verifying free space is the last one.
with that many problems, I believe that your hard drive may be failing.
once chkdsk completes, you should really run it again, Sorry. :)