Ok, here's the rundown. I have a desktop that I built 2 years ago. Everything was running perfectly until about a month ago. Without any software or hardware changes, the system developed a problem. Bear with me, it's honestly difficult to explain. The most obvious symptom is with the mouse. Sometimes, and seemingly at random, the mouse starts exhibiting weird behavior. It never freezes or stutters, but sometimes it's like the system refuses to acknowledge that the mouse is there. For example, I can sometimes move the cursor down to the start bar and nothing I do will have any effect. If I move the cursor over something, they don't do that highlight effect. If I click, nothing. If I right click or middle click, nothing. Meanwhile, my keyboard is functioning perfectly. So while the mouse gets no response from trying to click the start button, I can hit the windows key on the keyboard to make it pop up. If I try to click on an item from the start menu after using the keyboard to open it? It closes the start menu as if I clicked elsewhere. Sometimes when it happens, the window I was currently use starts showing this non-responsiveness. Sometimes the window I was using is the only window that will work. Alt+tabbing to another window gives me unresponsive windows on top. When I click on one of these windows that fails to give a response, the window usually loses focus but isn't covered by another window. Sometimes the system registers clicks that I didn't do. Sometimes it registers them as the wrong mouse button. I have been looking at the monitor without touching the mouse and seen the middle-click circle appear.
Now, this seems to mostly revolve around the mouse. I use a Logitech Wave K350 Keyboard and Performance MX Mouse with the Unifying receiver. I connected a regular USB mouse. When I noticed the problem happening while using the wireless mouse, I grabbed the wired mouse and checked to see if the problem disappeared. It didn't. When the system became unresponsive, it was unresponsive to both mice at the same time. I do think the problem occurs less often when I use the wired mouse exclusively, but I'm not sure what that indicates.
I have 3 disk drives. There's a 256GB Crucial C300 SSD as my primary drive. There's a WD2001FASS Western Digital 1.5TB HDD. There's a 500GB knock-off brand laptop drive thrown in there from when my previous laptop died. When I suspected that maybe there was an issue with my windows installation, I decided to try a new installation. I installed windows on the WD drive. After booting into that installation, none of these problems appeared again. Everything ran perfectly, albeit much slower due to not being a SSD. Seeing this as a victory sign, I proceeded to remove the original windows installation on the SSD and install a fresh copy. As soon as I booted into the fresh win7 session, the problems manifested in full force. Everything described above started happening again. I can boot into the copy on the HDD and it runs flawlessly. I can boot into the copy on the SSD and it's deathly painful to use.
I'm stumped. I've been using this SSD with this mouse on the same Win7 installation for over 2 years, and then the problem pops up out of nowhere. Switching to an installation on another drive removes the problem, but it's an unacceptable "solution". Using a wired mouse exclusively might help, but it's also not an acceptable "solution", as my monitor is a 50" plasma tv and my "desk" alternates between the coffee table in front of the couch and the tv stand if I want to sit insanely close for maximum immersion in a game. If the mouse itself was broken, then the problem wouldn't disapear when I switched to the HDD's win7 install. If it was software related, it would've had to be triggered by the installation/update of something, but there was no such update/change. WIthout any driver install/update, the mouse and keyboard work with a fresh copy of win7 out of the box. Installing the Logitech Setpoint and Unifying Driver/Software doesn't fix it. Uninstalling them doesn't, either. Removing the mouse and the software from the equation, that seems to point at the drive itself. Can a problem with the SSD somehow cause these problems? I don't claim to know everything about computers, but that just doesn't sound possible to me. Right now I'm thinking about backing up the SSD, then formating it completely before doing yet another install. I want to avoid that if possible, as it's an awful thing to do to an SSD, but... Whatever it takes, right?
Sorry for writing this book, and thanks for reading it. TL;DR - Nope, there's no way to shorten this.