Event Viewer shows error every 2 minutes

Jkc73 Topic Starter

Post #1December 1, 2008, 8:12 PM UTC last edited December 1, 2008, 8:33 PM UTC

Hi all,

New HDD, new install of OS,

Then BSoD

(The bugcheck was: 0x1000008e (0xc0000005, 0xbf80677c, 0xa9821c74, 0x00000000).
A dump was saved in: C:\WINDOWS\Minidump\Mini120108-01.dmp.

( More about this later, if needed.)
I have no doubt if I fix the few errors in the event viewer, my BSoD happening again will be reduced for now.

These entries from the Event Viewer may be of some assistance,

Event Type: Information
Event Source: EventLog
Event Category: None
Event ID: 6006
Date: 1/12/2008
Time: 8:09:44 PM
User: N/A
Computer: LEO
Description:
The Event log service was stopped.

Data:
0000: ff 00 00 00 ÿ…
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: EventLog
Event Category: None
Event ID: 6009
Date: 1/12/2008
Time: 8:10:29 PM
User: N/A
Computer: LEO
Description:
Microsoft ® Windows ® 5.01. 2600 Service Pack 3 Multiprocessor Free.

~~~~~~`~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: EventLog
Event Category: None
Event ID: 6005
Date: 1/12/2008
Time: 8:10:29 PM
User: N/A
Computer: LEO
Description:
The Event log service was started.

Event Type: Error
Event Source: iviVD
Event Category: None
Event ID: 9
Date: 1/12/2008
Time: 8:10:02 PM
User: N/A
Computer: LEO
Description:
The device, \Device\Scsi\iviVD1, did not respond within the timeout period.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 10 00 01 00 64 00 ……d.
0008: 00 00 00 00 09 00 04 c0 …….À
0010: 00 01 00 00 00 00 00 00 ……..
0018: 00 00 00 00 00 00 00 00 ……..
0020: 00 00 00 00 00 00 00 00 ……..
0028: 00 00 00 00 00 00 00 00 ……..
0030: 00 00 00 00 07 00 00 00 ……..

More information is not available regarding this error———^ at the "Help and Support Center" at http://go.microsoft.com/fwlink/events.asp.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 1/12/2008
Time: 8:10:53 PM
User: NT AUTHORITY\SYSTEM
Computer: LEO
Description:
The Network Location Awareness (NLA) service was successfully sent a start control.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 1/12/2008
Time: 8:10:53 PM
User: N/A
Computer: LEO
Description:
The Network Location Awareness (NLA) service entered the running state.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 1/12/2008
Time: 8:10:53 PM
User: NT AUTHORITY\SYSTEM
Computer: LEO
Description:
The Application Layer Gateway Service service was successfully sent a start control.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 1/12/2008
Time: 8:10:53 PM
User: N/A
Computer: LEO
Description:
The Application Layer Gateway Service service entered the running state.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 2/12/2008
Time: 1:42:20 AM
User: NT AUTHORITY\SYSTEM
Computer: LEO
Description:
The Fast User Switching Compatibility service was successfully sent a start control.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 2/12/2008
Time: 1:42:20 AM
User: N/A
Computer: LEO
Description:
The Fast User Switching Compatibility service entered the running state.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 2/12/2008
Time: 1:42:24 AM
User: NT AUTHORITY\SYSTEM
Computer: LEO
Description:
The SSDP Discovery Service service was successfully sent a start control.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 2/12/2008
Time: 1:42:24 AM
User: N/A
Computer: LEO
Description:
The SSDP Discovery Service service entered the running state.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 2/12/2008
Time: 1:42:25 AM
User: N/A
Computer: LEO
Description:
The Telephony service entered the running state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Below are some of the suspects of mine

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 2/12/2008
Time: 1:42:25 AM
User: LEO\Owner
Computer: LEO
Description:
The Remote Access Connection Manager service was successfully sent a start control.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 2/12/2008
Time: 1:42:29 AM
User: NT AUTHORITY\SYSTEM
Computer: LEO
Description:
The dlcc_device service was successfully sent a start control.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 2/12/2008
Time: 1:42:29 AM
User: N/A
Computer: LEO
Description:
The dlcc_device service entered the running state.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 2/12/2008
Time: 1:42:30 AM
User: N/A
Computer: LEO
Description:
The Remote Access Connection Manager service entered the running state.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 2/12/2008
Time: 1:42:31 AM
User: NT AUTHORITY\SYSTEM
Computer: LEO
Description:
The IMAPI CD-Burning COM Service service was successfully sent a start control.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 2/12/2008
Time: 1:42:31 AM
User: N/A
Computer: LEO
Description:
The IMAPI CD-Burning COM Service service entered the running state.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 2/12/2008
Time: 1:42:37 AM
User: N/A
Computer: LEO
Description:
The IMAPI CD-Burning COM Service service entered the stopped state.

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 2/12/2008
Time: 1:44:29 AM
User: LEO\Owner
Computer: LEO
Description:
The server {323CE21C-A448-40AA-BA74-7FCF1E441069} did not register with DCOM within the required timeout.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 2/12/2008
Time: 1:46:35 AM
User: LEO\Owner
Computer: LEO
Description:
The server {323CE21C-A448-40AA-BA74-7FCF1E441069} did not register with DCOM within the required timeout.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 2/12/2008
Time: 1:48:40 AM
User: LEO\Owner
Computer: LEO
Description:
The server {323CE21C-A448-40AA-BA74-7FCF1E441069} did not register with DCOM within the required timeout.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

And the Error Event continues every 2:05 minutes,

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 2/12/2008
Time: 3:58:20 AM
User: LEO\Owner
Computer: LEO
Description:
The server {323CE21C-A448-40AA-BA74-7FCF1E441069} did not register with DCOM within the required timeout.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 2/12/2008
Time: 4:00:25 AM
User: LEO\Owner
Computer: LEO
Description:
The server {323CE21C-A448-40AA-BA74-7FCF1E441069} did not register with DCOM within the required timeout.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I have tried to use the following:

Using Regedit, navigate to the following registry value ->HKCR\Clsid\clsid value\localserver32
The clsid value is the information displayed in the message.
In the right pane, double-click Default. The Edit String dialog box is displayed. Leave this dialog box open.
Click Start, and then click My Computer.
Using the information displayed in the Value data box of the Edit String dialog box, navigate to the program.
Right-click the program name, and then click Properties.
The Properties dialog box for the program is displayed.
To determine who the vendor is for this program, refer to the Version tab.

The Value data box of the Edit String dialog box was empty, or I was looking in the wrong place.

I hope this little bit of information helps, I will keep researching as always.

Thanks for any advice offered,

Jkc73

Jkc73

Post #2December 2, 2008, 8:31 AM UTC

The dlcc_device has been prevented from starting,(using Spybot's Tools > System Start Up )
dlcc_device is the Dell Printer Device Monitor. ( I'm low on ink )

And due to telling the Printer Program not to bother me about it,
I was creating a log in the event viewer.
How simple, though it took some time.
Lets hope that is all.

Jkc73

Jkc73

Post #3December 7, 2008, 2:32 AM UTC

Well a quick fix is not always a permanent one,

The need to print has made itself known.

Therefore my fix has caused me not to be able to print, so reversing my fix is my only alternative.

Now it is time to find a real fix.

Please help

Jkc73

Doug

Post #4December 7, 2008, 3:37 AM UTC

What Software Firewall are you running? Try running with only the native Windows Firewall.

Doug

Post #5December 7, 2008, 3:54 AM UTC

1. Click Start | Control Panel and select the System applet. 2. Click the Remote tab. 3. Under Remote Assistance, make sure the Allow users to connect remotely to this computer checkbox is unchecked.

Doug

Post #6December 7, 2008, 4:01 AM UTC

Problem-solving checklist:
Only worry about the ones that relate to your hardware and software that is installed.
http://www.eventid.net/display.asp?eventid…COM&phase=1

Jkc73

Post #7December 7, 2008, 4:11 AM UTC

Hi Doug,

My current Firewall is the free version from C O M O D O, Currently running in Training Mode, with the Defense+ also running in Training Mode. ( Disabled )

Windows Firewall ( Active )

Remote Assistance ( Unchecked )

Errors still,

About to visit http://www.eventid.net/display.asp?eventid…COM&phase=1

Thanks for your help,

Jkc73

Jkc73

Post #8December 7, 2008, 6:36 AM UTC

Nothing applies here -> [http://www.eventid.net/display.asp?eventid…COM&phase=1]
( Unless I remove the default messenger that comes with windows xp )
A lot of people have referred to messenger causing this event error.
( Not just at the site above )

Will keep researching

Thanks for your advice, as always

Jkc73

Doug

Post #9December 7, 2008, 7:05 AM UTC

Kill the messenger! Serious.
That is just for MS convenience for sending error reporting back to them for their benefit.
Have you ever heard of anyone ever getting a call from MS, saying "Thank you for your error report… here's what we'll do for you." ?

You can google "kill the messenger" or do some research at http://www.grc.com/default.htm.
I think you've mentioned previous experience using the GRC stealth firewall testing? Same guy.

Keep on researching re: your blue screen, and keep us posted.

What actually happens. Does it reboot successfully sometimes?
Have you checked in Device Manager? <– yellow or red warnings means reinstall the Driver.
You've just re-installed Windows…. did you install the Chipset Drivers?

Best Regards,

Jkc73

Post #10December 7, 2008, 9:38 AM UTC

The messenger has been shot, still the event error occurs,

Have you checked in Device Manager? <– yellow or red warnings means reinstall the Driver.

Please see here to advise.

Device Manager shows 2 yellow warnings, both from the Non-Plug and Play Drivers, they are as follows ~

C:\WINDOWS\system32\drivers\Parport.sys
( Device Instance Id ) ROOT\LEGACY_PARPORT\0000
CURRENT STATUS: Stopped
START UP TYPE: Demand
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:\WINDOWS\system32\drivers\Serial.sys
( Device Instance Id ) ROOT\LEGACY_SERIAL\0000
CURRENT STATUS: Stopped
START UP TYPE:Automatic
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Upon an attempt to start these drivers, the same message was displayed for both drivers on each occurrence.

The system encountered the following error while attempting to start the service. The service cannot be started, either because it is disabled or it has no enabled devices associated with it.

Keep on researching re: your blue screen, and keep us posted.

From my research, this could have caused the B.S.o.D.
These being for the Non-Plug and Play Drivers, for parallel & serial ports, I think maybe it is to with the Chipset Drivers

I would require some more assistance from here, just to be safe.

Thanks in advance,

Jkc73

✨ Ask AI

Ask AI