Windows 10

[Ian Warren]

Marty , just stick with tried and trusted and plug into your and tinker with Win8 , currently for you the best way to go.

[Splitpin]

Ian , I've tinkered .... and tinkered , and it works for 5 minutes then shuts down (no explanation) I'm 100 % sick of it .
Really keen to know how other Win8 users are doing with this ..... like you Fozzer , how do you do it ?

[toprob]

Ian , I've tinkered .... and tinkered , and it works for 5 minutes then shuts down (no explanation) I'm 100 % sick of it .
Really keen to know how other Win8 users are doing with this ..... like you Fozzer , how do you do it ?

Remind me again, do you have a 64 bit system?

I recall having to debug FSX when I was getting it running on my new system, and this involved checking Event Viewer after every crash, and Googling the error message, in relation to FSX, and for each problem I was able to find a solution on one of the flightsim forums. Then I'd move onto the next issue, until I managed to get them all.

FSX really doesn't like 64 bit systems, but it can be made to work with a few tweaks.

[Splitpin]

Ian , I've tinkered .... and tinkered , and it works for 5 minutes then shuts down (no explanation) I'm 100 % sick of it .
Really keen to know how other Win8 users are doing with this ..... like you Fozzer , how do you do it ?

Remind me again, do you have a 64 bit system?

I recall having to debug FSX when I was getting it running on my new system, and this involved checking Event Viewer after every crash, and Googling the error message, in relation to FSX, and for each problem I was able to find a solution on one of the flightsim forums. Then I'd move onto the next issue, until I managed to get them all.

FSX really doesn't like 64 bit systems, but it can be made to work with a few tweaks.

Yep , its a 64 bit Rob.

[toprob]

Yep , its a 64 bit Rob.

Have you ever checked Event Viewer after a crash? I did find a useful post on one of the FS sites showing how to view FSX errors, but I can't find it now. From memory, you'd run Event Viewer -- just go to the Start menu and type 'event viewer' -- and go to Custom Viewer > Administrative Events. Then you get a list of errors/warnings, just look for the top one for FSX.

By clicking on the error line, you get details in the Preview Pane. (Make sure this is set to display in the View menu.)

The details of the error message normally show enough details of the errors, such as the defaulting module, so you can just search for this on Google, or in my case, Bing:)

I just typed 'FSX {the name of the defaulting model} error' and looked for results from the normal flightsim forums. I was able to find solutions for all my issues (four or five different problems, from memory) and hit them on the head one by one. Now I (almost) never get a FSX crash.

[johnkiwi]

If it's a CTD ( crash to desktop) I found the AVSIM guide helped me. From memory, tweaking the cfg with himemfix and a couple of others and it all came right. Havent had a CTD since ( he says busily touching every wooden object in reach...)

[Splitpin]

Rob .........

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: uiautomationcore.dll, version: 7.2.10240.16397, time stamp: 0x55af0841
Exception code: 0xc0000005
Fault offset: 0x00064473
Faulting process id: 0xc8c
Faulting application start time: 0x01d0d184ec963064
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\WINDOWS\SYSTEM32\uiautomationcore.dll
Report Id: f4582c8b-5b9c-4155-8b26-2897cb354141
Faulting package full name:
Faulting package-relative application ID:

[toprob]

Yes, uiautomationcore.dll is a very common problem with FSX and 64 bit, I think there is a replacement uiautomationcore.dll available online, you just need to search for it in relation to FSX i.e. 'fsx uiautomationcore.dll error'

[dbcunnz]

Try this one Marty
http://fsxeu.com/uiautomationcore-dll/

[Splitpin]

Big D ...CP ... Rob ..... just flew for an hour and no crash. Changed a/c mid flight , weather, time , views ....and nothing ....thanks very much

[cowpatz]

Glad it's all sorted SP. Only a BSOD is worse than a CTD.

[Splitpin]

BSOD ?

[dbcunnz]

Blue Screen of death

[Ian Warren]

The ominous BSOD .. that even happens even after a simple startup .. it simply dose happen even on a PC brand new ... had one go pop in less than a week .. BRAND NEW! .. that was when I walked away from AMD machines, it was not the first ... but giving that .. that was 20 years back.

[Fozzer]

In the Olden Days, on my previous Pentium Pro, Dual Core, 2.8 GHZ processor with Windows XP installed on my tower Computer ran perfectly!

Window 8 only arrived pre-installed in my brand-new, sooper-dooper, Intel i7, 3.9 GHz Tower bundle of joy Gaming Computer!!

The very first thing I did was to make my Win 8.1 display on my screen exactly the same way as my trusty Win '98/XP OS, which I am familiar with!

At the moment my Win 8.1 runs fine (64-bit)...so no need to tempt fate and install Windows 10!.... ...!

My 8.1 'aint broke!...(Frying Pan and Fire!).... ...!

Paul..... ...!

[mfraser]

I've just had too many problems to continue with it.

I've been following this thread and researching Windows 10 quite a bit. I haven't done it myself yet, but the recommendation is to upgrade and do one of two things. If its good for you, stick with Windows 10. If it's not, roll back to Windows 7 or 8 and wait for MS to fix whatever problems you had with 10. Why? Because the free upgrade takes a snapshot of your hardware which is the new way MS verifies and activates Windows 10 for future installs. No more typing in serial numbers! As long as your device hardware matches the stored snapshot Win10 will self activate once its installed. So if you upgrade and then rollback you can install Win10 again at a later date (including a fresh install) without needing a key - even outside the one year free upgrade period. The only caveat is if you change the hardware substantially during this period and try to reinstall Win10 after July 2016, as the hardware won't match the device snapshot in which case you WON'T be able to continue without a key to type in.

Hope this info helps people wondering what the fuss and rush is about. By all accounts Win10 seems to be the way to go - but you still have until July next year to get your free copy!

[Ian Warren]

- but you still have until July next year to get your free copy!

Good to know ... That's almost a year for others to find problem and for hear about update and patch, at the moment I'll stick Win7 only the sake for the work I do here.

[Agent X20]

Just remember if you do end up trying out Win10, your rollback option only lasts for one month - before Win10 deletes the backup...

[dnkiwi]

Hi guys just a quick update on my experience with windows 10 I have been running it now since release and apart from a corrupt upgrade file that caused windows to crash constantly. the issue was resolved with a quick call to Microsoft who told me it was something at their end that had caused the initial issue of the crashing and within 24 hours they had patched the unnamed issue and had me back up and running windows 10 and since then I have no hassles and am running steam without crashes I have installed the updates they pushed out .my thoughts on it so far is I'm happy to continue on windows 10 and see how thing go its just been a steep learning curve adjusting to the new layout. I'm still yet to try my fsx steam copy and try and add my addons to it i will let u guys know as i take the plunge and share any fixes i find

[NZ255]

I am on the insider program with my laptop but sticking with 8.1 + StartIsBack (because I could never adapt to the start screen) on my tower. Will probably upgrade to win10 in a few months time.