BleepingComputer.com: Boot Problem

Posted in another forum but not getting any more replies on this issue. I know eveyone is busy but I am pressed for time as I have to go out of town soon. I am helping a friend whos desktop would not start after a power blip. Computer was running fine before the power blip but after the blip it would only boot to screen asking for safe mode, last known, etc. Ran CHKDSK from XP cd and computer then tried to boot with WinXP splash screen but then shows a BSOD stop error 0x000000BE.

What I found after trial and error is that this computer will boot up normally to the desktop if I boot first to Hiren's Boot CD and then select "boot to hard drive" It will boot this way every time without failure. It runs great with no apparent problems. If I try to boot regular with no cd in drawer, get the above BSOD.

I have cleaned and scanned with several programs and all have shown clean. (malwarebytes, Kaspersky TDSS Killer, Norman TDSS Cleaner, Microsoft Malicious Software, Dr. Web Cure It!)


Any suggestions on this strange boot issue would be appreciated.

System manufacturer and model?

You could try the fixmbr and/or fixboot commands from the Recovery Console.

Louis

eMachine
Model T3092
Windows XP Pro SP3

I could give fixboot a try but was afraid to go the fixmbr route after reading that it could make things worse. The computer can be used as it, just have to leave this boot disc in and hit one extra key when starting.

This post has been edited by ladylei: 17 July 2010 - 12:26 PM

the /fixboot and /fixmbr command is safe all they do is repair the boot sector and the Master Boot Record to there original configurations.

Descriptions of each

FIXBOOT

fixboot drive name:

Use this command to write the new Windows boot sector code on the system partition. In the command syntax, drive name is the drive letter where the boot sector will be written. This command fixes damage in the Windows boot sector. This command overrides the default setting, which writes to the system boot partition. The fixboot command is supported only on x86-based computers.

FIXMBR

fixmbr device name

Use this command to repair the MBR of the boot partition. In the command syntax, device name is an optional device name that specifies the device that requires a new MBR. Use this command if a virus has damaged the MBR and Windows cannot start.

Warning This command can damage your partition tables if a virus is present or if a hardware problem exists. If you use this command, you may create inaccessible partitions. We recommend that you run antivirus software before you use this command.

You can obtain the device name from the output of the map command. If you do not specify a device name, the MBR of the boot device is repaired, for example:
fixmbr \device\harddisk2
If the fixmbr command detects an invalid or non-standard partition table signature, fixmbr command prompts you for permission before it rewrites the MBR. The fixmbr command is supported only on x86-based computers.

from http://support.microsoft.com/kb/314058

coxchris, the below message is what I was concerned about. The computer is useable as it, just have to boot to CD, then to hard drive. I may try that as a last resort but I may look around a little longer.

Quote

I don't think there is a virus present but I can't rule out a hardware problem that may be causing this issue.

This post has been edited by ladylei: 17 July 2010 - 04:10 PM

Well...if you have a hardware problem now...eventually you may not be able to boot at all and do any troubleshooting of your suspicion.

Then what?

The fact is...that warning seems to confuse what triggers what...your partition tables may already be damaged, resulting in your current situation.

The only instance I know of where fixmbr is not necessarily advised...is on systems with nonstandard boot setups (such as a system employing a recovery partition, a Dell system, etc.

http://en.community.dell.com/support-forum...5/19670233.aspx

It's your choice, as I see it.

Louis

Thanks for the info Louis. If this were my PC I would give it a try right now. But since everything is running well I think I'll pass that by my friend and let him know it may take care of the problem before I give it a try.