VR CTD

[njflyer]

Hi all,
I am getting constant CTD in VR lately, it seems that whenever I use a complex addon at a paywayre airport (FSL A320 and UK2000 EGKK for example). VR was stable for a while, the only changes I have made is installed more airports to my P3D install.
I tried everything I could think off, reduce the sliders, etc. Even with default settings, I still get VR to crash constantly. I am running out of ideas, but needless to say it's super frustrating. I dont experience and CTD whatsoever with any other sims (MSFS or XP11, which are set up with settings on high).
I even re-installed the client yesterday but no luck. I can see major stuttering going on while in VR, and after a while I get a CTD. VR is stable with default aircraft...

My system specs are:
i9-10900K (default settings, no OC)
32GB RAM
SSD Drive
RTX3080

[njflyer]

I forgot to include the event viewer log:

Faulting application name: Prepar3D.exe, version: 5.2.22.27615, time stamp: 0x60db69bf
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x1600
Faulting application start time: 0x01d78585d5f94893
Faulting application path: D:\Program Files (x86)\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: unknown
Report Id: b69a2db8-2966-4ccb-b4bf-93a296f90797
Faulting package full name:
Faulting package-relative application ID:

my VR headset is a Reverb G2
Thank you in advance!

[njflyer]

it would be nice to get a response from LM, I am at a stage where VR is pretty much unusable with complex paywayre like FSLabs. This used to work and was stable, is anyone else getting stability issues in VR with 5.2?

[truthknown]

I used to get a lot of the same errors with FSLABS. Not necessarily with VR but sometimes while in VR. Now i keep getting BSODs which I think is truly a cooling problem in my rig. FSLABS is very demanding on the system, especially combined with high P3D settings and VR.

Do you happen to use RTSS? Using scanline sync to limit my framework was the cause of numerous problems with FSLABS. I moved my limit to the framerate limit box instead and a lot of problems went away.

Chris

[JorgenSA]

As described in many threads before, when you see this in an Event Viewer report:

Exception code: 0xc0000005

then you are looking at "something" that is trying to write to an area of RAM where it has no access rights - VR or no VR.

This "something" has until now, with P3D, always turned out to be an incompatible or badly programmed add-on.

Jorgen