booting problem

[atc_traffic856]

windows xp pro dell p3 system
the problem is within the booting up sequence:
computer reaches the desktop and than reboots again completing the same scenario. Throwing this question for some tips as where to start troubleshooting>> Video card connection> software problem or both >> hopefully it is not the MB> If I receive a few suggestions then I will go from there.
Thankyou

[Paul Komski]

I suppose it could be Sasser (http://ask-leo.com/what_are_lsass_lsassexe_and_sasser_and_how_do_i_kn ow_if_im_infected_what_do_i_do_if_i_am.html) or one of its RPC exploit cousins. If its not malware then you could try a repair installation (http://www.michaelstevenstech.com/XPrepairinstall.htm).

[Sylvander]

...your computer restarts repeatedly when you try to start Windows XP (http://support.microsoft.com/?kbid=314466)

[Paul Komski]

If the PC really actually gets to the Desktop, as described, then the link entitled "Black startup screen is briefly displayed and your computer restarts repeatedly when you try to start Windows XP" is not relevant.

Does the restarting also happen in Safe Mode?

[Sylvander]

"not relevant"
Huh!? :confused:

That link was saying that if:
(a) There was a Fatal system error... [is this not possible at this late stage?]

And...
(b) The Automatically restart option is configured....

And...
(c) The Paging File on the Windows partition [this is the only one that counts] isn't big enough to take the memory dump from the amount of installed RAM...

The PC would restart repeatedly.

Isn't the black screen just what would happen if this took place at an earlier stage of Startup?

Perhaps you could explain?
What have I misunderstood?

[Paul Komski]

Res ipsa loquitor

SYMPTOMS
When you attempt to start Microsoft Windows XP, the black startup screen may be briefly displayed, and then your computer restarts repeatedly.

If the booting gets as far as the desktop and crashes/reboots then software running from windows is almost certainly involved or is the direct cause. If not then a direct hardware failure could be implicated but I doubt the registry or paging file would be implicated.

Windows XP may encounter a problem during startup that results in a STOP error message. Depending on the system configuration, the blue screen may not be displayed long enough for you to record the error information. However if the system gets to the desktop and experiences a "Fatal Error" a BSOD should have been displayed - but has not been reported.

The symptoms described are very typical of sasser type worms - particularly on an older system that may not have any SPs, are unpatched and/or lack an effective firewall.

[Sylvander]

"if the system gets to the desktop and experiences a "Fatal Error" a BSOD should have been displayed"
But the point made by that web page is that the problem only takes place because/if/when Windows is NOT configured to display an error message [on a BSOD], but instead to Automatically restart.

I think what then happens is....
On restart...
Because the dump of RAM to the Paging File has failed...
The system continues to experience that [attempt to dump to Paging File] Fatal Error, which is different to the original cause...
And so it repeats continuously. :(

p.s. I don't understand Latin, but managed to find a way to translate to:
"the thing speaks for itself (http://en.wikipedia.org/wiki/Res_ipsa_loquitur)".

[Paul Komski]

A persistent rebuttal including the quote:NOT configured to display an error message
I think the configuration referred to deals not with automatically displaying a BSOD error message but with automatically restarting after the appearnce and close down of such a BSOD. It is recommended to prevent the restart automatically or to try safe mode in order to read the BSOD. It is the restart which can be changed via the registry and not the appearnce (however fleeting) of the BSOD with its STOP message.

As far as I am aware there are not any STOP messages in this case. Nor should they be "fleeting" when booted completely to the Desktop.

PS If there have been minidumps then this should appear in the Dr Watson logs etc - and so can be checked out.

[Paul Komski]

If you want to give yourself a temporary scare or cant remember what a BSOD looks like then try the BSOD screen saver.

http://technet.microsoft.com/en-gb/sysinternals/bb897558.aspx

Making note of the words such as "If this is the first time you have seen this message restart your computer". Etc, etc.

[Sylvander]

1. "there are not any STOP messages in this case"
It would be nice to get positive confirmation of that.
If the reboot isn't caused by [the Windows response to] a stop error, what would be causing it I wonder?

2. "Nor should they be "fleeting" when booted completely to the Desktop"
Any idea why they would be fleeting at an earlier stage but not at this later stage?

3. "I think the configuration referred to deals not with automatically displaying a BSOD error message but with automatically restarting after the appearance and close down of such a BSOD. It is recommended to prevent the restart automatically or to try safe mode in order to read the BSOD. It is the restart which can be changed via the registry and not the appearance (however fleeting) of the BSOD with its STOP message"
OK, got that.
Yet another thing to try to remember. :(

[atc_traffic856]

I am sorry for I should have given a more concise explanation.
This is exactly what happens:
1. After booting up this PC Dell p3 XP/pro the very first scene is a black screen/ which is normal/ there is a dell message of alert at the top left hand corner of the screen/ message is a typical Dell about cover removable
2. Booting process continues/ with no given messages/ no extra clues to sound defects/ timing is normal from start to desktop/ When it finally reaches the desk top/ you have enough time and clarity of the d/t to see the Icons on the screen and the typical colors of the screen/ this is very very short although.
3. Now this may help> after the milli/second screen exposure/ there is a sounding "click" and then the process starts again >> booting and restarting same over and over again??
I can get into the sys setup and also safety mode. I am trying to cut corners here as where to start trouble shooting > maybe starting to see as you have mention software first and then after I have done the necessary software trouble shooting eg virus, windows error , file error, et cetra.
The next step would be hardware old connectors check them/ power source
maybe replace>>
I really would need help trying to bug out the software trouble shooting/this would be the hardest area>> Maybe if you could possibly give me a bit of a sequence structure to begin it/ that would really help.
Thank you all>>

[Paul Komski]

If you can boot successfully to safe mode then you could next run msconfig and uncheck "load startup items" and then reboot normally. If the system restarts normally then you should have got back your networking and such like functionality and be able to install service packs and other anti-malware ulitities or scan the system with HijackThis etc.

The fact that you can get to safe mode implies a software based problem. You could then also go back into msconfig and add back the startup items one by one to see if you can thus "grab" the culprit.

It would be nice to get positive confirmation of that.
Dr Watson Logs: http://support.microsoft.com/kb/308538 assuming one ever gets into windows, as via safe mode.

[Sylvander]

To check whether or not the hardware is OK....
Boot a distro of Linux off a "live" CD.
e.g. Knoppix 5.1.1 (http://iso.linuxquestions.org/knoppix/knoppix-5.1.1/)
If that works just fine there's nothing amiss with your hardware [HDD not included] or BIOS's configuration settings.

That would suggest the problem is with the Windows environment.

Oops, Paul got in 1st.
I failed to spot atc could get into Safe Mode. :o

[atc_traffic856]

Thank you Paul and Sylvander/Info extremely helpful/I will proceed as you both have mention and give feed back info/ or request more help.
thank you again

[atc_traffic856]

Again thank you everyone for your support.
I went into safe mode, and selected out of the selection list, Safe mode
But even in Safe Mode it did the replica of Normal Booting.
I then went back into the Safe mode list, and selected Last Good Connection. Enter and it booted to the desktop, without rebooting.
I received at that point a Downloaded malware called a anti spyware and sure enough with all the criteria attach to it. Purchase etc you are at risk, blah blah. The lady whom owns this PC said she did download this anti spyware, because there were numerous amt of flashes that she was at risk.
I re-stored it at a later date well beyond her download.
After this I rebooted and deleted through the panel the program she download, after that a cleaner, regcure, adware. Plus a few other odds and ends. All went ok after this clean up.