Jack_Carver Posted October 29, 2014 Share Posted October 29, 2014 (edited) i have one and a half year playing and i never could activate 64-bit mode from the launcher, always shown a "0xc000007b" error. One year ago exactly, i formatted my PC and neither worked, so yesterday i tried again and reinstalled to see if it worked, but not only did not work but it also now i cant check Nvidia PhysX effects neither... And this last i always had set. For this last problem, i have reinstalled graphic driver and PhysX driver to check if the problem was by the new warframe installation but neither worked, so i don´t know what i can do. CHECKED: For a strange reason, Warframe PhysX is emulated by CPU and it´s ignoring my PhysX config, which is selected as GPU from Nvidia control panel. Edited November 1, 2014 by Jack_Carver Link to comment Share on other sites More sharing options...
Letter13 Posted October 29, 2014 Share Posted October 29, 2014 The "0xc000007b" error usually means you need to update your Microsoft Visual C++ runtime libraries. If it's just the 64-bit version it means you need to update the 64-bit Visual C++ runtime libraries. I am assuming you're running a 64-bit version of windows; if you're not then you obviously can't run the 64-bit executable. Link to comment Share on other sites More sharing options...
Jack_Carver Posted October 29, 2014 Author Share Posted October 29, 2014 (edited) yes, i have 64-bit Windows and i have installed MV C++ 2005, 2008, 2010 and 2012, all x86 and x64 versions and as I mentioned, this error I have done before and after formatting, so I neither worked with c ++ updated to its latest version Edited October 29, 2014 by Jack_Carver Link to comment Share on other sites More sharing options...
Jack_Carver Posted November 1, 2014 Author Share Posted November 1, 2014 i read that now you only can switch PhysX if you start Warframe x64, but if i can´t launch it because i can´t solve that problem, then, neither W x64 and neither PhysX now? -.-" Link to comment Share on other sites More sharing options...
Jack_Carver Posted November 1, 2014 Author Share Posted November 1, 2014 SOLVED: after three hours checking the dll files with "dependency walker" program, i found a problem with "xinput1_3.dll" which is from directx, i looked that happened and i found a solution which said that i had that delete this file from ...\Syswow64 and only this, reinstal the last directX and solved. 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