Event 7000 Errors

[jsmartin22]

Hello,

My system has started to "hang" and I believe the issue is realted to either the hard drive controller. Error is: The device, \Device\Ide\iaStor0, did not respond within the timeout period. Hard drive and memory check out OK and I also did system restore, with no help.

However, to ensure the above is the problem, I want to understand or eliminate 2 other errors, system 7000 errors, which are frequent.

1. The AVG9IDSAgent service failed to start due to the following error:
The system cannot find the file specified.
2. The DgiVecp service failed to start due to the following error:
The system cannot find the device specified.

Item #2 has occurred for a long period of time, but item #1 is more recent. Any insight into these errors and possible fixes?

Thanks.

Scott

[AnnMarie]

Hi jsmartin22. The first error is related to an AVG9 service. This latest version of AVG is causing various problem on a number of computers so if I were you, I would uninstall AVG and see if this resolves your problem.

The second error appears to be related to a service installed by a printer. Do you have any problem printing from this computer?

[jsmartin22]

Originally Posted by AnnMarie

Hi jsmartin22. The first error is related to an AVG9 service. This latest version of AVG is causing various problem on a number of computers so if I were you, I would uninstall AVG and see if this resolves your problem.

The second error appears to be related to a service installed by a printer. Do you have any problem printing from this computer?

Ann Marie,

1. As for AVG, I reinstalled ver 8.5 and this item was resolved.
2. As for the DGIVECP driver, I tracked it down and it is related to a Samsung printer: I have two, ML-2510 and CLX-3160FN. No issue with either. The attachment references the driver. Now that I've tracked down the driver, not sure what to do with the information. Looks like it references a parallel port, but I am connected to the printers via USB. Suggestions for next step?

My real issue, I think, is still the iastor error--possibly an OS issue or possibly related to drive controller or hard drive.

Thx!

Scott

[AnnMarie]

2. As for the DGIVECP driver, I tracked it down and it is related to a Samsung printer: I have two, ML-2510 and CLX-3160FN. No issue with either. The attachment references the driver. Now that I've tracked down the driver, not sure what to do with the information. Looks like it references a parallel port, but I am connected to the printers via USB. Suggestions for next step?

All I can suggest is to uninstall and reinstall both printers and hope that the error goes away. If you are not having any problems with either printer, personally, I wouldnt worry about it.

My real issue, I think, is still the iastor error--possibly an OS issue or possibly related to drive controller or hard drive.

See if this Intel document helps.

[jsmartin22]

Ann Marie,

Thx. I had some combination of a system and hard drive failure, which I resolved by installing a new hard drive and System7. So far no issues, but I still do have the DGIVCEP error, even with system7. Oh well..it looks bening.

More interesting to me is why I've had 3 Seagate hard drives fail in the last 6 months, with at least two of them having Event9, iastor errors. Oh well..computer back to normal now.

Thx again.

Scott

[AnnMarie]

Gosh what bad luck!

Scott you said in your first post that your HD checked out ok. What utility did you run that gave it a clean bill of health and how did you eventually determine your HD had failed?

[jsmartin22]

Scott you said in your first post that your HD checked out ok. What utility did you run that gave it a clean bill of health and how did you eventually determine your HD had failed?

Ann Marie, you are correct. During the early phase of the problem, I observed system 'hangs' for 10 - 30s; during this time, I recorded only a single iastor error, and the hard drive checked out OK with both SeaTools and the standard chkdsk utility. Even though I could easily observe the problem, it was not being observed in the event log nor in disk diagnostics.

After 1 - 2 days of system hangs, my system began to consistently register iastor errors. Eventually I received a "critical" error in the event log which indicated a severe hard drive fail--basically the SMART data had faulted for > 70C. Looks like the disk temporarily heated up and the SMART detection recorded the issue. At this point, Seatools also noted the issue with their short Self-Test. Then I just went to a new Server-Grade disk (3 yrs old, but new) and installed system7.

[AnnMarie]

Thanks for posting that information Scott. I hope you were able to backup your data before the drive failed.

Re the DgiVecp.sys error, it may just be buggy software. We could try changing the start mode in the registry and see if this fixes the problem.

Let's see what type of startup it has. Hit the Windows key + r on your keyboard and copy and paste the below command in the Run box.

regedit /e C:\look.txt "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DgiVecp"

Click ok. This will export the contents of that key to a "look.txt" file in your C folder. Click on your C folder and find look.txt and and copy and paste the contents in this thread.

[jsmartin22]

Ann Marie,

Thx for always trying to help. Here is the output per your above post.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\DgiVecp]
"Type"=dword:00000001
"Start"=dword:00000002
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):5c,00,3f,00,3f,00,5c,00,43,00,3 a,00,5c,00,57,00,69,00,6e,00,\
64,00,6f,00,77,00,73,00,5c,00,73,00,79,00,73,00,74 ,00,65,00,6d,00,33,00,32,\
00,5c,00,44,00,72,00,69,00,76,00,65,00,72,00,73,00 ,5c,00,44,00,67,00,69,00,\
56,00,65,00,63,00,70,00,2e,00,73,00,79,00,73,00,00 ,00
"DisplayName"="DgiVecp"
"WOW64"=dword:00000001
"TurnAroundDelay"=dword:00000032
"PreTurnAroundDelay"=dword:00000032
"MinimumStallTime"=dword:00001f40
"CurrentInUse"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\DgiVecp\Enum]
"Count"=dword:00000000
"NextInstance"=dword:00000000
"INITSTARTFAILED"=dword:00000001

Scott

[jsmartin22]

Inadvertent post.

[AnnMarie]

The startup type is automatic. We can change it to manual and see if this helps.

Go here and download Scott.reg to your desktop. Rightclick on it and choose merge. Reboot and let me know if this helped. Also make sure your printer still works ok. If not we can change it back so no biggie.

[jsmartin22]

Ann Marie,

Error is gone so that is great. One item that may be an issue is the "Smart Panel", a supplemanary piece of software is not working. As you know, I just converted to System7 and I didn't verify it worked before. I can still print. Can I change back to the "before" state to test and see if the "Smart Panel" app works? Thx!

Error details for the app below

Problem Event Name: APPCRASH
Application Name: SSMMgr.exe
Application Version: 3.2.2.6
Application Timestamp: 4aaa1a84
Fault Module Name: SSMMgr.exe
Fault Module Version: 3.2.2.6
Fault Module Timestamp: 4aaa1a84
Exception Code: c0000005
Exception Offset: 00003032
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: b236
Additional Information 2: b2361424fbb1c1a85154eaf345a8cd2e
Additional Information 3: dbfb
Additional Information 4: dbfba397288b8b2a287eeed1556612f4

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

[AnnMarie]

Sure. Go here and download Scott1.reg. Follow the previous instructions and reboot.

[jsmartin22]

Ann Marie,

Thx. Your fix was fine; it is my samsung "Smart Panel" programs that are having problems. Thx for my EventID 7000 problems.

Scott

[AnnMarie]

You are welcome Scott. SSMMgr.exe appears to be the Samsung printer monitor, for checking ink levels etc. Have you checked for an updated driver for this printer yet?