Windows 7: Background program using 100% CPU. PC slow at startup.

Did a chkdsk and defrag but still PC randomly ruins at 100% and cannot find background pgm causing it. It is not listed in msconfig. Any suggestion greatly appreciated

Welcome to Seven Forums!

What shows in Task Manager? Might be AV at boot, what AV do you run?

Start in safe mode and see if you have the same problem. Also, as suggested, check that your AV isnt doing a scan when booting - ESET Nod32 is a bugger for doing this.


Dave

Download Process Explorer to see which program is hogging the system's resources
Process Explorer

I think it had something to do with power settings. Even a safe mode boot was very slow. So I got another drive and tried to install 7 but again everything slow. Reseated memory and ran diagnostics. Will just keep an eye on it.

You asked for help, several of us made suggestions & yet you did your own thing... WHY???

Where did you get your copy of Windows 7???

If you truly want help with this issue, help us help you by answering our questions and following our suggestions!

I'm sorry if I didn't solve it exactly as you suggested but as I was in the process of going through msconfig and stopping all services I found that this did not solve my slow response so I did some more investigating and found that it was not related to Win 7 but to the laptop itself as it took a long time for windows to just come up. From my knowledge of XP and the like I reasoned that my issue was independent of Win 7 so I looked at other ways my PC could be running slow. I put another HD in and started to reload Win 7 and I noticed it took a very long time for the files to load so I started reseating the memory and so far it seems to have fixed my problem.

Download and run memtest: Memtest86+ - Advanced Memory Diagnostic Tool

This will test your RAM.

Dave

Thanks Dave... I will...

It wasnt that you didnt solve per our suggestions, it was that we've been asking you for more info to help you and you didnt give it.

Also, couldnt determine from your earlier post that simply reseating RAM fixed it, rather your previous post suggests the issue was related to power settings not RAM!

Very strange indeed!