This is a tough one, we’ve touched on most of the environmental issues that come up, and the nvwgf2umx error is usually purely graphical in nature. Is it still referencing the nvwgf2umx.dll for every error? (The memory location may change but that doesn’t matter since we have no frame of reference where they get assigned at runtime). There’s got to be something going on driver side if every project crashes in 5.0. Just hard to pinpoint where and why.