Here are my last results -TEST SETTINGS:* [bUFFERPOOLS] Poolsize=204800* Latest nVidia Driver = 196.21* no nHancer - default graphic card settings* Antialiasting and Antisotrophic filtering set by FSX* sound settings - lowest possible for my Creative xFi - 16 bit 44100 CD quality* PMDG 747 + EDDF (Aerosoft)+ASA+MyTraffic 2010 (50%)TEST RESULT:On ground in EDDF graphics stable and couple of Alt-Ent did not corrupted the picture...After take off, (few hours later) on route, going in the FSX menus (load flight) brought me directly to the "Black Screen Of Death" without corruptions before that.CONCLUSION:Might be the right track but we are still not there..............

It would be great if this proved to be the answer, but your experience sounds painfully familiar. At the risk of putting a damp squib on the hopes for "Bufferpools" as a fix, I spent ages trying every combination I could think of when I was trouble-shooting this last year. Fiddling with Bufferpools was one of the (many) things which seemed to make SOME difference, but in my experience the only thing which makes the problem actually go away, is to change the sound settings. There may be a "magic number" for Bufferpools - but unless anyone can explain in logic why there SHOULD be a magic number, I doubt it will turn out to be complete fix.I still hope I will be proved wrong, but I honestly think that the sound fix is the only one that is likely to work for the time being, because so far as anyone has been able to find out, the only RELEVANT thing that's changed from XP Pro to Vista/ Windows 7 is the way that sound gets handled in DX9. IMHO this single fact is capable of explaining everything we see with the disappearing textures problem, including why the problem does not arise under XP Pro and why it goes away with the DX10 preview in Vista/ Windows 7. Unless there's an equally plausible reason why the Bufferpools settings, or any other fix, OUGHT to make a difference, then personally I would distrust the solution in principle. Possibly an update to the video driver and/or the sound driver would make the sound play nicely with the graphics. But until that happens - and there's no sign of interest from Nvidia or ATI in such a small market - either your combination of hardware and drivers works properly with the new implementation of DX9, or it doesn't.I mention this because on the one hand obviously we all want to find another solution, but on the other hand this is a well-trodden path and it's easy to waste a lot (and I mean a lot) of time heading down it. Last year I spent hour after hour on the problem, working through it pretty systematically, with notes and so on. There were plenty of times when I thought I'd found a fix. So I would embark on some long-ish flight on VATSIM, only to find that everything suddenly disappeared right at the approach phase, to everyone's irritation. It's great that people are still trying, but they say that repeating the same thing in hope of a different outcome is a sign of madness ...Tim

...a sign of madness ...

Well, Tim you are damn right. I was enjoying my time with XP and FS9 until the new hardware mania hit me and here I am - all set up for hell of a good sim experience however at the end I got BSOD and all this crap... Now, every time my flight gets disrupted in my favorite part - the approach - believe me I am getting really mad. And I start digging all over again in the net just to reach a yet another solution and then to try to implement it in a hope for a good result. Maybe I should scrap the FSX and wait for PMDG and Aerosoft to finish the FS11 somewhere in the unknown future (the last one is my 2010 Christmas wish). Cheers,

I still cannot enter the menus, or change views often. But that is OK. WIth those settings I do not get the textures disappearing as long as I stay out of the menus. The sim runs stable even at lower fps with bufferpools at 300.

The above poster has a great idea. I did a kilobytes to byte conversion. I wanted 200KB (KiloBytes) of bufferpools so that was 204800 bytes. I entered this in and I have not seen any problems just like before, but this may work for others where even with 200 and 300 they were having problems.Try entering this:[bUFFERPOOLS]Poolsize=204800John U.

RJAA-KDFW was noticeably better with these settings, but after landing I taxied to a jetway with no terminal. Just for good measure I ALT+ENTERed and was presented with a glorious black screen. Its a shame, because FSX runs much more fluid in W7. Back to XP64 for the moment....

RJAA-KDFW was noticeably better with these settings, but after landing I taxied to a jetway with no terminal. Just for good measure I ALT+ENTERed and was presented with a glorious black screen. Its a shame, because FSX runs much more fluid in W7. Back to XP64 for the moment....

BlueRidge - what is your personal take on XP64 vs Vista64 Ultimate for FSX/PMDG? I saw definite improvements with this issue when I moved up from XP32 to Vista64 (I still have to be 'gentle' on the alt-enter, though!)...but if I take the 'half-step' back to XP64 (I have a copy of that from MS during an 'upgrade promo' many, many years back), do you think that is superior to Vista64?I guess my concern is that it moving to XP64 will solve the alt-enter Black Screen issue, only to lose quite a bit of overall performance due to lack of DX10 support. :( Thoughts?Cheers!

BlueRidge - what is your personal take on XP64 vs Vista64 Ultimate for FSX/PMDG? I saw definite improvements with this issue when I moved up from XP32 to Vista64 (I still have to be 'gentle' on the alt-enter, though!)...but if I take the 'half-step' back to XP64 (I have a copy of that from MS during an 'upgrade promo' many, many years back), do you think that is superior to Vista64?I guess my concern is that it moving to XP64 will solve the alt-enter Black Screen issue, only to lose quite a bit of overall performance due to lack of DX10 support. :( Thoughts?Cheers!

I would recommend a dual boot with XP64 while things get sorted out with the W7/Vista issues related to this thread. XP64 has has cured texture corruption & black screens in my system, but several months ago was causing CTDs with the MD11X related to my sound card. It now runs solid using onboard sound from the motherboard. Overall I think you could be very pleased in that half step backwards. I have not been pleased running FSX in DX10 so I really dont think you are loosing out in that arena. Although there are a few hardcore DX10ers in the forum.

I would recommend a dual boot with XP64 while things get sorted out with the W7/Vista issues related to this thread. XP64 has has cured texture corruption & black screens in my system, but several months ago was causing CTDs with the MD11X related to my sound card. It now runs solid using onboard sound from the motherboard. Overall I think you could be very pleased in that half step backwards. I have not been pleased running FSX in DX10 so I really dont think you are loosing out in that arena. Although there are a few hardcore DX10ers in the forum.

Dang it, just lost s long reply, no time to retype....the short is, was Black Screening flying CS727-pro in and out of Ord with ChicagoX and MyTraffic when I tried to re-enter from menu.Put FSX.exe in XP-SP3 compatibility mode and could not get it to Black Screen as many times as I re-entered the menu.I'll keep flying and report back, if its anything, though I imagine you guys have already probably been down this route.MOst display settings maxed, NVdrivers, 196.34, Rivatuner - enhanced aplication 4sxAA, 16xAF, Gama Corection and SuperSampling as well as V-sync=on FPS locked at 34.

DX10 is the only solution for me. Nothing else I can do.

Or don't go to Europe!...In 99% of the cases with BSOD the flight was in Europe. Just recently I started flying the rest of the world - guess what - no problems what so ever.... I've been practicing VHHX (Kai Tak by Fly Tampa) landings and no matter the scenery is very populated there was no problems after many landings and then Alt+Ent..

DX10 is the only solution for me. Nothing else I can do.

Same here.

I'm using an eVGA X58 mobo, and it seems that setting the Low Memory Gap to 2GB in the BIOS (I use a 2GB GTX285) and setting max PCIE payload to 4096KB has dispensed with most of the black screen unhappiness. Backing off the AA to 4xS seems to help with the disappearing texture issue, too.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I took the big step backwards to XP64 and have been running FSX for a month now without one problem, I can alt enter, alt tab fly anywhere day, night, dusk no problems at all, I know OS are expensive but for me is was the best solution, I could not stand the black screens and disappearing textures anymore.

I took the big step backwards to XP64 and have been running FSX for a month now without one problem, I can alt enter, alt tab fly anywhere day, night, dusk no problems at all, I know OS are expensive but for me is was the best solution, I could not stand the black screens and disappearing textures anymore.

I wish it were so simple......With XP 64 I get a cream/white coloured window after I use ALT enter a few times (about 10 or so times).The sound keeps going - but you cannot recover the visuals. There doesn't seem to be any texture corruption on the aircraft or scenery with this event.Does anyone have a fix for the cream/white coloured window problem??????If I can fix this problem then I would gladly stay with XP 64.Pete

I get the cream screen occasionally with my xp64 system. Strangely enough, I never had the cream colored window error with xp32, but the move to 64 was worth it because I no longer get OOMs. Anyways, I find I eventually get back the screen by alt entering back to full screen where the screen is blank, and fiddling with the windows key on the keyboard and the fsx task bar icon a few times. It is a frustrating situation, but I ultimately get back to the correct screen.

I wish it were so simple......With XP 64 I get a cream/white coloured window after I use ALT enter a few times (about 10 or so times).The sound keeps going - but you cannot recover the visuals. There doesn't seem to be any texture corruption on the aircraft or scenery with this event.Does anyone have a fix for the cream/white coloured window problem??????If I can fix this problem then I would gladly stay with XP 64.Pete

Have you turned OFF Tooltips within FSX?