Unstable system – Error Resolution

Process Explorer
One of the best tools to find out what’s happening in your system is Process Explorer.
Once installed, it opens a dialog box that shows global system performance metrics like those shown in Task Manager. The information includes the amount of committed and available virtual and physical memory as well as paged and non-paged kernel buffer usage.

Graphs show the CPU usage history of the system as well as the committed virtual memory usage, and on Windows 2000 or higher systems an I/O graph shows I/O throughput history.

Red in the CPU usage graph indicates CPU usage in kernel-mode whereas green is the sum of kernel-mode and user-mode execution.

When committed virtual memory, which Task Manager labels in its graphs on Windows 2000 and higher as “PF Usage” and on NT 4 as “Mem Usage”, reaches the system Commit Limit, applications and the system become unstable.

The Commit Limit is the sum of most of physical memory and the sizes of any paging files. In the I/O graph the blue line indicates total I/O traffic, which is the sum of all process I/O reads and writes, between refreshes and the pink line shows write traffic.

Error resolution

  1. So, whenever you expect FSX to hang, to stop or to restart….let this Process Explorer run in background.
  2. Have a look if your system is in balance with the Commit Charge values.
  3. Take a flight plan and GO!
  4. The moment the FSX shows an error, make note of the time
  5. Look in the Process Explorer if it could be an Memory Error (Current > Limit)
  6. Open Event Manager clicking Start button, type “event, select Event Viewer
  7. In Event Viewer Select Administrative Events and look for the event that corresponds with the time of occurrence
  8. Most of the time you will read Application Error or Application Hang
  9. Now find which module causes the error (e.g. g3d.dll or ai_player.dll)

Windows Task Manager and Process Explorer
In the Performance tab,total system memory used (RAM plus page file) and maximum available are shown in the Commit Charge(K) panel, listed as Current and Limit respectively.
Total RAM and Available RAM is listed in the Physical Memory (K) panel.
The Page File Usage panel displays the total commit charge graphically as a bar graph and, over time, as Commit History.
Note that for the Task Manager, Page File Usage does not mean just Page File or SWAP file; it means total system memory used (RAM plus page file).
Note that some numbers are listed in KB which will look slightly different from the other numbers listed in MB.

Under the processes tab, the value listed in the memory column is RAM only and not total memory used by Image Name

  1. If you did not already have this tool on board….download VMMap from here
  2. Lanch VMMap and select the process FSX
  3. In the view sort the Details Column and find the .dll involved
  4. So, .dll is called from FSX folder or else? Now you know!
  5. Now that you located the .dll, go to this website
  6. Search for the .dll in the library (on the menu @ the right side of the screen)
  7. Download the tool, repair the dll’s ( most of the time more than 1…)
  8. Done

If you wan the tool for 30-days free….install the download , run once, select repair, then you get a warning…STOP

Uninstall the application via the All Programs…and then a screen pops up for a 30-day free use! Fill the form, receive the key and there you go!