February 15, 201412 yr I have a GTX 780 and just completed a fresh installation of P3D 2.1. I'm having an issue (not previously experienced in 2.0) with the driver resetting itself (not sure if it's a coincidence or not, but it seems to be associated with the Carenado). I'm wondering if anyone else is having this issue and if I would benefit from rolling back my driver to the previous WHQL version.
February 15, 201412 yr I have a GTX 780 and just completed a fresh installation of P3D 2.1. I'm having an issue (not previously experienced in 2.0) with the driver resetting itself (not sure if it's a coincidence or not, but it seems to be associated with the Carenado). I'm wondering if anyone else is having this issue and if I would benefit from rolling back my driver to the previous WHQL version. What do you mean with "resetting itself"? Do you talk about the nVidia Inspector profile which will be overwritten with any driver update, or what? Spirit
February 15, 201412 yr Author The display freezes (permanently) and the nVidia driver emits a popup in the system tray that the display driver has been reset. P3D has to be forcibly terminated.
February 15, 201412 yr I guess to understand now what you mean. An error occured with your GPU and the driver was successfully reset. The event viewer can give you more details about this error. I run the latest Beta Driver without any problem. Did you monitor the temperature of your GPU? Maybe it gets too hot. Is the power connection to your GPU strong enough? It needs 2 extra direct power cables. Spirit
February 15, 201412 yr Author Nothing terribly informative in the event viewer: "Display driver nvlddmkm stopped responding and has successfully recovered." I run a hardware monitor app...GPU temp hangs out in the low 70's which is nominal for this card. GPU has all the 12 volt rails connected. This system runs Assassins Creed 4 w/ options full tilt like a boss. I've ONLY experienced this problem since upgrading P3D to 2.1 and only in the Carenado. It's very odd...though it looks like the Carenado has "other" issues plaguing it currently so if the end result is that I don't fly this plane, then oh well. Will try latest betas and delete the shader cache next, I guess.
February 15, 201412 yr ..... "Display driver nvlddmkm stopped responding and has successfully recovered." I run a hardware monitor app...GPU temp hangs out in the low 70's which is nominal for this card........ OK, that's the error which I thought and know. I had this with a GTX670 for a while and could cure it with some OC adjusting and tried to be < 60 degrees Celsius My new GPU GTX780 TI is OC too and is only around 59 to 61 degrees celsius even it's said 80 degrees would be ok too. ...... I've ONLY experienced this problem since upgrading P3D to 2.1 and only in the Carenado...... Is this airplane certified for P3D v2.1? Spirit
February 15, 201412 yr Author Is this airplane certified for P3D v2.1? I would hope so It's the one that ships with the sim!
February 15, 201412 yr My new GPU GTX780 TI is OC too and is only around 59 to 61 degrees celsius even it's said 80 degrees would be ok too. I NEVER use the default fan speed. I always run at 60%, 40 to 50c. i doubt that's your problem though?
February 15, 201412 yr Author Unrelated to this issue, I was experimenting with solutions for the "blurries" that have re-manifested with a vengeance in 2.1. In the course of investigating this, I noticed my DPC levels were exceedingly high in 2.1 and seem to be coincidental with the driver pooping the bed and sound stutters. At the recommendation of several people on the P3D forum, I changed my affinity mask to 15 (which is somewhat counter-intuitive considering FSX would rather have Core 0 free). This seems to have been a magic bullet in that it not only removed the blurries, but DPC levels dropped, my sound has stopped stuttering (mostly), and I have yet to experience a driver reset. It's a bit of a loosey-goosey correlation and hardly scientific by any stretch, but I'm hopeful I might yet salvage my P3D experience.
February 15, 201412 yr Hi there, is the Affinity mask =15 standard and in the cfg or does it need to be added? if so where does it go and what do I need to type. Do you think that it will cure my blurries using photoscenery as its got to be worth a try. If not then I think im off back to 2.0 till 2.2 comes out.
February 17, 201412 yr I NEVER use the default fan speed. I always run at 60%, 40 to 50c. i doubt that's your problem though? Why should lower temperature be a problem? I use EVGA Precision for controlling the fans depending on the temperature. Spirit
Create an account or sign in to comment