Xp Pro won't boot, event 7001, 7026 messages. System drivers refuse to load. Hubby driving me nuts.

  • Thread starter Thread starter MachineMessiah
  • Start date Start date
M

MachineMessiah

Guest
Xp Pro won't boot, event 7001, 7026 messages. System drivers refuse to load. Hubby driving me nuts.

Hi, I hope some one can help me get my husband's computer running or
he's going to drive me nuts on the holiday.
Xp pro w/service pack 2.
Windows One Care, no third party AV or firewall.
Automatic updates are on.
He shut it off about 10 pm last night, turns on about 7pm today Windows
hangs just after the boot screen (default).
He's not into tweaking and installed Encyclopedia Britannica a few days
ago. Windows one care did some updates yesterday about 2pm.
I got it to boot to safe mode a few times, here's what I'm getting from
the event monitor:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/3/2007
Time: 9:30:49 PM
User: N/A
Computer: COLOSSUS
Description:
The DHCP Client service depends on the NetBios over Tcpip service which
failed to start because of the following error:
A device attached to the system is not functioning.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-----------------------------------
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/3/2007
Time: 9:30:49 PM
User: N/A
Computer: COLOSSUS
Description:
The DNS Client service depends on the TCP/IP Protocol Driver service
which failed to start because of the following error:
A device attached to the system is not functioning.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
------------------------------------
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/3/2007
Time: 9:30:49 PM
User: N/A
Computer: COLOSSUS
Description:
The TCP/IP NetBIOS Helper service depends on the AFD service which
failed to start because of the following error:
A device attached to the system is not functioning.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-------------------------------
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/3/2007
Time: 9:30:49 PM
User: N/A
Computer: COLOSSUS
Description:
The IP Traffic Filter Driver service depends on the TCP/IP Protocol
Driver service which failed to start because of the following error:
A device attached to the system is not functioning.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---------------------------------
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/3/2007
Time: 9:30:49 PM
User: N/A
Computer: COLOSSUS
Description:
The MSFWDrv service depends on the IP Traffic Filter Driver service
which failed to start because of the following error:
The dependency service or group failed to start.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
----------------------------------
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/3/2007
Time: 9:30:49 PM
User: N/A
Computer: COLOSSUS
Description:
The OneCare Firewall service depends on the MSFWDrv service which failed
to start because of the following error:
The dependency service or group failed to start.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
------------------------------
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/3/2007
Time: 9:30:49 PM
User: N/A
Computer: COLOSSUS
Description:
The IPSEC Services service depends on the IPSEC driver service which
failed to start because of the following error:
A device attached to the system is not functioning.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-----------------------------
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 7/3/2007
Time: 9:30:49 PM
User: N/A
Computer: COLOSSUS
Description:
The following boot-start or system-start driver(s) failed to load:
AFD
Fips
intelppm
IPSec
MRxSmb
MSFWHLPR
NetBIOS
NetBT
RasAcd
Rdbss
Tcpip

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
------------------
Lot's of networking stuff seems to be having problems. Speculation as to
what hardware device I sould be lookiing at? Network card? Evil
motherboard?
Tried going back one day w/system restore, no go. Tried shutting off One
Care and firewall per directions I found an Microsoft, seems to have
wiped out all the rest of the restore points as well.
Help!
 
RE: Xp Pro won't boot, event 7001, 7026 messages. System drivers refus

RE: Xp Pro won't boot, event 7001, 7026 messages. System drivers refus

Thier is a update or fix for tcp/id its kb925922 As far as getting the OS to
boot,try booting to xp cd,recovery,select 1 For C: Press enter for password,
Type:Fixboot Agree,type:CHKDSK C: /R When its thru,type:EXIT Let xp
start up,remove cd

"MachineMessiah" wrote:

> Hi, I hope some one can help me get my husband's computer running or
> he's going to drive me nuts on the holiday.
> Xp pro w/service pack 2.
> Windows One Care, no third party AV or firewall.
> Automatic updates are on.
> He shut it off about 10 pm last night, turns on about 7pm today Windows
> hangs just after the boot screen (default).
> He's not into tweaking and installed Encyclopedia Britannica a few days
> ago. Windows one care did some updates yesterday about 2pm.
> I got it to boot to safe mode a few times, here's what I'm getting from
> the event monitor:
>
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7001
> Date: 7/3/2007
> Time: 9:30:49 PM
> User: N/A
> Computer: COLOSSUS
> Description:
> The DHCP Client service depends on the NetBios over Tcpip service which
> failed to start because of the following error:
> A device attached to the system is not functioning.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> -----------------------------------
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7001
> Date: 7/3/2007
> Time: 9:30:49 PM
> User: N/A
> Computer: COLOSSUS
> Description:
> The DNS Client service depends on the TCP/IP Protocol Driver service
> which failed to start because of the following error:
> A device attached to the system is not functioning.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ------------------------------------
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7001
> Date: 7/3/2007
> Time: 9:30:49 PM
> User: N/A
> Computer: COLOSSUS
> Description:
> The TCP/IP NetBIOS Helper service depends on the AFD service which
> failed to start because of the following error:
> A device attached to the system is not functioning.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> -------------------------------
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7001
> Date: 7/3/2007
> Time: 9:30:49 PM
> User: N/A
> Computer: COLOSSUS
> Description:
> The IP Traffic Filter Driver service depends on the TCP/IP Protocol
> Driver service which failed to start because of the following error:
> A device attached to the system is not functioning.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ---------------------------------
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7001
> Date: 7/3/2007
> Time: 9:30:49 PM
> User: N/A
> Computer: COLOSSUS
> Description:
> The MSFWDrv service depends on the IP Traffic Filter Driver service
> which failed to start because of the following error:
> The dependency service or group failed to start.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ----------------------------------
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7001
> Date: 7/3/2007
> Time: 9:30:49 PM
> User: N/A
> Computer: COLOSSUS
> Description:
> The OneCare Firewall service depends on the MSFWDrv service which failed
> to start because of the following error:
> The dependency service or group failed to start.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ------------------------------
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7001
> Date: 7/3/2007
> Time: 9:30:49 PM
> User: N/A
> Computer: COLOSSUS
> Description:
> The IPSEC Services service depends on the IPSEC driver service which
> failed to start because of the following error:
> A device attached to the system is not functioning.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> -----------------------------
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7026
> Date: 7/3/2007
> Time: 9:30:49 PM
> User: N/A
> Computer: COLOSSUS
> Description:
> The following boot-start or system-start driver(s) failed to load:
> AFD
> Fips
> intelppm
> IPSec
> MRxSmb
> MSFWHLPR
> NetBIOS
> NetBT
> RasAcd
> Rdbss
> Tcpip
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ------------------
> Lot's of networking stuff seems to be having problems. Speculation as to
> what hardware device I sould be lookiing at? Network card? Evil
> motherboard?
> Tried going back one day w/system restore, no go. Tried shutting off One
> Care and firewall per directions I found an Microsoft, seems to have
> wiped out all the rest of the restore points as well.
> Help!
>
>
>
 
RE: Xp Pro won't boot, event 7001, 7026 messages. System drivers refus

RE: Xp Pro won't boot, event 7001, 7026 messages. System drivers refus

In article <BB5D924E-6765-4CD9-8881-56B572231D47@microsoft.com>,
eckrichco@msn.com says...
> Thier is a update or fix for tcp/id its kb925922 As far as getting the OS to
> boot,try booting to xp cd,recovery,select 1 For C: Press enter for password,
> Type:Fixboot Agree,type:CHKDSK C: /R When its thru,type:EXIT Let xp
> start up,remove cd
>
>
> >

>

snip
Thanks for the reply.

Looks like I have to call Microsoft if I want to d/l that
Tcpip.sys file.
Anyone seen it online somewhere?
thanks
 
RE: Xp Pro won't boot, event 7001, 7026 messages. System drivers refus

RE: Xp Pro won't boot, event 7001, 7026 messages. System drivers refus

In article <BB5D924E-6765-4CD9-8881-56B572231D47@microsoft.com>,
eckrichco@msn.com says...
> Thier is a update or fix for tcp/id its kb925922 As far as getting the OS to
> boot,try booting to xp cd,recovery,select 1 For C: Press enter for password,
> Type:Fixboot Agree,type:CHKDSK C: /R When its thru,type:EXIT Let xp
> start up,remove cd
>
>

snip
Tried the fixboot + chkdisk. System hung during the check disk. Re
installed windows about a month ago after check disk got stuck for over
a day. Tried fixboot by itself, no luck.
thanks.
 
Back
Top