FSX crash caused by simprop.dll

One of our regular visitors ran in a severe problem after he had repaired FSX using the DvD’s. After starting FSX the sim crashed and with the event manager it indicates that simprop.dll (in the root of FSX) was the fault module. Before the repair action FSX was in SP2 mode (without Acceleration).
Resolution: After a repair action with the DVD’s you must run the SP1 servicepack as well as the SP2 servicepack. First run SP1 and then start FSX in default flight. Close FSX, then run SP2. When starting SP2 you will see no option to install….only to uninstall, so uninstall.  After uninstall, re-run SP2 again, start FSX and your problem with simprop.dll is solved.


UIAutomationCore.dll fix for FSX W7-64

This fix is not applicable for FSX-Steam Edition

This is a fix to stop FSX crashing when running Windows 7-64 in free flight and MP Sessions. These are the steps you must follow:

  1. Download UIAutomationcore.zipYou are advised to go to the download page. You will find the file in the FS-Software folder.
  2. Unpack the ZIP file and place the extracted UIAutomationCore.dll in the root of your FSX installation folder where the file fsx.exe resides. Make sure FSX is not running.
  3. After this action, start FSX and you will find that switching views in FSX, no longer eventually causes FSX to crash.

uiauto_vista32Without this fix, FSX will hang as well as you will be “timed out” in a multi player session.

The file version of UIAutomationCore.dll, you need to place into your FSX directory, is the File version: 6.0.6001.18000 (148k) with
Date modified 1/20/2008 9:24 PM.

Do not use any other versions, since this version is the only version that will stop the crashes.

…and the prove that the UIAutomationCore.dll is called by FSX:



Blue Screen of Death (BSOD)

What is BSOD:

The Blue Screen of Death (also known as BSoD or Blue Screen), known officially as a Stop Error  or a bug check, is the error screen displayed by the Microsoft Windows family of operating systems upon encountering a critical error, of a non-recoverable nature, that causes the system to crash.In Windows NT-based operating systems, the Stop error occurs when the kernel, or a driver running in kernel mode, encounters any error from which it cannot recover. This is usually caused by an illegal operation being performed, where the only safe action the operating system can take is to restart the computer. As a result data may be lost, since the user is not given an opportunity to save any unsaved data to disk.
The text on the error screen contains an error code along with four other codes, whose meanings depend on the error code itself, and an error name. Depending on the error code, it may display the memory address at which the problem occurred, together with identifying details of the driver file loaded at that address.

So far …so bad…

nirsoftThis applications might help you getting grip on the situation. Most of the time the BSoD event is that fast that you can hardly see the information.

  1. Download the application bluescreenview_setup from Nirsoft and install this on your PC.
  2. Let it run and the application will show you an overview of past BSoD’s
  3. nirsoft02Double click a line and this is what you get.
  4. The best information is the cause of the BSoD and which driver is giving you a headache
  5. In the File menu there is a Google link to find a resolution for the bug.


Setting Permissions To Folders

permission-01When you need Full permissions in a folder, sometimes your permission as a User (not as an Administrator) is blocked.

Please read in the next sample of the folder C:Program FilesWinRar and see how to change permissions. Click on the images to enlarge.

This is the situation:

in this folder WinRar the user named Users on Jan-PC has no full control of the files inside the folder.

Click on Advanced button and then on the tab Owner of the screen to come.

The Current Owner is indicated as Administrators on (Jan-PCAdministrators).
We will first change the owner of the folder by selecting here the Edit button.permission-02

On the Owner tab select Jan(Jan-PCJan), check the box Replace owner on sub containers and objects, give Apply and then…you get this warning.

OK? OK!permission-03

Now you are “owner” as a user,
select the Permissions tab and in the permission entries Users (Jan-PCUsers)


Select Change permissions and in the screen Permission Entries for WinRar you now see that the current permissions are not set to Full control.

Check the box Full control.





Close the Properties screen and re-open again and see the change.

In this sample, replace the statements (Jan-PC) with your own indication.permission-05


WARNING: if you don’t know what you are doing in a certain folder, nor can oversee the consequences of your action…don’t do it.permission-06


Changing permissions of folders and/or files can bee seen as a security hole in your system.