OOM without "dings"?

[HighBypass 2,339]

According to FSUIPC (registered) this is the VAS remaining (I think!) from the log file.

Minimum available memory recorded was 1219Mb

I'd had the sim running for about 3 hours - Sky Sim MD-11 was at cruise alt, weather was updating with METARs throughout (FSOpen Clouds).

I right clicked on the screen to see what (if any) air traffic was in the sim at the time (stock AI traffic, set at about 60% for heavies)

Then I got the "blue spinning timer donut of waiting".. No dings, no message - I run full screen with DX10 Fixer.

I alt-tabbed to the desktop to see if an error message had popped up. Nothing. Then the MSFS icon in the taskbar vanished, it appeared to have closed without telling me anything.

Could it have been an OOM without any warning? I was just about to save the flight due to real life 😉 (I don't have FSUIPC autosaves enabled).

Win7 64bit Ultimate

i7 950 3GHz processor

24 Gb RAM

nvidia GTX 960 2Gb gfx card

Cheers.

[Bob Scott 7,720]

It's possible.  You get an OOM any time the application asks the OS to allocate it more memory than is available in one contiguous block.  So you could conceivably have 1.2GB free, but fragmented into multiple smallish blocks, and if the program asks for more than is available in any of those blocks, bam, OOM.  But...generally in that case you'd get the "Your program has run out of available memory" popup.

Soooo...sounds more like your basic non-OOM random CTD to me.  You might check the Windows events log to see if there's a clue there.

[HighBypass 2,339]

Thanks, Bob. I've located the event log folder, but I don't know which log from yesterday will tell me anything?

Incidentally I'm repeating the flight and so far I've flown past the area where it happened. However, I was manually saving the flight at short intervals! 

[edpatino 1,964]

If you want to forget about more "dings", I suggest moving on to P3Dv4 or even X-Plane 😁. 64-bits makes a huge difference.

Cheers, Ed