Tech Support Forum banner
Status
Not open for further replies.
1 - 5 of 5 Posts

·
Registered
Joined
·
3 Posts
Discussion Starter · #1 · (Edited)
Windows Explorer sometimes needs >20s to show files, no other suspicious activities

Dear Experts,

I'm struggling with the following problem: After my XP SP3 runs for some hours it sometimes decides to drive me crazy out of a sudden. This means that opening a folder or opening a save dialog box takes ages. This weird behaviour does not stop until I log off and log on again. But that's obviously no solution. I have an up-to-date Sophos Antivirus and also scanned it with Symantec's Online Scan, Spybot Search & Destroy, Ad-Aware, Malwarebytes' Anti-Malware, and Kaspersky Online Scanner 7.0. Nothing found. Also the Hijackthis logfile is clean according to http://www.spywareinfoforum.com/index.php?showtopic=123947.

I now installed SpeedFan 4.38 and it reports 57 Celsisus core temperature for the CPU and 67 Celsisus core temperature for the GPU in idle mode. It's an Intel Core 2 Duo T7400 with 2.16GHz in an Dell Latitude D620. The graphics card is an NVIDIA GeForce Go 7300. Is this a normal temperature or is there something wrong? Or any other suggestions what I might want to check?

Thanks in advance,
Ptob
 

·
Moderator; Hardware
Joined
·
19,884 Posts
Re: Windows Explorer sometimes needs >20s to show files, no other suspicious activiti

You can open task manager to see if there is high cpu usage. If so, you can check the processes and see what is eating up the cpu cycles. You can also check Event Viewer to see if Windows is logging any errors. This could help locate any hardware issues such as RAM or HDD. I've seen apps such as Window Blinds cause this issue also.
 

·
TSF Team Emeritus , Microsoft Visitng Expert
Joined
·
4,279 Posts
Re: Windows Explorer sometimes needs >20s to show files, no other suspicious activiti

Hello T.Friedrich

These temperatures look OK to me.

Back up all your files and data and run chkdsk to check the hard drive.
Start/Run and type in
cmd
OK

When the command window opens, at the prompt type
chkdsk /r (there is a space before /)
Enter

Reboot for chkdsk to run.

Note
The /r switch tells chkdsk to try to repair any errors.
The process can complete relatively quickly or can take hours and hours depending on what is found. So be prepared just in case.

.
 

·
Registered
Joined
·
3 Posts
Discussion Starter · #4 · (Edited)
Re: Windows Explorer sometimes needs >20s to show files

Thanks for your quick responses. The CPU load is usually very low. There's no specific process eating up the CPU cycles. For the sake of completeness I still uninstalled Window Blinds, but since the problems just occurred recently months after I installed Window Blinds in the first place I don't think that it is causing the trouble.

I checked the Event Viewer. There no additional events at times when the Windows Explorer is so damn slow. But I also did a chkdsk /r and got the following log:

Checking file system on C:
The type of the file system is NTFS.
Volume label is WIN_SYS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 1900 unused index entries from index $SII of file 0x9.
Cleaning up 1900 unused index entries from index $SDH of file 0x9.
Cleaning up 1900 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x51388000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x5138e000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x5138f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x5138f000 for 0x1000 bytes.
Windows replaced bad clusters in file 2008
of name \DOCUME~1\ALLUSE~1\APPLIC~1\APPLEC~1\INSTAL~1\QUICKT~1.0\QUICKT~1.MSI.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 2 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

312560639 KB total disk space.
303714580 KB in 346556 files.
143284 KB in 33908 indexes.
8 KB in bad sectors.
521931 KB in use by the system.
22544 KB occupied by the log file.
8180836 KB available on disk.

4096 bytes in each allocation unit.
78140159 total allocation units on disk.
2045209 allocation units available on disk.

Internal Info:
60 d6 05 00 3b ce 05 00 32 03 09 00 00 00 00 00 `...;...2.......
11 49 00 00 02 00 00 00 bf 09 00 00 00 00 00 00 .I..............
bc 7e 9f 1b 00 00 00 00 0e dd 2f 8e 01 00 00 00 .~......../.....
a6 b0 17 4b 00 00 00 00 a6 04 59 1c 17 00 00 00 ...K......Y.....
a6 11 a4 e9 00 00 00 00 c0 ac e2 09 1a 00 00 00 ................
99 9e 36 00 00 00 00 00 98 38 07 00 bc 49 05 00 ..6......8...I..
00 00 00 00 00 50 44 69 48 00 00 00 74 84 00 00 .....PDiH...t...

Windows has finished checking your disk.

That apparently didn't change anything, but should I be worried about this log? The hard disk's S.M.A.R.T. attributes were never below any alarming threshold. What else could I check?

Thanks again,
Ptob
 
1 - 5 of 5 Posts
Status
Not open for further replies.
Top