Windows Explorer Stops When Clicking Sidebar

[otown]

This just started today. When I right or left click in the Sidebar area Windows Explorer stops and then restarts.

Any ideas?

 

[Ashvin Busviah]

hmm.. is that computer normally slow? what is the specs of that machine?

 

[otown]

I7-940 processor
8 Gigs memory
1T hard drive
ATI HD4670 Video card

 

[otown]

Some more info. If I set Sidebar to always be on top then the stopping and restarting of Windows Explorer is continuous. The icons in the Systems Tray disappear and then come back gradually.

 

[Ashvin Busviah]

Any errrors recorded under the event viewer?

 

[otown]

From the Event Viewer Application Log after I triggered the problem:

Log Name: Application
Source: Application Error
Date: 13/10/2010 7:08:48 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: xxx-PC
Description:
Faulting application Explorer.EXE, version 6.0.6002.18005, time stamp 0x49e02a1e, faulting module Explorer.EXE, version 6.0.6002.18005, time stamp 0x49e02a1e, exception code 0xc0000096, fault offset 0x0000000000026532, process id 0xc10, application start time 0x01cb6a6c95178cd4.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-10-13T11:08:48.000Z" />
<EventRecordID>47193</EventRecordID>
<Channel>Application</Channel>
<Computer>xxx-PC</Computer>
<Security />
</System>
<EventData>
<Data>Explorer.EXE</Data>
<Data>6.0.6002.18005</Data>
<Data>49e02a1e</Data>
<Data>Explorer.EXE</Data>
<Data>6.0.6002.18005</Data>
<Data>49e02a1e</Data>
<Data>c0000096</Data>
<Data>0000000000026532</Data>
<Data>c10</Data>
<Data>01cb6a6c95178cd4</Data>
</EventData>
</Event>

 

[Ashvin Busviah]

check and install any lastest windows update and also run a check disk on that machine

 

[otown]

Check Disk was run last night. I just updated the OS.....no change

 

[Ashvin Busviah]

hi.. ok
Download and run malware bytes
Malwarebytes Anti-Malware - Free software downloads and software reviews - CNET Download.com
Hmm that might give us an idea whether that computer got some infections !!

cheers
Ash

 

[ilikefree]

I would do a system file check after that as well.

http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html

Tutorial thanks to Brink

 

[otown]

Yesterday downloaded and ran Malware Bytes...it found a few problems and fixed them...but not my problem.

This morning I ran System File Check...it fixed a few problems and asked me to reboot which I did. The problem has gone away.....thanks very much.

I looked in the log and it says that Explorer.exe was corrupt and was replaced so I guess that was the problem.

There was also a lot of these in the log:
CSI 00000357 [SR] Verifying 100 (0x0000000000000064) components
2010-10-14 07:41:53, Info CSI 00000358 [SR] Beginning Verify and Repair transaction
2010-10-14 07:42:03, Info CSI 0000035a [SR] Verify complete
so what does this mean?

Also the log said that tcpmon.ini was corrupt and that it couldn't be fixed..should I do anything here?

thx...

 

[Ashvin Busviah]

you will need to replace the file by running chsk dsk /r from a windows cd

 

[otown]

you will need to replace the file by running chsk dsk /r from a windows cd

Do you mean "chsk dsk /r" or "sfc /scannow " from a Windows CD?

When I ran Check Disk, it first rebooted and ran before Windows started.

 

[Ashvin Busviah]

No, you need to put the windows cd, boot from cd. You need to select install windows, but you will not install windows then you will get the option, "run a repair" you need to run the repair from the prompt command, select the windows e.g c:/ then type in "chsk dsk /r" there is tutorial about that here, you can search it by typing "run a chsk dsk on vista" this process wil replace that corrupted file..

cheers
Ash

 

[otown]

Okay, I ran chkdsk from the Vista Recovery Disk and reran sfc /scannow. The only problem file seems to be tcpmon.ini. The system still seems to be okay.