Link to home
Start Free TrialLog in
Avatar of SteveHodge
SteveHodge

asked on

XP reboots after splash screen

This morning my XP Professional SP-3 machine refuses to get beyond the splash screen. It flashes up the splash screen then shows the boot failure dialog, but nothing works, not safe mode nor last known configuration. Whatever I do it reboots, shows the splash screen then the boot failure dialog. There have been no changes to hardware for a couple of weeks.  I tried loading the BIOS set-up defaults but got the same behaviour.
I have a rescue disk image back-up from a few weeks ago but don't want to use it if there is something simple I can do as I have installed a few programs since, and it would take a lot of time. I do have the original windows disk, so could use the recovery console I suppose
ASKER CERTIFIED SOLUTION
Avatar of Jonvee
Jonvee

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jonvee
Jonvee

Another earlier thread>
XP keeps rebooting just after splash screen disappears:
https://www.experts-exchange.com/questions/21697477/HELP-XP-keeps-rebooting-just-after-splash-screen-disappears.html
Avatar of nobus
try running chkdsk on the drive from recovery console  http://support.microsoft.com/kb/314058
Avatar of SteveHodge

ASKER

Thanks for this.
Fixed now, rather mysteriously
Not sure if it was hardware
I loaded the XPCD and it started Could not see the disk drives, but maybe this was because I didn't load the RAID drivers. Loaded the recovery console but did not ask it to change anything.
Also my Genie recovery disk, it loaded too and it had the RAID drivers so I could see all the disk drives, but again I did not change anything
Then, when I accidentally rebooted, the system started fairly normally. It wanted to run chkdsk, and did and then started
Question: could this have been some kind of intermittent hardware problem?? If so like the Terminator, it will be back, I suppose
Or could one or other of the system disks have fixed the problem - doesn't seem likely does  it?
Should welcome your opinion
to your Q's : probably a file, or link to it got corrupt on the disk
once you started from a cd, and accessed the disk, the problem was corrected.
Spli the points, both answers helpful