I have something of a problem that is having a definite impact on Wedge...
As a reminder: I have Windows 7 Ultimate on a brand new PC, Core i7 (4 cores + hyper-threading so that's 8), 8GB Ram, SSD HD, and so on.
When a core is running 100% CPU time, that's 100/8 = 12.66% = 13% in my task manager. So when a program is running a thread at 100%, there's a 13% for it in the task manager. Meaning there are still 7 cores available and under-used. All right?
Enter a recent issue. Well, about a few weeks ago I think...
When I boot my PC and use it, for the first day it'll be okay.
Then after some time, it'll develop a problem. On SOME actions, not ALL of them, the current program will suddenly jump to 13%, for a few seconds. It's not that important, but what matters to me is that it *effectively* slows down the entire computer, most notably the mouse cursor gets jerky, sometimes VERY jerky (i.e. it's only updated a few times every second.)
This happens systematically in these cases for instance:
- clicking the Start button (well, what replaced it...) -- not severe, though. But I see it's jerky for half a second.
- launching a program (whether it's stored on my SSD or regular HD...)
- launching my diff tool from within TortoiseSVN (which is pretty much needed for writing my changelog...) will take about 2 to 4 seconds with a jerky mouse, while when I first launch my PC, it takes much less than a second.
- sometimes -- just opening a *window* from inside a program (like the Settings window) will be jerky (like in my diff tool) or not (like in Opera). It's not related to Aero (I tried disabling it). The jerkiness appears during the time between my menu mouse click and the moment the window animation starts (i.e. the animation itself is very smooth and the mouse is only jerky before that).
All in all, with these, it feels a bit like my computer is slower than my old PC (XP + 2GB ram)...
Last time I rebooted, my problems were fixed but they started again the following day. I tried hibernating (= saving memory state and rebooting), and the problems were still there, so I'd like to suspect it's not a hardware problem, but...? What could it be! Everytime I search about this online, I find people saying to "upgrade video card drivers" (first thing I did of course...), or similar. Like, "upgrade your mouse drivers", lol. That one's funny.
I figured maybe someone around here already had a similar problem and they managed to fix it...? It's really making my changelogging life a hell right now!