XP WONT BOOT UP

[Don Hardie]

This happened when I tried to boot up one recent morning after the previous
nights shutdown.

My XP Pro SP3 won't boot up, when I try Start Windows normally I get the
Windows screen then it reboots, when I try to start from Safe mode etc., I
don't even to the Windows screen before it reboots.
I tried to do a repair reinstall from the XP PRO CD, it loads all the
windows files and then I get the blue screen with the Error Code 0x0000007b
(0xF78D254, 0x0000034, 0x00000000, 0x00000000).
I tried my PCI PC Analyser it gets to the code for “enter setup†when the
Windows screen comes up and the system reboots.

Can you help?

Don Hardie
ASUS P5GC-MX MOTHERBOARD
1.6 GHs Dual Core CPU
2GB PC5300 DDR2-667MHz RAM

 

[Tim Meddick]

Have you connected ANYTHING new /changed ANY new hardware to your system
recently?


==



Cheers, Tim Meddick, Peckham, London.

 

[Peter Foldes]

0x0000007B: INACCESSIBLE_BOOT_DEVICE
Windows lost access to the system partition or boot volume during the startup
process. Typical causes: Installing incorrect device drivers when installing or
upgrading storage adapter hardware, or a virus.
http://msdn.microsoft.com/en-gb/library/ms795508.aspx

 

[Randem]

Something that might help
http://www.randem.com/discus/messages/9402/9406.html?1236319938

--
Randem Systems
Your Installation Specialist
The Top Inno Setup Script Generator
http://www.randem.com/innoscript.html
Disk Read Error Press Ctl+Alt+Del to Restart
http://www.randem.com/discus/messages/9402/9406.html?1236319938

 

[Gerry]

Don

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms795508.aspx

0x0000007B: INACCESSIBLE_BOOT_DEVICE
(Click to consult the online MSDN article.)
Windows lost access to the system partition or boot volume during the
startup process. Typical causes: Installing incorrect device drivers
when installing or upgrading storage adapter hardware, or a virus.
Source: http://aumha.org/a/stop.htm

Advanced troubleshooting for "Stop 0x0000007B" errors in Windows XP
http://support.microsoft.com/kb/324103/en-us


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Paul]

This happened when I tried to boot up one recent morning after the previous
nights shutdown.

My XP Pro SP3 won't boot up, when I try Start Windows normally I get the
Windows screen then it reboots, when I try to start from Safe mode etc., I
don't even to the Windows screen before it reboots.
I tried to do a repair reinstall from the XP PRO CD, it loads all the
windows files and then I get the blue screen with the Error Code 0x0000007b
(0xF78D254, 0x0000034, 0x00000000, 0x00000000).
I tried my PCI PC Analyser it gets to the code for “enter setup†when the
Windows screen comes up and the system reboots.

Can you help?

Don Hardie
ASUS P5GC-MX MOTHERBOARD
1.6 GHs Dual Core CPU
2GB PC5300 DDR2-667MHz RAM

It's an Asus. Be careful

Asus has "overclocking protection". (There is a proper name for the
feature, perhaps COP ?) Anyway, if for any reason, the BIOS thinks
the computer has crashed during the last session, on the next BIOS POST
sequence, the BIOS settings get reset. The intent is to use
"stable" settings, so the computer can POST again.

Now, say in the process of resetting the BIOS, the conditions for
the disk interface get changed. Suddenly, the Southbridge is in
a different mode, and the disk driver used in Windows is no longer
correct for the job.

The solution is to visit the BIOS, and review the settings used
for disks. Intel has IDE, AHCI, and RAID as options, and you'd
want your choice to get restored.

As to why the "overclocking protection" got triggered, it doesn't
have to be due to overclocking. All it takes is some instability,
an abnormal shutdown of the computer, a power failure, and the next
time you start, it may happen. If this happens to you frequently,
it might be worth wasting time trying to figure out why. If
it happens once a year, just remember the symptoms and the
workaround (correct the BIOS setting).

Boot problems can also be caused by plugging in "funny" hardware,
such as leaving an unbootable floppy in the floppy drive,
your digital camera memory device in a card reader and so on.
But my bet right now, is this is Asus COP causing the BIOS settings
to change. I had one Asus motherboard, where I was constantly
into the BIOS to correct one of the storage devices. At least
the BIOS default after COP in that case, didn't cause a
boot problem. So for me, it was annoying but not critical.

HTH,
Paul

 

[Anna]

Paul:
Assuming the suggestions you've rec'd haven't resolved your problem...

1. We're assuming your system is malware-free. Is that a reasonable
assumption?

2. Have you tried running the chkdsk /r command via the Recovery Console?

3. While you're at it, it probably would be a wise idea to check out your
HDD with the diagnostic utility (generally) available from the disk's
manufacturer. Just on the off-chance you're dealing with a defective drive,
even though it doesn't sound like it.

4. If you have another HDD available, it might be useful to attempt a
fresh-install of the OS onto that disk to see if any problems arise.
Anna

 

[Anna]

Sorry Paul. I addressed my response to the wrong person. I meant, of course,
Don, the OP.
Anna

 

[Don Hardie]

Thank you all for your suggestions.
I ran Avira AnitVir Rescue CD and it didn't find any problem. I then tried
to boot up from a backup c drive in a removal caddy, this didn't work so I
disconnected the C drive and then it booted from backup. I then swapped the
drives and the system booted up and ran checkdisc on the problem drive and
found numerous problems.
I then formatted the problem drive and cloned the c drive onto it, and hope
it will work if I need the backup again.

Thank you all again.

Don