Re: Windows XP Professional BSOD (tcpip.sys) on Startup
From: A (anon_at_anon.com)
Date: 01/09/05
- Next message: Jon Erlandson: "Re: tired old processor.. (getting stuck at 100%)"
- Previous message: log file database: "log file database is full"
- In reply to: Rick \: "Re: Windows XP Professional BSOD (tcpip.sys) on Startup"
- Next in thread: A: "Re: Windows XP Professional BSOD (tcpip.sys) on Startup"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 9 Jan 2005 17:46:38 -0000
Rick "Nutcase" Rogers wrote:
> 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.
- Next message: Jon Erlandson: "Re: tired old processor.. (getting stuck at 100%)"
- Previous message: log file database: "log file database is full"
- In reply to: Rick \: "Re: Windows XP Professional BSOD (tcpip.sys) on Startup"
- Next in thread: A: "Re: Windows XP Professional BSOD (tcpip.sys) on Startup"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|