Here is the sc query ran for the 3 errors:

C:\Documents and Settings\>sc query aspi32

SERVICE_NAME: aspi32
TYPE : 1 KERNEL_DRIVER
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 2 (0x2)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

C:\Documents and Settings\>sc query ssport

SERVICE_NAME: ssport
TYPE : 1 KERNEL_DRIVER
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 2 (0x2)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

C:\Documents and Settings\>sc query dgivecp

SERVICE_NAME: dgivecp
TYPE : 1 KERNEL_DRIVER
STATE : 1 STOPPED
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 2 (0x2)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
--
Horsepower


"WindowsXPert" wrote:

> When you see an exception thrown (an error message) claiming that a device or
> service failed to start because <something> wasn't there, what's happening is
> that a call has been made externally to that device|service from another
> device|service which either depends on it or is a part of it.
>
> Remember that, in NT terms, a "device" is not a printer, a scanner, a
> monitor, or some peripheral component. The term is figurative and refers
> instead to a service. (Windows95/98/ME spoke to actual devices, WindowsNT
> speaks to services called "devices.")
>
> What's actually calling the "device" could be some residual code left behind
> by an uncircumspect uninstaller; a start-up item; a load line; a statement in
> the HKLM/Software/Microsoft/Windows/CurrentVersion/Run registry sub-key...
> there is a small handful of possibilities.
>
> The next couple of times the exception is thrown, try to make a mental note
> of what you're doing at the time. Is the machine booting up? Is the same
> application running every time this occurs? Are you trying to do the same
> type of work?
>
> You'll no doubt find the occurrences have something in common which will
> suggest (if not clearly identify) the culprit. From there, the process of
> eliminating the annoyance should be a given. Presently, there are too many
> potentially wild geese to chase before I could hand you a definitive 1-2-3
> step process. (You might start with the registry key above, logged onto the
> machine as the local administrator, though.)
>
> I'll ask for [ ] Notification of replies if you want to keep the thread open.
>
> Sam French
>
>
>
> "shawndiaz" wrote:
>
> > It states that SSPORT and DgiVecp services failed to start because they are
> > not there. Why is it trying to start something that's not there? It has been
> > there since 6/12/07. What is using these services to make XP need to start
> > them?
> > --
> > Horsepower