For those of you who are running Win7, I just came across this topic.. I haven't tested it yet, so I can't comment yet on my results:http://forums1.avsim.net/index.php?showtopic=275986

For those of you who are running Win7, I just came across this topic.. I haven't tested it yet, so I can't comment yet on my results:http://forums1.avsim.net/index.php?showtopic=275986

I've tested it and for me worked (so far). I will continue to stress and bravely Alt+Ent my flights... Will report in a few days.Heads up to ******* for the provided solution!

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.

Did the same as you, and XP 64 truly is the ultimate fix for FSX. FSX just runs better on XP, period, no need for workarounds, is works great, and like it is supposed to. The only way I can mess up FSX in XP is if I overstress my system, where if I overload the thing with AI planes, I can occasionally create OOM errors, or if I somehow get the GPU to overheat, I can get the nVidia driver to crash, and XP does not reload the driver like Vista can.And the only handicap to XP 64 is that MS SAPI (which is used for VOX ATC, Its Your Plane, and the new FS2Crew 2010 series) is not officially supported, but I can verify that it still does indeed work as intended, so really if you have a copy or can still find a copy of X x64, switch, you will not be sorry.

Did the same as you, and XP 64 truly is the ultimate fix for FSX. FSX just runs better on XP, period, no need for workarounds, is works great, and like it is supposed to. The only way I can mess up FSX in XP is if I overstress my system, where if I overload the thing with AI planes, I can occasionally create OOM errors, or if I somehow get the GPU to overheat, I can get the nVidia driver to crash, and XP does not reload the driver like Vista can.And the only handicap to XP 64 is that MS SAPI (which is used for VOX ATC, Its Your Plane, and the new FS2Crew 2010 series) is not officially supported, but I can verify that it still does indeed work as intended, so really if you have a copy or can still find a copy of X x64, switch, you will not be sorry.

While that may be the ultimate fix for you. If you use windows 7 64bit and don't want to have to go back to XP then run it in Vista SP2 compatibility mode. I didn't think it would work because I had the same problems on vista before I switched to Windows 7, however on my machine this has eliminated ALL black screens and corrupted textures even when I deliberately attempt to cause them. I heard someone before say to run it in XP compatibility mode but that doesn't work for everyone as if you have FSDreamteams scenery's they do not work and FSX will not even start. If you are having these problems on windows 7 at least try running in Vista compatibility you might be surprised. My Specs:Intel i7 920 @ 3.75EVGA X58 SLIGeForce GTX 2606Gb Ram @1600Nick

Did the same as you, and XP 64 truly is the ultimate fix for FSX. ......................

Scott,I have XP 64 SP2 as you do but, as I have posted before, I get the cream screen of death (CSOD) after I alt-enter a few times.Sometimes I can recover, other times I cannot.Can you please post your full system specs - eg motherboard brand and sound setup (onboard or dedicated sound card) and video card driver version?Also, did your XP 64 version come with service pack 2 on the disk or did you get SP2 via microsoft update?thanks,Pete

Scott,I have XP 64 SP2 as you do but, as I have posted before, I get the cream screen of death (CSOD) after I alt-enter a few times.Sometimes I can recover, other times I cannot.Can you please post your full system specs - eg motherboard brand and sound setup (onboard or dedicated sound card) and video card driver version?Also, did your XP 64 version come with service pack 2 on the disk or did you get SP2 via microsoft update?thanks,Pete

Pete, your XP-64 must have SP2 on it or else you must slip-stream SP2 on it at time of install. Do not install SP2 through Windows update as this method may not properly update.I think I had the CSOD before too and if not mistaken I think reinstalling the video driver cured it. Not sure what video card you are running but if Nvidia use driver 182.5 I also have my system set up per this link using Nhancer: http://www.simforums.com/forums/forum_posts.asp?TID=29041 I have not had an issue for over a year.

Pete, your XP-64 must have SP2 on it or else you must slip-stream SP2 on it at time of install. Do not install SP2 through Windows update as this method may not properly update.I think I had the CSOD before too and if not mistaken I think reinstalling the video driver cured it. Not sure what video card you are running but if Nvidia use driver 182.5 I also have my system set up per this link using Nhancer: http://www.simforums.com/forums/forum_posts.asp?TID=29041 I have not had an issue for over a year.

Gary,Thanks for the reply.I have XP x64 with SP2 on my system but I can't remember if I got to SP2 through Windows update or off the disk.Is there any way of telling from the disk contents?I am indeed running an Nvidia 8800 GTS with the good old 182.50 drivers but I have not tried a reinstall of the video drivers.I will give that a try.Thanks,Pete

I have tried everything, Still get black screens.

Gary and all,Tried the re-install of the video drivers using driver sweeper to remove them and then installed 182.50 as per Nick N's process and set up nHancer.Still getting the CSOD in XP 64.Gary, do you use "heavies" such as PMDG 747/MD11?Also, is your system overclocked (mine is)?Pete

Hello Jay. I'm glad someone else's PC has got the same "sound" quirk as mine but we're not really further forward towards a solution.I'm not sure we can exclude the graphics driver. I updated to the 185.85 driver today. This does NOT cure the problem, but the behaviour is slightly different: when switching from windowed to full screen mode with sound "on", I get a different sort of distortion from before: instead of the mucky background textures mixed with black etc, the whole screen flashes wildly mostly in black. But if this is a graphics driver issue, I don't understand why more people don't see it.Are you using a TV screen on HDMI? Or a monitor on DVI? Or a monitor on VGA?Tim

hi, do you still have the problem if you run fs in windowed mode. jim

It really seems like this thread is going backwards instead of progressing. Check out Page 14 and 15 for possible solutions or look here: http://forums1.avsim.net/index.php?showtopic=271292I really don't recommend using Bufferpools=0, because it causes a very ride range of results since a bufferpools of 0 varies from system to sytem and causes weird texture/scenery glitches where you'll see objects like buildings and trees in the air for a split second at times and it causes a massive stutter. It's just my opinion though, nobody is stopping you, but I have used 500KB for a long time and it has given me no problems. The game is actually a bit smoother, and the poolsize is still large enough to keep small textures and geometry (Think of bufferpools as form of geometry instancing: http://en.wikipedia.org/wiki/Geometry_instancing ) in memory and not cause graphical glitches/problems. I recommend that you read the whole thread that I linked at the beginning of the post ( http://forums1.avsim.net/index.php?showtopic=271292 ), and especially check out the latency post I made and the last post in the thread made by me. The results show that a bufferpools of 0 caused higher latency on one system than a bufferpools of 500KB, and one person a long time ago reported that when you set the latency of his memory in tune with his system, the graphical glitches went away. So it may be better to use 500KB than 0, because a bufferpools of 0 is not really a poolsize equal to 0, it is undefined.John U.

Gary and all,Tried the re-install of the video drivers using driver sweeper to remove them and then installed 182.50 as per Nick N's process and set up nHancer.Still getting the CSOD in XP 64.Gary, do you use "heavies" such as PMDG 747/MD11?Also, is your system overclocked (mine is)?Pete

Pete, make sure the disk cover or jacket says with SP2 or makes reference to SP2. Mine says "Includes service pack 2." I do not know how else to tell.I fly almost exclusively PMDG MD11, J41, 747 with heavy scenery UTX ASA Scenery Tech Genesis, GEX, FEX e.t.c. sliders right of center not maximum by any means. I am on a QX6700 @ 2.94 8800GTXI don

Pete, make sure the disk cover or jacket says with SP2 or makes reference to SP2. Mine says "Includes service pack 2." I do not know how else to tell.I fly almost exclusively PMDG MD11, J41, 747 with heavy scenery UTX ASA Scenery Tech Genesis, GEX, FEX e.t.c. sliders right of center not maximum by any means. I am on a QX6700 @ 2.94 8800GTXI don

Update:Tried all the above and sfc/scannow and disabled physics.Still get CSOD.Pete

Gary,Re CSOD problem......I noticed that my version (FSX Acceleration) is 10.0.61637.0 .Yours is 10.0.61472.Could this be a factor in the CSOD problem??I have also uninstalled and re-installed the 182.50 drivers using Driver sweeper and nHancer as per NickN - same problem.I have also uninstalled and re-installed the latest drivers using Driver sweeper and nHancer as per NickN - same problem.I also get the problem with or without FSInn running.If I just stay in full screen mode (or windowed mode) at all times the problem doesn't arise, but it is unrealistic never to get out of full screen mode during a long flight.Also windowed mode has problems with the jaggies - full screen is by far the best.Perhaps it is time for a change to the latest ATI cards.Has anyone with ATI cards on XP64 experienced the CSOD??Pete