Just completed a 1hr flight and a 2hr flight in MSFS2020 with NO issues in VR. Any other game like BF6 etc. run fine . This seems very strange and hard to believe it is not MS2024
You can suspect whatever you want, but if you do not show the requested data, you will never get an analysis or solution.
Simple logic says otherwise. If it was a Microsoft issue, itād be happening to everybody. The issues are happening to a small subset of sim users due to their unique hardware/ software/streaming situation. Xbox and PS5 excluded.
AsoboReport-Crash-1258620687.txt (35.6 KB)
Your logic is wrong. As I stated in a prior post . No other program or games are effected. I can run MSFS2020 in Ultra with NO issues 2 and 3 hrs at a time. MSFS2024 after the SU5 update it crashes just look at all the others that have reported different variations of the same problem. CRASHES. If itās not happening to greatā¦
People who criticize ,only comment and donā't help but hinder should be removed . These forums are for sharing knowledge and experience with others. So if you have a solution please share many would appreciate constructive insight.
You should consider, that only a very few people are reporting crashes compared to the number of users. And you are the only one reporting it for VR. So there is definitely a very rare trigger condition. You are doing or having something very special. An addon, a controller, a hardware component, a driver or something else. You have to identify the trigger condition. Or you have to hope someone else does it for you. The Windows log can help you. In your log above I see a lot of security entries. Security Software is a very good reason for crashes, in particular, if the observed software changes - after an update for example.
I reported this last week:
It would be very helpful if some of the āothersā would pipe up and share details of their crashes in VR. Having followed this thread for a while it seems that there are not many people that are having this problem. I fly exclusively in VR and have not had any CTD problems although I have a G2 headset rather than a Pimax. I know these things are very frustrating but the only way to track them down is to compare circumstances and configurations until you find the common denominator. I feel your pain.
I agree , however itās not just in VR as my quote says itās in 2D also randomly. I have also got the 0x0000005 error along with different errors in the event viewer I have posted here.
Check out the post below:
I can further add to this post that every flight results in CTD , it just takes a little longer at simple airports. It is apparently a memory access violation at the corre rendering engine. With no pressure on VR memory - the sim barely used 12G of 24G available. And it all started with SU5. It is kinda funny to blame it on things other than MSFS2024.
It is kinda funny to blame the MSFS2024, since it works perfect, in particular in VR since SU5. Really a big step forward in terms of smoothness.
I think, this generic statements will not help you. There must be a specific trigger on your system.
I chose to completely reinstall my operating system . I believe it may have been a windows update issue conflicting. Many have had this problem. Since I did there are no issues yet. I am testing the new OS install and using driver 610.47 it seems to be good now. Thanks for your help I will keep you posted. Your effort is appreciated
Thank you!
Yes - it could have been caused either by the Windows system itself or by buggy drivers, which can sometimes conflict after updates.
Thatās why 8 days ago I wrote to you in a private message that I see errors related to the Windows system or hardware (i.e., potentially buggy drivers) and I do not see the issue coming from MSFS itself.
Fly safe.
It is kinda funny to pronounce the program perfect because it works on your system. What is not helpful is their āsupportā which consisted of platitudes about the vanilla state. Well it crashes all the same. At which point they said that that they coulf not diagnose the cause of the crash from the files they requested and wished me good.luck.. obviously no interest in analyzing the true developer level crash dump. Obviously the business.model is not geared towards solving userās problems
But it is even more funny to blame the software, when thousands of users confirm better performance and stability in VR, and only 3 to 5 having CTDs. There is no vote for this thread. 0. Nothing. Maybe you should think about it.
Yeah, thatās what I was expecting. They are limiting the analysis to their software components. External reasons are not covered.
If the problem is caused by the user, it is more or less impossible.
I guess it gives you some sort of satisfaction to misinterpret what is being said with authority. What is caused by the user? MSFS in vanilla state with stock cessna aircraft. Stock airport. Reasonable rig with graphics settings at or below what is reasonable for the system. Stable frame rate (until it is not). A healthy windows system passing all hardware and DISM checks. So come again, what is caused by the user here? The fact that you got lucky and msfs works for you does not mean that it is not a problem for me or that it is a stable system. Neither it means that it is decent for a business to not care about the customer but the business model is such that an individual or small group does.not matter.
And others reported similar problems BTW.
Driver software, security tools, system settings, VR software configuration, background software, ā¦ should I add more? There are a few hundred items, which can cause the MSFS to crash.
But if thousands of users confirm a better performance and stability and only a few report a CTD, it is very unlikely, that the simulator is the root cause. In this case the number of users with issues would be far higher.
Yes, but how many? 3? 5? āRealā bugs have at least 700 votes, the popular ones more than 1000 and the real critical ones 3000. This one has 0.
You have a problem on your system. Believe it or not, it doesnāt matter. You will not get a solution until you find it on your own.
Iām running the almost exact same setup and am currently having amazing performance in VR.
NOTE. Set your DLSS back to K. I have found that using M is unstable for a 4090 card, the M is 50-series specific.