2 hours ago, AJZip said:

I've taken them out again so am back to 32GB.   

Dude! That really stinks.  🙁 

Ive been enjoying this journey AJ and benefiting form your tests! This is truly a kick in the guts! Sorry for your woes mate!

Well, it's always a bit of a lottery with adding ram, even if they are same specs, so in the next week or so I will sell the extra sticks and go for 2x32Gb.  No rush as the two sims are both working well with 2x16's.

Most of the time spent reloading stuff onto the C drive has, of course, been MSFS2020.  Despite my unease about the concept of streaming apps, I'm beginning to see their plus points!  😁

Edited January 20, 20251 yr by AJZip

This reminds me my ordeal of trying to ping down the CTDs I once had in 2020. It appeared to be due to the instability of my video card and took me enormous amount pain and time trying to chase it down. In the end it turned out to be my 16GB x 2 sticks what were slowly going bad. Replaced them with a new 32GB x 2 and all has been good so far. Seems you having the bad luck the opposite way around.. 

Did you try booting up with just the two new sticks? And did you set your bios to default? Some systems hate XMP with 64gb

 

Edited January 20, 20251 yr by HiFlyer

19 hours ago, HiFlyer said:

Did you try booting up with just the two new sticks? And did you set your bios to default? Some systems hate XMP with 64gb

 

No to the first question.  The new sticks purported to be the same make/speed/spec as the existing ones so there would have been no advantage to swop.  I think it was a classic 'PC's don't really like anyone adding extra sticks to an existing set up' case.

Yes - the BIOS was perfectly happy, with all 4 sticks recognised and running OK.  It was Windows 11 that was unhappy.  Out of four attempts at boot up, 3 were extremely long and ended with the Win 11 'Error, trying to fix' followed by the 'Can't fix'; 1 actually booted up fine and I ran MSFS2024 with 64Gb RAM!!  On next boot up, I was back to the Win 11 blocker! 

I took the new sticks out but Win 11 clearly was in a huff and now refused to cooperate at all, just saying 'Can't fix'.  I had a Win 11 Repair/Recovery USB and that booted up OK but - to my surprise - it didn't give the option either to Repair or to 'Reinstall but keep existing files'.  It only gave me an option to 'Reinstall - this will remove all files and folders'.

I'm 7/8ths back to reloading all of my programs and have both sims working at a basic level - it's all those addons with their various quirks/dependencies/tips and tricks that takes the time...much of which is simply remembering what you had to do to get them working in the first place!  😄

 

Edited January 21, 20251 yr by AJZip

Some months ago I also upgraded from 2x16GB sticks to 4x16 GB sticks, system boot succesful, but I dont remember quite, after that problems, or with the sim. Either way: I deinstalled the lot and reinstalled 2x32GB and that is working (most of the time, and problems I had lately are possible yes or no due to this). I thought DX12 would make memory usage better btw.

2 hours ago, AJZip said:

No to the first question.  The new sticks purported to be the same make/speed/spec as the existing ones so there would have been no advantage to swop.  I think it was a classic 'PC's don't really like anyone adding extra sticks to an existing set up' case.

 I was thinking more along the lines of doing this to check if there was a problem with the 2 new sticks

i've had problems running 4 sticks at their xmp settings, where any combination of 2 ran fine on the same PC at the XMP settings. With 4 might just need to detune the wait states a little, or run the PC at a slower clock, like HiFlyer mentioned, if just to test 

1 hour ago, dogmanbird said:

i've had problems running 4 sticks at their xmp settings, where any combination of 2 ran fine on the same PC at the XMP settings. With 4 might just need to detune the wait states a little, or run the PC at a slower clock, like HiFlyer mentioned, if just to test 

Even only 2 at max XMP speeds were a problem, but with the slowest XMP it works at least. Latest BIOS update of course.

11 hours ago, HiFlyer said:

 I was thinking more along the lines of doing this to check if there was a problem with the 2 new sticks

I see where you are coming from. I didn't really think to do that - I'm pretty sure there must be a subtle difference between the two pairs and don't really suspect that there is actually a problem with them as a matched pair by themselves.

I'm struggling through a few weeks of trying to get my Pimax CL to work with MSFS 2024.
My rig:

i9-14900K

95GB RAM (Vengeance)

NVIDIA GeForce RTX 5080

Game Ready Driver 572.70

 

When I attempt to use the Pimax Crystal Light for MSFS 2024, I get a host of problems and an eventual error termination of the program.  DCS works seamlessly and brilliantly.  It's trying to play MSFS2024 that is the issue. 

 

I've dumbed down MSFS 2024 graphics settings to the lowest recommendations on all forums to include the recommended settings on Pimax KB.

The headset only works properly (and wonderfully, I might add) if I CTRL-ALT-DELETE and leave that prompt open.  Which renders the mouse and pointer useless in the simulator.

Then it eventually crashes or terminates with error: The instruction at 0x00007FFD5F4 referenced memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.

 

It's beautiful though, with the Task Manager prompt open.  It's gotta be the 1st prompt too.  Having Task Manager open eventually leads to lagging and crashing.

 

This system is a new build with nothing else running in the background.

 

I'm lost. But your post and thread are shining some light.

57 minutes ago, LazerSlugg said:

I'm struggling through a few weeks of trying to get my Pimax CL to work with MSFS 2024.
My rig:

i9-14900K

95GB RAM (Vengeance)

NVIDIA GeForce RTX 5080

Game Ready Driver 572.70

 

When I attempt to use the Pimax Crystal Light for MSFS 2024, I get a host of problems and an eventual error termination of the program.  DCS works seamlessly and brilliantly.  It's trying to play MSFS2024 that is the issue. 

 

I've dumbed down MSFS 2024 graphics settings to the lowest recommendations on all forums to include the recommended settings on Pimax KB.

The headset only works properly (and wonderfully, I might add) if I CTRL-ALT-DELETE and leave that prompt open.  Which renders the mouse and pointer useless in the simulator.

Then it eventually crashes or terminates with error: The instruction at 0x00007FFD5F4 referenced memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.

 

It's beautiful though, with the Task Manager prompt open.  It's gotta be the 1st prompt too.  Having Task Manager open eventually leads to lagging and crashing.

 

This system is a new build with nothing else running in the background.

 

I'm lost. But your post and thread are shining some light.

Your specs are much better than mine so you should be getting as good or better results.  That said, I've just had a torrid time today after the SU1 update for the VR in 2024 with huge and continuous stutters all day.  This evening, it seems to have settled down a bit so maybe folks round the world downloading and trying out putting a strain on things.

That said, it was a good reminder to me of all the stuff that you have to tweak...and after the update you have to put everything in place again!  I'll give it some thought, look through my notes and post a few suggestions of things to check tomorrow, if that's of any help.

Do you have MSFS2020, by the way?  That is a LOT easier at present to get a decent result in VR at the moment...

Edited March 7, 20251 yr by AJZip

Well, whatever else one might say about MS/Asobo/MSFS etc , there is never a dull moment!  🙂

In the last week, I've porpoised like a rookie pilot on his first lesson from climbs and dives of expectation, happiness, anger, comprehension, bewilderment, confusion, clarity, utter confusion...and ending with the best 3-4 flights so far in MSFS2024 VR with BATC.

In fact... and feel free to bite on a piece of wood to stop the screams while I say it...3-4 flights that were actually subtly but tangibly better than the identical flights I immediately then did in MSFS2020.

There - I've said it.   I'll go for a lie down to recover and then, when I feel better, outline the good, the bad and 'the mind boggles' I experienced, in case they are of any help for other folks also battling in the alien world that is MSFS2024 Flight Simulator...  

Edited March 12, 20251 yr by AJZip

So, "the good, the bad and the mind boggles"...

You know I have to get 'the mind boggles' out of my system first 😄

And I do it, not so much to vent (although, no doubt, I will), but for the reason that this may/does impact on a number of MSFS2024 users.

It is along MS/ASOBO's secret philosophy of "why make things difficult for our customers when, with a little more effort and thought, we can make it *@!**@ impossible for them."

 

To expand.

- MSFS2024 did the mandatory SU1 update

- I allowed a day before trying to boot up to let the round-the-world-simultaneous strain on the networks had settled (TIP - never try meddling with settings in MSFS2020 or 2024 for new stutters and delays within 24 hrs of a major update in either sim.  It is almost always strain on the networks and servers that's causing the issues...)

- Booted up MSFS2024.  All good.  Did a flight in the stock Cessna.  Fine.  Nothing much seemed different, but fine.

- Went to load up the fabulously good Black Square Duke.  Ah...not on the list.  No matter - went into my Just Flight account, redownloaded and all good.

-  Booted up the Grand Duke in VR, had a fly round.  Landed.  All OK

- Booted up BeyondATC.  Restarted the Grand Duke.  'Found' the VR Toolbar (if you are still struggling to get that to work, shout and I'll give some tips that certainly work for me).  But, hang on - no BATC box in the toolbar.

- Reloaded the BATC VRToolbar into my Community folder.  Still no joy.

- Posted on BATC Discord a number of times and, at last, a BATC support guy gave me the vital information.  "For some users, the SU1 update has put the Community folder into a different location.  Check in MSFS2024 Settings where your Community folder has been put."

 

OK - crazy.  But we have a solution.

To misquote an old joke, "Praise the heavens, for it could be worse.  And so I did praise the heavens.  And it DID get worse!"

 

I'll carry on the additional challenges and ultimate solution next post, shortly.

Edited March 13, 20251 yr by AJZip