[Malcontented]

Hello,

So my laptop has suddenly slowed down and many of the programs are either causing the system to lock up or just won't open. Worryingly my anti-virus and general maintenance software, Windows Live One Care, has 'stopped or is not working'. But I established in the malware forum with jwang01 that the problem is not malware related. Driver issue? I'm really not sure.

Here's a link to what we've already done and some more detail.

http://www.geekstogo...er-t264104.html


Thanks in advance,

Malcontented

[Advertisements]

Please download the Event Viewer Tool by Vino Rosso VEW from here and save it to your Desktop:
Double-click VEW.exe
Under Select log to query... select
Application
System
Under select type to list select
Error
Warning

Then Click the radio button for Number of events
Type 5 in the 1 to 20 box
Then click the Run button.

Notepad will open with the output log....Please cut and paste the Output log in your next reply

[happyrock]

Please download the Event Viewer Tool by Vino Rosso VEW from here and save it to your Desktop:
Double-click VEW.exe
Under Select log to query... select
Application
System
Under select type to list select
Error
Warning

Then Click the radio button for Number of events
Type 5 in the 1 to 20 box
Then click the Run button.

Notepad will open with the output log....Please cut and paste the Output log in your next reply

[Malcontented]

Hello Happyrock,

Thanks for helping me out. Here's the log:


Vino's Event Viewer v01c run on Windows Vista in English
Report run at 12/01/2010 01:46:30

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 12/01/2010 01:44:42
Type: Error Category: 16
Event: 4609 Source: Microsoft-Windows-EventSystem
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

Log: 'Application' Date/Time: 11/01/2010 20:13:08
Type: Error Category: 16
Event: 4609 Source: Microsoft-Windows-EventSystem
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

Log: 'Application' Date/Time: 11/01/2010 20:10:08
Type: Error Category: 16
Event: 4609 Source: Microsoft-Windows-EventSystem
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

Log: 'Application' Date/Time: 10/01/2010 23:36:17
Type: Error Category: 16
Event: 4609 Source: Microsoft-Windows-EventSystem
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

Log: 'Application' Date/Time: 10/01/2010 13:22:20
Type: Error Category: 16
Event: 4609 Source: Microsoft-Windows-EventSystem
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 12/01/2010 01:44:33
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 11/01/2010 22:40:56
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 11/01/2010 22:40:55
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 11/01/2010 20:12:53
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 11/01/2010 20:10:51
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 12/01/2010 01:45:27
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: spldr Wanarpv6

Log: 'System' Date/Time: 12/01/2010 01:45:27
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error: The dependency service or group failed to start.

Log: 'System' Date/Time: 12/01/2010 01:44:46
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030}

Log: 'System' Date/Time: 12/01/2010 01:44:46
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}

Log: 'System' Date/Time: 12/01/2010 01:44:43
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1068" attempting to start the service fdPHost with arguments "" in order to run the server: {145B4335-FE2A-4927-A040-7C35AD3180EF}

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 12/01/2010 01:44:03
Type: Warning Category: 0
Event: 263 Source: PlugPlayManager
The service 'TabletInputService' may not have unregistered for device event notifications before it was stopped.

Log: 'System' Date/Time: 12/01/2010 01:42:31
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 11/01/2010 22:48:31
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 11/01/2010 22:40:57
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 11/01/2010 20:12:24
Type: Warning Category: 0
Event: 263 Source: PlugPlayManager
The service 'TabletInputService' may not have unregistered for device event notifications before it was stopped.

[happyrock]

Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. To do this, follow these steps:

1. Open an elevated command prompt. To do this... click... Start, click All Programs, click Accessories... right-click Command Prompt, and then click ..Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
2. Type the following command, and then press ENTER:
sfc /scannow
The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.

To determine which files could not be repaired by the System File Checker tool, follow these steps:

1. Open an elevated command prompt.
2. Type the following command, and then press ENTER:
findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txt
copy and paste the file back here...

Edited by happyrock, 12 January 2010 - 09:35 AM.

[Malcontented]

Hello,

I used the System File checker tool but all i got was the following message: 'Windows Resource Protection did not find any integrity violations.'
I then typed the second part in anyway and it came up with, 'FINDSTR: Cannot open %windr%\logs\cbs.log'.

[chavekotte]

Hi Malcontented,
I have the exact same problem. How did you end up fixing it? I don't see the tech's reply posted.

THANKS!

[rshaffer61]

The log will not be created if nothing was replaced or repaired.
Tutorial for running chkdsk in Vista\Win 7 located HERE.

Direct to: chavekotte

Please start your own topic
Although your issue may seem similar there can be other factors that may need to be resolved.
By bumping on someone's topic it makes it confusing for the tech to understand who they are helping. This can in turn cause the wrong support to be given and can cause instability or worse to happen to your system.
Please post more information as to your exact issue in your topic. Include any error messages you get as well as your system specs. This will help us to assist you more efficiently.
Thank you for your cooperation.