Like many, I’ve been so frustrated with the CTD since the release of the VR version. My sim crashes only in VR mode with Reverb G2. I’ve done all the tricks and fixes presented on this forum and had given up.
I learned that VCRUNTIME140 error is actually CPU related and not my GPU although I get driver timeout. What happens is that CPU crashed and is no longer able to send frames to render, and GPU times out and shuts down the app to avoid BSOD or system crash.
So I decided to check the stability of my system. I run a mild 5.0Ghz overclock with XMP profile and tried removing both the OC and XMP to make sure that it wasn’t the overclock that is causing the issue. Running Linpack Extreme (Intel’s Math Kernel Library), I found out that my stock frequency was not stable with my manual voltage. It will spit out wrong residual values every loop. Now, it’s almost impossible to get 20 loops of matched residuals, but a stable system should be getting most of the calculations right. I had to adjust my VCORE and VCCIO/VCCSA (System Agent Voltage) to get the system stable.
I flew 5 or so 1-2 hour long flights (my system always CTD around 45 minutes or less) and have not crashed yet. I still believe the sim itself is extremely sensitive to any instability, overclock and crashes more than any other apps/games, but for the first time, I am beginning to enjoy the VR experience without crashing every single time.
Check your system with Linpack Extreme or IntelBurn, and see if your system will get most of the calculation right. Make sure to choose the 10GB data set and run about 10-20 loops to see if the residuals match. If you get hardware error, that’s a no-no. If your residuals are all over the place, you may want to adjust your oc or voltage (as XMP is overclocking and can create a big instability issue if the SA voltage is not sufficient).
