I have enetered the highmemfix=1 tweak to the fsx.cfg - I will do some test flights shortly. Your tips have been noted, thanks! I will look at them if my next set of test flights turns out negative. To answer some of your questions:CoolP: Nope, flying in full screen. with "screens" I primarily meant the Map screen, the save dialog, that kind of stuff. Concerning the logging tools, I thought Windows would have its own... The stuff that came with my Mac is for Mac OS X. However, a Mac is just a PC with another name, so what works for a normal PC should work for a Mac too, as long as you're running in Windows. Are there any specific programs you'd recommend? skully: nice to know I'm not on my own ;) Of course, having an ATI card and not using ATITools, I can't set the antialiasing to anything different but FSX's default settings. Ramiro: Don't have ENB installed, so that's not going to work for me I'm afraid. I used to have it, but I eventually decided that I didn't find it such a great enhancement. And anyway I'm too lazy and ignorant to make it match my preferences...

From the FSL (Concorde X) forums, full screen isn't recommended as it seems to run into some memory trouble whereas windowed does not in some cases (usually 'high load' from scenery + plane). So maybe you want to test some windowed sessions too and see if it helps on that maybe graphic memory/management trouble. Regarding the tools, Windows (to my knowledge) does not come with things to log e. g. voltages, I think that the Mac tools don't offer this too. That's stuff which needs some sensor to access and then displays some graphs you can follow.You don't actually need to know which voltage is which there, just look out for peaks or large losses when the black screen happens again.If you would then post the actual name of the graph, some hardware savvy surely can help. But in regard to your all-in-one system, the actual countermeasures are very limited of course. If we would e. g. find out that the PCI-E voltage suddenly drops for no reason, we could only tell you to contact your Mac dealer while a normal PC would allow to test e. g. another graphics card or power supply easily. HWMonitor would be a free one, but I don't know if it can access the more uncommon Mac sensors.The purpose would just be to log the voltage stuff in the background while you are flying. If the black screen happens, watch out for some unique changes at that time. With Windows, you can of course log the memory amounts or the threads, which isn't a bad idea too. How much RAM is FSX e. g. using when your black screen happens?

This may helphttp://www.simforums.com/Forums/bios-info_topic39128&SID=754zab25-7312-f41f7bf3-40757-0392476852.html

He's using a iMac so all that BIOS/EFI stuff may be very limited and also should be pre-set to working (stable) values I guess.

Of course, he is too, oh well nevermind. That's what happens when you speed read

highmemfix seems to have solved all the problems. Did a flight with the PMDG MD-11 from EDDF to EHAM without encountering any issues. When I did it yesterday without highmemfix, I encountered problems after 10 minutes or so. So, chapter closed and thanks for the input, guys! That's enough reason for me to go and buy the McPhat MD-11 repaint package that includes the KLM repaint. CoolP: Yes, I refrain from fiddling with EFI and hardware stuff as it will void my warranty. As it is, due to the iMac's design, overclocking and that stuf is also virtually impossible. It is very prone to overheating so any deviations from the recommended settings are like digging your own grave. Julian: I am too what...?

That's great news. Lets hope that the small fsx.cfg fix helps the other guys too.

Anyone got something new on that problem? Since I thought the black screen is a sign of running out of video memory I swapped my video card with a friend, now I have a Club3d nvidia 550Ti with 3072 MB of VRAM (!). After I got that, I decided to give ENB another try.That should kill all lacks of video memory, I thought, but it does not: when using ENB the screen still goes black when trying to enter menus in FS. It also seems that as many people who do use ENB, only very few have these problems I have.

Sometimes I've found just hitting 'Esc' followed by 'Continue flying' is enough to kick-start FSX back to life. I fly full screen and when I want to access the menus I simply tap the Alt key twice to show the menus. Do what I want and then tap the Alt key three times, holding it down on the last press to make the menu bar vanish. This is with Sticky Keys enabled.

Anyone got something new on that problem? Since I thought the black screen is a sign of running out of video memory I swapped my video card with a friend, now I have a Club3d nvidia 550Ti with 3072 MB of VRAM (!). After I got that, I decided to give ENB another try.That should kill all lacks of video memory, I thought, but it does not: when using ENB the screen still goes black when trying to enter menus in FS. It also seems that as many people who do use ENB, only very few have these problems I have.

Well I helped you with your CTD maybe also with this one just sent me an email have something to try for you?

@ awf you have a pm