Jump to content

Windows 8 + FSX = Constant crashing.


Jay Oakley 1299775
 Share

Recommended Posts

I cannot do a single flight without FSX crashing whilst I'm in the air, I've literately attempted 6 flights in the past two days and ALL of them have crashed either whilst departing or whilst cruising.

I just get the basic explanation of 'FSX is not responding' as seen below:

http://puu.sh/bnUR1/fb4d0f251d.jpg

 

Has anyone got ANY ideas what so ever on how to fix this, I've not yet had a single flight without incident.

 

Thank you.

Link to comment
Share on other sites

Error log is as follows:

 

81690331610

5

BEX

Not available

0

fsx.exe

10.0.61472.0

475e17d3

StackHash_1eab

0.0.0.0

00000000

PCH_76_FROM_ntdll+0x0003D2EC

c0000005

00000008

 

C:\Users\Joao\AppData\Local\Temp\WERC83.tmp.appcompat.txt C:\Users\Joao\AppData\Local\Temp\WERF63.tmp.WERInternalMetadata.xml C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_fsx.exe_5646acee86b8b42c84aeb9bb22c1524cc5ef9e_75b82f04_cab_0f88100d\memory.hdmp C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_fsx.exe_5646acee86b8b42c84aeb9bb22c1524cc5ef9e_75b82f04_cab_0f88100d\triagedump.dmp

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_5646acee86b8b42c84aeb9bb22c1524cc5ef9e_75b82f04_11e6b106

 

0

a5318835-35dd-11e4-beef-7054d2597978

0

90022a1e02ae8f431ee2edfdccb82c59

Link to comment
Share on other sites

Here's another log from last nights crash:

 

81714093235

5

BEX

Not available

0

fsx.exe

10.0.61472.0

475e17d3

StackHash_1eab

0.0.0.0

00000000

PCH_0F_FROM_ntdll+0x0003D2EC

c0000005

00000008

 

 

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_c0609b46a3a5734453ff863ab9cb759408382c0_75b82f04_110fac89

 

0

348617cc-3462-11e4-beee-7054d2597978

0

b02dd20be97efd737e09b6f827a0ec8e

0

BEX

Not available

0

fsx.exe

10.0.61472.0

475e17d3

StackHash_1eab

0.0.0.0

00000000

PCH_0F_FROM_ntdll+0x0003D2EC

c0000005

00000008

 

 

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_fsx.exe_c0609b46a3a5734453ff863ab9cb759408382c0_75b82f04_1f095c9b

 

0

2a734beb-3394-11e4-beee-7054d2597978

4100

 

 

 

Here's another one from the flight before that, there are several errors so I don't know if this is the correct one:

 

fsx.exe

10.0.61472.0

475e17d3

FSInn.ocx

1.2007.508.1

464077c7

c0000005

0007fbcd

1370

01cfc86409dc49db

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

C:\PROGRA~2\FSFDT\FSInn\FSInn.ocx

c6b87476-345c-11e4-beee-7054d2597978

Link to comment
Share on other sites

Tried again just now and here's the errors I got:

 

fsx.exe

10.0.61472.0

475e17d3

FSInn.ocx

1.2007.508.1

464077c7

c0000005

0007fbcd

1590

01cfc9fdbcf1ce74

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

C:\PROGRA~2\FSFDT\FSInn\FSInn.ocx

4ee9470a-35f8-11e4-beef-7054d2597978

 

598908234

1

APPCRASH

Not available

0

fsx.exe

10.0.61472.0

475e17d3

FSInn.ocx

1.2007.508.1

464077c7

c0000005

0007fbcd

 

 

C:\Users\Joao\AppData\Local\Temp\WERBE6F.tmp.WERInternalMetadata.xml

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_8b60f73cefb4426ebbf6ade1746d6423a856198_75b82f04_0cbaff12

 

0

4ee9470a-35f8-11e4-beef-7054d2597978

0

ff640daaac11221db491055f47818d17

Link to comment
Share on other sites

I went back to W7 just because I never got EZDok to work reliably. Other than that the sim was running fine.

I would start by disabling all addons and testing, then one addon, then another and so on to find out for sure which one is causing it.

Also, try to run a memory test, memtestx86 is probably the best way to do so. I've had quite a bit of grief with overclocked hardware and memory failures.

Link to comment
Share on other sites

Have you already installed UIAutomationCore? If not, do it because it will solve some unexpected Crashes-to-Desktop.

Do you want your Virtual Airline to become an official partner on VATSIM or to participate in the VAA Program?
Visit https://www.vatsim.net/pilots/virtual-airlines

Tim Wong
Director of Virtual Airline Relations
VATSIM.net Virtual Airlines and Special Operations Administration
9KMxVhG.png

 

Link to comment
Share on other sites

Yes, so find UIAutomationcore.dll, from Windows Vista I think. Searching online for it you'll find it. After that retry your flight. Just drop the file into your FSX install folder.

Also, you would probably be better of to install FSX outside Program Files, only because write access in that folder needs admin rights. Some addons might not work well if you have it installed there.

 

 

//Mats

Link to comment
Share on other sites

Looks like the issue is this arising, this time it just automatically closes on it's own, didn't manage to find any errors, only logs I have are these:

 

A program accessed information from a location sensor or default location

 

FriendlyName=Windows ;

ImagePath=C:\WINDOWS\Explorer.EXE;

PID=5672;

Username=JOAOPC\Joao;

SID=S-1-5-21-2075658502-1541188355-3690146550-1001

 

The Windows Location Provider has successfully started

The Windows Location Provider has successfully shutdown

 

Any ideas now?

Link to comment
Share on other sites

Currently installed add-ons will probably not work if you change the location of FSX. But, newly installed will, as most either find the install directory themselves or ask you to supply them with that information.

The logs are not related to FSX this time.

Did you by the way run a memorytest? Just to make sure your hardware isn't failing.

Link to comment
Share on other sites

  • Board of Governors

I don't use Win8, so am not sure, but.... If he uninstalls and reinstalls FSX, won't the addons point to wherever the %APPDATA% location of FSX is? If not, maybe just need to uninstall and reinstall the addons after moving the FSX location?

Don Desfosse
Vice President, Membership

Link to comment
Share on other sites

  • 1 month later...

I find that FSX tends to be more stable (on Win8.1) when installed someplace other than C:\Program Files(x86)\Microsoft Games\Microsoft Flight Simulator X. Make sure that FSX is installed as Administrator, set to run as Administrator, you have full ownership of the FSX directory, and all addons are installed as Administrator. Furthermore, I've found that FSInn is highly problematic on my machine, causing slowness and crashes in FSX even before the 8.1 upgrade from 7. vPilot is a lot more stable. Finally, make sure your FSUIPC4 is fully updated. If you have a joystick, you will need to map it via FSUIPC because Windows 8 will eventually (and quietly) shut off your joystick and leave you unable to turn it back on.

2uo1990.png

 

You don't need Red Bull to get your wings.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...