Snougar Posted November 28, 2014 Share Posted November 28, 2014 Loving Update 15.5 so far!Though last night my game crashed 3 times within 45 minutes. Each time the game CTD'd, came up with the Crash Reporter and then Nvidia said the driver stopped.Now after a lot of trouble-shooting it seems to be PhysX causing the issue (Disabled it and have not had a crash since!). BUT I don't know if this is a driver/PhysX issue or an issue DE introduced with 15.5.The reason I say this is because I own a GTX970 and I've read the GTX900 series do apparently have issues with games that are using PhysX on the GPU (Metro Last Light, Borderlands 2/TPS, Batman AO etc). But I also read that DE did change the PhysX Apex particles this update. The fact I have never had an issue with PhysX or Warframe on my GTX760 in the past, I am a little confused what is the actual cause of the problem. So anyone else using a GTX970/980 having issues with PhysX in Warframe? System specs:Intel i5-3570K @ 4.7GHzGA-Z77-D3H16GB DDR3-1600Galax GTX970 4GB EXOC Black Edition60GB Vertex IIICorsair HX-520Windows 7 SP1 x64Forceware 344.75All other drivers up to dateTemp wise the CPU peaks at about 45-47C and the GTX970 barely pushes 45C when playing Warframe. No other games have issues; 40 hours of Far Cry 4 and not a single crash or sign of instability. Prime95 for a few hours makes the CPU 58-62C and FurMark pushes my GPU to about 65C. Link to comment Share on other sites More sharing options...
Snougar Posted November 28, 2014 Author Share Posted November 28, 2014 Bump along with a bug number:WAR-366334Also I did about 5-6 rounds of Void without a single issue. Went do to the Alad V event (Destroying the reactor) and mid shooting the reactor it just crashed again with a driver stopped error. :( Link to comment Share on other sites More sharing options...
[DE]Linkski Posted November 28, 2014 Share Posted November 28, 2014 Bump along with a bug number: WAR-366334 Also I did about 5-6 rounds of Void without a single issue. Went do to the Alad V event (Destroying the reactor) and mid shooting the reactor it just crashed again with a driver stopped error. :( Hi Snougar, Is there any chance you could repro this for us one more time and provide another WAR-####? We are actively looking at this issue as we speak. Thanks! Link to comment Share on other sites More sharing options...
Ezard Posted November 28, 2014 Share Posted November 28, 2014 (edited) So you guys are aware - I'm using 2 GTX 970s in SLI and haven't had a single problem, so it's unlikely to be on Nvidia's end (unless Snougar is running different drivers to me - I have the v344.75, which is the beta version) Edited November 28, 2014 by Ezard Link to comment Share on other sites More sharing options...
DE_Js Posted November 28, 2014 Share Posted November 28, 2014 Snougar, You're correct, NVidia communicated us patches to improve compatiblity with their latests series The recent changes on particles were for ppl that were playing without VSynch So perhaps, try with VSynch off and Vsynch on and see if that makes a difference for you Link to comment Share on other sites More sharing options...
Snougar Posted November 28, 2014 Author Share Posted November 28, 2014 (edited) Hi Snougar, Is there any chance you could repro this for us one more time and provide another WAR-####? We are actively looking at this issue as we speak. Thanks! Well I've been trying for the past hour to get it to crash, haha. Though when it did crash it was during one of the Mesa missions that I can't get back into. For now I've just left it PhysX on and will log again if it crashes. So you guys are aware - I'm using 2 GTX 970s in SLI and haven't had a single problem, so it's unlikely to be on Nvidia's end (unless Snougar is running different drivers to me - I have the v344.75, which is the beta version) 344.75 has been out of beta quite a while now, its been signed off. 344.80 is the latest hotfixed for the 980s (Far as I know they haven't put up the next beta). I'm thinking this may be an issue with my PhysX libraries, left overs from when I was on my 760. I will test this out tomorrow and will try the legacy version as well to see if it helps. Edited November 28, 2014 by Snougar Link to comment Share on other sites More sharing options...
Agua Posted November 28, 2014 Share Posted November 28, 2014 (edited) I have the same issue, but from before the update. It seems like nvidia driver crashes and then recovers, but WF crash completely. I've had this issue on other games, but it is really rare on them, and even when it happens it only freezes for a second and afterwards I can continue playing. On warframe it is very common and the game crashes completely. Then when I try to send the report it fails every time. If there is anything I can do to help you fix this please let me know. I will probably play a little tonight and a lot tomorrow. I am using: Intel® Core™ i7 3720QM Procesador NVIDIA® GeForce® GTX 670M con 3GB GDDR5 VRAM DDR3 1600 MHz SDRAM, 16GB 256GB SSD Windows 8.1 Nvidia drivers up to date. Edited November 28, 2014 by Agua Link to comment Share on other sites More sharing options...
Snougar Posted November 28, 2014 Author Share Posted November 28, 2014 (edited) Snougar, You're correct, NVidia communicated us patches to improve compatiblity with their latests series The recent changes on particles were for ppl that were playing without VSynch So perhaps, try with VSynch off and Vsynch on and see if that makes a difference for you I play in borderless window mode with v-sync on, though I'm not sure if v-sync works properly outside of fullscreen mode. Though I'll definitely try fullscreen without v-sync and see how it goes. Hope it all gets sorted, Screen tearing will drive me nuts haha. Edited November 28, 2014 by Snougar Link to comment Share on other sites More sharing options...
Snougar Posted November 30, 2014 Author Share Posted November 30, 2014 So the past two days I've been playing quite a bit, With V-sync and the settings that were originally causing the CTD/Driver issues and I've yet to have a single crash.So it was either the Mesa stuff causing it, or one of the hotfixes sorted it out? Link to comment Share on other sites More sharing options...
Snougar Posted December 1, 2014 Author Share Posted December 1, 2014 Well I spoke too soon alas! Warframe CTD'd again and Nvidia drivers stopped and restarted.I did get the crash reporter this time: WAR-369185DE Wizards, do your thing! Link to comment Share on other sites More sharing options...
HorizonEdge Posted December 2, 2014 Share Posted December 2, 2014 gtx970 i5-3570 12gb 1600 600 watt psu sevral ssd/hdd 64 gb 256 gb 1tb Ive gotten the crash to desktop with driver dying and restore message since U15, after mesa I started ctd with no message or error reporter, the update from 12/1(today) Im getting the driver crash notification again. Ive tried on the previous patches core park/unpark vsync on/off, full screen(normally boarderless), I will try physx. not had an issue in any other game. Link to comment Share on other sites More sharing options...
IamLockeJaw Posted December 12, 2014 Share Posted December 12, 2014 970 gtx, i7 3770 16 gb Ram750 PSmore hd's than I should, but WF is running off an SSD.Can barely do solo missions, and any group mission crashes to desktop. This is mildly annoying. Link to comment Share on other sites More sharing options...
Jytra Posted December 13, 2014 Share Posted December 13, 2014 (edited) I don't have a 9 series, but I've got a Tri-Titan setup (7 series). I had EVGA's Precision opened up to monitor the GPU usage of the three cards, and I noticed that the one that handles the PhysX in a non-dedicated mode would spike to 100% usage before completely locking up my system. I should also add that I'm using Gsync (vsync disabled in Warframe), and that disabling PhysX seems to work fine in preventing a lockup. Edited December 13, 2014 by Jytra Link to comment Share on other sites More sharing options...
Icebreccer Posted December 15, 2014 Share Posted December 15, 2014 I have GTX 970 too and disabled the PhysX effects since the crashing became a real annoyance. When I used the PhysX effects the game seemed to always crash during Void missions or Dark Sector missions. Other missions it was better. Well, at least the few runs I did in Europa. I love the PhysX effects and would love to use them. And turning VSync off is not an option for me as the game looks really wonky to me if I turn it off. Link to comment Share on other sites More sharing options...
Hatzeputt Posted December 16, 2014 Share Posted December 16, 2014 (edited) I got an GTX 660 Ti and before U 15 I could play all content no problem with every setting at max and still rarely dropping below 50 fps. As of late any void that takes longer than 10 minutes will crash, especially prone are survivals. Next culprit is DS or infested in general with the hideous amount of particles spawned thanks to the new moas, here disabling PhysX worked like a charm, no crashes. Voids however remain unplayable! Even with PhysX disabled I also noticed that the lighting of certain rooms is far too bright. (Was not the case before.) To summarize: Before U 15.X No gameplay issues, no fps issues everything @ max nice and smooth 1920x1080 Since U 15.X Insane particle spam causes performance issues, these can be circumvented by completely disabling PhysX at least in DS/infested tile sets, with PhysX disabled, no problem but well it does not look and feel quite as nice a rather bad trade off for some stupid new enemy (swarm moa) Void, completely unplayable for anytime longer than 10 minutes, game will crash, driver will recover, game will recover as well of some sort but the screen will remain black, effectively making the game recovery unsuccessful. (the MS recommended fix for TDR delay has been applied). I do not get ANY crashes doing grineer tile sets and some very very rare ones on corpus tile sets, with PhysX enabled, without PhysX I do not get any crashes at all on grineer, corpus or infested tile sets. Voids are still a catastrophe however. No other current game I am playing causes frequent CTD as WF does right now (in void missions) Its also no overheating issue since my gpu does not exceed 50°C hell it does not even reach 50. Same for the rest of the system. Edited December 16, 2014 by Hatzeputt Link to comment Share on other sites More sharing options...
Icebreccer Posted December 17, 2014 Share Posted December 17, 2014 I also noticed that the lighting of certain rooms is far too bright. (Was not the case before.) Yeah I noticed that too. Here is the room with the worst eye blinding brightness: Link to comment Share on other sites More sharing options...
Hatzeputt Posted December 17, 2014 Share Posted December 17, 2014 (edited) Yeah I noticed that too. Here is the room with the worst eye blinding brightness: Precisely one of the rooms I was referring to. Update: Today after suffering another crash on my first mission overall and first void mission, a T2C within not even 4 minutes of playing I snapped and reverted my driver to 334.89....... Tried a survival (T1s) for testing purposes and it went smoothly well beyond 25 minutes, tried several other void missions as well, as it turns out the all too bright lighting is gone as well, if reverting to an almost 1 year old driver fixed my problems I will be more than happy! So far so good. I should also mention this worked with PhysX on and AA on high among everything else except shadows which I always keep on low. Update 2 Several hours and more than 2 dozen void missions and others later including several survivals I am happy to say not a single crash (aside from the server hick up). The old driver runs much more stable it seems. Edited December 17, 2014 by Hatzeputt Link to comment Share on other sites More sharing options...
Icebreccer Posted December 18, 2014 Share Posted December 18, 2014 Anyone tried the new beta drivers? I'm gonna test them tomorrow. Link to comment Share on other sites More sharing options...
Icebreccer Posted December 18, 2014 Share Posted December 18, 2014 The new beta drivers don't fix anything. Still same crashes with PhysX effects and way too bright rooms. Also the game has crashed three times even without the PhysX effects (all times in Void). Does anyone know a working drivers for the GTX 970? And also how is the fixing coming along? Will Nvidia release new drivers or is this both game+driver issue? Link to comment Share on other sites More sharing options...
UKRookieAndrew Posted December 18, 2014 Share Posted December 18, 2014 PhysX doesn't seem to be working at all for me. Is anyone else having this problem? Link to comment Share on other sites More sharing options...
IronRushBR Posted December 19, 2014 Share Posted December 19, 2014 Same boat here guys... Geforce GTX 970 and 344.75 driver. Many, many crashes. I don't know if is nvidia problem because the only game with problem is warframe. Sometimes the game completely crashes. Sometimes crashes and the driver recover from the crash and warframe get a black screen. If this black screen happens, I keep hearing the sounds from the game with black screen. Link to comment Share on other sites More sharing options...
Icebreccer Posted December 19, 2014 Share Posted December 19, 2014 Sometimes the game completely crashes. Sometimes crashes and the driver recover from the crash and warframe get a black screen. If this black screen happens, I keep hearing the sounds from the game with black screen. Yes, exactly the same thing what happens to me. Link to comment Share on other sites More sharing options...
TheRipper7 Posted December 19, 2014 Share Posted December 19, 2014 im running on a GTX770 and i dont tend to have any problems however after update 15 i did notice that my game started to lag a bit more and fps dipping below 50 ( because i usually run on above 60 fps ) idk if this is the game or just our graphic cards Link to comment Share on other sites More sharing options...
IronRushBR Posted December 19, 2014 Share Posted December 19, 2014 Yes, exactly the same thing what happens to me. Do you overclock your card, Jud? I like to overclock. I am experience on that. My system is rock solid and well tested with hours of fullmark, 3dmark 11 and 13 loops, cpu burn test, etc. The OC I am using right now is not agressive. In fact is very low one. THE ONLY GAME I am having problem is Warframe with that black screen crashes. Link to comment Share on other sites More sharing options...
Icebreccer Posted December 19, 2014 Share Posted December 19, 2014 I have MSI's GTX 970 so it's overclocked by default. Though I use the default profile which isn't OC AFAIK. 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