XP Home reboots, safe mode stops at mup.sys

[candyman200]

I've been working on a Presario 5000 w/XP Home. Compaq Tech Support recommended repairing the OS. I created the 6 disk set (Recovery CD not available) and ran repair. Repair completed then ran fixmbr, fixboot, chkdsk /r, bootcfg /default successfully. Exited the console and the PC still reboots.

I can use a new HDD to bootup and I can see the original PC w/NTFS and FAT partitians. I have copied the important data to a CD. When I try to restart with the original HDD it still reboots.

I cannot get into any form of Safe (or Last Good) mode.

I'd appreciate any input you can offer.

Thanks in advance.

 

[linney]

Not exactly sure what you did with the 6 Disks you mention, did that allow you just to access the Recovery Console?

To repair Windows itself you would need a Recovery CD (or partition).

"The Windows XP startup disk allows computers without a bootable CD-ROM to perform a new installation of the operating system. The Windows XP startup disk will automatically load the correct drivers to gain access to the CD-ROM drive and start a new installation of Setup. You cannot upgrade from a Windows XP startup disk."

http://www.microsoft.com/downloads/...FamilyID=E8FE6868-6E4F-471C-B455-BD5AFEE126D8

How to Perform an In-Place Upgrade (Reinstallation) of Windows XP (Q315341)

http://support.microsoft.com/support/kb/articles/q315/3/41.asp

Your hard drive manufacturer will have free diagnostic software (run from floppy and bootable) to thoroughly check the condition of the suspect drive.

 

[candyman200]

According to Compaq Tech Support - when you boot from the disks you are offered 2 options - install or repair (true). If you run install you need the XP Home installation CD. If you run repair from the recovery console then you can fix boot records, chkdsk and repair, fix boot config, etc. Again, according to Compaq tech support this should correct any corruption and get the OS running again.

Since I'm still having a problem I guess the process doesn't work as indicated. Because I can boot from another HD, I can assume there's not a hardware (excluding the orignal HD) issue. I check the MAXTOR site for a diagnostics.

I have a feeling there's a corruption somewhere but I don't know how to pinpoint it.

Any other additional suggestions will be gladly accepted.

*** Fix what's broken, whether it's a machine or a process. People don't need to be burdened by problems that could be corrected.

 

[linney]

Assuming you have a dual booting operating system (or some way to access the suspect drive), perhaps you can access the Event Viewer of the operating system that is loaded on the suspect drive.

If you do have some sort of access, you might be able to browse to C:\WINDOWS\system32\config and then locate the SysEvent.evt file. Either you can read it directly from any second operating system you may have, or, you can now place a floppy in the drive and use the Copy command to copy SysEvent.Evt to A: (This last option may be limited by - HOW TO: Add More Power to Recovery Console By Using Group Policy in Windows XP Professional

http://support.microsoft.com/default.aspx?scid=kb;en-us;310497&FR=1&PA=1&SD=HSCH

)

Take the floppy with SysEvent.Evt to another XP machine and load the Event Viewer. Under Action select Open Log File and browse to the file on the floppy. Open the Saved Log File and read it.

When you close the Event Viewer the saved file is not retained on the second operating system.


As you at least do have access to the Recovery Console this may be an option for you.

An easy to follow recovery console description when unable to start computer due to corrupt registry.

http://www.digitalwebcast.com/2002/03_mar/tutorials/cw_boot_toot.htm

This is a layman's version of Q307545 in simple language.

 

[candyman200]

Thanks for the reply "linney".

I installed a 2GB HD configured for Win2K as the primary and the questionable HD as the slave. I can access the slave with no problem. The SysEvent is corrupt so I can't read it. If I delete the file will the system recreate it (not corrupt I hope)?

On the original HD the boot partitian is NTFS, several programs and data is stored on the FAT partitian.

I ran the Maxtor diagnostics and the HD is good. I also updated the BIOS and still an issue on bootup.

*** Fix what's broken, whether it's a machine or a process. People don't need to be burdened by problems that could be corrected.

 

[allteltec]

I would try this, boot to the Repair Concel using your 6 floppys and use this guide.

http://www.digitalwebcast.com/articles/viewarticle.jsp?id=8658

 

[candyman200]

Thanks allteltec and linney for the digitalwebcast link. I'll try it early next week and I'll post the results. Have a great New Year everyone.


*** Fix what's broken, whether it's a machine or a process. People don't need to be burdened by problems that could be corrected.

 

[linney]

If I delete the file will the system recreate it (not corrupt I hope)?"

Probably it would be recreated but I wouldn't bother trying as it (SysEvent.Evt) is not really relevant at the moment, it is the other files in that folder (Config, and don't delete them until you get into the Charlie White article) that I would be worrying about.

You might be able to glean a minimal amount of information (hardly much of a help) by looking at it in Notepad. Or you could see if this link is of any help regarding that file, SysEvent.Evt.

auto export event logfile
thread779-940195

It seems like you may have corrupted Window's configuration files and this may be preventing you from booting, your best bet is to re-install XP. I would contact Compaq and try for a duplicate Recovery CD, your bound to need it sooner or later I would imagine.

Meanwhile the Charlie White article has proved itself to be a life saver on many occasions.