Valkyr-Umbra Posted November 7, 2018 Share Posted November 7, 2018 (edited) I got a new Razer mouse (trinity) and it uses the new razer synapse 3, so I installed that yesterday. It looks like razer synapse 3 and warframe have compatability issues. I've tested this several times now, just writing up what I've found out, but warframe crashes if I try to launch it with the razer synapse 3 app open. If I open razer synapse 3 with Warframe already open, its fine. My bug number in case it helps: WAR-2047866 EDIT: I'm reasonably certain its an interaction with razer synapse 3, I tried and failed to log in several times with it open, closed it it worked, opened it it crashed, closed it again and it worked. I also tried restarting my computer with no effect. Edited November 7, 2018 by Valkyr-Umbra Link to comment Share on other sites More sharing options...
Valkyr-Umbra Posted November 9, 2018 Author Share Posted November 9, 2018 Just wanna say, I'm basically certain at this point. I haven't had one instance where the Warframe client doesn't crash with razer synapse 3 open, and every time I close it, the game opens find. Not sure who's end this is on, might be Razer's, I'll make a post on their forums to. Link to comment Share on other sites More sharing options...
samok79 Posted November 9, 2018 Share Posted November 9, 2018 Same with me (from Windows Application event logs - translated to Eniglish from my local language version via google translate) The name of the application that caused this error: Warframe.x64.exe, version: 2018.11.9.16, time stamp: 0x5be60142The module that caused the error: RzChromaSDK64.dll_unloaded, version 2.11.5.25, time stamp: 0x5b973795Exception code: 0xc0000005Error position: 0x00000000000013f4The process identifying the error: 0x1054The startup time for the application causing the error is 0x01d4788114bd366bThe path to the application that caused the error: 😧 \ Steam \ steamapps \ common \ Warframe \ Warframe.x64.exeThe path to the module causing the error is: RzChromaSDK64.dllReport ID: 80e698b6-0aa5-47b8-96c1-df385ca774d0Full name of the package causing the error:Relative Application ID of the Issuing Package: Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now