Service Control Manager The Remote Procedure Call (RPC) service terminated unexp

  • Thread starter Arlan R Spratte
  • Start date
A

Arlan R Spratte

Every Time I try to go on line I get the message Service
Control Manager The Remote Procedure Call (RPC) service
terminated unexpectedly.

What Can you do to fix this?

Specifications
Dell Computer Corporation
System Model: OptiPlex GX1 450MTbr+
BIOS Version: Dell Computer Corporation A02
Operating System
Microsoft Windows XP Professional
Version: 5.1.2600
Service Pack: 0.0
Location: E:\WINDOWS
PID: 55274-OEM-0011903-00102
Hot Fix: Q319580
Memory (RAM)
Capacity: 256 MB
Processor
Intel Pentium II processor
Version: x86 Family 6 Model 5 Stepping 2
Speed: 448 MHz
General Computer Info
System Name: SCHOOLXP-DE55LL
Domain: WORKGROUP
Time Zone: Central Standard Time
Connection: Workstation (standalone)
Proxy Server: Auto
IP Address: 0.0.0.0
IPX Address: Not Enabled
Local Disk
Total Capacity: 12.50 GB
Sum of Hard Disks: (C: E: )
Used: 3.07 GB
Free: 9.42 GB
Error Log
Date - Time Source Description
Sunday, December 07, 2003 Serial While validating that
\Device\Serial2 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial3 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial4 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial5 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial6 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial7 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial8 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial0 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial3 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial4 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial0 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial3 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial2 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Serial While validating that
\Device\Serial3 was really a serial port, the contents of
the divisor latch register was identical to the interrupt
enable and the receive registers. The device is assumed
not to be a serial port and will be deleted.
Sunday, December 07, 2003 Service Control Manager The
Remote Procedure Call (RPC) service terminated
unexpectedly. It has done this 1 time(s). The following
corrective action will be taken in 60000 milliseconds:
Reboot the machine.
Sunday, December 07, 2003 Service Control Manager The
Remote Procedure Call (RPC) service terminated
unexpectedly. It has done this 1 time(s). The following
corrective action will be taken in 60000 milliseconds:
Reboot the machine.
Sunday, December 07, 2003 Service Control Manager The
Remote Procedure Call (RPC) service terminated
unexpectedly. It has done this 1 time(s). The following
corrective action will be taken in 60000 milliseconds:
Reboot the machine.
Sunday, December 07, 2003 Service Control Manager The
RpcImpersonateClient call failed with the following error:
No security context is available to allow impersonation.
Monday, December 08, 2003 Service Control Manager The
Remote Procedure Call (RPC) service terminated
unexpectedly. It has done this 1 time(s). The following
corrective action will be taken in 60000 milliseconds:
Reboot the machine.
Monday, December 08, 2003 Service Control Manager The
Remote Procedure Call (RPC) service terminated
unexpectedly. It has done this 1 time(s). The following
corrective action will be taken in 60000 milliseconds:
Reboot the machine.
Monday, December 08, 2003 Service Control Manager Timeout
(30000 milliseconds) waiting for the crd service to
connect.
Monday, December 08, 2003 Service Control Manager The crd
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, December 08, 2003 Service Control Manager The
Remote Procedure Call (RPC) service terminated
unexpectedly. It has done this 1 time(s). The following
corrective action will be taken in 60000 milliseconds:
Reboot the machine.
Monday, December 08, 2003 Service Control Manager Timeout
(30000 milliseconds) waiting for the crd service to
connect.
Monday, December 08, 2003 Service Control Manager The crd
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, December 08, 2003 Service Control Manager The
Remote Procedure Call (RPC) service terminated
unexpectedly. It has done this 1 time(s). The following
corrective action will be taken in 60000 milliseconds:
Reboot the machine.
Monday, December 08, 2003 Service Control Manager The
RpcImpersonateClient call failed with the following error:
No security context is available to allow impersonation.
Sunday, December 07, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Sunday, December 07, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Sunday, December 07, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BF from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Sunday, December 07, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Sunday, December 07, 2003 Applicatio n Error Faulting
application svchost.exe, version 5.1.2600.0, faulting
module unknown, version 0.0.0.0, fault address
0x00000000.
Sunday, December 07, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Sunday, December 07, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Monday, December 08, 2003 Applicatio n Hang Hanging
application notepad.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, December 08, 2003 Applicatio n Hang Hanging
application notepad.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, December 08, 2003 Applicatio n Hang Hanging
application notepad.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, December 08, 2003 Applicatio n Hang Hanging
application notepad.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, December 08, 2003 Applicatio n Hang Hanging
application notepad.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, December 08, 2003 Applicatio n Hang Hanging
application notepad.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, December 08, 2003 Applicatio n Hang Hanging
application notepad.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, December 08, 2003 Applicatio n Hang Hanging
application notepad.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, December 08, 2003 Applicatio n Hang Hanging
application notepad.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, December 08, 2003 Applicatio n Hang Fault bucket
02121908.
Monday, December 08, 2003 Applicatio n Hang Hanging
application notepad.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, December 08, 2003 Applicatio n Hang Hanging
application notepad.exe, version 5.1.2600.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.
Monday, December 08, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Monday, December 08, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Monday, December 08, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Monday, December 08, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Monday, December 08, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Monday, December 08, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Monday, December 08, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
Monday, December 08, 2003 MsiInstall er
============================== =======================
Excep tion code: C0000005 ACCESS_VIOLATION Module:
E:\Program Files\MSN\MsnInstaller\MSNSIGN .DLL Function:
0x2706a733 ==================
============================== ===== Registers: EAX:00000
000 EBX:000400E2 ECX:00000000 EDX:2709B43C ESI:00000001
EDI:77D4993B CS:EIP:001B:2706 A733 SS:ESP:0023:0006E1D4
EBP:0006E1E4 DS:0023 ES:0023 FS:003B GS:0000
Flags:00010202 Cal l stack: Address Frame 2706A733
0006E1E4 0 -- 0x00093138 0x0009CDF8 0x0006E214 0x2706F475
27040166 0006E1F4 0 -- 0x00000016 0x00000001 0x00000000
0x0006E288 2706F475 0006E214 0 -- 0x000400E2 0x00000016
0x00000001 0x00000000 77D43A5F 0006E240 0 -- 0x2706F41A
0x000400E2 0x00000016 0x00000001 77D43B2E 0006E2A8 0 --
0x00000000 0x2706F41A 0x000400E2 0x00000016 77D45874
0006E2FC 0 -- 0x005571A8 0x00000016 0x00000001 0x00000000
77D458A4 0006E324 0 -- 0x0006E334 0x00000018 0x005571A8
0x00000016
Monday, December 08, 2003 EventSyste m The COM+ Event
System detected a bad return code during its internal
processing. HRESULT was 800706BA from line 44 of
d:\nt\com\com1x\src\events\tie r1\eventsystemobj.cpp.
Please contact Microsoft Product Support Services to
report this error.
 
K

Kevin

You can run an anti-virus program to find and remove the worm you have been
infected with. Probably Blaster or one of the variants. Do a Google search
for "blaster worm removal" and that should get you going again. Use a
firewall, anti-virus, spyware and adware application.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top