Troubleshooting Definitions


troubleHello Captains,
in an effort to support you in resolution of errors that might occur during the download, installation and/or activation phase or your installation is preventing you from using your flightsimulator during start up and normal use, please find here a summary of the FMM (Frequently Made Mistakes…)

Last months I have extremely been busy reading and supporting the P3D forum and even supported remotely and successfully some of the “hard cases”.

Before we dive into the FMM, first of all some definitions, because then we know what we gonna talk about.

  1. Crash to desktop (CTD) What is a CTD: a crash to desktop (or CTD) is a computer program crash which is said to occur when a program unexpectedly quits, abruptly taking the user back to the desktop. Usually, the term is applied only to crashes where no error is displayed, hence all the user sees as a result of the crash is the desktop. Many times there is no apparent action that causes a CTD. During normal function, the program may freeze for a shorter period of time, and then close by itself. Also during normal function, the program may become a black screen and play the last few seconds of sound (depending on the size of the data buffer) that was being played repeatedly before it crashes to desktop. Other times it may appear to be triggered by a certain action, such as loading an area. One way to track down the source of CTD for games is to run them in windowed-mode.
  2. 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 Erroror 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.
  3. Fatal system error What is: A fatal system error, also known as a system crash, stop error, kernel error, or bug check, is when an operating system halts the moment it reaches a condition where it cannot operate safely.When a bug check is issued a crash dumpfile will be created if the system is configured to create them. This file contains a snapshot of useful low-level information about the system that can be used to debug the root cause of the problem. If the user has enabled it, the system will write an entry to the system event log. The log entry contains information about the bug check (including the bug check code and its parameters) as well as a link which will report the bug to Microsoft and provide the user with prescriptive suggestions if the cause of the check is definitive and well-known.
  4. Application crashes (APPCRASH) When program files or files within your computer’s registry have become corrupted, this can cause the programs to unexpectedly crash. When a program crashes, you will likely get an Appcrash error. The error message will say “Prepar3d” (or whichever program has crashed) has stopped working” and then list rows of technical information regarding the cause of the crash.

Having said this, on this website you will find already some hints to get grip of a malicious situation.

Advertisements

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:

uiauto_vista32a