Startup

[Guest]

This computer was working fine until the hard drive and one stick of memory
were taken out to check things in another computer. The problem started when
we put these items back into the original computer. The computer refused to
boot into windows. It would not even boot into safe mode. When a normal
boot was attempted it would go all the way to the screen for loading XP. It
would be on that screen for longer than usual, the green loading bar would
finally pause in the middle, the I would see a quick flash of blue screen
with writing all over it. It would the reboot itself and go to the screen
telling me windows didnt boot correctly...etc....

So I finally gave up and did a fresh install of win xp pro. Setup went fine
until it was time to start windows for the first time. It was doing the same
thing except that now i can boot into safe mode. I checked many things over
the next few days: Hardware placement and connections.......Different memory
sticks....different hard drives with existing and new
instalations......changing bios settings....running msconfig and doing
different boot options....disabling and updating drivers. Nothing seems to
work, I still have the same problem.

All I am asking for now is some ideas on where to look. I thought it might
have been a driver or some software problem but now I dont even know where to
look. Any help is greatly appreciated since this is a fairly expensive
system that was custom built.

 

[beb]

Look in event view and device manager for an indication of any error or
warnings. Check the hard drive connection cable with a know good one. Check
any connector that you handled if you might of damaged one.

 

[Guest]

I did this in safe mode since it is all i can do.
i go to event viewer through the manage option. in system i see an error for
Service control manager that says the following boot start or system start
drivers failed to load: Fips, IPSec, MRxSmb, NetBios, NetBT, Processer,
Rdbss, Tcpip

There are a couple of other errors but that one stands out since I
originally thought it was a driver anyway. I also looked at device manager
but it is completly empty. never seen that before, but at thie point it
doesnt surprise me.

 

[Detlev Dreyer]

This computer was working fine until the hard drive and one stick of
memory were taken out to check things in another computer. The problem
started when we put these items back into the original computer. The
computer refused to boot into windows.

Apparently a home-made hardware issue. "Handling ESD sensitive parts"
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4N3KLN

 

[Detlev Dreyer]

There are a couple of other errors but that one stands out since I
originally thought it was a driver anyway. I also looked at device
manager but it is completly empty. never seen that before, but at thie
point it doesnt surprise me.

"No Items Appear in the Device Manager List When You Open It"
http://support.microsoft.com/?scid=kb;en-us;311504

 

[Guest]

I can now see items in the device manager. It tells me my onboard ethernet
card (a marvell yukon gigabit) has no drivers loaded. After alot of research
last night I have concluded that the computer needs this device to start. I
tried using the cd that came with the motherboard, but when i try to load the
drivers an error comes up that the ini file is not as expected.(whatever that
means) so i went to the website and downloaded the newest driver to a cd. I
then tried to run that driver but got the same error. obviously i cant just
do a driver update from the problem computer since the ethernet card is down

 

[Detlev Dreyer]

obviously i cant just do a driver
update from the problem computer since the ethernet card is down

As already posted in this thread, this is no WinXP problem. While
fiddling around in the computer, the hardware (incl. mobo) got either
shot by electrostatic fire and/or the cards do not sit firmly in their
slots anymore. "The problem started when we put these items back into
the original computer" (quote) should give you the clue.