1 hour ago, Rob G said:

It's 1000 watts and it's less than a year old

Most likely not the problem  then. 

Have you checked your X.M.P settings in your BIOS? I was in the same spot with a brand new computer that I spent a ton of money on. All I had to do was disable X.M.P in my BIOS and the CTD's stopped. Apologies if you've already tried this. 

5 hours ago, DylanM said:

Agreed. If it is new and adequate, make sure you have direct power connects from it to the card inputs (not daisy-chained).

1000 watts, less than 1 year old. Direct connected. Lots of other games run fine, including other VR games.

54 minutes ago, Bdub22 said:

Have you checked your X.M.P settings in your BIOS? I was in the same spot with a brand new computer that I spent a ton of money on. All I had to do was disable X.M.P in my BIOS and the CTD's stopped. Apologies if you've already tried this. 

Tried it this morning but it didn't fix anything.

This morning I discovered that ASUS had a BIOS update for my motherboard specifically for Windows 11. I immediately installed it but it also didn't fix the issue, which can occur any time between before even getting to the main screen to 20 minutes.

Some other things I tried today: set affinity so leave out CPU 0 and 1, and set priority to LOW.

UPDATE: The module listed as the problem is WwiseLibPCx64P.dll. Saw some other threads that indicated problem was solved by uninstalling certain programs but I don't have any of those programs installed on my machine. That module is in the Flight Simulator execution folder so it makes me think this is a MSFS issue but then why doesn't everyone have it?

Edited October 28, 20214 yr by Rob G
More info

OK, new information: It seems to be working fine in SAFE mode (MSFS Safe Mode, not Windows 11 Safe Mode).

So I know the first thing to assume is that it's something in the Community Folder. However, prior to now, I had already tried removing all the files in my Community Folder. Is there more than one or something? I read that it could be something in the Community Folder OR a third party add-on. Where do I look for third party add-ons?

At least it's working. Makes it much less frustrating to look for the offending add-on.

UPDATE: Forgot to mention that all of a sudden, when starting the sim, I was told there was a mandatory update of about 40-50Mb. I don't know if that had anything in it to fix my issue or not. My Community folder is empty so I am going to start putting things back one at a time and see what happens. With an empty folder I am running fine in standard mode (no MSFS Safe mode). I will keep reporting in on progress.

Edited October 28, 20214 yr by Rob G

Well, actually it has become hit and miss. The sim will come up several times in a row with a mod in the Community folder and then suddenly it won't come up at all if I don't remove it. I tried having the sim come up on my other monitor for convenience and it would CTD the minute I started it. That's a weird one, both of my monitors are high quality ones.

So...... still trying to figure out root cause of all this but today's mandatory update didn't completely fix my issue but it seems better a little at least. 

Someone posted on Facebook this morning that on Xbox they are getting crashes every 15 minutes. Someone else posted that Market place purchases were the likely cause, and they should uninstall them until they find the cause of the crashes. This started happening after the last update. You might want to remove all your market place purchase which are not in the community folder, and see what happens. . 

Edited October 29, 20214 yr by Bobsk8

I seem to have resolved the issue for me. The sim is running very nicely, on Windows 11. I don't think it was any one thing. Let me tell you what I have ended up doing:

• Updated my ASUS ROG MAXIMUS Hero XII (WiFi) motherboard BIOS with an update that says it is specifically for Windows 11 support.
• Found out that FLYTAMPA had several updates to the Las Vegas package since I bought it so I updated to the latest.
• Turned off XMP in my BIOS
• Set the sim priority to LOW and removed two CPU's with AFFINITY for the sim

Of course I have no idea if some smaller collection of things would have resolved the issue but it's running really nicely now, including in VR with my Quest 2 using Airlink, so I am done fiddling around with it. I know nothing about flying and am looking forward to finally starting to take the tutorials and and get myself up the learning curve so I can do more than just take off and fly around the origin airport, then crash trying to land LOL.

A huge thanks to everyone for making so many suggestions and pointing me to great threads to read other suggestions;. I would never have gotten to this point without it.

Happy Flying :-).

 

58 minutes ago, Rob G said:

I seem to have resolved the issue for me. The sim is running very nicely, on Windows 11. I don't think it was any one thing. Let me tell you what I have ended up doing:

• Updated my ASUS ROG MAXIMUS Hero XII (WiFi) motherboard BIOS with an update that says it is specifically for Windows 11 support.
• Found out that FLYTAMPA had several updates to the Las Vegas package since I bought it so I updated to the latest.
• Turned off XMP in my BIOS
• Set the sim priority to LOW and removed two CPU's with AFFINITY for the sim

Of course I have no idea if some smaller collection of things would have resolved the issue but it's running really nicely now, including in VR with my Quest 2 using Airlink, so I am done fiddling around with it. I know nothing about flying and am looking forward to finally starting to take the tutorials and and get myself up the learning curve so I can do more than just take off and fly around the origin airport, then crash trying to land LOL.

A huge thanks to everyone for making so many suggestions and pointing me to great threads to read other suggestions;. I would never have gotten to this point without it.

Happy Flying :-).

 

Glad to hear that you have solved your problem, and interesting to hear how.  

2 hours ago, Rob G said:

I seem to have resolved the issue for me. The sim is running very nicely, on Windows 11. I don't think it was any one thing. Let me tell you what I have ended up doing:

• Updated my ASUS ROG MAXIMUS Hero XII (WiFi) motherboard BIOS with an update that says it is specifically for Windows 11 support.
• Found out that FLYTAMPA had several updates to the Las Vegas package since I bought it so I updated to the latest.
• Turned off XMP in my BIOS
• Set the sim priority to LOW and removed two CPU's with AFFINITY for the sim

Of course I have no idea if some smaller collection of things would have resolved the issue but it's running really nicely now, including in VR with my Quest 2 using Airlink, so I am done fiddling around with it. I know nothing about flying and am looking forward to finally starting to take the tutorials and and get myself up the learning curve so I can do more than just take off and fly around the origin airport, then crash trying to land LOL.

A huge thanks to everyone for making so many suggestions and pointing me to great threads to read other suggestions;. I would never have gotten to this point without it.

Happy Flying :-).

 

I will bet the Fly Tamp update is what caused your problem. I had one livery that needed an update  that CTD my MSFS every time I tried to start a flight.