H
Harold
Having some major problems here...
A couple of weeks ago, Window starting freezing up randomly. At first,
it was once every couple of days or so - figured it was overheating
and I'd work on it this weekend.
As of this weekend, it's been freezing once every hour or two. I've
been checking the event logs, and every freeze is preceeded by the
following messages:
ESENT : wuaueng.dll (2380) SUS20ClientDataStore: The database engine
stopped the instance (0).
ESENT : wuauclt (2380) The database engine stopped.
Now, sometimes these are the ONLY two recent messages. At other times,
these are immediately preceeded by the following chain of events:
ccSetMgr : Application starting
ccSetMgr : Application started
GhostStartService : The description for Event ID ( 0 ) in Source (
GhostStartService ) cannot be found. The local computer may not have
the necessary registry information or message DLL files to display
messages from a remote computer. You may be able to use the
/AUXSOURCE= flag to retrieve this description; see Help and Support
for details. The following information is part of the event: Service
started.
NProtectService : The service was started.
Task Manager Lite : The description for Event ID ( 105 ) in Source (
Task Manager Lite ) cannot be found. The local computer may not have
the necessary registry information or message DLL files to display
messages from a remote computer. You may be able to use the
/AUXSOURCE= flag to retrieve this description; see Help and Support
for details. The following information is part of the event: The event
log file is corrupt..
ccEvtMgr : Application starting
ccEvtMgr : Application started
SecurityCenter : The Windows Security Center Service has started.
ESENT : wuauclt (1680) The database engine 5.01.2600.2180 started.
ESENT : wuaueng.dll (1680) SUS20ClientDataStore: The database engine
started a new instance (0).
And then, IMMEDIATELY afterwards, I get the ESENT "database stopped
the instance" and "database stopped" errors. Now, sometimes the
computer freezes and those Ghost / NProtectService messages don't
appear in the message logs... sometimes it's just the ESENT database
manager stopping out of nowhere. So I'm not sure if those events are
related to the crash.
Can anyone recommend a solution?
Thanks,
Robert
A couple of weeks ago, Window starting freezing up randomly. At first,
it was once every couple of days or so - figured it was overheating
and I'd work on it this weekend.
As of this weekend, it's been freezing once every hour or two. I've
been checking the event logs, and every freeze is preceeded by the
following messages:
ESENT : wuaueng.dll (2380) SUS20ClientDataStore: The database engine
stopped the instance (0).
ESENT : wuauclt (2380) The database engine stopped.
Now, sometimes these are the ONLY two recent messages. At other times,
these are immediately preceeded by the following chain of events:
ccSetMgr : Application starting
ccSetMgr : Application started
GhostStartService : The description for Event ID ( 0 ) in Source (
GhostStartService ) cannot be found. The local computer may not have
the necessary registry information or message DLL files to display
messages from a remote computer. You may be able to use the
/AUXSOURCE= flag to retrieve this description; see Help and Support
for details. The following information is part of the event: Service
started.
NProtectService : The service was started.
Task Manager Lite : The description for Event ID ( 105 ) in Source (
Task Manager Lite ) cannot be found. The local computer may not have
the necessary registry information or message DLL files to display
messages from a remote computer. You may be able to use the
/AUXSOURCE= flag to retrieve this description; see Help and Support
for details. The following information is part of the event: The event
log file is corrupt..
ccEvtMgr : Application starting
ccEvtMgr : Application started
SecurityCenter : The Windows Security Center Service has started.
ESENT : wuauclt (1680) The database engine 5.01.2600.2180 started.
ESENT : wuaueng.dll (1680) SUS20ClientDataStore: The database engine
started a new instance (0).
And then, IMMEDIATELY afterwards, I get the ESENT "database stopped
the instance" and "database stopped" errors. Now, sometimes the
computer freezes and those Ghost / NProtectService messages don't
appear in the message logs... sometimes it's just the ESENT database
manager stopping out of nowhere. So I'm not sure if those events are
related to the crash.
Can anyone recommend a solution?
Thanks,
Robert