k70 rapidfire K70 causes hard crash/reset in games only - repeatable error

[raraku]

hey everybody,

 

I have what I think is an interesting issue - I've been using my K70 keyboard for over a year now without any issues to report. Recently I had to change my motherboard and reinstalled my PC.

 

For the first few days, everything was good, then suddenly I started getting these hard resets/crashes - no memorydump/no blue screen nothing - just a hard reset.

 

After a lot of troubleshooting, I eventually found the cause was my K70 keyboard and only while playing games (confirmed in MW and in Apex Legends)

 

Here's what I did to troubleshoot

 

- Reinstalled Windows 10 (3 times)

- Ran full Memory Check - all clear

- Ran CPU Stress test - all clear

- Ran GPU stress test - all clear

- Ran GPU and CPU stress test at the same time - all clear

- Ran HDD diagnostics (samsung magician on my SSD's) all clear

- Tried every different USB port, no change

- Unplugged everything except the KB - still crashes

- Upgraded firmware on keyboard

- Upgraded all BIOS/Firmware/Drivers/Windows updates

- Reinstalled windows and DIDN'T install any new drivers or windows updates

 

I cannot get more than 30-45 seconds into gameplay before my PC will hard reset - I can only assume the game is trying to talk to the keyboard or something to that effect and it causes my system to die. In windows it seems to be OK for the most part.

 

Has anybody encountered something like this? If so, how did you fix it? I love this keyboard but right now it's totally unusable for me.

 

I can also repeat this error and crash my PC at will - I've recorded a video if you're super keen, but for me this is something I've never encountered before. Any help would be appreciated

[c-attack]

Can you define 'hard reset' on your end? Full power off and click? Or forced restart with no Windows shutdown sequence?

 

There is nothing in the game that should be interacting with the keyboard beyond its normal function. There are a handful of games that have SDK lighting effects tied to specific in-game events, but Modern Warfare and Apex Legends are not among them. It is certainly possible those games have a tie in with another peripheral company, but I don't play either. Regardless, those are two highly popular games. If there was some type of intrinsic error with the KB physically or the CUE software, I would expect this thread to already be 10 pages long. I don't think it would go unnoticed.

 

Try removing CUE from the equation. Before launch, open the task manager and kill the CUE app. Might as well kill off Corsair.Service (32 bit) and Corsair.Service (CPUID) just to be thorough.

 

Can you get your system specs in here? Motherboard/CPU series would be the most relevant and if there is going to be some type of software conflict, it usually revolves around competing monitoring programs or competing RGB programs. *Maybe Windows version too since there is an active issue with the older defunct CUE programs.

Edited December 22, 2020 by c-attack

[raraku]

Can you define 'hard reset' on your end? Full power off and click? Or forced restart with no Windows shutdown sequence?

 

I've had two separate errors, but essentially they're the same. I've had the full power off and I have to turn off the PSU and unplug for 30 secs and it comes back (maybe 10% of the time) and the other 90% of the time its a forced restart, no shutdown sequence. Literally a black screen, then BIOS logo appears.

 

Try removing CUE from the equation. Before launch, open the task manager and kill the CUE app. Might as well kill off Corsair.Service (32 bit) and Corsair.Service (CPUID) just to be thorough.

 

Done that as part of my testing, forgot to add to the list. Originally I wasn't using the ICUE app at all - I installed it to upgrade the firmware and tried again, same issue - I get the reboots if its installed or not - current build has never had it installed, same error

 

Can you get your system specs in here? Motherboard/CPU series would be the most relevant and if there is going to be some type of software conflict, it usually revolves around competing monitoring programs or competing RGB programs. *Maybe Windows version too since there is an active issue with the older defunct CUE programs.

 

Sure - specs are below

 

Motherboard - Asus PRIME H370M-PLUS (previous MB was MSI MPG Z390M GAMING EDGE AC, it was faulty, its's currently getting replaced)

Processor - Intel Core i5-9400F

RAM - 2x 8GB Sticks of Corsair Vengeance 2133Mhz DDR

GPU - Asus GeForce GTX 1060

1x Samsung 1Tb SSD 860 Evo Storage Drive

1x Samsung 256GB Nvme SSD Boot/OS drive

 

I can get this error on a totally clean install, system drivers, no RGB utilities or anything

[c-attack]

It's still possible to have a hardware error with the KB and basic Windows drivers. However, I would expect it to non-responsive to a BSOD at worst. Full and immediate shutdown screams power problem, particularly if it goes into a full off state where you need to flip the PSU switch. These are really difficult problems to deal with because it could be the MB or the PSU and most troubleshooting guides start with: "replace the PSU with your alternative power supply to test." That's not a viable option for a lot of people. Playing the percentages, it is more often the PSU than a motherboard problem and since you are onto your back-up already that is something to consider as well.

[jasonorme666]

I had the same issue and ICue was the problem.

Also go into device manager, right click on your keyboard and other USB devices (included generic USB hub and USB root hub). and make sure "Allow compute to turn off this device to save power" is UNTICKED in power management.