more crashing on launch

I posted on the end of the thread started by warmanbrent, but I think this may have gone dormant - and I was on the second page. I have tried removing the FSUIPC4.dll files, but it made no difference. So I've been without FSX for a couple weeks now. I hope someone can help.

Here is my original message and event log:

Robert

I now have this 'crash on launch' problem - which must have started after the last Windows update. I followed the advice above. My event log is below; I don't really understand it (actually, not at all). So if someone could interpret for me I'd be most grateful:

Fault bucket 539040964, type 1

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: fsx.exe

P2: 10.0.61637.0

P3: 46fadb14

P4: simprop.dll

P5: 10.0.61637.0

P6: 46fadb59

P7: c0000005

P8: 00006da7

P9:

P10:

Attached files:

\\?\C:\Users\User\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt

\\?\C:\Users\User\AppData\Roaming\Microsoft\FSX\dxdiag.txt

\\?\C:\Users\User\AppData\Roaming\Microsoft\FSX\scenery.cfg

\\?\C:\Users\User\AppData\Roaming\Microsoft\FSX\fdr.dat

\\?\C:\Users\User\AppData\Roaming\Microsoft\FSX\DLL.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA311.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA331.tmp.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA340.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA360.tmp.txt

These files may be available here:

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_781c28822ff89480d6af42253053c37e2def23f6_00000000_1c58d0d1-96e6-41ca-b04c-2f61f9a53651

Analysis symbol:

Rechecking for solution: 0

Report Id: e228d1ba-f7d0-451d-b3dc-f4370026eba5

Report Status: 268435456

Hashed bucket: 9a08d6b996e9269c83b74278da4fd771

Cab Guid: 0

simprop.dll as the faulting module is pretty serious. You haven't done anything like a "Repair" to your FSX, have you? I'll do a quick Google search and see what comes up!

https://answers.microsoft.com/en-us/windows/forum/all/fsx-will-not-load-with-simpropdll-event-error-with/f77565e8-2291-4518-954b-095902cba154#:~:text=Simprop.,can%20come%20up%20in%20FSX.&text=You%20will%20need%20to%20uninstall,Acceleration%2C%20leaving%20FSX%20intact).

From what I can see you will need to completely uninstall all FSX (SP1 &2, Acceleration) and reinstall it.

AD

Try putting a X in the DirectX 10 preview box on the graphics settings page.

Stinger

Sent from my SM-G935F using Tapatalk

Thanks for all the suggestions folks. I uninstalled Acceleration and reinstalled it. After this, FSX launched and then put itself in the taskbar as a black box that wouldn't open. I pressed on and tried again; on this second attempt I was asked to approve the running of a dozen or more modules. But got into FSX sucessfully. On choosing my Navajo I was again asked to approve component modules. Then flew for a bit until I got a message to say that the trial period was up and I would have to register.

Closed.

Started again: got an error message, code 1-80004005. Clicked Yes for more info but got an unavailable return for the website. But FSX went ahead and launched with no requests on modules this time. Aircraft chosen without any problems, completed a short flight and then FSX stopped with the message that my trial period had expired.

I guess this is some sort of progress from complete crash on launch - but obviously not there yet. All further suggestions welcome. I want to keep reinstalling FSX as the very last resort. But maybe I cannot avoid this.

Robert

1. In Windows Vista,and Win 7 click the Start button, type regedit in the Start Search box, and then click regedit.exe in the Programs list.

User Access Control permission If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.

2. Expand the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\CLASS\{4D36E967-E325-11CE-BFC1-08002BE10318}

3. After you find the folder, double-click Upperfilters on the right side.

4. Change the value from 0 to PartMgr, and then click OK. (mine said CLEANBOOT on one line and partmgr on the next, just remove one line leaving PartMgr as the value)

5. Close Registry Editor, and then try to use the activation wizard.

.... and is it the same for Windows 10 Mr Zippy?

Robert

.... and is it the same for Windows 10 Mr Zippy?

 

Robert

Yes!

A more detailed explanation by jethrom:

https://www.flightsim.com/vbfs/showthread.php?318953-How-To-Activate-FSX-and-Accelerator-After-A-Fresh-Install-On-Windows-10&p=2093062#post2093062

Yes!

 

A more detailed explanation by jethrom:

 

https://www.flightsim.com/vbfs/showthread.php?318953-How-To-Activate-FSX-and-Accelerator-After-A-Fresh-Install-On-Windows-10&p=2093062#post2093062

Many thanks Mr ZIppy, all sorted now and flying normally (well, as normally as I fly!). When I got to the line in regedit, it was all lower case, restoring the capitals put it right. Very odd error that.

Robert