Razer Tartarus V2 controller D-pad sticking / glitch

Hey everyone! I appreciate all the help. I suggested performing the SFC scan and creating a local Windows user account so it can help us isolate the issue. And yes, I agree that these steps are tedious. Keep in mind that this is not an official fix. By the way, the team is watching this thread and they're monitoring everyone's post. I appreciate the collation of data, video tutorial, and for everyone who tried the steps too. It's surprising that the issue is happening to another gaming keypad brand too. Our aim is to determine the cause of this and create a fix. I'll update this thread again once I got a follow-up from the team.

Hello again! here is another interesting information, my friend has a logitech g600 , and it also sticks ! how do you like this?

im still having no problems but there is no way that the fix i am using is going to work i just mean it can't be that simple. think i just have had good luck and will probably have the bug happen again later :slightly_sad: but anyway

device manager/find the hid complaint consumer device with razer tartrus in it and disable it and leave all the other tartrus things on

https://cdn.discordapp.com/attachments/587332804627529738/800397261837172756/unknown.png

and no it decided it would do it today why is it so random arg ¬¬

I can't write messages ! at least in English.

Seegeth
For me System File Checker did not help at all, found corrupted files and fixed them, but the problem continued.

Ahhh, yes, that's right -- you mentioned that before, and I forgot (sorry!)

NoahArk620
While SFC has detected an error on my secondary device (log stated that it fixed a file related to Microsoft NET 4.5 distribute), and promptly fixed it, the Tartarus Pro issue stil crops up after 2 hours of testing.

Okay, so two users for whom System File Checker alone was ineffective. Based on this, I'm going to edit that out of the list of short term fixes on my summary post. Thanks!

Also, that was the only error that my run at the System File Checker found too: related to the Microsoft .NET Framework, although mine is version 4.8.


We all seem to be unanimous on the fact that some solutions seem to work over a short term range, but then the issue recurs again a while later. I don't understand it, but I feel like it must be relevant, right?! ... like something gradual or cumulative is building up over time, in sort of the same way that too many cookies can bog down your internet performance ... @Razer.Speedcr0ss, is the tech team able to validate this theory, and/or provide feedback on this?


Keep us posted on whatever it is you're testing, @CptCraptacular ... fingers crossed it's sustainable, and looking forward to you sharing your method.


In terms of software, here's what we've got so far:

I can chime in,

I had performed System File Checker prior to converting my main admin account on my secondary device (which i use for testing nowadays) into a local admin account. While SFC has detected an error on my secondary device (log stated that it fixed a file related to Microsoft NET 4.5 distribute), and promptly fixed it, the Tartarus Pro issue stil crops up after 2 hours of testing.

In terms of softwares on my side, I can only think of ‘Discord’, ‘Nvidia Geforce Experience’, ‘Microsoft Office 2016’, ‘Microsoft OneDrive’, ‘Google Drive’, ‘Apple iCloud’, ‘Steam’ and ‘Google Chrome’ being the only softwares that are the same between my primary and secondary device, and are running on the background. Work PC (Tertiary drvice) only had Google Chrome.

Like @Seegeth, my systems has practically went unchanged for the past year except for updates on Windows, and Synapse.

Alright, so I’ve been thinking and wondering about some questions/hypotheses. Would the following theories be helpful to test, or not?



Theory #1
In my previous post, I mentioned short term fixes, which ended up being briefly effective for a range of 3 – 14 days. Of those listed, most of them could be done individually (independent of the other short term fixes). The one I am uncertain of is the System File Checker. Therefore, I am wondering …

True or False:

[indent]Running the System File Checker alone – provided it detects and repairs errors! – is effective at providing a short term fix for a few days to a couple weeks.

Running the System File Checker alone – when it detects no errors – is not effective.[/indent]

@Razer.Speedcr0ss ... would determining this be helpful at all to the Razer tech team, in isolating the issue? Or does it not really make enough difference to be worth testing? Testing would need to be done by someone who would be more possibly likely to have errors detected in their system files (therefore, someone who has not recently run the system file checker, and had their errors repaired).



Theory #2
@Seegeth performed extensive testing (7-10 days) on converting the primary admin Windows user account to a local account. So did @NoahArk620 I think? Although it seemed promising, this only ended up being effective as a short term fix. Limited testing was also performed on creating a brand new subordinate local Windows user account. For a couple/few days, Seegeth said this was testing well. Is it worth it to explore this further?

[indent](a) Have someone test this theory for a couple weeks? It’s important to be sure that this is the ONLY Windows user who is logged in, during testing. Don't make the same mistake I did and be logged into both, at the same time, lol! :rolleyes:

(b) If it tests well for a couple weeks, assign admin status to this new account and test further.[/indent]

Besides asking if this would be worth it, we should also consider: is it fair to ask someone to go to this extent? On the one hand, setting up a new local is quick, easy, and clean – and it only really needs to be used when you’re gaming/testing. On the other hand, it is still kind of onerous – especially for users who would need to download and configure voice chat platforms and addon managers, etc, for their gaming purposes.

So, @Razer.Speedcr0ss ...

• Would testing this provide enough value to the Razer tech team to be worth it?
  

And fellow troubleshooters ...

• Is there anyone who might be willing and able to undertake this testing?
  

Theory #3
It is entirely possible (maybe even probable!) that the issue is caused by a software conflict – some application that perhaps we all have in common, as @KAWAiiSONG suggested. If so, determining what it is could be like finding a needle in a haystack. KAWAiiSONG provided some advice, and while that advice is certainly valid and very thorough, it seems a bit extreme. It reminds me of testing for food allergies: strip your diet down to basically nothing, and then gradually add one new type of food per week, until you’re finally able to determine which food is causing your allergic reaction. This is certainly effective at tracing the origin, … but is there an easier way?

Would it be helpful to post screenshots of our Task Manager (CTRL + ALT + DEL), showing which applications and/or background processes we have running? Or a screenshot listing everything that launches on startup? Or a screenshot of the extensive list of items under the Details and/or Services tab? …. Or should we simply start by announcing names of all the programs/applications we ourselves have running at any given time, which we feel might be likely to be popular among other gamers? @Razer.Speedcr0ss , is this something you could find out and advise us on? What would be the quickest and easiest way to begin narrowing down software commonalities among our community here, which might be causing a conflict?


Please contribute your thoughts, ideas, opinions, feedback ... and feel free to come forward with your own theories, too! There are no bad ideas. Remember: Razer prides itself on being "For Gamers, By Gamers", right? Well -- we are the gamers, so we're definitely part of the team.
[indent]This would be an exceptionally good time for @Razer.Speedcr0ss to offer us all free branded merch, as a courtesy/thank-you gesture for all of our patience and testing, haha! :big_grin_:[/indent]

Okay, so to summarize ...

Razer tech troubleshooting queries and steps:

• Determine if the issue occurs while playing a different game(s).
  
• Ensure the device is not plugged into a USB hub.
  
• Determine if the issue occurs on a different PC with Synapse 3 installed.
  
• Verify your Windows version and OS build (Windows key; then search "winver").
  
• Verify your Synapse 3 version ... go to Synapse, Settings, About.
  
• Ensure that you have the latest version of the Microsoft .NET Framework.
  
• Ensure that you have the latest updates installed for Microsoft Visual C++.
  
• Run the Windows System File Checker tool.
  
• Perform a clean re-install of Synapse 3 (more comprehensive than a standard re-install).
  
• Collect and submit Synapse 3 logs.
  

Unsuccessful fixes:

• Switching USB ports to a different port on my PC (front port to rear port).
  
• Running the 'repair' tool in Windows to repair the installation of Synapse 3.
  
• Replacing the device with a new replacement device (RMA).
  
• Excluding Razer modules (Chroma Studio; Macro) from a clean re-install.
  
• Creating and using a new Windows user local account, while simultaneously remaining logged into your primary admin account.
  

Various successful immediate work-arounds:

• Pressing the affected button again ceases the immediate current occurrence of the looping repeated function. Note however that the issue continues to occur. The frequency varies per user.
  
• Logging out and exiting the Synapse 3 software entirely.*
  
• Connecting the device to a different PC without Synapse 3 software installed.*
  
• Using third party key binding software such as reWASD instead of Synapse 3.*
  

[indent]* Note: This will result in some functional [/indent]

Various successful short-term fixes:
* Note: Issue typically recurs between 3 - 14 days.

• Clean uninstall/re-install of Synapse 3 software. Standard uninstall/reinstall may be sufficient, but clean is better.
  
• Logging into a different Synapse 3 user account (razertest; razerperipheralstest; etc.).
  
• Converting your primary Windows user account to a local account (if it's not already local).
  

These each seem to be

Seegeth
Broke again. Within 2.5 h, stuck once.

Oh, damn -- so frustrating! Just to be clear, this failure was under which of the following circumstances?

[indent](a) The 7th to 10th day after you converted your main user admin account to a local account?[/indent]

... or ...

[indent](b) Right after you had just tried converting your main user admin account back to an online account?[/indent]

Seegeth
I don't think so. After using New Local Account, i converted my administrator (microsoft account) to local and it works. I have all my processes active.

This has nothing to do with it! I originally and always had a Local administrator account! that it never helped me!

So!
1.Disable any extraneous Windows services that are installed by third-party software that is not part of the OS.
2. Press the Windows key + R key combination. A menu will appear to enter https://i.imgur.com/sKSZ6YB.png
3.Write msconfig and click ok. The system setup application will open.
4. Go to the Startup tab and disable all applications from the list.
5.Next, go to the Services tab and check the box next to "Do not show Microsoft services", then click Disable all.
6. After these actions, click "ok", you will be prompted to restart your PC. Please reload it. After restarting, try starting the game without launching any programs.

Ok, reporting in just after a few hours of testing. I followed through @Seegeth steps, but I omitted the part involving making a new test local account.

I had already done sfc /scannow, converted my main admin account to local account, restarted pc, and log back into Synapse 3.0 through my own account. The problem unfortunately occurred sometime after 2 hours of testing.

Maybe i'll try making a new local account next time, but for now, my current conclusion is that it doesn't work.

(I remember doing something else prior, and had no issues for 2 weeks, but it comes back with a vengeance right after, but that was months ago already.)

@Seegeth

Thanks a lot for the suggested steps! I will try this on my secondary device where I still have synapse 3.0 installed.

I personally rely heavily on Microsoft account syncing for work between my primary and secondary account, so I am wondering if you had tested reverting back to Microsoft account afterwards to see if the issue continues to show up?

*EDIT*

Oh wow, I was expecting my OneDrive to not sync up after converting to Local, testing this would be a breeze!

Just quick question to everyone, this month's Synapse update hasn't been pushed out yet, has it? I am still on 3.5.1215.121019.

@roger32025 Nice to see you again, Draxille! It is so nice to see you roaming in this forum too!