Sluggish comp: Constant disk activity LIGHT but no I/O in ResMon

enjo

Honorable
Jun 25, 2013
2
0
10,510
I am out of ideas on how to determine the cause of my constantly glowing disk activity light and extremely sluggish computer and hope you can offer suggestions as to what to do next short of re-installing Windows.

The problem disappears when I safe boot (any/all flavors). The problem remains when I clean boot. I've even force-terminated services/processes that survive the clean boot.

I ran sfc and chkdks and neither found any errors. Resmon shows virtually no disk, cpu, and memory activity after the machine settles down from boot-up. Zero page faults. I've run various virus and malware scans in hopes of finding a self-hiding process or root kit but nothing has been detected.

Configuration: Win 7 Home Premium 64 bit on Acer 5750 with i7-2630QM and 8GB memory

Perhaps there is a crazy driver that is gets skipped or substituted when booting in safe mode? How might I determine what is different between the safe boot and clean boot environments besides the video drivers?

I'm really at my wits-end and would appreciate any ideas you might have on how to proceed. Many thanks!
 
You can do a SFC /SCANNOW with administrator privilege. It is for file system error.

Than you can run a CHKDSK C: /f/r from CMD as administrator.

The last resort will be a format and clean install of windows. I think this is your best bet.

In safe mode only the necessary drives will load to run the basic functions of OS. In normal mode all the drivers will load (necessary/unnecessary) to function.
 

enjo

Honorable
Jun 25, 2013
2
0
10,510
Thank you for your reply. There is a big difference between a clean boot and a normal boot. The problem I face is that msconfig does not provide sufficient options to isolate whatever is causing the disk activity light. I'm asking the community for information and assistance.

Obviously, the last resort is to reinstall windows. Perhaps there are other utilities. Perhaps this has happened to others and they got lucky and found the cause. Perhaps this has happened to others and they finally had to reinstall windows. Perhaps the problem remained even after their reinstall. It would be helpful to learn of the experiences of others.

I should have mentioned that I already ran SFC and chkdsk. I will edit my original post.