Windows XP Professional BSOD (tcpip.sys) on Startup

[A]

My Windows XP Professional system has recently developed a problem. When I
start up the computer for the first time in the morning, it never boots
first time, usually second or third. Just as the logon screen is about to
appear, a blue screen of death appears, with an error. I can see the error
is to do with tcpip.sys. How can I get a copy of the error to show you guys?
The computer restarts a few seconds after the blue screen appears, so I
don't really get a chance to write it down. Once the computer has been
running for a while, I can restart it as many times as I wish, and it starts
first time without the BSOD.

I thought the problem may be RAM related, but I downloaded the Microsoft
Windows Memory Diagnostic, which didn't find any errors.

Incidentally, I built this computer myself almost 3 years back, and this
problem is only recent. It is an AMD Athlon XP 1900+ with 512MB Crucial DDR
RAM if that's of any use.

Many thanks in advance.

 

[Rick \Nutcase\ Rogers]

Hi,

The behavior you are describing is typical of a failing bit of hardware.
Swapping in known-good parts is often the way to discover which one it is.
This is especially so if the failures happen when the system is cold-booted.
When it is warm, or just restarted, the component is already operating
correctly. As the error mentions tcpip.sys, I would start with the network
card.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[A]

The behavior you are describing is typical of a failing bit of hardware.
Swapping in known-good parts is often the way to discover which one it is.
This is especially so if the failures happen when the system is
cold-booted. When it is warm, or just restarted, the component is already
operating correctly. As the error mentions tcpip.sys, I would start with
the network card.

Thanks very much. As it so happens, I have some other network cards lying
around, so this will be an easy starting point.

 

[Jon Erlandson]

The events view might provide more information.
http://www.windowsnetworking.com/j_helmig/wxpevent.htm

 

[A]

The behavior you are describing is typical of a failing bit of hardware.
Swapping in known-good parts is often the way to discover which one it is.
This is especially so if the failures happen when the system is
cold-booted. When it is warm, or just restarted, the component is already
operating correctly. As the error mentions tcpip.sys, I would start with
the network card.

Replaced the network card yesterday. Started the computer up this morning,
and no blue screen, so it looks as if this has cured it! Many thanks!

 

[Rick \Nutcase\ Rogers]

Glad to hear it.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org