Jim Young

Locked.

This is a possible solution - https://www.thewindowsclub.com/desktop-icons-moved-primary-to-secondary-monitor.

I definitely have no other solution. Hope you find a fix.

As others have suggested, make sure the monitor is your main monitor. FSX probably thinks it is opening and closing on your main monitor. On your desktop, right click and select NVIDIA Control Panel. Goto Setup multiple displays and make sure the main monitor, whether numbered 1 or 2, is shown left of your secondary monitor. You can go to multiple displays and drag the monitor you consider your primary monitor. In my case, my 34" monitor is shown as 2 and my 25" monitor is shown as 1 but FSX always opens on Number 2.

Before you shutdown FSX, make sure the sim is on the right monitor. When you restart, it should appear on the same monitor used when you quit. Same goes with full screen mode and Windows mode. If you shutdown in Windows mode, it will start up in Windows mode.

This is not an issue with Reality XP. Garmin just does not release databases. You can personally buy one for $1000 plus but I don't think you want to invest that much money. Any further discussions of distribution of databases with links will be removed as AVSIM has a strict policy of no piracy. I can guarantee you this thread is being watched by appropriate authorities. You paid for a database and a gauge. That's all you will get unless Garmin releases a free update. So please stop asking!

I know now and why I mentioned above the taxiway lights do not work. I will remove the runway lights.

No. You cannot. It was developed for FSX. I have FSX installed but had this scenery installed on my system for a long time. I just went into the Addon Manager and added it to my scenery. Yes, have to agree, the taxi lights do not work. I have the scenery sitting near the top of my Addon Manager with MSE Missouri below it.

The runway lights work - The jetways do not move and are stationary where you pull the aircraft up to the door and it will appear to be working. So, no Sode jetways.

Working perfectly for me. Just add the scenery via the Addon Manager then go to other addons tab and add the textures.

It was not the intention of Microsoft to release a dumbed-down version of Acceleration. Acceleration came with many new aircraft and scenery and updated FSX SP1 in the process. SP2 was coded so that anyone who did not purchase Acceleration (for a measly $19.95) could still have the upgrades to FSX (like DirectX 10) but could not use any of the products that came with Acceleration. Do not know how to prove it to you otherwise. I do know for a fact you cannot have SP2 and Acceleration installed at the same time.

And my registry shows partmgr so changed to PartMgr and it still did not ask for activation but did a repair for FSX (activated again) and then a repair for Acceleration and this time it immediately asked for a key. It is obvious Windows 10 is not Vista or Windows XP, the OS's when FSX/Acceleration was first released. But it is great we have some experts who find little details about the registry issue and have the ability to reset the registry (if FSX would not activate).

Make sure you uninstall Acceleration by running the setup program on the third disk. SP1 is on the third disk. You'll have to search for SP2. Install them after uninstalling Acceleration or you will have issues.

You can still get FSX to work by installing SP1 and SP2. At least you'll have DX10 as SP2 is the freeware version of Acceleration.

You're incorrect. Acceleration was release a few months before the freeware version - SP2. Microsoft wanted to make as much money as possible first. SP2 is the freeware version and it does not contain any of the payware products. You cannot install SP2 and Acceleration together as the products are coded differently so that one cannot get access to the payware products installed by Acceleration. So, if you installed SP2 and then got someone to give you the payware products in Acceleration and then copied and pasted the product into your SP2 installation, then you would have major issues. Here is a link to the lead developer's comments on Acceleration and SP2 - https://blogs.msdn.microsoft.com/ptaylor/2007/10/03/acceleration-and-sp2/

As far as I know there is only one key required for FSX Gold. I did some Googling and could not find an answer to that. If it does require an activation key and he cannot find it, then he'll have to install SP2 which is exactly the same as Acceleration but is missing some payware aircraft and scenery. Still, it will provide him DirectX10 functionality and updates to FSX. He will also have to install SP1 first as Acceleration contains SP1.

Run the following fix - https://support.microsoft.com/en-us/help/928080/error-1722-when-reinstalling-flight-simulator-x, then install Acceleration

That sounds exactly what was happening to me. After using my new build for a month or two, I decided one day to rip apart my system and clean it up as things were working so well. After doing this, I would complete some flights but suddenly get a BSOD or crash the next time. There was no consistent scenario except it happened only if using Prepar3D. Thought I had it fixed by identifying the GPU Tweak utility and going to a default user mode but suddenly started getting more crashes so ripped the system apart two nights ago and found some "garbage" in between some cpu pins. I also searched and made sure I had the latest cpu chipset driver and also installed the latest BIOS again. But that was later and after I put my computer back together and found it running great again. If you have any scenery or aircraft not specifically made for Prepar3DV4, I would temporarily disable them to make sure they are not the cause of your problem. Some gauges made for previous versions may not work in P3DV4 properly. Make sure too you have all of the Microsoft Visuals as some P3D addons use older Microsoft Visuals. You should have both the 64 bit and 32 (x86) versions. I have 2005 (x86 version only), 2008, 2010, 2012, 2013, and 2017 installed. I did not install these MSV's, they were installed by some other program that uses them. Also make sure you have Microsoft.net versions installed too. Look in C:\Windows\Microsoft.net\Framework (for x86) and Framework64 (for 64 bit versions). I have the following: v1.0.3705 (x86 only) v1.1.4322 (x86 only) v2.0.50727 (both versions) v3.0 (both versions) v3.5 (both versions) v4.0.30319 (both versions)

I strongly believed the ASUS GPU Tweak II program was causing my random crashes but have since determined the program was NOT causing my strange random crashes. I ended up taking my system apart, removing the CPU and then checking the pins the CPU sits on. I built my current system and wanted to be sure I did not accidentally bend any of the pins. Looking closely with my eyes, they all looked in perfect condition but decided to use a magnifying glass and look closer. The pins were all straight but I did see some microscopic "trash" around several pins. Believe it was some thermal paste that accidentally dropped on the pins. Removed it with a needle and installed the CPU and put the system back together and all seems well again. The ASUS GPU Tweak can be put into any mode (Game or OC Mode) and no crash. The reason I suspected your ReLife GPU program was because dwrite.dll is related to Microsoft DirectX Typography which, according to Google means: "the style and appearance of printed matter. The art or procedure of arranging type or processing data and printing from it." According to Google, the primary cause of dwrite.dll errors is a corrupted registry. If you have a registry cleaner like CCleaner, I would run that program. I use Advanced System Care's registry cleaner about twice a month. Your crashes did stop when you disabled the dll.xml's and it could be related to a process there. Make sure you have P3D set to start up in Administrative Mode for ALL users as there are several users on your computer (even though you are the only user). To do that, right click on the P3D icon on your desktop, right click Prepar3D and select properties, click on the compatibility tab and then look all the way down and make sure it is set for ALL users. I believe it is not by default.

What is happening to you has happened to me but, for me, it does not matter the aircraft. For me it was the GPU Tweak utility for my Nvidia GTX 1080ti. Can you disable the Radeon Relife and see if this fixes your problem? You have to do these things one at a time until you find a solution. If you did a bunch of things to try to fix the problem and the problem was fixed, you would not know what you did to fix it. It is not Windows 10. Of course it could be drivers but again, please do not check your drivers and update until you have tried the disabling or uninstalling of the Radeon Relife. Page 16 suggests updating drivers and has a recommended freeware program to use. Fixing drivers has fixed problems for others in the past but not for all so it is another hit or miss fix. The fact that P3D worked okay by disabling the dll.xml's and made you think it was fixed but all it did was take some load off of your sim. If any of the modules being loaded by the dll.xml, I would think it is the fsuipc. That causes crashes many times if it is not kept up to date. The fsuipc has caused crashes for me even though I only use it to log my FPS until I updated it. Still it has also caused serious pausing in the P3DV4 and making the game unplayable until it is updated. It's a nice utility but it can cause issues. I have did not get crashes after setting up a default profile for my GPU overclocking program but today I ran P3D in "Silent Mode" and got another crash. I should have changed the profile to the default but decided to try the Silent Mode and see it I could keep it at that. Now I have totally uninstalled the ASUS tweaking program. I did that to see if I get any more crashes. If so, my issue is narrowed to the motherboard pins that hold the CPU. If any are bent and touching another pin, it causes this problem too.

Apologize. I was looking at the version of your dwrite.dll and that version is the same as mine. I have a recent crash report and my OS version is the same as yours. I got the build number from going to the Windows Update page, clicking on OS Build Info on the right side of the page. So I was wrong. I have the QW787 and flew it just today (and a couple of times yesterday) and have yet to get a crash. It is difficult for me to believe your crashes are caused by the QW787. There are thousands of users and so far only you have reported an error showing the faulting module as dwrite.dll. By the way, just because the error report showed dwrite.dll was the faulting module, it does not indicate it was the cause of the crash. It just provides a clue and, in this case, the Internet shows dwrite.dll is associated with DirectX and Topography and this is why I suggested your video card drivers were corrupted or out of date. Your video card is DX12 capable so the specifications indicate it is compatible. Do you have any utility that is overclocking or adjusting the vram on the video card? For me I have a utility called the ASUS GPU Tweak II. Some GPU makers have gadgets like this they provide with their cards. I did some searching and your card might have come with the Radeon Software Crimson ReLive Edition which is AMD's advanced graphics software for enabling high-performance gaming and engaging VR experiences. So I believe this package is equal to the ASUS GPU Tweak II that I have installed. I had issues with the ASUS Tweak II as it was causing random crashes with P3D but mostly with the PMDG aircraft. I had a crash with the CS757 too but do not recall having crashes with the QW787. As I recalled, I had so many crashes, I reset Windows 10 and reinstalled everything (which did not help). I just recently reinstalled the QW787 as I wasn't going to reinstall everything until I got my crashes fixed. The ASUS GPU Tweak utility was showing no issues. The fans were working and I did not see anything abnormal. I had the tweak utility set at OC Mode or Game Mode. It controlled the fans well and they remained in the 60C range. I decided to go the User Profile Mode. For the ASUS GPU utility, the Profile Mode allows you to set your own settings so I left everything at default but raised the GPU fans to 100%. No more crashes since doing this. I believe it was a setting ASUS set up in Game Mode and/or OC Mode. I have seen a lot of members having unexplained crashes and believe it is the utility that controls the GPU. Try doing what I did (if you have a similar utility) by using the default settings for the GPU but increase the speed of the fans as the default settings does not control the fans very well.

dwrite.dll is a Windows 7/8/10 system file developed by Microsoft. It could be corrupt. To check, open the Command Prompt in elevated status (click on search box>type cmd>right click on Command Prompt and select Run as Administrator). Once open, type SFC /scannow and then click on Enter (note the space between SFC and /). It will scan your system for corrupt and missing files and replace any if found. I do see where it loaded successfully as module 128 so it is not missing but still could be corrupted. The dll is responsible for "Microsoft DirectX Typography Services" which, to me, is related to your graphics card and terrain mapping. Perhaps just reinstalling the drivers for your Radeon graphics card will fix it. Windows 10 is out of date too. There was an update released on 14 August. Run Windows Update. I have never seen anyone get this error before. Does the error only occur when running the QW787? What about any default or other aircraft installed (must be at the same airport and scenery where the QW787 crashed). It could be a problem too with scenery. It could also be one of the modules loading via your dll.xml (there are two in P3D)(see page 10, AVSIM CTD Guide). Whenever I get an error, the first thing I do is to disable the dll.xml's and remove all Add-on Scenery from the Documents/Prepar3D v4 Add-ons folder and move them to a Temp folder. I then run P3DV4 with the same scenario where I got the crash and see if this fixes the problem. If it does, I know my problem is associated with a loaded module or an add-on scenery. The AVSIM CTD Guide has further guidance.

I think it has something to do with permissions as I stated above but here is one possible fix - https://forums.flightsimlabs.com/index.php?/topic/9386-fsl_a32xxdll-causing-crash/ When you installed the A320, you should have seen security warnings to accept the loading of modules. If not, then maybe your anti-virus program has quarantined one of the modules. You should only install FSX addons with the anti-virus program disabled or exempt the program from being scanned during installation.

I have a feeling it is a permission thingy like in the past - https://forums.flightsimlabs.com/index.php?/topic/7178-installation-instructions-for-a320-x-fsx/