Having a similar lock-up issue with the following specs:
Win 10 64bit
Corsair Vengeance K95 RGB Gaming Keyboard
Logitech G13 Gameboard
Razer Naga Gaming Mouse
Some Specifics:
1. Software worked without issue after install. After closing and attempting to reopen I experienced the lock up. Had to force quit program via Task Manager. Restarted Computer and program worked again. Close program, reopen, locked up again.
2. Read some of the posts in this thread and started unplugging things to see what would happen. Long story short, keyboard seems to be causing a conflict but ONLY AFTER USING ESCRIBE'S DEVICE MONITOR. I can launch, close and relaunch the program all day long without issue but the first time I open the device manager I start having some kind of conflict with the keyboard. This conflict will resolve if I restart my computer OR if I use Task Manager to force close the Device Monitor window as shown in the screenshot below.
(EDIT: I'm an idiot and kept referring to the Device Monitor as "Device Manager". Fixed that)
Escribe Software ISSUE
in EScribe, Software and Firmware
Posted
Having a similar lock-up issue with the following specs:
Win 10 64bit
Corsair Vengeance K95 RGB Gaming Keyboard
Logitech G13 Gameboard
Razer Naga Gaming Mouse
Some Specifics:
1. Software worked without issue after install. After closing and attempting to reopen I experienced the lock up. Had to force quit program via Task Manager. Restarted Computer and program worked again. Close program, reopen, locked up again.
2. Read some of the posts in this thread and started unplugging things to see what would happen. Long story short, keyboard seems to be causing a conflict but ONLY AFTER USING ESCRIBE'S DEVICE MONITOR. I can launch, close and relaunch the program all day long without issue but the first time I open the device manager I start having some kind of conflict with the keyboard. This conflict will resolve if I restart my computer OR if I use Task Manager to force close the Device Monitor window as shown in the screenshot below.
(EDIT: I'm an idiot and kept referring to the Device Monitor as "Device Manager". Fixed that)