G
Guest
Please help. This happened back in February and we thought it was my hard
drive so completely formatted them and when that didn't work bought a new
hard drive. Things were fine until tonight and the same symptoms. Computer
just shut down in the middle of playing SWG online then will not get itself
past my login without eventually crashing. I have tried system restore. I
can run in safe mode this time so far. Following is more info for someone
who can read and understand this (which I can't) Any suggestions are
welcomed!!
System shut down and crash after loading personal settings. Can only run in
safe mode. System restore didn't help.
I see the error this time about a device attached to the system. I have not
recently attached any new devices or installed any programs.
First time this problem appeared (February) I installed new drives and
restored windows to get things back together.
Same thing just happened tonight (April 10, 2006)
after an automatic microsoft update
I am sending all the info from my error file just in case it helps
Tuesday, March 28, 2006 Service Control Manager The Secdrv service failed to
start due to the following error: The process cannot access the file because
it is being used by another process.
Monday, April 10, 2006 Service Control Manager Timeout (30000 milliseconds)
waiting for the Norton AntiVirus Auto-Protect Service service to connect.
Monday, April 10, 2006 Service Control Manager The Norton AntiVirus
Auto-Protect Service service failed to start due to the following error: The
service did not respond to the start or control request in a timely fashion.
Monday, April 10, 2006 System Error Error code 10000050, parameter1 ffffffb6,
parameter2 00000000, parameter3 b64115b8, parameter4 00000000.
Monday, April 10, 2006 Service Control Manager The ISSVC service terminated
with service-specific error 4294967295 (0xFFFFFFFF).
Monday, April 10, 2006 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, April 10, 2006 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, April 10, 2006 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, April 10, 2006 Service Control Manager The TCP/IP NetBIOS Helper
service depends on the AFD Networking Support Environment service which
failed
to start because of the following error: A device attached to the system is
not functioning.
Monday, April 10, 2006 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, April 10, 2006 Service Control Manager The following boot-start or
system-start driver(s) failed to load: AFD Fips intelppm IPSec MRxSmb NetBIOS
NetBT RasAcd Rdbss SAVRTPEL SPBBCDrv S YMTDI Tcpip WS2IFSL
Monday, April 10, 2006 DCOM DCOM got error "%1084" attempting to start the
service ntmssvc with arguments "-Service" in order to run the server:
{D61A27C6-8F53-11D0-B FA0-00A024151983}
Monday, April 10, 2006 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, April 10, 2006 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, April 10, 2006 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, April 10, 2006 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, April 10, 2006 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, April 10, 2006 Service Control Manager The TCP/IP NetBIOS Helper
service depends on the AFD Networking Support Environment service which
failed
to start because of the following error: A device attached to the system is
not functioning.
Monday, April 10, 2006 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, April 10, 2006 Service Control Manager The following boot-start or
system-start driver(s) failed to load: AFD Fips intelppm IPSec MRxSmb NetBIOS
NetBT RasAcd Rdbss SAVRTPEL SYMTDI Tcp ip WS2IFSL
Monday, April 10, 2006 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, April 10, 2006 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, April 10, 2006 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, April 10, 2006 Service Control Manager The following boot-start or
system-start driver(s) failed to load: Fips intelppm SAVRTPEL SY MTDI
Monday, April 10, 2006 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, April 10, 2006 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, April 10, 2006 DCOM DCOM got error "%1084" attempting to start the
service ntmssvc with arguments "-Service" in order to run the server:
{D61A27C6-8F53-11D0-B FA0-00A024151983}
Monday, April 10, 2006 Service Control Manager The following boot-start or
system-start driver(s) failed to load: Fips intelppm SAVRTPEL SY MTDI
Monday, April 10, 2006 DCOM DCOM got error "%1084" attempting to start the
service StiSvc with arguments "" in order to run the server:
{A1F4E726-8CF1-11D1-B F92-0060081ED811}
Monday, April 10, 2006 DCOM DCOM got error "%1084" attempting to start the
service ntmssvc with arguments "-Service" in order to run the server:
{D61A27C6-8F53-11D0-B FA0-00A024151983}
Monday, April 10, 2006 DCOM DCOM got error "%1084" attempting to start the
service StiSvc with arguments "" in order to run the server:
{A1F4E726-8CF1-11D1-B F92-0060081ED811}
Friday, February 17, 2006 Applicatio n Error Faulting application
iexplore.exe, version 6.0.2900.2180, faulting module shdocvw.dll, version
6.0.2900.2805, fault address 0x00018d20.
Friday, February 17, 2006 Applicatio n Error Fault bucket 250702100.
Friday, February 17, 2006 DrWatson The application, C:\Program Files\Internet
Explorer\iexplore.exe, generated an application error The error occurred on
02/17/2006 @ 03:11:59.984 The exception generated was c0000005 at address
77778D20 (SHDOCVW!Ordinal146)
Friday, February 17, 2006 nview_info None
Friday, February 17, 2006 nview_info None
Sunday, February 19, 2006 SecurityCe nter The Windows Security Center Service
was unable to establish event queries with WMI to monitor third party
AntiVirus and Firewall.
Sunday, February 19, 2006 EventSyste m The COM+ Event System detected a bad
return code during its internal processing. HRESULT was C0000005 from line 44
of d:\qxp_slp\com\com1x\src\event s\tier1\eventsystemobj.cpp. Please contact
Microsoft Product Support Services to report this error.
Sunday, February 19, 2006 ESENT wuauclt (3748) Corruption was detected during
soft recovery in logfile C:\WINDOWS\SoftwareDistributio
n\DataStore\Logs\edb.log. The failing checksum record is located at position
END. Data not matching the log-file fill pattern first appeared in sector 194
(0x000000C2). This logfile has been damaged and is unusable.
Sunday, February 19, 2006 Applicatio n Error Faulting application
iexplore.exe, version 6.0.2900.2180, faulting module ntdll.dll, version
5.1.2600.2180, fault address 0x000111de.
Friday, February 24, 2006 Applicatio n Hang Hanging application iexplore.exe,
version 6.0.2900.2180, hang module hungapp, version 0.0.0.0, hang address
0x00000000.
Friday, February 24, 2006 Applicatio n Hang Fault bucket 126637809.
Friday, February 24, 2006 Applicatio n Hang Hanging application
EverQuest2.exe, version 1.0.0.1, hang module hungapp, version 0.0.0.0, hang
address 0x00000000.
Friday, February 24, 2006 Applicatio n Hang Fault bucket 41315240.
Sunday, February 26, 2006 Applicatio n Hang Hanging application
EverQuest2.exe, version 1.0.0.1, hang module hungapp, version 0.0.0.0, hang
address 0x00000000.
Sunday, February 26, 2006 Applicatio n Hang Fault bucket 41315240.
Tuesday, February 28, 2006 Applicatio n Error Faulting application
everquest2.exe, version 1.0.0.1, faulting module everquest2.exe, version
1.0.0.1, fault address 0x0039677f.
Tuesday, February 28, 2006 Applicatio n Error Fault bucket 269667252.
Tuesday, February 28, 2006 DrWatson The application, C:\Program
Files\Sony\EverQuest II\EverQuest2.exe, generated an application error The
error occurred on 02/28/2006 @ 21:38:16.678 The exception generated was
c0000005 at address 0079677F ()
Monday, April 10, 2006 Applicatio n Error Faulting application launchpad.exe,
version 0.0.0.0, faulting module launchpad.exe, version 0.0.0.0, fault
address
0x0013cdfd.
Monday, April 10, 2006 Applicatio n Error Faulting application userinit.exe,
version 5.1.2600.2180, faulting module msvcrt.dll, version 7.0.2600.2180,
fault address 0x0002ee58.
Monday, April 10, 2006 EventSyste m The COM+ Event System detected a bad
return code during its internal processing. HRESULT was 8007043C from line 44
of d:\qxp_slp\com\com1x\src\event s\tier1\eventsystemobj.cpp. Please contact
Microsoft Product Support Services to report this error.
drive so completely formatted them and when that didn't work bought a new
hard drive. Things were fine until tonight and the same symptoms. Computer
just shut down in the middle of playing SWG online then will not get itself
past my login without eventually crashing. I have tried system restore. I
can run in safe mode this time so far. Following is more info for someone
who can read and understand this (which I can't) Any suggestions are
welcomed!!
System shut down and crash after loading personal settings. Can only run in
safe mode. System restore didn't help.
I see the error this time about a device attached to the system. I have not
recently attached any new devices or installed any programs.
First time this problem appeared (February) I installed new drives and
restored windows to get things back together.
Same thing just happened tonight (April 10, 2006)
after an automatic microsoft update
I am sending all the info from my error file just in case it helps
Tuesday, March 28, 2006 Service Control Manager The Secdrv service failed to
start due to the following error: The process cannot access the file because
it is being used by another process.
Monday, April 10, 2006 Service Control Manager Timeout (30000 milliseconds)
waiting for the Norton AntiVirus Auto-Protect Service service to connect.
Monday, April 10, 2006 Service Control Manager The Norton AntiVirus
Auto-Protect Service service failed to start due to the following error: The
service did not respond to the start or control request in a timely fashion.
Monday, April 10, 2006 System Error Error code 10000050, parameter1 ffffffb6,
parameter2 00000000, parameter3 b64115b8, parameter4 00000000.
Monday, April 10, 2006 Service Control Manager The ISSVC service terminated
with service-specific error 4294967295 (0xFFFFFFFF).
Monday, April 10, 2006 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, April 10, 2006 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, April 10, 2006 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, April 10, 2006 Service Control Manager The TCP/IP NetBIOS Helper
service depends on the AFD Networking Support Environment service which
failed
to start because of the following error: A device attached to the system is
not functioning.
Monday, April 10, 2006 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, April 10, 2006 Service Control Manager The following boot-start or
system-start driver(s) failed to load: AFD Fips intelppm IPSec MRxSmb NetBIOS
NetBT RasAcd Rdbss SAVRTPEL SPBBCDrv S YMTDI Tcpip WS2IFSL
Monday, April 10, 2006 DCOM DCOM got error "%1084" attempting to start the
service ntmssvc with arguments "-Service" in order to run the server:
{D61A27C6-8F53-11D0-B FA0-00A024151983}
Monday, April 10, 2006 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, April 10, 2006 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, April 10, 2006 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, April 10, 2006 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, April 10, 2006 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, April 10, 2006 Service Control Manager The TCP/IP NetBIOS Helper
service depends on the AFD Networking Support Environment service which
failed
to start because of the following error: A device attached to the system is
not functioning.
Monday, April 10, 2006 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, April 10, 2006 Service Control Manager The following boot-start or
system-start driver(s) failed to load: AFD Fips intelppm IPSec MRxSmb NetBIOS
NetBT RasAcd Rdbss SAVRTPEL SYMTDI Tcp ip WS2IFSL
Monday, April 10, 2006 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, April 10, 2006 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, April 10, 2006 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, April 10, 2006 Service Control Manager The following boot-start or
system-start driver(s) failed to load: Fips intelppm SAVRTPEL SY MTDI
Monday, April 10, 2006 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, April 10, 2006 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, April 10, 2006 DCOM DCOM got error "%1084" attempting to start the
service ntmssvc with arguments "-Service" in order to run the server:
{D61A27C6-8F53-11D0-B FA0-00A024151983}
Monday, April 10, 2006 Service Control Manager The following boot-start or
system-start driver(s) failed to load: Fips intelppm SAVRTPEL SY MTDI
Monday, April 10, 2006 DCOM DCOM got error "%1084" attempting to start the
service StiSvc with arguments "" in order to run the server:
{A1F4E726-8CF1-11D1-B F92-0060081ED811}
Monday, April 10, 2006 DCOM DCOM got error "%1084" attempting to start the
service ntmssvc with arguments "-Service" in order to run the server:
{D61A27C6-8F53-11D0-B FA0-00A024151983}
Monday, April 10, 2006 DCOM DCOM got error "%1084" attempting to start the
service StiSvc with arguments "" in order to run the server:
{A1F4E726-8CF1-11D1-B F92-0060081ED811}
Friday, February 17, 2006 Applicatio n Error Faulting application
iexplore.exe, version 6.0.2900.2180, faulting module shdocvw.dll, version
6.0.2900.2805, fault address 0x00018d20.
Friday, February 17, 2006 Applicatio n Error Fault bucket 250702100.
Friday, February 17, 2006 DrWatson The application, C:\Program Files\Internet
Explorer\iexplore.exe, generated an application error The error occurred on
02/17/2006 @ 03:11:59.984 The exception generated was c0000005 at address
77778D20 (SHDOCVW!Ordinal146)
Friday, February 17, 2006 nview_info None
Friday, February 17, 2006 nview_info None
Sunday, February 19, 2006 SecurityCe nter The Windows Security Center Service
was unable to establish event queries with WMI to monitor third party
AntiVirus and Firewall.
Sunday, February 19, 2006 EventSyste m The COM+ Event System detected a bad
return code during its internal processing. HRESULT was C0000005 from line 44
of d:\qxp_slp\com\com1x\src\event s\tier1\eventsystemobj.cpp. Please contact
Microsoft Product Support Services to report this error.
Sunday, February 19, 2006 ESENT wuauclt (3748) Corruption was detected during
soft recovery in logfile C:\WINDOWS\SoftwareDistributio
n\DataStore\Logs\edb.log. The failing checksum record is located at position
END. Data not matching the log-file fill pattern first appeared in sector 194
(0x000000C2). This logfile has been damaged and is unusable.
Sunday, February 19, 2006 Applicatio n Error Faulting application
iexplore.exe, version 6.0.2900.2180, faulting module ntdll.dll, version
5.1.2600.2180, fault address 0x000111de.
Friday, February 24, 2006 Applicatio n Hang Hanging application iexplore.exe,
version 6.0.2900.2180, hang module hungapp, version 0.0.0.0, hang address
0x00000000.
Friday, February 24, 2006 Applicatio n Hang Fault bucket 126637809.
Friday, February 24, 2006 Applicatio n Hang Hanging application
EverQuest2.exe, version 1.0.0.1, hang module hungapp, version 0.0.0.0, hang
address 0x00000000.
Friday, February 24, 2006 Applicatio n Hang Fault bucket 41315240.
Sunday, February 26, 2006 Applicatio n Hang Hanging application
EverQuest2.exe, version 1.0.0.1, hang module hungapp, version 0.0.0.0, hang
address 0x00000000.
Sunday, February 26, 2006 Applicatio n Hang Fault bucket 41315240.
Tuesday, February 28, 2006 Applicatio n Error Faulting application
everquest2.exe, version 1.0.0.1, faulting module everquest2.exe, version
1.0.0.1, fault address 0x0039677f.
Tuesday, February 28, 2006 Applicatio n Error Fault bucket 269667252.
Tuesday, February 28, 2006 DrWatson The application, C:\Program
Files\Sony\EverQuest II\EverQuest2.exe, generated an application error The
error occurred on 02/28/2006 @ 21:38:16.678 The exception generated was
c0000005 at address 0079677F ()
Monday, April 10, 2006 Applicatio n Error Faulting application launchpad.exe,
version 0.0.0.0, faulting module launchpad.exe, version 0.0.0.0, fault
address
0x0013cdfd.
Monday, April 10, 2006 Applicatio n Error Faulting application userinit.exe,
version 5.1.2600.2180, faulting module msvcrt.dll, version 7.0.2600.2180,
fault address 0x0002ee58.
Monday, April 10, 2006 EventSyste m The COM+ Event System detected a bad
return code during its internal processing. HRESULT was 8007043C from line 44
of d:\qxp_slp\com\com1x\src\event s\tier1\eventsystemobj.cpp. Please contact
Microsoft Product Support Services to report this error.