Game Crashes Nvidia Display Driver (April 2015)

[Nethereal]

Yeah, I've been having the same problems since about a month, a month and a half ago as well. I figure it's just my gpu showing its age, a 8800 gt. Tried all sorts of software workarounds, switching settings in the launcher and the game, rolling back drivers and the like. Nothing fixed it. Don't know if this is at all relevant, but I was playing Starcraft during all this, and never had a problem with it. Only newish games seemed to be affected, I'm guessing. Ah well, I have to upgrade anyway.

[Leyers_of_facade]

Just saw this post today....and I finally know that I am not the only one experiencing these display driver crashes... (I thought it was due to problems in my graphics...) 

 

graphics card used: NVIDIA GTX 850M

 

I didn't record the errors as I thought it was only me, but I remember the watchdog thingy error message some time ago. Also I have a lot more crashes in January and February, it largely reduced in the next 2 months, but the problem is getting severe again.... and not sure if it might help, but sometimes when it crashes the entire warframe screen will change into a lot of weird colored squares (or pixel) and basically crash the game, but this situation happens mainly during the earlier months, the situation in may is more of the game freezing up and i have to use task manager to shut game

[Urlan]

The watchdog message posted by Kildyu suggests that the issue may be due to the driver itself having issue with how it handles Direct x 11. If it is similar, it might be worth trying Direct x 9 by disabling both x10 and x11 in the launcher.

 

With the 8800GT, many of them had problematic capacitors that caused gradual damage when the card when into heavy use and because the large amount fo heat the card puts out starts to fry the VRAM if you aren't careful. Maybe the card could be retired to a less intensive use to give it a longer lifespan. Otherwise, the 8800 GT was a pretty good card!

 

Crazy blocks and weirdly rendered pixels are commonly textures crashing while on the way through the VRAM, this can be caused by corrupted softwarre drivers or by heat related gradual damage. If its the driver, switching to an older driver using a clean install might help - as long as the manufacturer has an older working driver. Otherwise, its possible that the laptop's built in card has started a gradual spin into the VRAM going out, high heat situations should speed the VRAM's issues and Warframe seems to cause even my PC video cards to run hotter than normal; you might be able to chill the card and see if the issue takes longer to occur.

[kildyu]

Alright crashed again today. In launcher Dx11, Dx10, 64bit, multithreaded rendering were all off. I created a memory dump in task manager right after it occurred, I also left the game running after it happened (game is minimized but still running, I can hear things happening and even control my character still) rather than closing it and after a few minutes it crashed. I submitted the crash report and got WAR-470951. Will try an earlier driver now - looking in event viewer the earliest was Apr 17, shortly after the GTA5 driver 350.12 - going to try 347.88.

 

Here are a few lines from EE.log right before the crash, I think the majority of the repeated lines in my previous EE.log were post crash, and am seeing similar things here.

 

1917.440 Phys [info]: Tearing detected for ragdoll GrineerMarineRagdollUnconscious. Disabling CCD.

1917.890 Phys [info]: Tearing detected for ragdoll GrineerMarineRagdoll. Disabling CCD.

1919.363 Phys [info]: Tearing detected for ragdoll GrineerMarineRagdoll. Disabling CCD.

1919.475 Sys [info]: Ragdoll::CommonInit() 1ms

1919.632 Phys [info]: Tearing detected for ragdoll GrineerMarineRagdoll. Disabling CCD.

1920.487 Sys [info]: GiveItem Queuing resource load for Transmission: /Lotus/Sounds/Dialog/GenericMissions/SurvivalInterimRaidSuccess/SurvivalRaidSuccessTransmission

1920.487 Sys [info]: OnTransmissionLoaded: /Lotus/Sounds/Dialog/GenericMissions/SurvivalInterimRaidSuccess/SurvivalRaidSuccessTransmissionfinished with result 1

1920.500 Sys [info]: Created /Lotus/Interface/Transmission.swf

1920.536 Sys [info]: UI Destroy prior background region

1920.536 Script [info]: --- Set global: gPortraitRegion

1920.536 Sys [info]: Finished new region

1920.550 Script [info]: Survival: Client: trying to catch up with new reward count= 5, current=4

1920.550 Sys [info]: Created /Lotus/Interface/SurvivalReward.swf

1920.550 Script [info]: Survival: Gave reward tier 0 at 1500.238

1920.568 Script [info]: Survival: Client: Reward count matches new reward count.

1921.032 Sys [info]: GiveItem Queuing resource load for Transmission: /Lotus/Sounds/Lotus/HeavyTransmission

1921.032 Sys [info]: OnTransmissionLoaded: /Lotus/Sounds/Lotus/HeavyTransmissionfinished with result 1

1921.160 Sys [info]: Ragdoll::CommonInit() 1ms

1922.307 Phys [info]: Tearing detected for ragdoll GrineerMarineRagdoll. Disabling CCD.

1922.694 Sys [info]: Ragdoll::CommonInit() 1ms

1923.052 Phys [info]: Tearing detected for ragdoll GrineerMarineRagdollUnconscious. Disabling CCD.

1923.136 Phys [info]: Tearing detected for ragdoll GrineerMarineRagdoll. Disabling CCD.

1923.426 Phys [info]: Tearing detected for ragdoll GrineerMarineRagdoll. Disabling CCD.

1923.562 Sys [info]: Ragdoll::CommonInit() 1ms

1924.001 Sys [Warning]: Ignoring scripted animation for dead avatar: MacheteWomanAvatar608

1925.985 Script [info]: --- Set global: gPortraitRegion

1927.860 Gfx [Warning]: D3DAssert: IDirect3DSwapChain9Ex::Present() returned 0x88760868 (D3DERR_DEVICELOST)

1928.561 Gfx [Error]: Driver changed from READY to NOT_READY

1928.649 Sys [info]: Texture streaming NORMAL -> DISABLED [Heap: 563,355,528/571,342,848]

1928.845 Gfx [Error]: Driver changed from NOT_READY to PENDING-RESET

1928.855 Gfx [Warning]: ResetDriver called on: Dx9Driver

1928.973 Gfx [info]: Borderless mode. Desktop resolution is 1920x1080

1928.974 Sys [info]: Using a VSync-Interval of 30Hz

1929.110 Gfx [Error]: Driver changed from PENDING-RESET to NOT_READY

 

I have also adjusted my BIOS, setting my RAM settings to factory default instead of leaving them on AUTO as per http://www.tomshardware.com/answers/id-1876964/constant-nvidia-display-driver-crash-recovery.html If this doesn't work I will also look in to the GPU memory clock mentioned there.

Edited May 22, 2015 by kildyu

[Urlan]

Is the warframe you are using Hydroid? If so, the problem could be tied to the Hydroid memory bug related to ragdolling enemies through the map boundries. Otherwise, it sounds like the driver or card are crashing during a Lotus communication call in your survival. Its a shame that switching to Direct x 9 didn't allow the game to run in a stable manner. That would leave the card or the driver if the issue isn't the game filling the card's RAM until it crashes. That would still usually go through Direct x calls though.

[kildyu]

I was not, somebody else was. 

 

Here some parts from the first EE.log right before the crash as well.

 

6122.581 Game [info]: BladeSawmanAvatar202 client side kill! dd: 162

6122.582 Game [info]: RifleLancerAvatar201 client side kill! dd: 165

6122.899 Game [info]: RifleLancerAvatar200 client side kill! dd: 118

6122.900 Game [info]: RifleLancerAvatar199 client side kill! dd: 210

6124.171 Game [info]: RifleLancerAvatar204 client side kill! dd: 77

6124.171 Game [info]: RifleLancerAvatar206 client side kill! dd: 137

6124.171 Game [info]: RifleLancerAvatar205 client side kill! dd: 364

6124.247 Sys [info]: Created /Lotus/Interface/ChallengePopUp.swf

6124.485 Game [info]: RifleLancerAvatar207 client side kill! dd: 73

6124.485 Game [info]: RifleLancerAvatar203 client side kill! dd: 129

6125.203 Script [info]: ERROR: TeleportAndFade.lua: 5CreditsPickup Was not teleported to a waypoint because the waypoint was null

6125.203 Script [info]: Defaulting to putting them at the initial spawn point

6126.915 Game [info]: BladeSawmanAvatar209 client side kill! dd: 242

6127.159 Sys [info]: GiveItem Queuing resource load for Transmission: /Lotus/Sounds/Dialog/GenericMissions/SurvivalLifeSupportIncoming/SurvivalLifeSupportIncomingTransmission

6127.159 Sys [info]: OnTransmissionLoaded: /Lotus/Sounds/Dialog/GenericMissions/SurvivalLifeSupportIncoming/SurvivalLifeSupportIncomingTransmissionfinished with result 1

6127.170 Sys [info]: Created /Lotus/Interface/Transmission.swf

6127.191 Sys [info]: UI Destroy prior background region

6127.191 Script [info]: --- Set global: gPortraitRegion

6127.191 Sys [info]: Finished new region

6128.598 Sys [Error]: An object of type  wasn't unregistered from the event manager

6132.106 Script [info]: --- Set global: gPortraitRegion

6141.188 Gfx [Warning]: D3DAssert: Dx11OcclusionQuery::Create() returned 0x887A0005 (The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.)

[Urlan]

Try doing the same mission without Hydroid or Vauban in the team to see if it still crashes without their abilities overworking the renderer. This report was using the Direct x 11 settings enabled again? It seems that a similar gPortraitRegion script is the last thing that ran before crashing similar to the Direct x9 error log you listed before. Perhaps the similar Lotus trasmission is a point of contention? It would be helpful to know how the Lotus transmission plays, is it rendered in game or by linking embedded flash libraries? If it is rendered by the ingame Evolution engine, I would definately look at the driver, if its an embedded flash, it might be worth checking the cache for the game again and rechecking your flash for updates.

[kildyu]

Try doing the same mission without Hydroid or Vauban in the team to see if it still crashes without their abilities overworking the renderer. This report was using the Direct x 11 settings enabled again? It seems that a similar gPortraitRegion script is the last thing that ran before crashing similar to the Direct x9 error log you listed before. Perhaps the similar Lotus trasmission is a point of contention? It would be helpful to know how the Lotus transmission plays, is it rendered in game or by linking embedded flash libraries? If it is rendered by the ingame Evolution engine, I would definately look at the driver, if its an embedded flash, it might be worth checking the cache for the game again and rechecking your flash for updates.

 

That was from the first EE.log, from my first post. I had just included some of the error messages before - that was ~25 lines before the crash for comparison. I've done 3 successful missions now after the RAM change, and driver rollback. 20-30 minutes each.

[kildyu]

In Archwing this time, so 347.88 and explicit RAM timing was not it.

 

 

5772.734 Sys [Warning]: Avatar ShieldSkiffAvatar3233 destroyed before Agent /Npc/ShieldSkiff341 detached! Detaching now.

5773.690 Sys [Warning]: Avatar ShieldSkiffAvatar3211 destroyed before Agent /Npc/ShieldSkiff319 detached! Detaching now.

5774.294 AI [info]: OnAgentCreated /Npc/GrineerSpaceDrone353 numLive 20 numSpawned 344 AutoSpawnEnabled: 0 IsAutoSpawn 0

5774.296 AI [info]: OnAgentCreated /Npc/MissileSkiff354 numLive 21 numSpawned 345 AutoSpawnEnabled: 0 IsAutoSpawn 0

5774.297 AI [info]: OnAgentCreated /Npc/ShieldSkiff355 numLive 22 numSpawned 346 AutoSpawnEnabled: 0 IsAutoSpawn 0

5774.298 AI [info]: OnAgentCreated /Npc/GrineerSpaceMarine356 numLive 23 numSpawned 347 AutoSpawnEnabled: 0 IsAutoSpawn 0

5774.299 AI [info]: OnAgentCreated /Npc/CombatPod357 numLive 24 numSpawned 348 AutoSpawnEnabled: 0 IsAutoSpawn 0

5774.299 Script [info]: Created a squad (5) with leader /Npc/GrineerSpaceDrone353

5774.299 Script [info]: Creating squad with enhanced AI!

5774.834 Sys [Warning]: Avatar GrineerSpaceMarineAvatar3208 destroyed before Agent /Npc/GrineerSpaceMarine316 detached! Detaching now.

5775.388 Sys [Warning]: Avatar GrineerSpaceDroneAvatar3230 destroyed before Agent /Npc/GrineerSpaceDrone338 detached! Detaching now.

5776.631 Sys [Warning]: Avatar GrineerSpaceMarineAvatar3197 destroyed before Agent /Npc/GrineerSpaceMarine305 detached! Detaching now.

5779.417 Sys [Warning]: Avatar GrineerSpaceDroneAvatar3232 destroyed before Agent /Npc/GrineerSpaceDrone340 detached! Detaching now.

5780.308 Sys [Error]: Set owner called multiple times on item SpaceDroneAuraUpgrade3962

5780.308 AI [info]: OnAgentCreated /Npc/StasisDrone358 numLive 20 numSpawned 349 AutoSpawnEnabled: 0 IsAutoSpawn 0

5780.309 AI [info]: OnAgentCreated /Npc/GrineerSpaceDrone359 numLive 21 numSpawned 350 AutoSpawnEnabled: 0 IsAutoSpawn 0

5780.309 AI [info]: OnAgentCreated /Npc/LaserDrone360 numLive 22 numSpawned 351 AutoSpawnEnabled: 0 IsAutoSpawn 0

5780.311 AI [info]: OnAgentCreated /Npc/MissileSkiff361 numLive 23 numSpawned 352 AutoSpawnEnabled: 0 IsAutoSpawn 0

5780.311 AI [info]: OnAgentCreated /Npc/LaserDrone362 numLive 24 numSpawned 353 AutoSpawnEnabled: 0 IsAutoSpawn 0

5780.311 Script [info]: Created a squad (5) with leader /Npc/StasisDrone358

5780.311 Script [info]: Creating squad with enhanced AI!

5781.253 Sys [Warning]: Avatar MissileShieldSkiffAvatar3239 destroyed before Agent /Npc/MissileShieldSkiff347 detached! Detaching now.

5781.906 Sys [Warning]: Avatar GrineerSpaceMarineAvatar3234 destroyed before Agent /Npc/GrineerSpaceMarine342 detached! Detaching now.

5782.979 Sys [Warning]: Avatar GrineerSpaceMarineAvatar3224 destroyed before Agent /Npc/GrineerSpaceMarine332 detached! Detaching now.

5784.818 Gfx [Warning]: D3DAssert: IDirect3DSwapChain9Ex::Present() returned 0x88760868 (D3DERR_DEVICELOST)

5785.115 Gfx [Error]: Driver changed from READY to NOT_READY

5785.200 Sys [info]: Texture streaming NORMAL -> DISABLED [Heap: 396,057,568/573,964,288]

5785.262 Gfx [Error]: Driver changed from NOT_READY to PENDING-RESET

5785.285 Gfx [Warning]: ResetDriver called on: Dx9Driver

5785.378 Gfx [info]: Borderless mode. Desktop resolution is 1920x1080

5785.378 Sys [info]: Using a VSync-Interval of 30Hz

5785.458 Gfx [Error]: Driver changed from PENDING-RESET to NOT_READY

[Urlan]

Well while the archwing Grineer drones, dying before they should can be an issue, I don't think that is what is causing your issue. It could still be your driver, or graphics card itself. If someone has more experience with running the game in borderless, you might want to defer to them on this, but I think it might be best to lower the resources the game is using. Turn off Borderless fullscreen mode and try to run the game in native resolution if possible to see if you still experience a similar issue. If it is a resource issue, the card maybe the problem. Basically reduce your ingame settings as well you can while still having decent stability or gameplay and then try the same missions that crashed. If you crash around the same times, it should be drivers or the game, if the game lasts longer for turning down settings, it becomes more likely that it is a graphic  card hardware issue.

[EWar]

Status update: No crashes so far since updating to driver 352.86 (PhysX still disabled in Warframe for good measure).

[MrHobbs]

Hey guys I have a GTX 960 GPU, I have it on the base clock of 1127 should I tune it down a little? 

[kildyu]

Drivers back up to 352.86 as they seemed to have no affect. Changed from Borderless to Fullscreen, all graphics on low/off, and in the nvidia control panel for warframe Power Management - maximum performance; Threaded optimization - on; triple buffering - off; vertical sync - adaptive as recommended by nvidia support to me. Didn't crash today though most games were fairly short.

 

I did have one moment where the game froze, I alt tabbed to check task manager, and it said "not responding" for a second then went to normal, tabbed back in game and everything was fine. Not sure if it was related or not.

 

I'm going to start turning graphics back up pretty soon and see if anything bad happens again.

[Urlan]

I am glad that worked so far. Before you turn the graphic settings back up, do you mind doing something of a stress test? A mid length survival run or Jupiter, Europa Ice planet, or the Derelict should do it. All three tilesets have alot of graphic doodads and different elements that when loaded may show if the card is able to run at these reduced settings or if it was just coincidence.

[Cray]

Just a few minutes ago, I was doing a simple grineer survival, not even 10 minutes in, drivers crash, display goes full dark, BSOD.

 

Win7, x64, NVIDIA GeForce GTX 560 Ti, driver version is 340.52.

 

This is the first time it did a full BSOD. Usually the game just crashes or freezes/plays with a black screen to the point I have to close it manually. It only started doing this in the last few days for me. No WAR numbers yet, as I was stupid and didn't submit any crash reports.

Edited May 24, 2015 by DeltaPhantom

[kildyu]

I am glad that worked so far. Before you turn the graphic settings back up, do you mind doing something of a stress test? A mid length survival run or Jupiter, Europa Ice planet, or the Derelict should do it. All three tilesets have alot of graphic doodads and different elements that when loaded may show if the card is able to run at these reduced settings or if it was just coincidence.

I guess "a few short" may have not been the best way to describe it. I did 3 20-25 minute runs on Jupiter and Saturn (so 6 total); 3 4-8 extractor runs on earth; 1 4 wave run in Archwing Uranus; 2 20-25 minute Mercury runs, and 1 20 minute run on Ceres.

[kildyu]

A few more games today. 20 minute ODS, freeze/disconnect on another ODS. Turned graphics back up, but stayed fullscreen. 20 minute T1 Survival, 40 minute T3 survival, freeze/disconnect on another T3 survival. Switching to fullscreen may have spared the driver from crashing, but the game seems to still be having an issue with something. Don't have anything from the EE.log from those. Didn't see anything out of the ordinary and didn't make a copy of them after it happened. Doing a fresh reinstall, see what happens and then try windowed mode if there are still issues.

[DesertxFox]

Anyone find a solution to the driver crashes or the cause of them even?

[DarkeTH]

(White screen with sounds) just became (white crash) for me after last update .. screen goes white then the game crashes.

 

And it happens more frequently now.

[aerosoul1337]

After I gave up my old amd cup (crashes and freeze while hosting since 16.5),

I built a new powerful pc:

Windows 7 64 bit

i7 4790K

GTX 980 (driver: 352.86  ^WHQL)

16G DDR3 1866

warframe installed in intel 530 series 480G SDD

Internet 100Mb

 

But

U16.6 is now game breaking!

 

My game performance drops like hell.

 

OK

my FPS before update 16.6

Liset: 400~450
Solo mission: 250~350
Raid:: 180~250

 

FPS after update 16.6

Liset: 60~400

Solo mission: 50~120

Raid:: 19~50

 

The fps drop can happen even when idling in liset.

 

This is just so wrong!

Edited May 28, 2015 by aerosoul1337

[Urlan]

I would try running in direct x 9 mode to see if that reduced the frames per second lag. If it does, it might be that the update build is missing some of the resources used for running in direct x 10 and 11 or that update broke how some of the display setting work.

[[DE]Linkski]

We are still working to resolve this issue. Can anyone please confirm whether or not this display driver crash happens with v-sync enabled?

[Sloan441]

This as been extremely intermittent for me. It only seems to be an issue on void maps and only infrequently. Temperatures are stable at around 65 degees C on the GPU. I always run v-sync.

 

Machine is a 2500K/TitanX running Win7-64 with 8gigs of RAM. Presently, still running driver version 350.12.

 

Still running with v-sync enabled and I'll hit a few void maps and see what happens...

 

Ran 4 T1MD and 1 20min T1S (all I had time for and had lots of keys to expend), no issues. Will try again tonight after work with some longer survivals to see what happens. 40min T2S and a couple of T2MDs and still no crashes.

Edited May 29, 2015 by Sloan441

[sirwarriant12]

I've had very frequent driver crashes lately, especially when running with people. Solo not as much but it's pretty much a guaranteed crash if I play with someone. I usually run the game on the Max settings in DX9 with vsync off since DX11 for whatever reason is a guaranteed crash. I usually have no crashing problems except of late. Temps are always fine and fps stays around 45-60 with a 650ti.

[manuman1171]

After the latest update which applied itself on my computer just a few minutes ago the game is completely failing to launch, going to a white windowed screen and then closing, followed by a message window saying that Warframe has encountered an "internal error". The program also fails to respond when I attempt to send a crash report. I've been really enjoying Warframe so far and hope not too many other people are suffering from this problem and that you manage to solve it soon so I (and anyone else suffering from this problem) can back to this excellent game :)