Gigabyte Osmium woes

Permabanned
Joined
19 Oct 2007
Posts
6,322
Location
.
Further to my review on the OCUK store about this keyboard, it now appears to be slowly dying. About 25% of the time I boot my PC it doesn't work, I have to pull the cable out of the PC and plug it back in and reboot the PC otherwise I can only use my mouse.

About 50% of the rest of the time after a few hours use one of the keys will stick so this happens (see code below) until I do the same - unplug it and plug it back in and reboot. I can press the key and it will just add characters whilst the other character keeps scrolling. Mainly the W key or the spacebar.

Code:
wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww~

Anyone else have this issue? Won't be buying Gigabyte products ever again!
 
Possibly faulty yep, your first issue is similair to what im getting on my new ozone strike pro. Not detected on boot sometimes and random disconnects in windows and games. Tested on both usb2/3 ports in my rig in sig. Also tested in my second system where it lights up but no keys work at all. usb legacy suspend disabled and still the issues persist. Applied for and received an rma for it. Shame as when it works it's a great keyboard.
 
I had lots of multiple key-takes after a year or so using an Osmium. It got worse, so I looked on their forums and it is an issue a fair number of people have. Tried a "firmware upgrade to fix this issue" (no effect).

I tried to RMA it to them (under a 2 year warranty), and Gigabyte said "since it is a fault with the switch, you must contact the retailer", which I did and managed to get a full refund.

Won't be buying Gigabyte again either, not so much for the product fault but the shoddy RMA service.
 
Had a brown switch osmium since Christmas and no issues with it at all. Very happy with mine. Its mostly used for typing (I'm a programmer) rather than FPS gaming.

Do you have another keyboard to try? Its worth eliminating a MB fault as the cause.
 
Back
Top Bottom