Windows 7 has High CPU Usage and slow performance

Anonymous
2009-11-18T04:59:29+00:00

Hello all,

I've searched the forums, but was unable to find anything relevant.  I recently upgraded to Windows 7 from Vista.  It was running fine for about a week then all of a sudden everything started running very slow.  I checked the the processes tab in task manager and I am constantly running at 70-80% CPU usage.  I think this is very high considering the computer is only a few months old.  It seems like others are having this problem as well, but no real solutions.

I have turned off file indexing as well as disabled the HD audio device. 

Please help!

Here are my hardware specs:

AMD 9550 Quad-Core

64-bit

6GB Ram

Thank you in advance for your help.  I am ready to toss this thing from my second story window.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2010-01-02T19:29:42+00:00

I think the answer might be the Windows Media Player and Windows Media Network Sharing Services as zxypher suggested.  The fix for that is to adjust were the Windows Media Player services search for media files. 

It seems to be a bad problem for me as well upgrading from Vista to Windows 7.  The default search location for media is set to C:\Users\ instead of down in the My Music folders.

Go into Media Player.  From the menu -> File -> Manage libraries -> select each library (music, video, pictures, recorded tv [if you have]) and check the paths that it is managing and make sure it is not too close to the root of the C: drive.  For example, it should be something like c:\users\Jim\Music and c:\users\Public\Music BUT NOT **** c:\users as they will cause the whole directory tree to be re-indexed over and over (when you surf the web or change any files in your profile).

If you have multiple users who login to the computer, you may need to repeat the process for each user if all users have added managed folders which are actively changing on a regular basis.

If this is your issue and you do it correctly, then the high CPU should drop in minutes (or seconds down to nothing).

This is the CORRECT way to adjust the WMNSS/WMPNetwk.exe process issues.

A little more information can be found here:

http://social.answers.microsoft.com/Forums/en-US/w7performance/thread/2fe4901b-2eaf-4a99-b487-e6a6213b10b3/

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

253 additional answers

Sort by: Oldest
  1. Anonymous
    2010-07-15T11:40:56+00:00

    Registry cleaners are always bad! Can you contact the SMC Networks support?


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-07-16T09:06:47+00:00

    Kevin:

    I just bought my computer three weeks ago.  Straight out of the box, it was SLOW.  CPU usage was 100% FROM THE BEGINNING.  I have not added any programs.  So, to say try everything else, I think not.  The product is flawed.  I wish you would just go back to Windows 98 SE where everything worked.  For a product that is touted as being a "Plug-n-Play" application, I sure do have to learn a lot of stuff to use it.  If the specialized software I had ran on MAC, I would buy that instead.  Sorry, but I wouldn't recommend Windows.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-07-16T17:32:15+00:00

    Guess I was wrong about the registry cleaners!  I will contact SMC Networks support and post back again.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-07-22T03:23:38+00:00

    It was the page file in my case. I moved the page file to a different drive (not leaving any on the system drive, despite Windows' warning), so that it would be created there. I also ran chkdsk on my system drive and it made changes. I've rebooted a few times since and haven't had the problem again. Unfortunately, it took a kernel profiler to find this out! I wonder if they'll end up making a better way to discover these issues; or maybe a way to report them.

    Regardless, my issue is fixed now.

    Was this answer helpful?

    0 comments No comments