XP splash screen crashes, then re-starts, then finishes.


S

SpokaneTim

Hi,

I had a spyware problem that I got rid of by wiping the HD and reinstalling
Windows XP Home. But something is corrupting the install and after a week or
so the OS is so distorted I have to re-install to get functionality back. One
early sympton of this problem seems to be the XP splash screen crashing
during the bootup, then restarting, and finishing. I am using an eMachines
OEM copy of XP Home. During the boot sequence I first get the bios splash
screen, then an XP splash screen, then my desktop appears and populates.

But with this current OS corruption problem the XP splash screen begins to
load, then the screen goes black for a two second count, then the XP splash
screen re-appears and the boot process finishes. An ex-microsoft programmer
looked over my system last time I had this problem and commented that he was
surprised, with the OS system problems he found, that the computer booted up
at all. Running SFC /SCANNOW doesn't seem to make any difference. Whatever
the problem is, it isn't contained in the main system file structure. I wish
I could tell you more, but the ex-Microsoft programmer didn't point out and
explain to me what the OS problems were.

I would appreciate any assistance/suggestions with determining why the XP
splash screen stops and starts during bootup. This NEVER happened before the
spyware problem. I have jumped through a number of hoops trying to rid my
system of whatever might be interfering with the OS install. Before this
sypware problem, installing the OS from the disk was never a problem.

Thanks for the help!
SpokaneTim
 
Ad

Advertisements

G

Gerry

Tim

Copies of the Stop Errors reports are needed if you want targetted help.

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Right click on
the My Computer icon on the Desktop and select Properties, Advanced,
Start-Up and Recovery, System Failure and uncheck box before
Automatically Restart.

Do not re-enable automatic restart on system failure until you have
resolved the problem. Check for variants of the Stop Error message.

An alternative is to keep pressing the F8 key during Start-Up and select
option - Disable automatic restart on system failure.

Do the errors occur during the boot process or after? Do they occur in
safe mode?

Have you tried Last Known Good Configuration?
A description of the Safe Mode Boot options in Windows XP
http://support.microsoft.com/kb/315222/en-us

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?


--



Hope this helps.

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

Anna

SpokaneTim said:
Hi,

I had a spyware problem that I got rid of by wiping the HD and
reinstalling
Windows XP Home. But something is corrupting the install and after a week
or
so the OS is so distorted I have to re-install to get functionality back.
One
early sympton of this problem seems to be the XP splash screen crashing
during the bootup, then restarting, and finishing. I am using an eMachines
OEM copy of XP Home. During the boot sequence I first get the bios splash
screen, then an XP splash screen, then my desktop appears and populates.

But with this current OS corruption problem the XP splash screen begins to
load, then the screen goes black for a two second count, then the XP
splash
screen re-appears and the boot process finishes. An ex-microsoft
programmer
looked over my system last time I had this problem and commented that he
was
surprised, with the OS system problems he found, that the computer booted
up
at all. Running SFC /SCANNOW doesn't seem to make any difference. Whatever
the problem is, it isn't contained in the main system file structure. I
wish
I could tell you more, but the ex-Microsoft programmer didn't point out
and
explain to me what the OS problems were.

I would appreciate any assistance/suggestions with determining why the XP
splash screen stops and starts during bootup. This NEVER happened before
the
spyware problem. I have jumped through a number of hoops trying to rid my
system of whatever might be interfering with the OS install. Before this
sypware problem, installing the OS from the disk was never a problem.

Thanks for the help!
SpokaneTim


Tim:
It's a bit difficult (at least for me) to precisely understand what your
problem is at *this* point, (assuming there's a problem at all).

The gist of the "problem" (again, if I correctly understand your description
of it) is, as you state...
"But with this current OS corruption problem the XP splash screen begins to
load, then the screen goes black for a two second count, then the XP splash
screen re-appears and the boot process finishes."

Is that it? A black screen appears for two seconds in between the appearance
of the XP splash screens"?

Otherwise the system boots without incident and properly functions? No
problems encountered accessing programs, manipulating data, etc. etc.?

If this is all it is, i.e., a two-second black screen during the boot
process, there's nothing particularly unusual about an event of that kind.
It happens possibly because of some very minor glitch of one sort or another
affecting this or that hardware component. Or because of some trivial
problem affecting a program or application or an XP OS system file.
Generally speaking one can live with this situation assuming there are no
other problems affecting the system.

But if the present situation is uncomfortable to you - perhaps because you
think future problems may arise stemming from this "problem" - why don't you
run the chkdsk /r command and see if that helps in any way. Or even consider
a full-blown Repair install of the XP OS.

Naturally you're continuing to use your anti-malware programs to determine
if there's a problem there.
Anna
 
S

SpokaneTim

Gerry,

I really appreciate your taking the time to try to help me find an answer to
this perplexing problem.

I followed your suggestions to 1.) Disable automatic restart on system
failure, 2.) try Last Known Good Configuration (doesn't apply in this
situation because I just re-loaded the OS, so there is no LKGC), 3.) Are
there any yellow question marks in Device Manager (There were none.)

But as I struggled with this problem and researched it on the internet, I
found the suggestion to "Enable Boot Logging" from Safe Mode, and logged the
drivers loading at startup. Of course I got a long list of correctly loaded
drivers, but did get a short list of drivers that did NOT load at startup.
The listing of non-loaded drivers were:

Service Pack 312 17 2008 14:49:17.500

Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Did not load driver \SystemRoot\system32\DRIVERS\serial.sys
Did not load driver \SystemRoot\system32\DRIVERS\p3.sys
Did not load driver \SystemRoot\system32\DRIVERS\processr.sys
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Did not load driver \SystemRoot\system32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\system32\DRIVERS\mrxsmb.sys
Did not load driver \SystemRoot\system32\DRIVERS\ipnat.sys

I have looked around the internet and have found that A LOT of individuals
have had almost the exact same set of drivers not load on their systems.
Usually these people are concerned because there are long system boot delays
associated with these non-loaded drivers.

I have been trying to find anything that might explain 1.) Why these drivers
didn't load, 2.) how to fix the system so they will load, 3.) What is the
significance of these drivers.

But so far I haven't been able to get any of these three questions answered.
I am loading my system from a Gateway OEM boot disk that is in almost perfect
condition. It is possible that the OS didn't load perfectly because the disk
is only 99% perfect, but that doesn't seem reasonable.

Any suggestions you could give me for Why these drivers didn't load,and how
to fix the system so they will load, would be of great assistance.

Although I have found a lot of people having the same problem as I, I
haven't found any solutions yet.

Thanks again for your help (and any other readers who may have the knowledge
to help me!)

SpokaneTim
 
S

SpokaneTim

Gerry,

I really appreciate your taking the time to try to help me find an answer to
this perplexing problem.

I followed your suggestions to 1.) Disable automatic restart on system
failure, 2.) try Last Known Good Configuration (doesn't apply in this
situation because I just re-loaded the OS, so there is no LKGC), 3.) Are
there any yellow question marks in Device Manager (There were none.)

But as I struggled with this problem and researched it on the internet, I
found the suggestion to "Enable Boot Logging" from Safe Mode, and logged the
drivers loading at startup. Of course I got a long list of correctly loaded
drivers, but did get a short list of drivers that did NOT load at startup.
The listing of non-loaded drivers were:

Service Pack 312 17 2008 14:49:17.500

Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Did not load driver \SystemRoot\system32\DRIVERS\serial.sys
Did not load driver \SystemRoot\system32\DRIVERS\p3.sys
Did not load driver \SystemRoot\system32\DRIVERS\processr.sys
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Did not load driver \SystemRoot\system32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\system32\DRIVERS\mrxsmb.sys
Did not load driver \SystemRoot\system32\DRIVERS\ipnat.sys

I have looked around the internet and have found that A LOT of individuals
have had almost the exact same set of drivers not load on their systems.
Usually these people are concerned because there are long system boot delays
associated with these non-loaded drivers.

I have been trying to find anything that might explain 1.) Why these drivers
didn't load, 2.) how to fix the system so they will load, 3.) What is the
significance of these drivers.

But so far I haven't been able to get any of these three questions answered.
I am loading my system from a Gateway OEM boot disk that is in almost perfect
condition. It is possible that the OS didn't load perfectly because the disk
is only 99% perfect, but that doesn't seem reasonable.

Any suggestions you could give me for Why these drivers didn't load,and how
to fix the system so they will load, would be of great assistance.

Although I have found a lot of people having the same problem as I, I
haven't found any solutions yet.

Thanks again for your help (and any other readers who may have the knowledge
to help me!)

SpokaneTim
 
S

SpokaneTim

Anna,

I have continued my research, and have discerned that I have a series of
drivers that are not loading when the system starts up. I "Enabled Boot
Logging" from Safe Mode to get a complete list of loaded and non-loaded
drivers. The short list of drivers that don't load are:

Service Pack 312 17 2008 14:49:17.500

Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Did not load driver \SystemRoot\system32\DRIVERS\serial.sys
Did not load driver \SystemRoot\system32\DRIVERS\p3.sys
Did not load driver \SystemRoot\system32\DRIVERS\processr.sys
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Did not load driver \SystemRoot\system32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\system32\DRIVERS\mrxsmb.sys
Did not load driver \SystemRoot\system32\DRIVERS\ipnat.sys

I believe that these drivers that don't load are at the root of my system
acting strangely at startup, and then acting progressively more weird as time
goes by.

So is it any easier for you to understand "precisely" what my problem is at
"this point? (It's a bit difficult (at least for me) to precisely understand
what your
problem is at *this* point, (assuming there's a problem at all).)

Gerry didn't have any difficulty at all understanding my support request,
but now that I have further uncovered reasons for my computer's strange
startup behavior, maybe you can provide some meaningful support.

Or perhaps you don't know enough about the XP OS to actually provide
meaningful support? I researched and discovered "Enable Boot Logging" from
Safe Mode, and that lead to my discovery that a set of drivers weren't
loading properly. I am not a tech, so I don't know all the debugging options
available to someone analyzing the XP OS, but I would think that someone
responding to questions on this support page would.

It was NOT helpful to get responses from you like:
"It's a bit difficult (at least for me) to precisely understand what your
problem is at *this* point, (assuming there's a problem at all)."
"Is that it? A black screen appears for two seconds in between the
appearance of the XP splash screens"?"

You might want to reconsider responding to people seeking the gracious
assistance of sharp XP techs. You don't appear to have the emotional or
character qualities necessary to help others in need. And since I found the
next obvious step in the solution to this problem (Enable Boot Logging from
Safe Mode) with no experience at all, I appear to equal you in computer
technical skill, and I KNOW I am not qualified to respond to supplicants on
this support page.

SpokaneTim
 
Ad

Advertisements

A

Anna

SpokaneTim said:
Anna,

I have continued my research, and have discerned that I have a series of
drivers that are not loading when the system starts up. I "Enabled Boot
Logging" from Safe Mode to get a complete list of loaded and non-loaded
drivers. The short list of drivers that don't load are:

Service Pack 312 17 2008 14:49:17.500

Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Did not load driver \SystemRoot\system32\DRIVERS\serial.sys
Did not load driver \SystemRoot\system32\DRIVERS\p3.sys
Did not load driver \SystemRoot\system32\DRIVERS\processr.sys
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Did not load driver \SystemRoot\system32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\system32\DRIVERS\mrxsmb.sys
Did not load driver \SystemRoot\system32\DRIVERS\ipnat.sys

I believe that these drivers that don't load are at the root of my system
acting strangely at startup, and then acting progressively more weird as
time
goes by.

So is it any easier for you to understand "precisely" what my problem is
at
"this point? (It's a bit difficult (at least for me) to precisely
understand
what your

Gerry didn't have any difficulty at all understanding my support request,
but now that I have further uncovered reasons for my computer's strange
startup behavior, maybe you can provide some meaningful support.

Or perhaps you don't know enough about the XP OS to actually provide
meaningful support? I researched and discovered "Enable Boot Logging" from
Safe Mode, and that lead to my discovery that a set of drivers weren't
loading properly. I am not a tech, so I don't know all the debugging
options
available to someone analyzing the XP OS, but I would think that someone
responding to questions on this support page would.

It was NOT helpful to get responses from you like:
"It's a bit difficult (at least for me) to precisely understand what your
problem is at *this* point, (assuming there's a problem at all)."
"Is that it? A black screen appears for two seconds in between the
appearance of the XP splash screens"?"

You might want to reconsider responding to people seeking the gracious
assistance of sharp XP techs. You don't appear to have the emotional or
character qualities necessary to help others in need. And since I found
the
next obvious step in the solution to this problem (Enable Boot Logging
from
Safe Mode) with no experience at all, I appear to equal you in computer
technical skill, and I KNOW I am not qualified to respond to supplicants
on
this support page.

SpokaneTim


Tim:
First of all, I regret that you interpreted my response to your query as
unhelpful and that my response was expressed in a sarcastic and/or surly
way. I make no apology for the specifics of my response in terms of tone.

I was, of course, responding to your original post from which all I gleaned
from it (and still do after re:reading it more than once) is that when all
was said & done you referred to what you considered a problem involving "the
screen goes black for a two second count, then the XP splash screen
re-appears and the boot process finishes". This, after you apparently had
fresh-installed the OS because of some prior malware infestation. In any
event you did not indicate that aside from this "two second" black screen
issue during the bootup process there were any further problems affecting
either the boot process or the functioning of your system.

As I tried (apparently unsuccessfully) to explain, a momentary black screen
lasting only a couple of seconds during bootup is a perfectly normal
situation in many, if not most, systems. Again, as long as the system
otherwise boots without incident and there's no further problems with the
system properly functioning following bootup there's ordinarily nothing to
be concerned about.

Now as far as the list that you incorporated in your post above re the
"missing" drivers, this is, in most cases a quite normal occurrence in that
those "missing" drivers are simply not loaded (although they are potentially
available to the OS) because they are not needed by the OS for a variety of
reasons having to do with your installed hardware/software programs or
perhaps later will be loaded after being "called" by another driver. Again,
as long as the system is properly functioning with no untoward glitches and
nothing in Device Manager to indicate any problems, these "missing" drivers
are inconsequential.
Anna
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top