02-27-2003, 04:39 PM -
Yuri,
I did as you said. I noticed that I had tlbdata files throughout my Documents and Settings (I think I fouled up when I first tried to set up TLB). Also, I deleted some programs I no longer use or whose functions were replaced with TLB and its plugins.
Finally, I searched the web for others who might have this 100% CPU problem with Explorer. It appears, by the discussions in a lot of different user groups, this problem does occur and one user said Microsoft is aware of it, but won't fix it until SP2. In the meantime, I tried all of the suggerstions mentioned to work around it, including updating my video drivers.
So far, there have been some problems since Feb. 19, but not as frequent as before.
I saved part of the System Information report for the past 3 days with info about some of the problems I've had. Does any of this help?
System Information report written at: 02/28/03 01:50:28
System Name: XXXX
[Windows Error Reporting]
Time Type Details
2/26/2003 7:23 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module weathermon.dll, version 1.2.0.0, fault address 0x00004454.
2/26/2003 4:06 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module tlb.dll, version 2.2.0.1, fault address 0x00027902.
2/25/2003 7:52 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module shlwapi.dll, version 6.0.2800.1106, fault address 0x00003092.
2/24/2003 10:15 PM Application Error Faulting application jv16 powertools.exe, version 1.2.0.180, faulting module kernel32.dll, version 5.1.2600.1106, fault address 0x00013887.
2/23/2003 7:47 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module ntdll.dll, version 5.1.2600.1106, fault address 0x00006763.
2/23/2003 1:39 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module unknown, version 0.0.0.0, fault address 0x0000001c.
2/23/2003 12:59 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module weathermon.dll, version 1.2.0.0, fault address 0x00001fd3.
I did as you said. I noticed that I had tlbdata files throughout my Documents and Settings (I think I fouled up when I first tried to set up TLB). Also, I deleted some programs I no longer use or whose functions were replaced with TLB and its plugins.
Finally, I searched the web for others who might have this 100% CPU problem with Explorer. It appears, by the discussions in a lot of different user groups, this problem does occur and one user said Microsoft is aware of it, but won't fix it until SP2. In the meantime, I tried all of the suggerstions mentioned to work around it, including updating my video drivers.
So far, there have been some problems since Feb. 19, but not as frequent as before.
I saved part of the System Information report for the past 3 days with info about some of the problems I've had. Does any of this help?
System Information report written at: 02/28/03 01:50:28
System Name: XXXX
[Windows Error Reporting]
Time Type Details
2/26/2003 7:23 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module weathermon.dll, version 1.2.0.0, fault address 0x00004454.
2/26/2003 4:06 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module tlb.dll, version 2.2.0.1, fault address 0x00027902.
2/25/2003 7:52 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module shlwapi.dll, version 6.0.2800.1106, fault address 0x00003092.
2/24/2003 10:15 PM Application Error Faulting application jv16 powertools.exe, version 1.2.0.180, faulting module kernel32.dll, version 5.1.2600.1106, fault address 0x00013887.
2/23/2003 7:47 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module ntdll.dll, version 5.1.2600.1106, fault address 0x00006763.
2/23/2003 1:39 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module unknown, version 0.0.0.0, fault address 0x0000001c.
2/23/2003 12:59 PM Application Error Faulting application explorer.exe, version 6.0.2800.1106, faulting module weathermon.dll, version 1.2.0.0, fault address 0x00001fd3.