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

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!
 
"MachineMessiah" <Geoffthegodofbiscuits@cakeordeath.net> wrote in message
news:Z9adnUTKLqVfkBbbnZ2dnUVZ_jadnZ2d@giganews.com...
> 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!

Disconnect all attached hardware that isn't absolutely critical, leaving
only keyboard, mouse and monitor. Remove (if it's a card) or disable (in
the BIOS, if it's embedded on the motherboard) the network card.
Disconnect the network cable. Try restarting.

If it now starts, look in Device Manager for references to the network
card, and uninstall any present. Now shut down and re-install or re-enable
the network adapter, without connecting the cable, and restart and see if it
still boots and reinstalls the card. If all goes well, connect the cable
and see if you get an IP address and can browse. You may need to pop out
for another network card.

Then, attach the other hardware one piece at a time to see what has failed.

HTH
-pk
 
In article <ORQNx1evHHA.1204@TK2MSFTNGP03.phx.gbl>, test@dev.null
says...
big snip
> Disconnect all attached hardware that isn't absolutely critical, leaving
> only keyboard, mouse and monitor. Remove (if it's a card) or disable (in
> the BIOS, if it's embedded on the motherboard) the network card.
> Disconnect the network cable. Try restarting.
>
> If it now starts, look in Device Manager for references to the network
> card, and uninstall any present. Now shut down and re-install or re-enable
> the network adapter, without connecting the cable, and restart and see if it
> still boots and reinstalls the card. If all goes well, connect the cable
> and see if you get an IP address and can browse. You may need to pop out
> for another network card.
>
> Then, attach the other hardware one piece at a time to see what has failed.
>
> HTH
> -pk
>
>
>
>
thanks.
Weird thing is, we can get online, router sees his machine but I can't
see his machine on our workgroup.

--
The solution is:
1)Winrar
2)DvdDecrypter.
3)Install the ac3 audio codec.
 

>
> If it now starts, look in Device Manager for references to the network
> card, and uninstall any present. Now shut down and re-install or re-enable
> the network adapter, without connecting the cable, and restart and see if it
> still boots and reinstalls the card. If all goes well, connect the cable
> and see if you get an IP address and can browse. You may need to pop out
> for another network card.
>
> Then, attach the other hardware one piece at a time to see what has failed.
>
> HTH
> -pk
>
>
>
>
Removed network card then could not get system to see it again. Killed
all the networking. Restared onboard lan thru bios, have networking
back.Windows will not let me remove the remains of the the old linksys
card, says sytem needs it to boot. Now have 2 network devices, 1 diabled
but can not remove. Still stuck in safe mode.
Would it be worth it to just reinstall windows? If its failing hardware
the problem will remain.
--
The solution is:
Winrar and/or DvdDecrypter.
Install the ac3 audio codec.
 
"MachineMessiah" <Geoffthegodofbiscuits@cakeordeath.ne> wrote in message
news:o8adnWlzkcWWnBHbnZ2dnUVZ_s3inZ2d@giganews.com...
>>
>> If it now starts, look in Device Manager for references to the network
>> card, and uninstall any present. Now shut down and re-install or re-enable
>> the network adapter, without connecting the cable, and restart and see if it
>> still boots and reinstalls the card. If all goes well, connect the cable
>> and see if you get an IP address and can browse. You may need to pop out
>> for another network card.
>>
>> Then, attach the other hardware one piece at a time to see what has failed.
>>
>>

> Removed network card then could not get system to see it again. Killed
> all the networking. Restared onboard lan thru bios, have networking
> back.Windows will not let me remove the remains of the the old linksys
> card, says sytem needs it to boot. Now have 2 network devices, 1 diabled
> but can not remove. Still stuck in safe mode.
> Would it be worth it to just reinstall windows? If its failing hardware
> the problem will remain.

Re: the network card that Windows states is needed to boot:

Click Start>Run, type: cmd
Click OK

At a command prompt, type the following command , and press ENTER:

set devmgr_show_nonpresent_devices=1

Still at the command prompt, type the following command, and press ENTER:

start devmgmt.msc

When Device Manager opens, click View> Show hidden devices.

Remove any "phantom" (greyed out) entries that exist for your removed Linksys
adapter, under Network Adapters.

Remove any other "phantom" (greyed out) entries you can that exist under Network
Adapters.

Remove any "phantom" (greyed out) entries that exist for the Linksys device under
the Non- Plug and Play drivers section.

Remove the Linksys adapter by right-clicking its entry under Network Adapters, and
clicking Uninstall.

Close Device Manager.

Shut down and unplug the machine, then physically remove the Linksys card, then
reboot.

Post back with your results.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/
http://dts-l.org/goodpost.htm
 
In article <#Xj$EgrvHHA.1524@TK2MSFTNGP06.phx.gbl>, glee29
@spamindspring.com says...
> "MachineMessiah" <Geoffthegodofbiscuits@cakeordeath.ne> wrote in message
snip
>
> Re: the network card that Windows states is needed to boot:
>
> Click Start>Run, type: cmd
> Click OK
>
> At a command prompt, type the following command , and press ENTER:
>
> set devmgr_show_nonpresent_devices=1
>
> Still at the command prompt, type the following command, and press ENTER:
>
> start devmgmt.msc
>
> When Device Manager opens, click View> Show hidden devices.
>
> Remove any "phantom" (greyed out) entries that exist for your removed Linksys
> adapter, under Network Adapters.
>
> Remove any other "phantom" (greyed out) entries you can that exist under Network
> Adapters.
>
> Remove any "phantom" (greyed out) entries that exist for the Linksys device under
> the Non- Plug and Play drivers section.
>
> Remove the Linksys adapter by right-clicking its entry under Network Adapters, and
> clicking Uninstall.
>
> Close Device Manager.
>
> Shut down and unplug the machine, then physically remove the Linksys card, then
> reboot.
>
> Post back with your results.
>
Got it, finally.
thanks very much.
--
 
"MachineMessiah" <Geoffthegodofbiscuits@cakeordeath.ne> wrote in message
news:xYSdnfuMlMLfThPbnZ2dnUVZ_tninZ2d@giganews.com...
> In article <#Xj$EgrvHHA.1524@TK2MSFTNGP06.phx.gbl>, glee29
> @spamindspring.com says...
>> "MachineMessiah" <Geoffthegodofbiscuits@cakeordeath.ne> wrote in message
> snip
>>
>> Re: the network card that Windows states is needed to boot:
>>
>> Click Start>Run, type: cmd
>> Click OK
>>
>> At a command prompt, type the following command , and press ENTER:
>>
>> set devmgr_show_nonpresent_devices=1
>>
>> Still at the command prompt, type the following command, and press ENTER:
>>
>> start devmgmt.msc
>>
>> When Device Manager opens, click View> Show hidden devices.
>>
>> Remove any "phantom" (greyed out) entries that exist for your removed Linksys
>> adapter, under Network Adapters.
>>
>> Remove any other "phantom" (greyed out) entries you can that exist under Network
>> Adapters.
>>
>> Remove any "phantom" (greyed out) entries that exist for the Linksys device under
>> the Non- Plug and Play drivers section.
>>
>> Remove the Linksys adapter by right-clicking its entry under Network Adapters,
>> and
>> clicking Uninstall.
>>
>> Close Device Manager.
>>
>> Shut down and unplug the machine, then physically remove the Linksys card, then
>> reboot.
>>
>> Post back with your results.
>>
> Got it, finally.
> thanks very much.

Ah, good....glad you got it.
Is the hubby still sane? Are you? ;-)
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/
http://dts-l.org/goodpost.htm
 
Back
Top