nvlddmkm stopped responding...now happens in onslaught

[LordSky00]

22.16.5  fixed my video card crashing with "Display driver nvlddmkm stopped responding..." (in Windows' event viewer)  I was beyond happy that I could finally return to the plains with Physx enabled. Now I am encountering the same crash-to-desktop-but-game-is-still-running-error in the onslaught mode.

Quote

Shrine of the Eidolon: Hotfix 22.16.5

Fixed crashes on some 32-bit systems caused by 100 MB of memory reserved by disabled GPU particles prototype. These crashes were predominately noticed when loading into the Plains or a Void Sabotage tileset.

 

Edited April 24, 2018 by LordSky00

[-AoN-CanoLathra-]

I recommend just turning off PhysX for now, as NVidia has stopped supporting it, and DE is replacing it with something else.

Also, if you are using a 32-bit system, you need to upgrade.

Edited April 24, 2018 by -AoN-CanoLathra-

[taiiat]

i'm pretty certain that Changelog snippet doesn't apply to you - because to have PhysX enabled in the first place, you must be running the x64 build of Warframe. you cannot enable it on x86 builds of Warframe.

[--F--NerevarCM]

26 minutes ago, LordSky00 said:

22.16.5  fixed my video card crashing with "Display driver nvlddmkm stopped responding..." (in Windows' event viewer)  I was beyond happy that I could finally return to the plains with Physx enabled. Now I am encountering the same crash-to-desktop-but-game-is-still-running-error in the onslaught mode.

 

To begin with, its not a good idea to use physx in a 32bits system in a map that easily use 4GB RAM

Tbh, Its not a good idea to use 32bits systems.

[LordSky00]

I am running 64-bit windows 7 with 16GB RAM. I did notice that 22.16.5 helped. Perhaps a side effect of this bug fix worked on my issue.