It happened again

[Guest]

Last night my computer started chattering as if it was running, soon after my
printer acted like it was preparing to print. Then, a sheet of paper ran
through the printer - nothing was printed, the computer was in stand-by
noise, but was still chattering. This has happened a couple of times -
usually at the crack of dawn and wakes my husband and I up. I have windows xp
home edition, automatic updates, 4 different spyware programs - including
microsofts beta version, norton anti virus, zone alarm.....nothing shows up
but the usual cookies. What would cause my computer to do this?

 

[Slippery_one]

Try looking in you event viewer in the Administrative tools applet if
you can nail down what time it happens. That might give you a clue.

 

[Guest]

Great Idea - what I found is that
wuaueng.dll (3648) SUS20ClientDataStore: The database engine started a new
instance (0).
and
wuauclt (3648) The database engine 5.01.2600.2180 started.

Also noted that the W32time 29 which apparently has to do with connectivity.
Found this from the help and support center information from the event log.
WUA is Windows Update Agent.

Guess now all I have to do is turn off the WUA, and then it won't search for
connectivity at the crack of dawn. Still not sure why this spawned my
printed into acting possessed!

Thanks
Liz

 

[Slippery_one]

Great Idea - what I found is that
wuaueng.dll (3648) SUS20ClientDataStore: The database engine started
a new
instance (0).
and
wuauclt (3648) The database engine 5.01.2600.2180 started.

Also noted that the W32time 29 which apparently has to do with
connectivity.
Found this from the help and support center information from the
event log.
WUA is Windows Update Agent.

Guess now all I have to do is turn off the WUA, and then it won't
search for
connectivity at the crack of dawn. Still not sure why this spawned
my
printed into acting possessed!

Thanks
Liz

:

I felt pretty sheepish one day when an accountant (no skills with
computers) found the event viewer and pointed to the error. Oh well!


Check for scheduled events too!