G-Series Gaming Keyboards

[LoonyDoll]

I didn't see this issue in any threads.

I'm on my second G-19 keyboard, and have never had software problems with it. My first one failed a little after the warranty due to the spacebar failing. 

So now, I'm finally having problems with it software-wise. It was working fine until the start of March - I was playing SW:TOR and enjoying the G-keys - and then I noticed (because I don't use G-keys outside MMOs, very often) the backlighting was set to white, and the display was stuck on the Logitech logo, and that you couldn't toggle the backlight. Volume controls, and basic keyboard functionality was fine.  I emphasize that I've never had this problem before.

Skipping along, it turned out that simply unplugging the AC adapter to cycle the power to the keyboard fixed the "lock" - I could now toggle the backlighting on and off, and Windows now recognized the device/drivers. So I thought hey, maybe the LGS will pick up the keyboard now..

However, installing 8.20 sends my PC into a spiral of BSODs. As soon as LCore.exe loads, BSOD. I've never had a BSOD on my PC before. I know 8.2 is a hunk of **bleep** birthed from the deepest, darkest bowels of Logitech's supposed faltering software team, or so I'm getting the impression of - so I used legacy version 3.0 and 8.0. 3.0 allows full functionality to the G-19 keyboard, but if the LCore.exe is canceled (you try to uninstall it, or just stop process) BSOD.

With 8.0 and 8.20, I get a BSOD if LCore.exe starts while the keyboard is plugged in. While 3.0 doesn't crash my entire system when LCore.exe begins, it does when it ends, and I'm not comfortable with that kind of thing looming over my system.

My USB 2.0's no longer seem to recognize the keyboard, and occasionally plugging it into my USB3.0 ports (which, it would share with an external HD) seems to have to do with the HDD "flickering" and having to reinitalize. They're currently both in my USB 3.0 ports as I type this, without LGS installed, and the only problem is that I can't install the software outside of a legacy version.

For the record:

P67 Extreme4 Gen3  (the only BIOS update addresses a mouse issue, so no)

Intel-2600k

Nvidia 460GTX

Windows 7 HP x64

In summary:

-LCore.exe loading while the keyboard is plugged in causes BSODs.

-Legacy 3.0 version crashes system when a component (the display, LCore.exe, etc) is terminated. 

-I can't update my BIOS anymore unless "XAI mouse" means anything. 

-It was working with the newer LGSes until March.

I'd appreciate some ideas on dealing with this. If I seem bitter, I apologize - two pairs of G-35's and a pair of G930's later and now this, my blind support towards Logitech is not what it used to be, and I've exhausted a week figuring this keyboard's problem out. I don't want to bin another expensive Logitech toy, but this is something I can't figure out.

[LeVvE]

Did you try wiping the complete software, restart, then install again?

I think Driversweeper works but not sure.

Another way to solving if would be to reinstall windows, but thats a last resort thing.

[LoonyDoll]

I've purged everything surgically, and wiped my registry with CCleaner and made sure the Logitech entry was deleted as a several posts on similar issues involving the software suggest, but it still happens. 

Reinstalling Windows wouldn't be a problem, if it were the problem, but I was hoping for an actual idea of what was going on, rather than blaming Windows.

[Cintech]

Hello LoonyDoll,

Did you add a pen tablet and the software in March as this is a possible conflict another user reported? Do you see any  information in BSOD or error log referring to any other software or hardware? Do you have UAC turned off? Have you had the opportunity to try your G19 on a different computer so we can determine if you are experiencing a hardware issue?

Best Regards,

[LoonyDoll · Accepted solution]

I purchased an Intuos4 in January and usually used it through the keyboard's USB, but do not keep it plugged in. It worked quite fine from what I recall. I can't remember if it  stopped the software from functioning properly, only that the two "seemed" to not conflict.

the BSOD is short - I'll quickly google the solution to getting it to stay on and see what I can do in regards to Wacom software. 

UAC is set to never notify.

I don't have another PC on hand to try, but I'm sure it's something on my PC's end anyway, like the issues similar for the keyboard. 

I'll run some extra tests now, that I didn't think of, and get back to update. Thank you for the reply.

---

Christ. Okay, I feel nauseated. 

For the record this was the first time I condemned a product for a problem that was not necessarily its own - so don't think too badly for it, please. The problems others reported were 'quite' similar to what I experienced .. but my research was, for once, quite lazy and half-hearted, and assumptive.

I'm not sure if I mentioned this prior, but sometimes when unplugging my external HD the keyboard would also stop recieving power, as if I unplugged it as well. I tried to reinstall my AsRock drivers, and noticed my USB drivers (Eltron 3.0) weren't installing successfully. A quick google search thanks to on-screen keyboard reveals someone had a USB problem where they "Weren't working" and down the thread someone suggests making sure Windows isn't "allowed to turn the power off to the usb [port/hub] to save power"

Sure enough, unchecking them, and reinstalling the drivers, everything works. Plug in G-19, instant cooperation (to a 2.0 again, no less!). Plug in HD, instant registration. LGS 8.00? No blue screen. Everything working? Absolutely.

I apologize for the accusation and bad taste in words towards the product/software, and again, thank you for the assistance. 

I've not seen the suggestion to some who have issues with G-series keyboards registering to make sure Windows isn't regulating USB port/hub on/off to conserve power, but then again it might be better to tuck my tail between my legs and assume it was across several threads and, once again, the half-heartedness striked!

[dilburt]

I have the same problem on my system.  I'm running the G15 gaming keyboard and the Intuos 5 tablet but the symtoms are identical.  It appears that the conflict has something to do with the Visual C++ redistributable libraries.  Logitech Gaming Software version 8.2x (aka.  LCORE.EXE) has some sort of general problem loading the VC++ redistributables since it won't load them correctly unless it has full admin control which should not be required.

Whatever is the cause, the Logitech Gaming Software 8.2x and the Intuos tablets will not run at the same time.  If anyone has found a solution to this please post the details here.

[CharlesB]

We don't have a fix right now, but I can confirm that QA is indeed aware of this. If we can resolve it on our side, it's too late to make it into LGS 8.30, but we will be taking an honest gander at this and see what we can do.