Click to See Complete Forum and Search --> : PC not booting even in safe mode


abanerji
December 25th, 2005, 05:04 AM
I have a Compaq Presario (bought in 2002) with XP-Home. It came with the OEM's Windows CD. I have since then updated to SP1, and apply Windows update patches time to time. The immediate previous update was a few months back, and a few days back I got the latest MS patches (several). I have a sneaking feeling my present problem has happened due to some driver conflict, consequent to the latest patching.
Just info, AV software is updated daily. Have checked online for malware some days ago. Also, got a link from the spyware bulletin, and tested online for processes running ... nothing untoward. I am the only user of this PC, and practice safe browsing.

Now my problem of yesterday. I am writing this from a second PC, because my Presario is not booting. The WinXP-Home logo comes, continuous harddisc activity, then after some time a black screen, then I can see light on the DVD drive, and back to the WinXP-Home logo, and the same sequence goes on.
Once I got the safe mode choice screen, and it went upto IOMDISK.SYS load, and then failed to boot. The black screen came back.

Googled a bit, and got the sense IOMDISK.SYS may be the culprit. So, how do I correct my situation, please?

Gabriel
December 25th, 2005, 09:28 AM
Hi,
Welcome to WD formus abanerji
First try using the last known good method
http://support.microsoft.com/default.aspx?scid=kb;en-us;307852&sd=tech
If this won't do the trick try restoring your computer from the last restore point
If this won't do the trick you can try installing WindowsXP into the same directory (method I call "repair install")


Good Luck,
Gabriel

Ferrit
December 25th, 2005, 10:48 AM
Before i would try and reinstall of windows, I would.
Boot to the windows xp cd and when you get to the first choice.
Which is Repair from the consul, I would choose that and when you get to the cmd prompt.
Type this chkdsk /r <--- Space between the chkdsk and the /
Allow that to run and then reboot and see what happens