System Event ID: Error 7000

[Guest]

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?

 

[Guest]

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

 

[John John]

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.")

Well, that is certainly news to me, a device is a service and a service
is a device! Imagine the things we learn reading these help groups!

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.

While it is true that some services, er.. I mean "devices"... er no, I
mean services, can be started by an item in the above mentioned key,
services set to start at boot time are started by the Service Control
Manager and the instructions as to which services to start is for most
parts obtained from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

John

 

[John John]

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?

Information on these items is difficult to find. This is what I can find:

http://www.runscanner.net/getprocess.aspx?Process=ssport.sys&S1=GO
http://www.runscanner.net/getmd5.aspx?md5=5F77725EC309DE1242D8EFC8E9259A9F&process=ssport.sys

http://www.runscanner.net/getprocess.aspx?Process=DgiVecp.sys&S1=GO
http://www.runscanner.net/getmd5.aspx?md5=770471DE2550820FEEB7E5D24BF2E273&process=dgivecp.sys

Maybe you have or had something from Samsung installed on your pc?

If you cannot resolve the problem by finding and
reinstalling/uninstalling the software responsible for the service go in
the registry and set their start values to manual (3):

The startup for those items is controlled at the REG_DWORD Start value in:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<ServiceName>

Possible start values are: 0, 1, 2, 3, 4

Boot 0x0
System 0x1
Automatic 0x2
Manual 0x3
Disabled 0x4

If setting the service to manual doesn't fix things set them to disabled
and see if things improve.

John

 

[Guest]

I have run the sc query for the services mentioned. I forgot to mention that
in the original post. Sorry about that... Anyways, the error came up the same
for both services "kernel drivers win32_exit_code - 2

Now I know plenty about services and administration as I am an Administrator
for the company I work for but that doesn't mean much nowadays. Nither
service is in the local machine, but I will ask the user what is happening
when the errors pop-up and go from there.

Thank you,

 

[Guest]

Here is the sc query ran for the 3 failures:

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

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

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?

 

[Guest]

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

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

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?