windows xp crashes at loading and reboots

Microsoft Windows xp professional w/sp2
February 19, 2010 at 12:20:57
Specs: Windows Vista
Windows Xp crashs during windows loading screen and reboots. Displays a blue screen with no errors on it only the stop information, 0x00000024 (0x001902FE, 0xBA52F380, 0xBA52f07c,0x8AD5980F). This blue screen stays up for less than a second, needed to video record it to get the numbers. Windows doesn't load in normal mode, or any of the safe modes. I have tried chkdsk /r and /p. Bootcfg /scan fails, and /rebuild also fails. I have also cleared Cmos on my motherboard, which didn't work either. I also tested the ram, tried booting with 1 of 3 sticks in 3 times rotating the sticks, I wouldn't think all 3 would fail at the same time. The HD does show serial numbers tho and appears to be working. This all started when i was running a virus scanner, it crashed, and the problems started. Any help is appreciated, I have yet to try fixmbr, and a repair install. The fixmbr says it could cause a problem with the HD, that is the reason I haven't tried it yet. Any suggestions or help is appreciated. Thanks

See More: windows xp crashes at loading and reboots

Report •

February 19, 2010 at 19:48:14
Check your hard drive with the manufacturer's diagnostics.
See the latter part of response 1 in this:

(thanks to Dan Penny for this link:)
Hard Drive Diagnostics Tools and Utilities

If you don't have a floppy drive, you can get a CD image diagnostic utility from most hard drive manufacturer's web sites, but obviously you would need to make a burned CD, preferably a CD-R for best compatibilty, on another computer if you need to.

If the hard drive itself tests okay, any data problems found can be fixed, one way or another.

If the hard itself passes...........

" I have tried chkdsk /r and /p. Bootcfg /scan fails, and /rebuild also fails."

If you can get into Recovery Console by booting with the XP CD, and are able get into C:\Windows then....

"STOP: 0x00000024" = NTFS_FILE_SYSTEM

Your problem may be that the NTFS.SYS file is corrupted.

It's in the \i386 folder on the XP CD, and it's NOT compressed - 562kb

It's in normally in

On my computer, it's also in

Access the XP CD drive letter in Recovery Console, then the \i386 folder on the CD.

If you're not sure which drive letter that is, type the drive letter you think it might be, followed by a colon, press Enter; then type: dir , press Enter. If the drive letter is correct you will see about 6 files and 5 folders listed , including a \i386 folder .)

Then type cd\i386 (press Enter)

(I might have the syntax wrong - it can be different in the Recovery Console than it is in Windows - it might be cd \i386 or cd i386 - type: help cd
for how to use it )

Then copy NTFS.SYS to C:\Windows\System32\drivers

copy ntfs.sys C:\Windows\System32\drivers\ntfs.sys (press Enter)


copy ntfs.sys C:\Windows\System32\drivers\ (press Enter)

If that works, type: exit (press Enter)

which will exit the Recovery console and reboot the computer.

Don't press the key to boot from the XP CD again -
Try booting normally

If you're not allowed to do that, tell me (us) what the error message you get is, exactly.

Depending on what that message is, I may be able to tell you another command to try.


Make yourself a Linux boot CD of some kind that can read NTFS partitions (I know nothing about that),
and copy NTFS.SYS to C:\Windows\System32\drivers with that.

Then try booting normally.

"The fixmbr says it could cause a problem with the HD, that is the reason I haven't tried it yet. "

That's along the lines of the default message.
It always displays that message. If you have NOT used a program on the hard drive to allow a larger hard drive to be used with a system that has a bios that can't recognize the full size of the drive (generically called a dynamic overlay), or have NOT used a third party multi boot manager program on the drive, or similar, running won't do any harm, but that probably will NOT fix your specific problem.
Same for fixboot.
(Your hard drive is booting, and Windows is trying to load, so there's probably nothing wrong with the mbr or the boot sector.)

Running a Repair installtion procedure would pribably work, if there'snothing werong with the harddrive, but there's some risk to running that - NOTHING can go wrong that will prevent you from completeing Setup.

Report •

February 20, 2010 at 06:06:59
Perhaps may be wise to safeguard your data first - before setting about resolving the actual main problem?

Boot with a Knoppix/Ubuntu disk and copy all data off the drive to optical-media; and ideally verify those copies are accessible on at least one other system before proceeding further...

If you can access the HD OK then it pretty well rules out the drive itself as being an issue here? But the diagnostics "Tubes..." suggests wouldn't do any harm to run... (just in case...). and for respective .iso file - which download (whichever you prefer) and burn to a dvd. Use that disk to boot system...

Did you install any very recent updates from M$? There are numerous reports currently re' a slew of BSOD etc. following a particular update... And it doth also appear to provide false positives too re' virus issues..?

I did post a reference earlier this week re' thes update/BSOD issue; and here is another (perhaps the same one again) reference to it...

It may be worth to read as it "may" shed light on your current problem(s)...?

Report •

Related Solutions

Ask Question