Razer Tartarus V2 controller D-pad sticking / glitch
Userlevel 1
so while using the Tartarus V2, the d pad sticks and you keep moving in one direction till u press the same direction again. I know a lot of people have this problem while looking through the forums and the one solution is to delete razer synaps. but unfortunately I use a lot of razer products and that's the best way to match and customize RGB. so its either I deal with that annoying glitch and have cool colors and effects. or i delete synaps and don't deal with that glitch but now half my RGB features are useless. I was hoping to bring this back to the attention of the developers to see if u can make a small patch for synaps so the people who use the Tartarus can enjoy there gaming and RGB lights at the same time. Please and thank you.
This topic has been closed for comments
Page 5 / 20
Userlevel 2
Daisame
Thanks for posting all your info. If there is some issue with the way Tarturus interfaces with the motherboard, then it ONLY seems to happen when Synapse is running. The easiest work around to the issue is to uninstall Synapse, and the problem goes away. So if there is some mismatch between the hardware and software, it is aggrivated by Synapse. People can use thrid party software to remap keys, make macros, and the problem also does not present. It is ONLY with Synapse that people seem to have the issue (at least from reading threads here).
I tried to get an update after a month from Razer on this issue. They acted like they never talked to me before, startinig their tech support script from scratch again. It is extremely frustrating but leads me to believe that they are not taking this issue seriously. Frankly, I don't think they are even working on trying to fix the issue any longer. Until this hurts their business, they probably won't fix it.
I tend to agree with you on this.
After several conversations of copy/paste messages they all end in the same way, RMA or go away (paraphrasing of course)
Katyblossym
I didn't necessarily mean BIOS related, but motherboard related; how Synapse is talking to the hardware (motherboard). I only mentioned BIOS because its how I discovered my Tartarus was working last night. HOWEVER, I think I jinked myself because playing tonight I had more issues than I have in two weeks.
What I don't understand (at least on my machine) is how it can work perfectly one night and then be buggy as hell the next. Either way, I think we all agree that SOMETHING in Synapse needs to be fixed, but it probably won't happen until Synapse 4... or 5.. or 6...
Thanks for posting all your info. If there is some issue with the way Tarturus interfaces with the motherboard, then it ONLY seems to happen when Synapse is running. The easiest work around to the issue is to uninstall Synapse, and the problem goes away. So if there is some mismatch between the hardware and software, it is aggrivated by Synapse. People can use thrid party software to remap keys, make macros, and the problem also does not present. It is ONLY with Synapse that people seem to have the issue (at least from reading threads here).
I tried to get an update after a month from Razer on this issue. They acted like they never talked to me before, startinig their tech support script from scratch again. It is extremely frustrating but leads me to believe that they are not taking this issue seriously. Frankly, I don't think they are even working on trying to fix the issue any longer. Until this hurts their business, they probably won't fix it.
waaaghmachine
while this may lead to a solution, I don’t know if I subscribe to it being bios related since I can close Synapse and NEVER have a “sticky” key. I would get these issues maybe 4-6 an hour with Synapse running, and I went days without a single issue so long as Synapse wasn’t running.
I didn't necessarily mean BIOS related, but motherboard related; how Synapse is talking to the hardware (motherboard). I only mentioned BIOS because its how I discovered my Tartarus was working last night. HOWEVER, I think I jinked myself because playing tonight I had more issues than I have in two weeks.
What I don't understand (at least on my machine) is how it can work perfectly one night and then be buggy as hell the next. Either way, I think we all agree that SOMETHING in Synapse needs to be fixed, but it probably won't happen until Synapse 4... or 5.. or 6...
Katyblossym
Hey all, thought I may share something I experienced with the rest of you, maybe something to pick our brains on.
TLDR: After having to update my bios/chipset/virtual memory paging file settings due to a blue screen that has literally plagued me for years if I tried to update from my factory BIOS (but was forced to in order to make my new CPU work), I had no sticky dpad issues with my Tartarus v2 during 2 hours of play time. I am not sure what the particular "fix" was (if it remains working correctly), but I have an idea that it may have been the way my motherboard USB ports were communicating with my Razer devices, possibly with Synapse/drivers as a middleman but I am not sure. Synapse DID run an update after I did all my BIOS updates/fixes that I describe below in detail, but I also had a bunch of devices update drivers including my built in Realtek Audio on my motherboard.
Full Story (stick with me here): I have a Gygabyte Aorus AX370 Gaming K-5 (rev.1) motherboard that previously had a 1st gen Ryzen 1600x installed. Any time I would try to update my BIOS, I would pretty quickly get a PAGE_FAULT_IN_NONPAGED_AREA blue screen, which is one of the most unhelpful blue screens one can get. Any time I attempted to update the BIOS whenever I got brave, I would end up having to revert back to factory BIOS.
Because of WIN 11 (which I am running the DEV build of now), I had to upgrade my CPU, so I ordered a 3rd gen Ryzen 7 3700x. Although my motherboard supports 3rd gen AMD CPUs, it wasn't until it wouldn't post after the CPU install that I realized dreadfully that my BIOS had to be updated to a much later version to support 3000 series Ryzen CPUs.
After reinstalling my old CPU and installing specific BIOS updates, then required chipset drivers/etc for those specific BIOS versions in a specific order (quickly I must add to beat the dreaded blue screen), I continued to get the same blue screen. Eventually I went into my System Properties/Advanced/Performance Options/Virtual Memory and changed my paging file size from Custom Size to System Managed for both of my hard drives (the checkbox for automatically managed paging file size for all drives had previously been unchecked from things I had done in the past).
Once I did all this, I received no further blue screens. I decided to stress test my system instead of letting it just sit on the desktop by playing Destiny 2, and of course I used my Tartarus V2. Typically before when I would play, I would get the occasional sticky dpad that we have all been experiencing. Surprisingly, in my 2 hour playthrough last night, I had no issues with my Tartarus v2 at all, it worked perfectly (I did notice some slight popping noises in my Kraken Tournament headset, but I think that has more to do with the Win 11 Dev build I am on and not Synapse itself).
Note: All of my Razer devices remained in the same USB ports as they were before I did all the upgrades to my CPU/BIOS.
I ordered a Tartarus Pro and I am expecting it to come in tomorrow. I still have some USB ports available, so I am going to test it when it comes in, creating a "duplicate" profile that matches how I have my Tartarus v2 set up. Since the Tartarus Pro has the analog features that others in this forum have had the same issues with, I am curious to see if I see any of those issues as my Huntsman Elite is the non-analog version.
I will update after further testing and playing, hopefully SOMETHING that occurred during all my motherboard troubleshooting and fixing last night regarding my BIOS/CPU upgrades inadvertently fixed the issues I had with my Tartarus v2.
@Razer.Speedcr0ss I hope you see this.
while this may lead to a solution, I don’t know if I subscribe to it being bios related since I can close Synapse and NEVER have a “sticky” key. I would get these issues maybe 4-6 an hour with Synapse running, and I went days without a single issue so long as Synapse wasn’t running.
Hey all, thought I may share something I experienced with the rest of you, maybe something to pick our brains on.
TLDR: After having to update my bios/chipset/virtual memory paging file settings due to a blue screen that has literally plagued me for years if I tried to update from my factory BIOS (but was forced to in order to make my new CPU work), I had no sticky dpad issues with my Tartarus v2 during 2 hours of play time. I am not sure what the particular "fix" was (if it remains working correctly), but I have an idea that it may have been the way my motherboard USB ports were communicating with my Razer devices, possibly with Synapse/drivers as a middleman but I am not sure. Synapse DID run an update after I did all my BIOS updates/fixes that I describe below in detail, but I also had a bunch of devices update drivers including my built in Realtek Audio on my motherboard.
Full Story (stick with me here): I have a Gygabyte Aorus AX370 Gaming K-5 (rev.1) motherboard that previously had a 1st gen Ryzen 1600x installed. Any time I would try to update my BIOS, I would pretty quickly get a PAGE_FAULT_IN_NONPAGED_AREA blue screen, which is one of the most unhelpful blue screens one can get. Any time I attempted to update the BIOS whenever I got brave, I would end up having to revert back to factory BIOS.
Because of WIN 11 (which I am running the DEV build of now), I had to upgrade my CPU, so I ordered a 3rd gen Ryzen 7 3700x. Although my motherboard supports 3rd gen AMD CPUs, it wasn't until it wouldn't post after the CPU install that I realized dreadfully that my BIOS had to be updated to a much later version to support 3000 series Ryzen CPUs.
After reinstalling my old CPU and installing specific BIOS updates, then required chipset drivers/etc for those specific BIOS versions in a specific order (quickly I must add to beat the dreaded blue screen), I continued to get the same blue screen. Eventually I went into my System Properties/Advanced/Performance Options/Virtual Memory and changed my paging file size from Custom Size to System Managed for both of my hard drives (the checkbox for automatically managed paging file size for all drives had previously been unchecked from things I had done in the past).
Once I did all this, I received no further blue screens. I decided to stress test my system instead of letting it just sit on the desktop by playing Destiny 2, and of course I used my Tartarus V2. Typically before when I would play, I would get the occasional sticky dpad that we have all been experiencing. Surprisingly, in my 2 hour playthrough last night, I had no issues with my Tartarus v2 at all, it worked perfectly (I did notice some slight popping noises in my Kraken Tournament headset, but I think that has more to do with the Win 11 Dev build I am on and not Synapse itself).
Note: All of my Razer devices remained in the same USB ports as they were before I did all the upgrades to my CPU/BIOS.
I ordered a Tartarus Pro and I am expecting it to come in tomorrow. I still have some USB ports available, so I am going to test it when it comes in, creating a "duplicate" profile that matches how I have my Tartarus v2 set up. Since the Tartarus Pro has the analog features that others in this forum have had the same issues with, I am curious to see if I see any of those issues as my Huntsman Elite is the non-analog version.
I will update after further testing and playing, hopefully SOMETHING that occurred during all my motherboard troubleshooting and fixing last night regarding my BIOS/CPU upgrades inadvertently fixed the issues I had with my Tartarus v2.
@Razer.Speedcr0ss I hope you see this.
TLDR: After having to update my bios/chipset/virtual memory paging file settings due to a blue screen that has literally plagued me for years if I tried to update from my factory BIOS (but was forced to in order to make my new CPU work), I had no sticky dpad issues with my Tartarus v2 during 2 hours of play time. I am not sure what the particular "fix" was (if it remains working correctly), but I have an idea that it may have been the way my motherboard USB ports were communicating with my Razer devices, possibly with Synapse/drivers as a middleman but I am not sure. Synapse DID run an update after I did all my BIOS updates/fixes that I describe below in detail, but I also had a bunch of devices update drivers including my built in Realtek Audio on my motherboard.
Full Story (stick with me here): I have a Gygabyte Aorus AX370 Gaming K-5 (rev.1) motherboard that previously had a 1st gen Ryzen 1600x installed. Any time I would try to update my BIOS, I would pretty quickly get a PAGE_FAULT_IN_NONPAGED_AREA blue screen, which is one of the most unhelpful blue screens one can get. Any time I attempted to update the BIOS whenever I got brave, I would end up having to revert back to factory BIOS.
Because of WIN 11 (which I am running the DEV build of now), I had to upgrade my CPU, so I ordered a 3rd gen Ryzen 7 3700x. Although my motherboard supports 3rd gen AMD CPUs, it wasn't until it wouldn't post after the CPU install that I realized dreadfully that my BIOS had to be updated to a much later version to support 3000 series Ryzen CPUs.
After reinstalling my old CPU and installing specific BIOS updates, then required chipset drivers/etc for those specific BIOS versions in a specific order (quickly I must add to beat the dreaded blue screen), I continued to get the same blue screen. Eventually I went into my System Properties/Advanced/Performance Options/Virtual Memory and changed my paging file size from Custom Size to System Managed for both of my hard drives (the checkbox for automatically managed paging file size for all drives had previously been unchecked from things I had done in the past).
Once I did all this, I received no further blue screens. I decided to stress test my system instead of letting it just sit on the desktop by playing Destiny 2, and of course I used my Tartarus V2. Typically before when I would play, I would get the occasional sticky dpad that we have all been experiencing. Surprisingly, in my 2 hour playthrough last night, I had no issues with my Tartarus v2 at all, it worked perfectly (I did notice some slight popping noises in my Kraken Tournament headset, but I think that has more to do with the Win 11 Dev build I am on and not Synapse itself).
Note: All of my Razer devices remained in the same USB ports as they were before I did all the upgrades to my CPU/BIOS.
I ordered a Tartarus Pro and I am expecting it to come in tomorrow. I still have some USB ports available, so I am going to test it when it comes in, creating a "duplicate" profile that matches how I have my Tartarus v2 set up. Since the Tartarus Pro has the analog features that others in this forum have had the same issues with, I am curious to see if I see any of those issues as my Huntsman Elite is the non-analog version.
I will update after further testing and playing, hopefully SOMETHING that occurred during all my motherboard troubleshooting and fixing last night regarding my BIOS/CPU upgrades inadvertently fixed the issues I had with my Tartarus v2.
@Razer.Speedcr0ss I hope you see this.
Userlevel 2
I have the same issue with my huntsman analog.
Seems razer are completely ignoring the issue.
Seems razer are completely ignoring the issue.
New threads generally only clutter the issue. I don't know if it would be worth it. I just asked for an update on my case, I think everyone who has not already, needs to open support cases and keep on top of them for updates.
waaaghmachine
This issue extends to the Razer Huntsman V2 Analog. I’ve been giving the same instructions on using different ports, using a clean version of Synapse, and then Razer suggested I return it to the retailer for another one. Maybe I had a defective keyboard? Well… I’m trying again, this is my third keyboard, and to nobodies surprise, it has the same “sticky” keys. If I log out of Synapse, the issues go away completely.
The only thing I get from Razer anymore is an RMA offer, zero solutions to their flagship new keyboard, which isn’t getting “reviewed” by many prominent youtubers who typically cover Razer products (Badseed, RandomFrankP, HardwareCanucks).
With reports affecting not only Tartarus v2 and Pro, but also including their other newer product lines like Huntsman V2 Analog, and Naga Trinity, this could be a sign for things to come. Perhaps this warrants a new thread to have everyone chime in to get noticed. What do you guys think?
I have not heard from Razer support in about a month. So guess they stopped sending the automated "we have not heard from you in a while and want to see if you ware still having issues" email. I guess they got wise to my automated response saying I was still having the issue.
In any case, I don't know what (if anything) is being done to actually identify and correct the issue.
In any case, I don't know what (if anything) is being done to actually identify and correct the issue.
This issue extends to the Razer Huntsman V2 Analog. I’ve been giving the same instructions on using different ports, using a clean version of Synapse, and then Razer suggested I return it to the retailer for another one. Maybe I had a defective keyboard? Well… I’m trying again, this is my third keyboard, and to nobodies surprise, it has the same “sticky” keys. If I log out of Synapse, the issues go away completely.
The only thing I get from Razer anymore is an RMA offer, zero solutions to their flagship new keyboard, which isn’t getting “reviewed” by many prominent youtubers who typically cover Razer products (Badseed, RandomFrankP, HardwareCanucks).
The only thing I get from Razer anymore is an RMA offer, zero solutions to their flagship new keyboard, which isn’t getting “reviewed” by many prominent youtubers who typically cover Razer products (Badseed, RandomFrankP, HardwareCanucks).
olPiG
Got back from holiday this week, logged in and received a Synapse update. Now I don't appear to have this issue with the Tartarus (more testing needed) but I do now have it with my Naga Trinity, which I didn't before. Anyone else experienced the same?
Please keep us updated. :3 Razer Support has stopped their conversation with me already, so I had not been keeping things up to date.
I had been hearing Naga Trinity been having the same issue since a few months back though.
olPiG
Whats the 3rd party solution?
reWASD
Seegeth
Please let us know what the situation looks like after a long time.
I am using the third party solution for now.
Whats the 3rd party solution?
olPiG
Got back from holiday this week, logged in and received a Synapse update. Now I don't appear to have this issue with the Tartarus (more testing needed) but I do now have it with my Naga Trinity, which I didn't before. Anyone else experienced the same?
Please let us know what the situation looks like after a long time.
I am using the third party solution for now.
Got back from holiday this week, logged in and received a Synapse update. Now I don't appear to have this issue with the Tartarus (more testing needed) but I do now have it with my Naga Trinity, which I didn't before. Anyone else experienced the same?
Seegeth
I don't think so, keypads are a very niche product and Razer has many other more popular products.
The problem has been known for a long time and has not been fixed until then. If they knew how to fix it, they would have done it.
The only chance is that it will accidentally be fixed during the Synapse 3 update.
In general, you have to accept that the situation will not change and use third-party programs or hide the keypad in the drawer and that's it.
Others products seems to have the issue they have to fix it in the end.
Meanwhile this experience means the tartarus is going to be my last razer product. And I am going to advice my friend to avoid the brand in the future.
Was almost gonna buy this, hope there is a fix soon.
Tartarus looks really good, sucks that it unusable right now.
Tartarus looks really good, sucks that it unusable right now.
alexxedo
Going silent and not showing interest into solving the issue is maybe the worst thing they can do. It hurts their brand image a lot.
I don't think so, keypads are a very niche product and Razer has many other more popular products.
The problem has been known for a long time and has not been fixed until then. If they knew how to fix it, they would have done it.
The only chance is that it will accidentally be fixed during the Synapse 3 update.
In general, you have to accept that the situation will not change and use third-party programs or hide the keypad in the drawer and that's it.
KAWAiiSONG
Yes, other devices also lag, I have a Razer Naga Pro and she does it too! however, I have a guess that there is something else besides Razer, my friend has a mouse G 600 and it also sticks with him! maybe Razer and Windows have a problem at the same time and they need to solve it together! We are waiting for the Windows 21H1 update
I don't think Windows has anything to do with this. Handling standard input of a mouse or a keyboard is the 101 of an operating system especially with input coming from a human user which is pretty damn slow. However if manufacturers implements faulty drivers of software this kind of things can happen.
Maybe the logic in Synapse is not processing the USB frames coming from the keyboard resulting in overwrites and then ignoring key release or the Firmware of the device is bugged when behaving in Synapse mode.
Going silent and not showing interest into solving the issue is maybe the worst thing they can do. It hurts their brand image a lot.
alexxedo
Ok it seems we aren't gonna see any fix soon...
I don't understand why they do not want to fix this issue.
Are others peripherals than the tartarus line concerned by the problem ?
The other solution would be to wait for the guys of openrazer to release a windows version of their soft even if they aren't supporting the Tartarus pro yet.
I think I'll let a review on Amazon where I bought the product to warn other consumers so they don't buy it.
That's such a shame to have this bug, I bought a redragon K585 keypad and it does not match the tartarus in term of comfort and design.
Yes, other devices also lag, I have a Razer Naga Pro and she does it too! however, I have a guess that there is something else besides Razer, my friend has a mouse G 600 and it also sticks with him! maybe Razer and Windows have a problem at the same time and they need to solve it together! We are waiting for the Windows 21H1 update
Ok it seems we aren't gonna see any fix soon...
I don't understand why they do not want to fix this issue.
Are others peripherals than the tartarus line concerned by the problem ?
The other solution would be to wait for the guys of openrazer to release a windows version of their soft even if they aren't supporting the Tartarus pro yet.
I think I'll let a review on Amazon where I bought the product to warn other consumers so they don't buy it.
That's such a shame to have this bug, I bought a redragon K585 keypad and it does not match the tartarus in term of comfort and design.
I don't understand why they do not want to fix this issue.
Are others peripherals than the tartarus line concerned by the problem ?
The other solution would be to wait for the guys of openrazer to release a windows version of their soft even if they aren't supporting the Tartarus pro yet.
I think I'll let a review on Amazon where I bought the product to warn other consumers so they don't buy it.
That's such a shame to have this bug, I bought a redragon K585 keypad and it does not match the tartarus in term of comfort and design.
KAWAiiSONG
Has the Razer team left the chat? Why is there such silence on their part? the problem has not gone anywhere !!!
My Razer Support ticket has gone silent, and they closed it. So there won’t be any more news coming from them anymore now. @Razer.Speedcr0ss is the only hope we have now, but he has gone radio silent too.
bgzgamer
Ive come here to add that I just bought a tartarus v2 and started playing Apex with it. My movement keys WASD stick 2-3 times per game and thought it was a windows issue.. but now that i see this, its pretty obvious i bought a defective piece of hardware that razer has yet to fix.
The device is fine, the problem is in the Synapse 3.0 software
Ive come here to add that I just bought a tartarus v2 and started playing Apex with it. My movement keys WASD stick 2-3 times per game and thought it was a windows issue.. but now that i see this, its pretty obvious i bought a defective piece of hardware that razer has yet to fix.
Has the Razer team left the chat? Why is there such silence on their part? the problem has not gone anywhere !!!
Page 5 / 20
Sign up
Already have an account? Login
Log in with Razer ID to create new threads and earn badges.
LOG INEnter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.