Hi, so recently my mouse, keyboard, and headset have been disconnecting. It started with my mouse which is a g400s disconnecting periodically in game. Now if I play about 10 minutes of TF2 all of the USB devices decide to stop working and I have to restart my computer to fix it. My friends are telling me that my motherboard is dying, but I can do other things outside of TF2 without any issues or disconnecting noises. I was wondering if anyone has had issues with this or has any suggestions on fixing this problem.
For reference:
Motherboard: gigabyte z77x-ud3h
Windows 7
i5 3570
g400s mouse
g35 headset
Quickfire Rapid Mechanical Keyboard
Also, when restarting my computer the headset isn't recognized unless I replug it in. Thanks for any help.
For reference:
Motherboard: gigabyte z77x-ud3h
Windows 7
i5 3570
g400s mouse
g35 headset
Quickfire Rapid Mechanical Keyboard
Also, when restarting my computer the headset isn't recognized unless I replug it in. Thanks for any help.
Try this fix
Have you been using all the same peripherals for a while or is there a new addition in there? Also, have you recently updated drivers or firmware for any of those peripherals?
thrasherHave you been using all the same peripherals for a while or is there a new addition in there? Also, have you recently updated drivers or firmware for any of those peripherals?
The mouse is the newest, but I've had it for over two months now, I didn't update any drivers.
Try that procedure I posted. Follow the instructions carefully. Let me know if it helps
crespiTry that procedure I posted. Follow the instructions carefully. Let me know if it helps
I'm not exactly sure which ones I need to uninstall.
I'm not exactly sure which ones I need to uninstall.
Anything in mouse and pointer, keyboards, USB and hid sections that is greyed out
There will probably be a shit ton. That's normal since this is the first time you've done this. It may seem tedious but it's worth it.
crespiAnything in mouse and pointer, keyboards, USB and hid sections that is greyed out
There is so many lol.
There is so many lol.
Hmm. That's weird. Your mobo COULD be failing... It may be a power issue too. You may want to rule that out first (always try the easy fix first).
Unplug any USB shit you don't need for now (printer, external drives, even the headset) try playing with basically just ur KB and mouse plugged in and see if the problem still persists.
Unplug any USB shit you don't need for now (printer, external drives, even the headset) try playing with basically just ur KB and mouse plugged in and see if the problem still persists.
Well I don't want to jinx it but it seems as though crespi's fix somehow helped...I don't understand why but it did.
If I were you I would uninstall all of the current drivers you have for your USB accessories and then re-install them from their manufacturers sites. There you can get the most up-to-date ones. In case one of the drivers is messing up, you would never know until you re-install them one by one. If that doesn't do anything I would recommend what "crespi" had said.
Here's something I pulled off a quick google search. It's a pretty comprehensive explanation but it more or less explains the problem.
Several things can contribute to the addition of ghost devices in the Windows Device Manager. Some of these include adding or removing hardware, changes to tape drives or tape libraries, failure to use persistent binding, static indexing or hard ALPAs on storage area network (SAN) equipment. These sort of things allow changes to the SCSI device path presentation of a device to the operating system. These "ghost" devices can retain Port, SCSI, Target, and logical unit number (LUN) information that conflict with the active devices being used by Windows. Under these circumstances, hardware instability can result.
Glad it seemed to help so far. Hope it fixes it 100% You should reboot your computer now though, just for good measure.
Also, it seems that someone was +fragging my posts and -fragging yours. I think someone is trying to make me look like an asshole.
[quote]Several things can contribute to the addition of ghost devices in the Windows Device Manager. Some of these include adding or removing hardware, changes to tape drives or tape libraries, failure to use persistent binding, static indexing or hard ALPAs on storage area network (SAN) equipment. These sort of things allow changes to the SCSI device path presentation of a device to the operating system. [b] These "ghost" devices can retain Port, SCSI, Target, and logical unit number (LUN) information that conflict with the active devices being used by Windows. Under these circumstances, hardware instability can result.[/b][/quote]
Glad it seemed to help so far. Hope it fixes it 100% You should reboot your computer now though, just for good measure.
Also, it seems that someone was +fragging my posts and -fragging yours. I think someone is trying to make me look like an asshole.
crespiHere's something I pulled off a quick google search. It's a pretty comprehensive explanation but it more or less explains the problem.
Several things can contribute to the addition of ghost devices in the Windows Device Manager. Some of these include adding or removing hardware, changes to tape drives or tape libraries, failure to use persistent binding, static indexing or hard ALPAs on storage area network (SAN) equipment. These sort of things allow changes to the SCSI device path presentation of a device to the operating system. These "ghost" devices can retain Port, SCSI, Target, and logical unit number (LUN) information that conflict with the active devices being used by Windows. Under these circumstances, hardware instability can result.
Glad it seemed to help so far. Hope it fixes it 100% You should reboot your computer now though, just for good measure.
Also, it seems that someone was +fragging my posts and -fragging yours. I think someone is trying to make me look like an asshole.
I plus fragged you actually.
[quote]Several things can contribute to the addition of ghost devices in the Windows Device Manager. Some of these include adding or removing hardware, changes to tape drives or tape libraries, failure to use persistent binding, static indexing or hard ALPAs on storage area network (SAN) equipment. These sort of things allow changes to the SCSI device path presentation of a device to the operating system. [b] These "ghost" devices can retain Port, SCSI, Target, and logical unit number (LUN) information that conflict with the active devices being used by Windows. Under these circumstances, hardware instability can result.[/b][/quote]
Glad it seemed to help so far. Hope it fixes it 100% You should reboot your computer now though, just for good measure.
Also, it seems that someone was +fragging my posts and -fragging yours. I think someone is trying to make me look like an asshole.[/quote]
I plus fragged you actually.
Welp, it didn't fix it, it only delayed the inevitable. Everything froze again, maybe my mobo is dying sigh.
Well poop, that's unfortunate. Good luck man.
edit: just thought of something. This isn't really a fix, maybe more of a test. Try tuning your g400s' polling rate down to 500 or 250. I assume you have it at 1000. See if having it lower allows you to play longer before it disconnects.
edit: just thought of something. This isn't really a fix, maybe more of a test. Try tuning your g400s' polling rate down to 500 or 250. I assume you have it at 1000. See if having it lower allows you to play longer before it disconnects.
As above if your mouse is at 1000hz polling change it to 500hz. Try switching your keyboard from USB to ps/2...the ps/2 port is actually better for keyboards and supports N-key rollover. I had some freezing issues while playing with my system a long while back (would get hitching and other issues) that really seemed to clear up once I moved my KB over to the ps/2 port from USB. It was almost as if the USB was oversaturated (I have an old ass system) and it was creating conflicts. Btw I also have a quickfire rapid...use the ps/2 port, it's better and who knows maybe it could help.