I recently stated a message saying that I was having the dreaded blurries with Ground Environment. I got some great help and decided to make the adjustments that were reccomended. I defragged and tuned down my autogen density. However, now I get a problem where when on the ground (I was flying KLAX-KSFO via LDS 767 w/AS2006, UT and Radar Contact) that my screen goes black. It is not like a crash to desktop where MS flashes off and goes to DT. With this, the screen goes black. I can still hear my ac and can still access the menu bar. Soon after I get the message that FS9 encountered a serious problem and it forces me to restart FS. I have a Dell 8300 xpp h8/3.0 1gb ram, 40gb hd and a Nvidia Geforce 6800gt 256mb video card. I ran FS Manager to see if I had any scenery errors and I did not. I also ran it and found a few duplicate textures, yet those have been there in the past. So do you have any suggestions? These are the things that I think could be the problem:-Video Card driver problem? Which driver would be the best for this card?-I changed my startup from the Cessena at KSEA to a Cold/Dark 767, eliminating the need to load with the Cessena, shut it down and boot the 767. I heard that might cause problems. -While trying to add the latest update to GE, I get a message saying "startup error, problem occured because of missing media folder content". - I manually installed the second update as noted in the text, but I get this message when trying to load the update with the installer. -Some sort of corrupted file that some how got in my system-Bad luck!Any suggestions would be great. Here is my FS9 Config:FULL_SCREEN=1PERFORMANCE_MODE=0DEF_PERF_MODE=6TEXT_SCROLL=1AUTO_LOD=0DETAIL_TEXTURE=2WATER_EFFECTS=1TERRAIN_USE_VECTOR_MAP=1TERRAIN_USE_VECTOR_OBJECTS=1EFFECTS_QUALITY=2GROUND_SHADOWS=1SMOOTH_VIEW=1IMAGE_SMOOTHING=1TEXTURE_MAX_LOAD=1024COCKPIT_HIGH_LOD=1AIRCRAFT_SHADOWS=1LANDING_LIGHTS=1IMAGE_QUALITY=1TEXTURE_BLDG=1TEXTURE_GND=1TEXTURE_WATER=1AIRCRAFT_TEXTURE=2SEE_SELF=1TEXTURE_QUALITY=3LOD_TARGET_FPS=21NUM_LIGHTS=8UPPER_FRAMERATE_LIMIT=30TEXTURE_BANDWIDTH_MULT=400TERRAIN_ERROR_FACTOR=100.000000TERRAIN_MIN_DEM_AREA=10.000000TERRAIN_MAX_DEM_AREA=100.000000TERRAIN_MAX_VERTEX_LEVEL=21TERRAIN_TEXTURE_SIZE_EXP=8TERRAIN_AUTOGEN_DENSITY=5TERRAIN_USE_GRADIENT_MAP=1TERRAIN_EXTENDED_TEXTURES=1TERRAIN_DEFAULT_RADIUS=9.500000TERRAIN_EXTENDED_RADIUS=4.500000TERRAIN_EXTENDED_LEVELS=1IMAGE_COMPLEXITY=5DYNAMIC_SCENERY=1DYN_SCN_DENSITY=5DAWN_DUSK_SMOOTHING=1SUNGLARE=1LENSFLARE=1

Try doing a complete Reinstall from the downloaded Wrapper file, making sure that the destination folder is recognised. You may want to download a fresh file, just to make sure.Alastair

I tried that as well. I uninstalled GE and installed it soon after. Nothing happened.BZ

"that my screen goes black. It is not like a crash to desktop where MS flashes off and goes to DT. With this, the screen goes black. I can still hear my ac and can still access the menu bar."Sounds like a video card driver problem. Same thing happened to me more than once and it turned out uninstalling and reinstalling the video drivers fixed my problem. Recommend viewing this tweak guide at http://www.tweakguides.com/ATICAT_1.html for proper installation. He also has a guide for the NVIDIA cards (you didn't indicate what card you have).You might also check the event viewer and see what the error msg stated. If it referenced a FS9 module at fault, then it could be something amiss with your FS9 installation.I can't comment on the GE install errors you are getting. Looks like you have a bad installation. I had no problems after updating my GE installation.Your FS9 config looks okay but you might want to review the AVSIM FS9 Care and Maintenance Forum; the FS Simulator Tips and Tricks Forum; and the FS Hardware Forum for recommendations on the proper configuration of your FS9.cfg.You might want to check out this article at AnandTech in regards to the proper ATI drivers to use for your particular card: http://www.anandtech.com/video/showdoc.aspx?i=2701. Jim

Thanks. My video card is Nvidea GEforce 6800GT 256mb.Brad(not sure what driver I am running now)

If it happened after you modified the FS9.cfg file, try renaming it and let FS build a new one. (You'll have to make the same modifications) It's possible, during editing that a stray character got into it, corrupting it. This has solved problems, like this for me before!!

I also have GE and started getting this problem. Look at my post below to read about a possible curehttp://forums.avsim.net/dcboard.php?az=sho...07216&mode=fullGraham

BradzimI have had the exact same problem as you running the same programs (ASv6, UT, RC, and LDS). The screen goes black, I can still hear the sounds and the hard drive runs for a minute or two, then FS goes to the error reporting screen. One other thing always happens. Radar Contact will be locked up. I posted about this on the RC and AS forums because it started happening after I installed AS. It just occured to me that maybe RC is locking up as a result of the crash and not causing it. Otto always has the Comms when the crash happens. I did update RC to 4.01 and the problem seemed to stop for about 10 flights of varying length over a few weeks. Then yesterday I installed GE and it happened again after two flights. The pattren I'm seeing is that it seems to happen after the install of a new program. The other thres suggests power supply problems or aver heating. All my temps are monitored with alarms if the get hot and I have 550 watts of power which seems like it shoud be enough. Does this trigger any ideas for anyone here?

Hi there,I'm not sure if this is relevant but I know of at least two LDS users that had odd crashes (loss of FS menu bar, then CTD) that turned out to be caused or triggered by one of the Walk&Follow modules.Cheers, Holger

What is a Walk&Follow module?

>Hi there,>>I'm not sure if this is relevant but I know of at least two>LDS users that had odd crashes (loss of FS menu bar, then CTD)>that turned out to be caused or triggered by one of the>Walk&Follow modules.>>Cheers, HolgerYou're right about W&F Holger, there have been reports of this with their W&F ver 1.06. So far no response or solution suggested. I found out about it when I went to update my version (1.04) to it. Luckily I checked their forum first. Needless to say I'm still running ver 1.04 which is fine with me!! Their version 1.05 is also not affected by this serious bug. Hopefully they will fix this fast, as the previous versions are not available to new purchasers.

Oh no not another problem with this very buggy addon!! PMDG, when are you going to provide wingviews for your 747 so we don't have to use W&F?? (Unfortunately a rhetorical question as no response from PMDG is expected.)Bruceb

>Oh no not another problem with this very buggy addon!! PMDG,>when are you going to provide wingviews for your 747 so we>don't have to use W&F?? (Unfortunately a rhetorical question>as no response from PMDG is expected.)>>BrucebActually the version I have (1.04) hasn't had 1 issue! Every function works perfectly as advertised. Yes I had to remap keys to get them to work hand and hand with Active Camera, but you have to do that with any addon that uses keystrokes that are already used. That is why there is a remapping function in the first place!! This new problem though, does seem to be serious, and I think DBS should pull it back until fixed and put back version 1.05 which by all reports, does not have this issue. What are the other bugs you're referring too? Please qualify your statement!