This is a new one to me, and before I started to disable anything and get serious about troubleshooting, I thought I would ask if anyone had ever seen this problem, and possibly knew the cause and/or solution.First of all, a few preliminaries:I have flown FS since the days of the 5" floppies. I am a multiple monitor with multiple windows display addict. I don't know when I began the multiple monitor bit, but it was long ago and many versions prior to FS9 and FSX. Never, have I seen the issue in question before now.Secondly, this is a brand new issue that has raised its head. I have flown the aircraft in question with the existing setup for many months if not years. I also have not made any revisions, nor added anything I can think of just prior to seeing this issue. I don't believe there have been any changes of which I am aware since I took the same steps with no problem.Third: I have the RXP-GNS530-32 installed in all of the aircraft in question. For the flights in question, it was used only for the flights in the Twin Bonanza.Fourth: I have the ISG Smith's Style FMC installed in the Posky Bombardier CRJ200, and use it for controled flight.Fifth: The PSS default FMC was used for both the Dash 8 and Airbus 321.Sixth: Each flight has been flown multiple times over the past week.Okay, first chapter: (FS9)1. My wife was just taking a trip, so I thought I would duplicate her flights. (KLWB-ROA-KLWB is virtual. No I don't have a twin Comanche darn it.)2. Compiled a flight in the Twin Bonanza from my home base, KLWB to KROA.3. Compiled her first leg, KROA to KCLT in the Posky Bombardier CRJ2004. Compiled her second leg, KCLT to KLAS in the PSS/IFDG Airbus 3215. Compiled her return first leg, KLAS to KCLT in the PSS/IFDG Airbus 3216. Compiled her return second leg, KCLT to KROA in the PSS Dash 87. Compiled the return from KROA to KLWB in the Twin Comanche8. The initial flight had no problems.9. After landing, I switched aircraft for my next leg. I discovered that when I undocked either the RXP GPS, or the FMC for the new aircraft and then tried to move it to my secondary monitor, my primary screen went black for a few moments, then I got the MS window telling me FS9 had to shut down (with the check mark option if I wanted it to restart automatically.)10. If I restarted FS9, (I use the default MS Cessna 172), FS9 started up just fine.11. When I tried to select the previous PSS aircraft that had the monitor move problem, FS9 shut down again at that point. 12.I discovered that if I restarted my computer, then make a fresh startup of FS9, that I could then switch aircraft, and move undocked windows to my secondary monitor with no problem The flights were then completed with no issues.OK, at this point, I assumed that it was simply a glitch relative to switching these three party aircraft that was not compatible between the two. If I restarted from scratch, I thought the glitch was removed.I also considered that it might be a video problem, but I doubt that now due to the following discovery.Second Chapter;1. Just compiled a flight from KLWB to KJFK in the Eaglesoft Citation X (Older version with the isg1 Smith's Styhle FMS).2. I discovered that even though I startup with the MS172, from that point switch to the Citation, that when I try to move the FMC or the Default MS GPS to the secondary that I get the shutdown problem described above. I have tried restarting everything, switching monitors between the primary and secondary, various resolutions, etc. My first thought was that I had a video problem that was getting worse, and had now reached the point that undocked windows could not be moved any more. I am second guessing that now. I went back to the previous scenario, and they repeated exactly. No worse, and a fresh restart of the computer removed the problem. In addition, there is no sign of the problem in FSX with the same planes, and the same scenario exactly In other programs, I see no sign of the problem relative to undocked window movements.Seems to be more serious with the Citation than it was with the other three aircraft. I have not gone far enough yet to know just how many and which planes and windows have the problem and which don't. In the default 172 under default conditions, I see no sign of it, so I assume that it is a third party glitch somewhere. However, the MSFS GPS installed in the Citation has the same problem.Has anyone reading this ever seen anything like this?Thanks:RTHAdder: My system specs follow. I realize this is overkill, but I tried to list everyting I had in an Excel spreadsheet for future reference, and it is much easier to just copy the whole thing.Primary Computer:ASUS P6T Deluxe V2 LGA 1366 Intel ATX MotherboardIntel Core i7-975 Extreme Quad Core CPUScythe SY124010L CPU Fam6GB (3x2GB) 240 Pin DDR3 1600 OCZ3P1600LV6GK MemoryWinXP Pro 64 BitEVGA 01G-P3-1180-AR GeForce GTX 285 1GB 512 bigt DDR3 Video Graphics Card21

Thanks for the reply:Negative on the "g2d.dll error".I fear this may be awfully hard to find. Seems to have all kinds of variations. Some aircraft do not have the problem at all. Others have the problem with only certain windows. Others have the problem with all windows. Restarting the computer cures the problem with some, while others just ignore the restart.I did try a system restore point prior to when I knew this existed. Same thing. That was no solution.I told one fib also. I had forgotten that I did upgrade ASA to ASE. However, that is on the secondary computer anyway. For good measure I shut the secondary computer down and tried. Same old thing.Thanks again:RTHAdder: I did try reducing a window to as small as it would go. Same thing. When I moved it to the secondary monitor, I got a black screen followed by the MS window telling me FS9 had to shut down. It does ask me if I want to send a report to MS.

Did you get the dreaded g2d.dll error? The reason I ask. Ihave a similiar scenerio. Happened after upgrading #2 monitor to a 23" WS. But I get the g2d.dll error. Wont happen when undocking and moving if I make the gauges very small.

I am presently going through all of my aircraft to see who works and who does not. I hope to find a common denominator.To be continued:RTH

I am presently going through all of my aircraft to see who works and who does not. I hope to find a common denominator.To be continued:RTH

Hi, I am sorry that I cannot help you with your problem,but.......have you considered that your wife does not want to be followed!!!!!Eddie.

Heh Heh!Maybe you are right Eddie. I wondered what that strange guy was wandering around my hanger. I'll bet he sabotaged by birds. Unfortunately, the problem is back this morning. I thought I might have it by the tail when I quit last night and was able to get everything playing after computer restarts. However, this morning, I have not been able to move undocked windows to my secondary monitor with the Eaglesoft Citation X no matter what I try. I have not figured out what is causing this, nor what I did to get it to work some of the time yesterday. Seems to be a hit or miss situation.The last things I have tried are to shut down the secondary computer completely, and disable all antivirus provisions. The hunt goes on. It does seem to be totally unique to FS9. Same plane, same conditions in FSX have no problems.To be continued:RTH

Hi, I am sorry that I cannot help you with your problem,but.......have you considered that your wife does not want to be followed!!!!!Eddie.

Current Update:I have isloated my problem down to the Eaglesoft Citation X. Something I have done relative to this bird seems to be the root of the problem. The progression has been as follows:1. Yesterday was a hit or miss situation, working some of the time, and not working some of the time. Where I left off last night was that after restarting the computer, I could move undocked windows from the Citation X to a second monitor. I thought I had something with which I could live. Restarting the computer seemed to be the solution and it was working consistently.2. This morning, I got a black screen followed by a FS9 shutdown when I attempted the previous step every time (Citation X only).3. Based on a comment about this issue by another party, I tried reducing the size of the undocked windows (minimum size) before moving them. This worked, but only for only a little while.4. Presently, no matter what I do, I cannot move undocked windows to my secondary monitor without the shutdown (Citation X Only).My total progression this morning is as follows:1. Revised my monitor arrangement. I now have my dual ViewSonic Professional Series P815 Monitors on my Primary computer. The HPw2338 monitor is now hooked up to the secondary computer. I thought maybe there was a compatibility problem between non similar monitors, but this made no difference.2. I reduced the size of the undocked windows as mentioned above. After moving them, I could then resize them full screen with no problem. However, as also mentioned above, this quit working. Ironically I can move even oversized undocked windows from other aircraft besides the Citation X with no problem.3. I then restarted the computer and selected alphetically the first third party aircraft I have installed in FS9, and moved undocked windows to the secondary computer with no problem. Without shutting down FS9 or my computer, I then selected the next third party aircraft and did the same thing. I progressively did this with all of the many aircraft in my hanger (except the Eaglesoft Citation X) and had no problems at all. I moved default windows, third party FMC's, and the RXP GPS with no problems.4. I deleted the Eaglesoft Citation X and reinstalled it with the Flight1 wrapper. (Default installation, No addon gauges or anything)Same thing. When I tried to move any undocked window, I get a black screen for a few moments, followd by the shutdown window for FS9 asking me if I want to send a report to MS.I guess the wisest thing is probably to reference this thread to the Eaglesoft forum, although I am not confident that there is anything wrong with the bird. I feel sure that something else undesirable has happened elsewhere that it simply does not like, but I am at a loss as to what it is.Respectfully:RTH

Hello:I have thought I had it resolved also, only to see it raise its head agian. It almost seems like it is playing with me. It baits me into thinking I have it working ok only to laugh at me a little later. I cannot put my finger on the cause or solution YET.I have total backups up in two locations. I have replaced the aircraft several times, reinstalled with the flight1 wrapper for a fresh neutral bird, changed screen resolutions, and restarted the computer and/or FS9 so many times they may be getting tired of it. I find that at some point I am able to move an undocked windows either reduced to minimum size, or their normal default size at will. Then moments later, same old thing again. When I barely have the unlocked window into the secondary monitor, my primary screen with my panel goes black, and moments later I get the fs9 shutdown notice. I have seen the occasion where I was able to get the undocked window into the second monitor display, but when I moved it around there, I then had the shutdown.I fly in both FSX and FS9 and have a bunch of aircraft for each, both freeware and payware. Therefore, I cannot be sure as to exactly when this problem occured. It is possible that my most recent flights with the same ES Citation X were in FSX (no problem), and it has been longer than I realize that I chose this fine plane in FS9 (use to be my default startup selection in the Eaglesoft Hanger). Some months ago I went to WinXPPro 64bit. I wonder if as the older first version, if this model of the plane might not like the 64 bit system (highly unlikely I would think).I feel sure there is some setting, gauge, or other third party item somewhere causing this, but I don't have a clue as to what it is. Everything seems to work fine until I try to move an undocked window from the Eaglesoft Citation X panel to the secondary monitor. No other aircraft or program for that matter seems to be affected, and this bird worked fine for literally years.You say: "I noticed I'm showing to video cards in my FS hardware section .0 and .1". Are you sure you are not seeing the two ports on one card? Thanks for the reply:RTH

RTH. I have done all you have, sometimes twice. Think I have it resolved ( thought it was just the EScjet also). It will then rear its ugly head again. I have often wondered it was the difference in resolution between the two monitors. Have you tried shrinking the windows down as small as they go before migrating? .

I agree. It really is strange.I also thought it might be a mismatch between monitors, although it never showed up for months if not years. That is the reason I rearranged my monitor setup. Now, both monitors are the same model, size etc. Same problem.I am afraid that I never get any type of error message referenceing the "g2d.dll" and not familiar with it. A google search might shed some light on it.Strangely, I also had this show up once on my PSS Airbus 321. However, I was in a hurry and moving rapidly relative to moving windows around. A computer restart solved the problem. I hope this is not a sign of things to come with other birds.Looks like I am going to be relegated to flying the ES Citation X only in FSX, probably until a new complete reinstallation of everything, which I sincerely hope is a long way off.Thanks for the reply:RTH

This is strange. I too am running XP64. Also running an Nvidia GPU 9800. Was considering rolling back the driver from the latest to the 182 but I see you are running it and having the same problem. I never had this problem until switching from a 19" crt Monotor for my #2 monitor to a 23" LCD widescreen. Strange. But Iget the g2d.dll error everytime FS9.