Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Anyways: http://bfy.tw/Rjp
http://answers.microsoft.com/en-us/windows/forum/windows_7-gaming/win-7-64-bit-fsx-fatal-error-ctd-restart/14fc20fa-9dca-465b-be42-146414087ec5
http://www.flightsim.com/vbfs/showthread.php?269459-FSX-quot-fatal-error-occurred-quot
http://robbonline.se/How%20to%20fix%20FSX%20problem%20with%20windows%207%20UIAutomationCore.dll%20download/UIAutomationCore.dll.htm
http://www.ramoonus.nl/2010/01/01/the-fix-to-microsoft-flight-simulator-x-crash-on-windows-7-x64/
there will be details on this crash, paste them here (this is one option, the other is guessing what from 1000000 possibilities could cause your problem)
My system specs are: Windows 7 64, i5-2500K, 8 gigs of RAM, ATI Radeon 7850.
And here's the event viewer log, hope that helps:
Log Name: Application
Source: Application Error
Date: 6/21/2015 8:24:30 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: KORISNIK-PC
Description:
Faulting application name: fsx.exe, version: 10.0.62613.0, time stamp: 0x551a6ac5
Faulting module name: igd10umd32.dll, version: 9.17.10.3517, time stamp: 0x532b0c10
Exception code: 0xc0000005
Fault offset: 0x00209dcd
Faulting process id: 0x1508
Faulting application start time: 0x01d0ac4f66146c7b
Faulting application path: D:\Games\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Windows\system32\igd10umd32.dll
Report Id: c12a4c13-1842-11e5-bb2d-c860000a93e4
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-06-21T18:24:30.000000000Z" />
<EventRecordID>144358</EventRecordID>
<Channel>Application</Channel>
<Computer>KORISNIK-PC</Computer>
<Security />
</System>
<EventData>
<Data>fsx.exe</Data>
<Data>10.0.62613.0</Data>
<Data>551a6ac5</Data>
<Data>igd10umd32.dll</Data>
<Data>9.17.10.3517</Data>
<Data>532b0c10</Data>
<Data>c0000005</Data>
<Data>00209dcd</Data>
<Data>1508</Data>
<Data>01d0ac4f66146c7b</Data>
<Data>D:\Games\Steam\steamapps\common\FSX\fsx.exe</Data>
<Data>C:\Windows\system32\igd10umd32.dll</Data>
<Data>c12a4c13-1842-11e5-bb2d-c860000a93e4</Data>
</EventData>
</Event>
if you look at failing module, it's called igd10umd32.dll - this dll is part of - surprise - intel's drivers for their integrated gfx card
so what's going on there - you have intel's gfx card as well as dedicated one installed and the game tries to run the game on intel's when dx10 is selected no matter what you selected it to run on in FSX launcher; it crashes then most probably because you haven't assigned enough of your ram as hd's vram in bios
i've already reported this bug
Nvidia gpu
1.) Open up "NVIDIA Control Panel"
2.) Open the on "3D Settings" tab
3.) Click on "Manage 3D Settings"
4.) Either select "Global Settings" or "Program Settings". If you select "Program Settings" then you will need to add the game to it
5.) In "CUDA - GPUs" make sure you have it set to your dedicated gpu
Bios (I prefer you to not mess with your bios)
- Check your bios to see if you can change which gpu is used to display things
- May also be list as an option under power consumption? Change it from adaptive to high performance.
as long as you're not running mobile radeon, catalyst's don't have that needed option
EDIT: I have found this site, which might help, though it does seem rather convoluted just to get the DX10 option up and running: http://forum.avsim.net/topic/421849-dx10-fixer-atiamd-aa-and-vsync-guide/