January 31, 200719 yr I had this FSX crash problem within minutes into my first flight in FSX:"The instruction at "0x7c809783" memory at "0x15db2fe4". The memory could not be "written". Click on ok to terminate the program."I couldn't even switch from the 2-D to virtual cockpit in the default ultralight or switch to any other aircraft without getting it.Among the things I have tried based on forum searches and successes of others include:(1) Updating to latest DirectX 9.0C(2) Testing Ram (memtest86)(3) All sliders to left (minimal quality setting)(4) Reduce sound card acceleration in DirectX(5) Reduce AGP acceleration in DirectX(6) Update drivers (only partially - see below)(7) Remove AMD Dual Core Optimizer(8) Disable Microsoft Dual-Core Hotfix(9) Tell my NOD32 virus scanner to not scan communication from FSX(10) Shut down my Webroot SpySweeper mal-ware scanner.(11) Remove and re-install SimConnect.The only way I have been able get flights of some duration after all of the above is to do a Registry Healer scan and shutting down Webroot SpySweeper. Even before the selection screen comes up these make a difference - the thrilling music comes up in about 45 seconds versus several minutes. Even with this gyration which lets me change aircraft and 2-D versus virtual cockpits, I get a crash when I try to bring up the GPS cockpit window.There may be something wrong with my system but it doesn't bother FS9 at all. Some symptoms (which I have seen mentioned in various forums but which the experts/moderators couldn't reproduce):(a) When I try to install the latest ATI or Omega drivers, I get a black screen after the windows log-on. Am running with last summer's Omegas.(:( When I try to update my Via chipset drivers to 5-10a, I get a message that says that necessary files are missing from the download package. I'm currently using 5-09'sI welcome suggestions for other things to try with FSX and/or insights into what's "wrong" with my PC.
January 31, 200719 yr A Google search of "0x7c809783" indicates this error message occurs frequently with various applications so I do not think this error is directly linked to FSX or your FSX installation. Bad installs of video drivers has been known to cause major problems with FS9 and a complete uninstall/reinstall is recommended. After using ATI's uninstall program I also use Driver Cleaner Pro before doing any reinstall of new ATI drivers. You can find this program at this link: http://www.drivercleaner.net/. It use to be free but see there is a small charge for it now. You may be able to find a free copy at Guru3d.com where I think I got mine. Driver Cleaner Pro finds and deletes several more ATI files/registry entries than the ATI uninstall program finds. I would also make sure you completely uninstall the Omega drivers too and make sure any references to Omega are cleared from the Registry. Once your system is "clean", then accomplish your video card reinstallation. Make sure your Omega drivers are compatible with your ATI card. Regarding the Via Chipset Drivers: A bad installation of these drivers could also be causing your problems. I suggest going to the VIA Chipset website and try to find out why you are always getting a message that "necessary files are missing from the download package" whenever you try to install the updated drivers. I did a Google seach of "Via Chipset Drivers" and there are several sites you can visit to find a solution.Lastly, check your Performance Settings for your computer. Make sure the virtual memory setting (Page File) is set to "System Managed Size". My programs use to crash a lot when I set up my own settings and this suggestion fixed my problems. Hope you can find a fix soon.Oh! One more thing to recommend. Defrag your harddrive. FSX installations scatters files all over your hard drive. I defragged my hard drive just before installing FSX and then did a defrag after installation. I never saw so much RED (indicating fragments) in my life! I now regularly defrag especially after installing a new aircraft or scenery.Best regards,Jim
January 31, 200719 yr I agree, it does not sound like a FSX problem. A driver problem is more likely.I do not like Via's chipsets, and do not use them anymore. I have had too many incompatibility and stability issues with boards using their chipset over the years to trust them with an FS computer.RhettAMD 3700+ (@2310 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2 GB Corsair XMS 2.5-3-3-8 (1T), WD 250 gig 7200 rpm SATA2, CoolerMaster Praetorian case Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
February 1, 200719 yr Hello,Since the installation of FSX I have this from time to time.I reduced the problem with : defrag often (after each scenery installation) , boot PC , use FSAutostart before start of the Sim. I did not (yet) found the reason.May be the FSX Patch will solve it? Emile EBBR Z590 Aorus Elite, i9-11900K 3.5Ghz Nvidia RTX 5070, 32 GB Mem, SSD 3 Tera , 3 monitors Win11 Pro X64 LM P3D V6.1 Little Nav Map Hifisim Nvidia 591.44
February 1, 200719 yr Author Jim,Thanks for your suggestions.Have tried setting the pagefile to "System Managed Size" and defragging my hard drive - no benefit.Via has a Hyperion 4 in 1 driver arena in its support forums. On October 2 of last year a topic was opened for this problem. On October 27, the Via moderator threw in the towel on the problem because they were unable to reproduce it. On January 6/7 myglamorf posted that they had been successful with turning off virus scanner and other programs before attempting the install. I tried this once but maybe I didn't shut off enough...... Will also get Driver Cleaner and give it a try.Thanks again.Best regards,Steve
February 1, 200719 yr "they had been successful with turning off virus scanner and other programs before attempting the install. I tried this once but maybe I didn't shut off enough......"Steve,It's fairly common knowledge that you should always turn off any anti-virus programs prior to installing any software, especially driver updates. One reason is that changes are made to the registry and the anti-virus program may think it's a virus trying to change a registry setting and not allow it to happen. Some modern programs today will look for an anti-virus program running first and, if it finds one, will tell you to turn it off before continuing. Looks like you're almost there....Best regards,Jim
Create an account or sign in to comment