Hi,
XP Pro boots normally just fine. But Safe Mode = BSOD. ???
This is after "ntfs.sys" problems that crashed XP which I have been troubleshooting and trying to repair.
Anyone have any clues?
Synopsis:
After a motherboard powerdown during XP installation formatting which left the NTFS partitioned drive(s) in a state from which simple reformatting was ineffective, I zeroed the system drive with Seatools, repartitioned, reformatted FAT32 and reinstalled XP (unattended install with nVidia nForce3 SATA RAID drivers slipstreamed) onto IDE 0 E:\ = FAT32, etc. After that I succesfully installed a ton of pro audio applications on G:\Program Files (FAT32). When I went to group copy eight 1.9 GB audio sample files from the RAID 0 array (NTFS, not previously corrupted, no history of errors) to IDE 1 L:\ (NTFS) (corrupted during previous XP install and reformatted, but not completely zeroed first as the system drive was) I got a BSOD with a 0x50 ntfs.sys error again.
Disconnecting IDE 1 allowed me to boot into XP, but safe mode still BSOD'd. Paragon Drive Backup's linux-on-a-CD allowed me to rename the ntfs.sys file, and then XP booted with the corrupt drive attached so I could use the DVD burner to get the OS images off of its FAT32 partition.
Reformatted the IDE 1 NTFS partitions. Restored ntfs.sys.
But again, reformatting was ineffective, kept getting "XP wants to check one or more of your drives" messages on bootup and got another "ntfs.sys" BSOD error when I tried to copy a 5MB folder onto one of the newly reformatted IDE 1 NTFS partitions.
Wouldn't boot XP normal or safe again.
(I assume that the safe mode BSOD is related to the ntfs.sys problem, but...?)
So I zeroed IDE 1 (Seagate 200GB takes all night and half a day) and repartitioned/reformatted (using the procedure that had successfully restored the system drive on the previous goaround).
So now, I can boot into XP pro just fine and see all the drives/partitons in Windows Explorer, though I'm hesitant to do too much till I find the source of the problem. I no longer get the "Windows wants to check some of your drives" message on bootup. But the strange thing is, I cannot boot into Safe Mode. Safe Mode still gives me a 0x0A BSOD.
Anyone have any ideas? Is there some registry entry or log entry that safe mode is preoccupied with while the full OS can see around it? Or is there still some (possibly other) root problem cause lurking in there somewhere that the normal mode OS can't see? Somehow, this combination doesn't make sense to me.
When in the XP desktop environment I've saved all the data to DVD using the Nero software that came with the drive. Works OK. I can poke around here and there with no problems, run regedit, use the control panel, etc. but I'm not going to attempt that fateful file copy again till I try some other things. How can this be? Windows is happy to boot normally, but it absolutely will not boot into safe mode!
Anyone have any insights and/or suggestions?
I have a documented history of the problem and detailed system specs, minidump, etc. but I'll hold on that unless it's requested. Possibly relevant, though, is: 1GB RAM (memtest86 says it's OK), "Pagefile" = 50 MB on E:\ (5.5GB) plus 1.5 GB on D:\ (2GB) partition; and "Documents and Settings" on F:\ (6GB).
--torandson
XP Pro boots normally just fine. But Safe Mode = BSOD. ???
This is after "ntfs.sys" problems that crashed XP which I have been troubleshooting and trying to repair.
Anyone have any clues?
Synopsis:
After a motherboard powerdown during XP installation formatting which left the NTFS partitioned drive(s) in a state from which simple reformatting was ineffective, I zeroed the system drive with Seatools, repartitioned, reformatted FAT32 and reinstalled XP (unattended install with nVidia nForce3 SATA RAID drivers slipstreamed) onto IDE 0 E:\ = FAT32, etc. After that I succesfully installed a ton of pro audio applications on G:\Program Files (FAT32). When I went to group copy eight 1.9 GB audio sample files from the RAID 0 array (NTFS, not previously corrupted, no history of errors) to IDE 1 L:\ (NTFS) (corrupted during previous XP install and reformatted, but not completely zeroed first as the system drive was) I got a BSOD with a 0x50 ntfs.sys error again.
Disconnecting IDE 1 allowed me to boot into XP, but safe mode still BSOD'd. Paragon Drive Backup's linux-on-a-CD allowed me to rename the ntfs.sys file, and then XP booted with the corrupt drive attached so I could use the DVD burner to get the OS images off of its FAT32 partition.
Reformatted the IDE 1 NTFS partitions. Restored ntfs.sys.
But again, reformatting was ineffective, kept getting "XP wants to check one or more of your drives" messages on bootup and got another "ntfs.sys" BSOD error when I tried to copy a 5MB folder onto one of the newly reformatted IDE 1 NTFS partitions.
Wouldn't boot XP normal or safe again.
(I assume that the safe mode BSOD is related to the ntfs.sys problem, but...?)
So I zeroed IDE 1 (Seagate 200GB takes all night and half a day) and repartitioned/reformatted (using the procedure that had successfully restored the system drive on the previous goaround).
So now, I can boot into XP pro just fine and see all the drives/partitons in Windows Explorer, though I'm hesitant to do too much till I find the source of the problem. I no longer get the "Windows wants to check some of your drives" message on bootup. But the strange thing is, I cannot boot into Safe Mode. Safe Mode still gives me a 0x0A BSOD.
Anyone have any ideas? Is there some registry entry or log entry that safe mode is preoccupied with while the full OS can see around it? Or is there still some (possibly other) root problem cause lurking in there somewhere that the normal mode OS can't see? Somehow, this combination doesn't make sense to me.
When in the XP desktop environment I've saved all the data to DVD using the Nero software that came with the drive. Works OK. I can poke around here and there with no problems, run regedit, use the control panel, etc. but I'm not going to attempt that fateful file copy again till I try some other things. How can this be? Windows is happy to boot normally, but it absolutely will not boot into safe mode!
Anyone have any insights and/or suggestions?
I have a documented history of the problem and detailed system specs, minidump, etc. but I'll hold on that unless it's requested. Possibly relevant, though, is: 1GB RAM (memtest86 says it's OK), "Pagefile" = 50 MB on E:\ (5.5GB) plus 1.5 GB on D:\ (2GB) partition; and "Documents and Settings" on F:\ (6GB).
--torandson