Help with my computer

[Irrelevant]

alrighty, im on my laptop right now because my computer is having some technical difficulties.

When I turn on the computer it executes itself exactly like this;
Computer turns on.

First screen listing the RAM/Processor info pops up.
BIOS and CMOS synopsis appears.

The computer starts loading on the normal XP loading screen. Not the one where it asks you which profile to load, but before that. About 5-10 seconds into this, computer restarts and repeats the process only to restart again and never reaches the login screen.

prior to this malfunction of sorts there was a shortage of power due to too many appliances running at the same time :P, which was mostly my fault.
The computer was downloading some sort of upgrade and was shut of along with the rest of the house in mid-download.

im not very good with computers, and i dont use them much- i've searched through the handbook and technical errors section of it and havn't found any answer to my problem. Again I am not good with computers so excuse me if my description of how this whole thing goes on is a little sketchy.

[Zidane007nl]

Did you try to run Windows XP at Safe Mode? Hold F8 when turning on your computer and a startup menu will appear. You can select startup from Safe Mode there.

Did there appear an error when starting up, or a blue screen?

[Irrelevant]

Did you try to run Windows XP at Safe Mode? Hold F8 when turning on your computer and a startup menu will appear. You can select startup from Safe Mode there.

Did there appear an error when starting up, or a blue screen?

yes, a blue screen. even while trying to enter w/ safe mode.

[Belazor]

Copy down the entire hex error string and google the first octet. That should turn up some results.

[Irrelevant]

well.. i just rebooted from a ghost CD and wiped out the comp to start a new since nothing else was working....
thanks for the help tho -i tried it.

[Depu Techiikue]

Ah, yeah, sorry I didn't get to this sooner. Something similar happened to me a few months ago. I found out through hardcore customer support that it does this because a large portion of your Windows files become corrupt, and malfunction, causing the computer to think that it needs a reboot, since Windows files only change their functions when the computer needs to reboot. So, consequently, the only way to fix it is to either do what you did, or spend a long time going into your computer through CMD and using a lot of syntax and programming to fix it. :P

But since you got it up again, I'll go ahead and close this since the problem is solved.