January 16, 201412 yr Hi I was using the FSX with four monitirs like a chime, until the OV 43 touch screen received today, I set this screen at its place above myhead, everything is good. When I go to the FSX to test, I normally run fsx on 1st screen, 2rd & 3rd screens are duplicated (as one screen so lets say its a 2nd screen) for the PFDs & NDs on the both sides, drag the NDs and PFDs and they work normally without any probs, 3rd screen to the upper/lower eicas's, drag them and everything is good, the 4th scresn for the FMCs and work normally , BUT in the 5th screen which is to the OHpanel, open the OH panel and drag it to the 5th screen ----------》 after that I get the fatal error/crash to desktop problem....!!!!!!! The problem appears after passing the 4th screen and entering to the 5th screen, with four screen no problem but to 5th one I get the problem immediately..... I use a fatal error fix UIautomotion the right version with fsx opening with a sp2 conpatible. I need to do anything with yours help to finally complete my virtual home cockpit. Please guys give me the support to cross this problem and to makedream to be a real !!!! Thanks a lot..
January 16, 201412 yr This is an automatic message. This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons. The most likely reason is that the post was off topic. The topic could also have contained images or a video that were not appropriate to the original forum it was posted in. The images might not have been "illustrative" or "explanatory" in nature. The topic could have been moved because we deemed it to be more appropriately placed elsewhere. Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here. Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated. ADMIN BOT... Do not PM or send Email.
January 16, 201412 yr You need to download and run AppCrashView and post the crash report here (see AVSIM CTD Guide for link/information). It appears to be a display driver problem but can't be sure until we see a crash report. AVSIM has a hardware forum for monitors and a lot of people have 3 or 4 monitor setups. You might check there too to see if anyone has had problems with five (5) monitors. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 16, 201412 yr Author sorry for the mistake of posting my problem in wrong forum, sorry again so i download and run the CrashAppView, i attach the report for u My CTD report.txt thx waiting !!!!!!!!!!!
January 16, 201412 yr You Microsoft Visuals 2005 and 2008 are not up-to-date. Microsoft has set up a website where you can download and install the latest versions - http://support.microsoft.com/kb/2019667. The faulting module was the g2d.dll. As stated in the AVSIM CTD Guide: G2D.dll - The g2d.dll is indicated as the faulting module in the crash report. This module handles plain text messages, like the frame rate counter and those other plain text messages you see periodically while running FSX and the plain text words in the FSX Menu, like the words Options, View, etc. There may be something corrupted in your dll.xml which loads menu items. It has been fixed by rebuilding the FSX.cfg (deleting or renaming the FSX.cfg and then restarting FSX). Some others have fixed this problem by uninstalling/reinstalling the video card drivers or going back to a previous version. Hope this helps. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 17, 201412 yr Author You Microsoft Visuals 2005 and 2008 are not up-to-date. Microsoft has set up a website where you can download and install the latest versions - http://support.microsoft.com/kb/2019667. The faulting module was the g2d.dll. As stated in the AVSIM CTD Guide: G2D.dll - The g2d.dll is indicated as the faulting module in the crash report. This module handles plain text messages, like the frame rate counter and those other plain text messages you see periodically while running FSX and the plain text words in the FSX Menu, like the words Options, View, etc. There may be something corrupted in your dll.xml which loads menu items. It has been fixed by rebuilding the FSX.cfg (deleting or renaming the FSX.cfg and then restarting FSX). Some others have fixed this problem by uninstalling/reinstalling the video card drivers or going back to a previous version. Hope this helps. Best regards, I delete fsx cfg and new one created, also the microsoft visual updated to the last one. And nothing help. I dont think the deleting of the driver (which is 331.93) will fix the problem. Please guys more activities, the simulator is stoped to the 2nd day, please guys and friends, help !!!!!!!
January 17, 201412 yr The best answer is the one I provided. If deleting and rebuilding your fsx.cfg did not work, disabling modules in your dll.xml, or uninstalling/reinstalling your video card drivers, then your last resort is to uninstall FSX and reinstall it. I do believe though that there is a module in your dll.xml that is not working properly. It's easy to check. You just open up the dll.xml with notepad and in each line where it says <disabled>false<disabled> you change the false to true, save the file and reload fsx. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 17, 201412 yr Author The best answer is the one I provided. If deleting and rebuilding your fsx.cfg did not work, disabling modules in your dll.xml, or uninstalling/reinstalling your video card drivers, then your last resort is to uninstall FSX and reinstall it. I do believe though that there is a module in your dll.xml that is not working properly. It's easy to check. You just open up the dll.xml with notepad and in each line where it says <disabled>false<disabled> you change the false to true, save the file and reload fsx. Best regards, please see my DLL.XML content : <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Audio Environment Module</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>o:\Program Files (x86)\Flight One Software\Audio Environment\AEMODULE.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>TaxiSigns HD</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>O:\Program Files (x86)\FlightSimTools.com\TaxiSigns HD\TaxiSignsFSX.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Object Placement Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Options</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGOptions.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Events</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGEvents.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Sounds</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGSounds.dll</Path> </Launch.Addon> <Launch.Addon> <Name>A2A Feel</Name> <Disabled>False</Disabled> <Path>Modules\A2A_Feel.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>AccuFeelMenu</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\AccuFeelMenu.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> what now !!!!!!!!!!!
January 17, 201412 yr Author Now +1 this to the previuos tries, I have change all the <disable> false</disable> to <disable> true </disable> ONLY, i dont touch the ManualLoad>False</ManualLoad. The problem is still !!!!!! Also I have re-install the FSX, but nothing help. The problem is still !!!!!!
January 17, 201412 yr please see my DLL.XML content : <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> Leave this one at False <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> How come this one is still False? <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Audio Environment Module</Name> <Disabled>False</Disabled> How come this one is still false? <ManualLoad>False</ManualLoad> <Path>o:\Program Files (x86)\Flight One Software\Audio Environment\AEMODULE.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>TaxiSigns HD</Name> <Disabled>False</Disabled> How come this one is still false? <ManualLoad>False</ManualLoad> <Path>O:\Program Files (x86)\FlightSimTools.com\TaxiSigns HD\TaxiSignsFSX.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Object Placement Tool</Name> <Disabled>True</Disabled> Okay, disabled. <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>True</Disabled> Okay, disabled <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>True</Disabled> Okay disabled <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Options</Name> <Disabled>False</Disabled> How come this one is still false? <Path>PMDG\DLLs\PMDGOptions.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Events</Name> <Disabled>False</Disabled> How come this one is still false? <Path>PMDG\DLLs\PMDGEvents.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Sounds</Name> <Disabled>False</Disabled> How come this one is still false? <Path>PMDG\DLLs\PMDGSounds.dll</Path> </Launch.Addon> <Launch.Addon> <Name>A2A Feel</Name> <Disabled>False</Disabled> How come this one is still false? <Path>Modules\A2A_Feel.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>AccuFeelMenu</Name> <Disabled>False</Disabled> How come this one is still false? <ManualLoad>False</ManualLoad> <Path>Modules\AccuFeelMenu.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> How come this one is still false? <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> what now !!!!!!!!!!! Now +1 this to the previuos tries, I have change all the false to true ONLY, i dont touch the ManualLoad>False See my comments in RED above. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 17, 201412 yr Author See my comments in RED above. Best regards, That DLL.EXE copy before the editing, okay. Like I told u I change them all, nothing positive occurs, the problem still !!!!!!!!
January 18, 201412 yr Author The problem resolved, First comes the video properties of the windows and turn off the monitors 5, initializes the FSX after booting the screen where you choose the aircraft, re-opens the display properties and enables videos 5, and after that you can drag any window to any monitor fsx that the crash will not happen. But can anyone tells me excatly why that occurs, cfg creation & the dll.exe modifications not help, re-install the FSX & NVIDIA driver not help. What kind of that problems is ? And why it occurs ? !!!!!!
January 19, 201412 yr We have an excellent forum for monitors in the Hardware section. I bet the question has been answered there. If not, please post your question there and let's leave this forum and the CTD Forum. Thanks for posting your solution. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
Create an account or sign in to comment