ASUS Intel SKT1150 MoBo

Intel core i54670K 4x3.4GHz 6MB Cache

2x WD500GB SATAlll 7200rpm HDD (C has opsys on it 395/500 free; D has only Sims on it 450/500 free)

Windows 7 pro x64

3x Nvidia GTX770 gpus driving 5 screens, all 22” DVI monitors with same resolution, matched in FSX

Nvidia driver 442.19 and DX11

Centre view GPU 1 (top) 

45 left  & right views GPU 2 (middle)

90 left & right  views GPU 3 (bottom)

 

G’Day,  hope all the info above helps?  This is an old system but was quite ‘high end’ and has been running FS9 without any issues. It forms the ‘outside views’ part of my sim, with a slightly less spec computer operating 4 screens of panels; networked with Widescreen and FSUIPC.  Both sims are loaded into their own files ie no Programsx86!  As there seems to be no VATSIM or much else for FS9 anymore, thought I would (at last ) shift to FSX.  My internet is very slow (live in the sticks so its not fibre)  so I cant go steam.

 

I uninstalled  FS9 (including reg) and loaded FSX Gold boxed +accelerator and registered/activated it. Started FSX and instantly got CTD with ‘fatal error’.  Error log gave a ‘g2d.dll’ error message. 

Downloaded avsim CTD and FSX settings help guides and read them.  Updated Nvidia drivers. Went through the setup/tweak list in avsim guide. 

 

When I start FSX about 15 seconds after ‘FSX’ blurb page appears, GPU 2 & 3 drop out,  monitors show ‘no signal’ blank screen and monitor standby light, they will not recover until re-start pc.  FSX continues to run on GPU1 at good fps.

 

Cant find any error messages that refer to GPU stopping (have tried alt/enter; no response).

 

Isolated the FSX config and let it create a new one. Same same.

 

So I reinstalled FS9 (which has run faultlessly on this PC for 9 years) and it ran as per usual, except when I shut it down, then GPU1 & 3 give same error as 2 & 3 in FSX.

 

Having done same as above the lower spec PC runs FSX easily, 3 screens in VC and 45fps (I chop it back to 30 though).

 

Any ideas gents, help would be most appreciated. Feel I am missing something obvious but cant put a finger on it.  Head really starting to hurt………..

 

Anyone seen this before please?

 

Regards, Mike King

2 hours ago, MikeKing7 said:

My internet is very slow (live in the sticks so its not fibre)  so I cant go steam.

I don’t have a simple answer to your problem, but you don’t need a fast internet connection to use the Steam Edition of FSX. The only time you need any significant bandwidth is for the initial download of FSX and you could just leave it overnight for that. Subsequent running of the sim needs an absolutely minimal internet connection - you can also opt to run it offline. The Steam edition has a number of improvements which may, possibly, help with your problems:

https://fsxinsider.com/fsx-steam-edition-and-boxed-fsx-what-is-the-difference/

Even if they don’t, it’s much easier to get up and running as you no longer need to install Acceleration (or the service packs) and there are no potential registration issues as it doesnt need any.

Edited February 24, 20206 yr by vortex681

Thanks for your input Vortex681, I ran the 2 PCs networked and had the sim (FS9) on both. would I be able to install FSXSE on both from a single licence and would I need to work wideview and FSIUPC?

Regards

On 2/24/2020 at 4:12 PM, MikeKing7 said:

would I be able to install FSXSE on both from a single licence and would I need to work wideview and FSIUPC?

Regards

My understanding is that you can have the same Steam game on more than one machine but only one instance can be played at any time. No idea about wideview and FSUIPC.

Are they connected by SLI and what PSU are you using?

Hello acev, sorry for the delay in replying I have been away.  I use(d) 2 seperate PC (PC1 runs FS and 4 screens of panels, PC2 runs FS and 5 screens of views) linked with a cross over network cable and Wideview and FSUIPC.  Its worked well for about 8 years with really good FPS.

 

But took advice and upgraded to windows 10 pro and FSXSE, since which time its been a bale of trouble! such is life.......

It sounds like a complicated set up with many different possible issues, I would recommend starting from the ground up. Reformat and start with 1 screen at a time until you encounter the problem. This might help you work out where the issue is. 

If all else fails you can revert back to W7 if its a dedicated machine this shouldn't make much different on such old software.