Troubleshooting Definitions


Hello 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…) of error interpretation.

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

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. In this situation the desktop will not crash and down but just runs until YOU stop it.
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.

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.

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.

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.


Do you need help to report an error to the supplier of your APP?
Go to our contact page and tell us the story.

System File Checker tool

If you encounter a strange behavior of your system or if the system sends you a message indicating that some system file is damaged, the System File Checker might be able to help. Here is what you do:
Open an elevated Command Prompt (go to Start > All Programs > Accessories > right click on Command Prompt > Run as Administrator).

Type sfc /scannow into the Command Prompt window – note the blank in front of the slash (/). This will run for a while.

When it is done, you can end up with the following different results:
1. SFC did not find any corrupted files
2. SFC did find corrupted files and was able to fix the files
3. SFC was not able to fix all corrupted files

In the cases 2 and 3, SFC stores the results in the CBS.log which you find in C:/Windows/LogsCBS/CBS.log. This is a massive file of approximately 5MB and if you care to see it all, you must send CBS.log to one of your own folders from where you can double click on it. It will then open with Notepad.
Note: You cannot open it inside the CBS folder. You will get an Access denied message.

But most likely you are only interested in the part that shows the corrupted files that were fixed – or not fixed. For that you need a significant data reduction. You do that as follows:

Open another elevated Command Prompt and paste this command into it:

findstr /c:”[SR]” %windir%logscbscbs.log

This will show all the files you want to see in the Command Prompt window.

Since that window is not very practical for a detailed study, you want to paste the content into a Notepad, Word pad or Word file.

For that you right click on the Command Prompt window (any place is good) and click Select all. Then you click on the selected text in the window. Now this whole text is stored on the clipboard and you can paste it into a document file where you can analyze it.


You may want to add this string in the DOS box and it will write a text file in your preferred folder where you can open it:

findstr /c:”[SR]” %windir%logscbscbs.log >C:Users***yourname***Documentserror.txt

Warning: If you have tweaked your system and modified system files, the System File Checker may undo your tweaks.

Source: Windows Seven Forum

FSX sound enabled when in background.

Flight1 SoundStream Released
Flight1 Software announces the release of Flight1 SoundStream.  This ingenious tool keeps the Flight Simulator sound enabled even when FSX is running in the background. It lets you use add-on programs developed for Flight Simulator (such as moving maps) without interrupting the in-flight sound experience. Or you can read and answer an email or surf the web during a long flight – all this without your ears leaving the cockpit.

No more missed ATC calls and any warning sounds, and of course you will hear that the engines are still running!  Flight1 SoundStream runs as a module inside Flight Simulator and can be configured using the Add-Ons menu during the flight. You can enable and disable SoundStream at any time. And optionally, you can set a reduced sound volume to be used when FS is running in the background.  Get Flight1 SoundStream now, and enjoy a more complete sound experience with FSX and Prepar3D!  For more information on this product and a video demonstration, visit this site.