I agree with what you are doing, but I hate that you have to.
I wanted to test the sim in its default state so that LM can't pass the blame onto others. On many of their replies on other posts they refer people to a general debugging url with the usual questions about having an up date OS and drivers and then discuss what add-ons you are running. If the sim crashes with no add-ons installed then the problem more than likely is the sim. You maybe right about shadows, my crashes occur mostly and dusk or night time. Ive never tried a flight with shadows all switched off...wouldnt want to have the sim without them anyhow though to debug maybe worth a test.
At first I thought my GTX 980 was not up to the task, but when I saw 1080ti's with the same error, I thought not again, not another plague like OOM to destroy.
64 bit came so we could raise the sliders, but here we are again. (I realize not everybody has this issue currently)
I personally push the limits settings wise and lock frames at 20. I also likely fly much more often then most others usually have the sim running constantly depending on flight lengths, etc. Currently flying PMDG 777LR from EGLL (Aerosoft) to YMML (Orbx) and almost 9 hours in its all smooth and pegged at 20. But the fact that I/we have to be concerned about this DXGI bologna ever since version 4.3 (note that the first post here was 4 days after 4.3 was released and NVidia gets blamed w/o doubts or questions), reminds me of OOM all over again.
For me lowering the sliders prevents this error (specifically tessellation, shadow distance, and auto gen distance). I always use the latest graphics driver, so to me this is not specifically a graphics driver issue.
The only wild guess I have is that P3D is asking the grahics engine something the wrong way or mixing too much old with new tech. Performance wise 4.3 is very excellent, but it may be achieving this excellent performance with some method that compels the sys to call foul......again a wild guess from one w/o knowledge of such details.
I dont want to do this but I'm going to have to pray that some P3D users who are PC gurus or Elaine or other LM staff get this error because, I can see it now, version 4.4 comes out and everybody gets the error all the time. Thats how it happend with OOM - a few (myself included) were getting OOM's then eventually a runaway plague.