Obligatory note, the access violation appears to have come from a call to a PhysX function. Access violations tend to be a big sign of the possibility to attempt to write to other RAM addresses. Normally this is prevented by modern technologies such as ASLR and DEP, but there are ways around those protections. Due to Visual Studio indicating it's from ProjectionPlaneProperty, it looks like it could possibly be exploited by a malformed input file. I would have to do more research to confirm my suspicions of being exploitable, but I figured I'd file the bug report now so that it can be fixed more quickly.
This is a duplicate of issue 10790, I only saw that after posting this. i am not going to post the same level of info there that I did here because of the security aspects involved.