C
Cheryl-Lynn Roberts
I have a Dell Laptop Smart Step250N
I have been having problems with shut downs after 10 to 20
mins whether I am on line or not.
I have contacted Dell, have reinstalled Windows XP as
advised, made other changes as advised by
Microsoft...still have problem. I never know when it will
shut down.
Advanced System Information - Error Log
Please wait while information is being collected...
100% (collecting Error Log information)
Refresh screen
Error Log
Date - Time Source Description
Monday, October 27, 2003 DCOM DCOM got error "%1084"
attempting to start the service EventSystem with
arguments "" in order to run the server: {1BE1F766-5536-
11D1-B 726-00C04FB926AF}
Monday, October 27, 2003 DCOM DCOM got error "%1084"
attempting to start the service netman with arguments ""
in order to run the server: {BA126AE5-2166-11D1-B 1D0-
00805FC1270E}
Monday, October 27, 2003 DCOM DCOM got error "%1084"
attempting to start the service netman with arguments ""
in order to run the server: {BA126AE5-2166-11D1-B 1D0-
00805FC1270E}
Monday, October 27, 2003 DCOM DCOM got error "%1084"
attempting to start the service EventSystem with
arguments "" in order to run the server: {1BE1F766-5536-
11D1-B 726-00C04FB926AF}
Monday, October 27, 2003 Service Control Manager 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.
Monday, October 27, 2003 Service Control Manager 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.
Monday, October 27, 2003 Service Control Manager The
Messenger service depends on the NetBIOS Interface service
which failed to start because of the following error: A
device attached to the system is not functioning.
Monday, October 27, 2003 Service Control Manager 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.
Monday, October 27, 2003 Service Control Manager The
following boot-start or system-start driver(s) failed to
load: Fips IPSec MRxSmb NetBIOS NetBT OMCI Processor RasA
cd Rdbss SYMTDI Tcpip
Monday, October 27, 2003 DCOM DCOM got error "%1084"
attempting to start the service EventSystem with
arguments "" in order to run the server: {1BE1F766-5536-
11D1-B 726-00C04FB926AF}
Wednesday, October 29, 2003 DCOM DCOM got error "%1058"
attempting to start the service SENS with arguments "" in
order to run the server: {D3938AB0-5B9D-11D1-8 DD2-
00AA004ABD5E}
Wednesday, October 29, 2003 DCOM DCOM got error "%1058"
attempting to start the service SENS with arguments "" in
order to run the server: {D3938AB0-5B9D-11D1-8 DD2-
00AA004ABD5E}
Wednesday, October 29, 2003 W32Time Time Provider
NtpClient: An error occurred during DNS lookup of the
manually configured peer 'time.windows.com,0x1'. NtpClient
will try the DNS lookup again in 15 minutes. The error
was: A socket operation was attempted to an unreachable
host. (0x80072751)
Wednesday, October 29, 2003 W32Time The time provider
NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently
accessible. No attempt to contact a source will be made
for 14 minutes. NtpClient has no source of accurate time.
Wednesday, October 29, 2003 W32Time Time Provider
NtpClient: An error occurred during DNS lookup of the
manually configured peer 'time.windows.com,0x1'. NtpClient
will try the DNS lookup again in 30 minutes. The error
was: A socket operation was attempted to an unreachable
host. (0x80072751)
Wednesday, October 29, 2003 W32Time The time provider
NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently
accessible. No attempt to contact a source will be made
for 29 minutes. NtpClient has no source of accurate time.
Wednesday, October 29, 2003 W32Time Time Provider
NtpClient: An error occurred during DNS lookup of the
manually configured peer 'time.windows.com,0x1'. NtpClient
will try the DNS lookup again in 15 minutes. The error
was: A socket operation was attempted to an unreachable
host. (0x80072751)
Wednesday, October 29, 2003 W32Time The time provider
NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently
accessible. No attempt to contact a source will be made
for 14 minutes. NtpClient has no source of accurate time.
Thursday, October 30, 2003 W32Time Time Provider
NtpClient: An error occurred during DNS lookup of the
manually configured peer 'time.windows.com,0x1'. NtpClient
will try the DNS lookup again in 30 minutes. The error
was: A socket operation was attempted to an unreachable
host. (0x80072751)
I have been having problems with shut downs after 10 to 20
mins whether I am on line or not.
I have contacted Dell, have reinstalled Windows XP as
advised, made other changes as advised by
Microsoft...still have problem. I never know when it will
shut down.
Advanced System Information - Error Log
Please wait while information is being collected...
100% (collecting Error Log information)
Refresh screen
Error Log
Date - Time Source Description
Monday, October 27, 2003 DCOM DCOM got error "%1084"
attempting to start the service EventSystem with
arguments "" in order to run the server: {1BE1F766-5536-
11D1-B 726-00C04FB926AF}
Monday, October 27, 2003 DCOM DCOM got error "%1084"
attempting to start the service netman with arguments ""
in order to run the server: {BA126AE5-2166-11D1-B 1D0-
00805FC1270E}
Monday, October 27, 2003 DCOM DCOM got error "%1084"
attempting to start the service netman with arguments ""
in order to run the server: {BA126AE5-2166-11D1-B 1D0-
00805FC1270E}
Monday, October 27, 2003 DCOM DCOM got error "%1084"
attempting to start the service EventSystem with
arguments "" in order to run the server: {1BE1F766-5536-
11D1-B 726-00C04FB926AF}
Monday, October 27, 2003 Service Control Manager 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.
Monday, October 27, 2003 Service Control Manager 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.
Monday, October 27, 2003 Service Control Manager The
Messenger service depends on the NetBIOS Interface service
which failed to start because of the following error: A
device attached to the system is not functioning.
Monday, October 27, 2003 Service Control Manager 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.
Monday, October 27, 2003 Service Control Manager The
following boot-start or system-start driver(s) failed to
load: Fips IPSec MRxSmb NetBIOS NetBT OMCI Processor RasA
cd Rdbss SYMTDI Tcpip
Monday, October 27, 2003 DCOM DCOM got error "%1084"
attempting to start the service EventSystem with
arguments "" in order to run the server: {1BE1F766-5536-
11D1-B 726-00C04FB926AF}
Wednesday, October 29, 2003 DCOM DCOM got error "%1058"
attempting to start the service SENS with arguments "" in
order to run the server: {D3938AB0-5B9D-11D1-8 DD2-
00AA004ABD5E}
Wednesday, October 29, 2003 DCOM DCOM got error "%1058"
attempting to start the service SENS with arguments "" in
order to run the server: {D3938AB0-5B9D-11D1-8 DD2-
00AA004ABD5E}
Wednesday, October 29, 2003 W32Time Time Provider
NtpClient: An error occurred during DNS lookup of the
manually configured peer 'time.windows.com,0x1'. NtpClient
will try the DNS lookup again in 15 minutes. The error
was: A socket operation was attempted to an unreachable
host. (0x80072751)
Wednesday, October 29, 2003 W32Time The time provider
NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently
accessible. No attempt to contact a source will be made
for 14 minutes. NtpClient has no source of accurate time.
Wednesday, October 29, 2003 W32Time Time Provider
NtpClient: An error occurred during DNS lookup of the
manually configured peer 'time.windows.com,0x1'. NtpClient
will try the DNS lookup again in 30 minutes. The error
was: A socket operation was attempted to an unreachable
host. (0x80072751)
Wednesday, October 29, 2003 W32Time The time provider
NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently
accessible. No attempt to contact a source will be made
for 29 minutes. NtpClient has no source of accurate time.
Wednesday, October 29, 2003 W32Time Time Provider
NtpClient: An error occurred during DNS lookup of the
manually configured peer 'time.windows.com,0x1'. NtpClient
will try the DNS lookup again in 15 minutes. The error
was: A socket operation was attempted to an unreachable
host. (0x80072751)
Wednesday, October 29, 2003 W32Time The time provider
NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently
accessible. No attempt to contact a source will be made
for 14 minutes. NtpClient has no source of accurate time.
Thursday, October 30, 2003 W32Time Time Provider
NtpClient: An error occurred during DNS lookup of the
manually configured peer 'time.windows.com,0x1'. NtpClient
will try the DNS lookup again in 30 minutes. The error
was: A socket operation was attempted to an unreachable
host. (0x80072751)