@ Loadhaul ,
“The crash tends to result in the GPU crashing (not out of VRAM) indicating multiple warp errors in the event viewer. “
When did you first start getting the WARP errors in your P3Dv5 setup?
Could you do a screenshot of the WARP error information in your most recent crash?
Did you have the same PC setup when you were running P3Dv4?
Were you error free in P3Dv4?
Do you still have P3Dv4 installed?
As for the warp errors, it seems to only happen on severe crashes (maybe 1/10 times) - I think P3D crashes which therefore causes my GPU to throw these errors. The fact that the GPU crashes only sometimes indicates to me that the source is possibly from something else.
From what I remember it was when I installed the Nvidia 452.06 drivers, each driver from then on has been conflictive of this issue as well. At the same time it was when I also installed MSFS 2020. I did try P3D without MSFS 2020 last week - still caused crashing in P3D.
I did have P3D V4 installed and never had a single CTD in the 10 or so months of having it installed on my system. I then completely removed any trace of it and installed P3D V5. I was error free for at least a month in V5 without a single CTD. Then when MSFS 2020 came out I installed it and the Nvidia 452.06 driver and it seemed to of started crashing. It could've been happening a few weeks before that.
The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Graphics SM Global Exception on (GPC 0, TPC 0, SM 0): Multiple Warp Errors
The message resource is present but the message was not found in the message table