Thanks again Jay for your diligence in coming up with this solution in the first place. If things work out (based on some add'l testing) I plan on buying the MD-11 for FS-X too.... :( BTW, which version of nHancer are you using with the 182.50 drivers??Phil R.

Phil,I'm using nHancer v2.51.I cannot recommend the MD-11 strongly enough. It is simply the finest a/c available for FSX, IMHO. You won't be disappointed, and with the sound quality fix working I haven't had so much as a hiccup on any flight since. It is pure joy.So, keep testing, yes, but now just have fun flying your Queen.Happy Flying,Jay

Phil,I'm using nHancer v2.51.I cannot recommend the MD-11 strongly enough. It is simply the finest a/c available for FSX, IMHO. You won't be disappointed, and with the sound quality fix working I haven't had so much as a hiccup on any flight since. It is pure joy.So, keep testing, yes, but now just have fun flying your Queen.Happy Flying,Jay

Jay:Finally completed the EGLL-KLAX flight late last night... again, no problems at all. I used the "instant replay" feature quite a bit at the end and alot of "ALT-TAB" and I could not reproduce any of the previous problems. Tonight's assignment is: install and configure nHancer and another flight (probably KLAX-KJFK) and see how it goes...You da man!!Phil

Thanks to the folks on this thread for isolating the problem with the blank screens and corrupted textures to Sound/DirectX! THis issue has been driving me completely bonkers over the last 6 months :( Unfortunately I can't lower my sound quality below 16 bit and 44khz and I have a Creative X-Fi Gamer card. I tried the Creative Alchemy option that was suggested. It works except instead of corrupt textures now I consistently get a blue screen for "page fault in non paged area" when running FSX with PMDG 747! :( Has anyone else seen this behavior when trying this fix?So far the only thing thats working for me is to disable the X-Fi card and use the built in motherboard sound (realtek HD audio codec). No blue screens or corrupt textures (yet) but I notice that FSX stutters noticeably more than before.System Specs-WIndows 7 RC1 64 BitGigabyte EX58-UD4P motherboardIntel Core I7 920 (OC'd to 3.52 Ghz)Patriot DDR3 1600Mhz 12GB RAMWD Velociraptor SATA2 350GB drive (exclusive for FSX)EVGA GTX 260 Core 216 graphics (896MB) ThanksSk121_2000

Jay:Finally completed the EGLL-KLAX flight late last night... again, no problems at all. I used the "instant replay" feature quite a bit at the end and alot of "ALT-TAB" and I could not reproduce any of the previous problems. Tonight's assignment is: install and configure nHancer and another flight (probably KLAX-KJFK) and see how it goes...You da man!!Phil

As a last ditch effort to be able to fly my 747x on my new i7 system I have purchased a copy of windows xp 64 I am going to partition my drive and set up my sim and addons the same as my vista setup and see if the problems go away. If so, then I will abandon vista completely for flightsimming. I have read that none of these issues are problems with xp 64. I will update once I have everything set up. I purchased a full copy of XP 64 for $60 hope its not money wasted...Guthrie Zuehlke

As a last ditch effort to be able to fly my 747x on my new i7 system I have purchased a copy of windows xp 64 I am going to partition my drive and set up my sim and addons the same as my vista setup and see if the problems go away. If so, then I will abandon vista completely for flightsimming. I have read that none of these issues are problems with xp 64. I will update once I have everything set up. I purchased a full copy of XP 64 for $60 hope its not money wasted...Guthrie Zuehlke

Just an fyi I run XP-64 and experience black screens and white screens. I am not trying to be negative just making a statement that XP is not the be-all and end- all. However XP is superior to Vista in regards to general stability and I have far fewer problems with XP-64 than I did with Vista ultimate 64. I can also add that when a problem does stike I am not scratching my head wondering if it is a Vista issue or some other issue.

Hi, I switched to XP64 recently, and I am having a problem with the PMDG or any aircraft that I never had with XP32. When I alt tab to another application and try to come back to FSX in Full Screen mode, the screen is all white. Most of the time, and with a little patience, I eventually get back the full screen session by playing with the windows keyboard button or alt-return a few dozen times, and it seems it is based on pure luck. But this is very frustrating for me, since I need to view external apps like firefox or navigraph for airport charts or consult weather info directly from Active Sky Advanced. Hence, remaining in full screen mode for the entire flight is not an option. Nvidia driver is 182.50 and the latest Nhancer, FSX and XP64 are tuned per NickN's suggestions. I also have turned off tooltips and alt return between full screen and windowed mode doesn't help.Like I said, XP32 never exhibited this strange phenomeon. I switched to XP64 to get rid of the OOMs, and for that alone I'm grateful I made the switch. But it stinks that I have traded on problem for another :( Is this screen whiteout issue in XP64 related to what is being discussed in this thread? Or is what you all describing texture corruption i.e. panel or aircraft textures missing during flight?My full post in the FSX forum on what I'm experiencing and my current setup: http://forums1.avsim.net/index.php?showtopic=252653Thanks for your attention, I wish you luck in finding a solution

Hi, I switched to XP64 recently, and I am having a problem with the PMDG or any aircraft that I never had with XP32. When I alt tab to another application and try to come back to FSX in Full Screen mode, the screen is all white. Most of the time, and with a little patience, I eventually get back the full screen session by playing with the windows keyboard button or alt-return a few dozen times, and it seems it is based on pure luck. But this is very frustrating for me, since I need to view external apps like firefox or navigraph for airport charts or consult weather info directly from Active Sky Advanced. Hence, remaining in full screen mode for the entire flight is not an option. Nvidia driver is 182.50 and the latest Nhancer, FSX and XP64 are tuned per NickN's suggestions. I also have turned off tooltips and alt return between full screen and windowed mode doesn't help.Like I said, XP32 never exhibited this strange phenomeon. I switched to XP64 to get rid of the OOMs, and for that alone I'm grateful I made the switch. But it stinks that I have traded on problem for another :( Is this screen whiteout issue in XP64 related to what is being discussed in this thread? Or is what you all describing texture corruption i.e. panel or aircraft textures missing during flight?My full post in the FSX forum on what I'm experiencing and my current setup: http://forums1.avsim.net/index.php?showtopic=252653Thanks for your attention, I wish you luck in finding a solution

The release notes for Nvidia drivers* warn about using Alt+Tab. Use Alt+Enter instead.*This particular note has stopped getting printed in the Release Notes for the latest few sets of drivers, but I don't think's it's because Nvidia has found a fix.Tim

The release notes for Nvidia drivers* warn about using Alt+Tab. Use Alt+Enter instead.*This particular note has stopped getting printed in the Release Notes for the latest few sets of drivers, but I don't think's it's because Nvidia has found a fix.Tim

Thanks for the advice. I'll try using alt return from now on. But I'm still curious why this is happening to me in xp64 vs xp32, I'm so used to alt tabbing

I do NOT recommend the use of Alt-Tab when running FS full screen. This isn't just an FS thing either - there's a lot of games that screw up when you try to task switch like that out of a full screen 3D accelerated environment into a 2D desktop one and back. What you should actually do if you need to change a setting elsewhere (Active Sky etc) is use Alt-Enter, this switches FS between full screen and windowed mode. Put it into windowed for a second, do what you have to do, then hit Alt-Enter again to go back to full screen. This has never caused a crash or corruption issue for me across 3 different systems using both ATI and Nvidia cards.I tend to use my Macbook sitting next to me btw to load up charts, weather imagery etc while flying on the main desktop PC in fullscreen. Good use of the laptop if you have one and it'll keep the need to switch between full and windowed to a minimum.

Thanks for the advice. I'll try using alt return from now on. But I'm still curious why this is happening to me in xp64 vs xp32, I'm so used to alt tabbing

To add, this happened to me as well in XP32 using ATI cards running in SLI mode. It is an issue with FSX and video drivers. As Ryan has suggested using alt enter works better, but I minimize using it as much as possible.

usmc3073 & GaryA & hombrexp,The following may help you as I have had exactly the same white screen problems on XP64.I hope this is not another "false dawn" but it may be worth a shot as it worked for me.Here is what I found:Conditions:Same hardware as signature below except Windows XP x64 SP1 instead of Vista SP2.FSX + AccelerationOnly Addons:PMDG 747x & MD11REXLoaded saved MD11 flight.Noticed that time to switch between windowed and full screen (note: Alt + Enter not Alt + Tab) is noticeably slower than Vista.After about 5 or 6 switches between windowed and full screen the window/display went white but the sound continued.Absolutely no corruption of textures just a white screen instead of the black screen.Could not get display back no matter what I did.Then I shut down FSX.Restarted FSX and created a saved "default flight" - Cessna at Seattle.Loaded the saved "default flight" - Cessna at Seattle.Then loaded the presaved MD11 flight on top of it.Flew entire flight without any problems at all.Did many switches between full and windowed modes and accessed the menus many times which would normally cause the problem.Also did the same flight in the 747x (after loading the saved "default flight") which always caused the same problems however this performed flawlessly as well.Also found that frame rates were higher in XP 64 rather than Vista 64.Overall performance was better and smoother.Hoping it's not another false dawn.....PetePS I tried using the DirectX fix in XP64 of lowering the hardware sound acceleration but this did not fix the problem. I also could not find any settings in XP 64 that would allow me to lower the sound settings to say "16bit, 8000 Hz telephone quality" as one can in Vista.

Further to the above.I performed the same flight and it all went without a problem after many switches between full and windowed modes and accessing the menus many times. There were no white screen or any other problems.However, this time I tried instant replay at the end of the flight and the corrupted scenery textures and missing aircraft parts occured.This is the only time I have seen the problem of corrupted scenery textures and missing aircraft parts in XP64.I will try the same flight by using the DirectX fix in XP64 of lowering the hardware sound acceleration to see if this fixes the instant replay issue.Regards,Pete

Have tried the same flight by using the DirectX fix in XP64 of lowering the hardware sound acceleration to see if this fixes the instant replay issue.Again flight went without a problem. No white screens.Instant replay worked for 5 times but then on next instant replay, got the problem of corrupted scenery textures. Not recoverable.Out of ideas for the time being on the instant replay problem.Pete

So here's what I've found. I can't alt/enter anymore... wierd because I used to be able to. If I play around with the alt/tab/task manager enough I can eventually get back into full screen mode. I still get disappearing textures occasionally. I've found that if I exit FSX and restart it, 99% of the time it reloads ok. Lastly, I occasionally get CTD in the middle of long flights when in 8x time and switching views :D but sometimes even in normal speed.

Thanks for the followup. I will try loading the default flight with a default a/c next time around. I understand the nvidia recommendation of the use of alt return before task switching, but I was able to do the good old alt tab without concern hundreds of times in XP32 during long flights without the dreaded white screen, using the same driver 182.50 (albeit the 32 bit version).For me, XP64 and maybe a quirk with the Nvidia drivers for 64 bit may be the problem for me, but I can live with it. Thankfully, I never get corrupted panels or such, and I rarely use instant replay at the end of the flight since I only use FSRecorder and I view that replay after shutting down FSX. One more note, the white screen happens for me regardless of aircraft type after too many switches between apps. I frequently slew around in the default Trike Ultralight while making afcad edits or updating Ultimate Traffic 2 repaints live in FSX and get the white screen after too much usage, the system gives up. So for me, it doesn't seem to be particular to the PMDG a/c. During normal flights, it will rear its ugly albino head after a while and I have to pause the flight and jiggle my way back with the windows button and the taskbar. Its extremely annoying, but I guess I'll have to alt return from now on...FSRecorder is a nifty app for FSX or FS2004 because it records many more parameters for replay, even the AI aircraft movements! And it has tons of replay options and different methods of moving forward or backward, with NO time limits for replay length. I suggest you try it out at http://www.fs-recorder.netYou will never use the built in FSX instant replay ever again.