I downloaded the new beta drivers and am wondering if anyone else is running into this problem.

 

I get the following error when loading fsx with the new driver.

 

 

 

Sometimes, FSX just hangs and I never see that error message pop up.

 

If I revert my configuration to single screen, and re-install SB4, the error goes away. If I then re-enable triple screen, the same error comes up. If I revert my driver to last version, it works fine. Anyone else run into this and have a solution?

 

I've uninstalled all drivers using safe mode and re-installed.

 

I've uninstalled and re-install SB4 several times.

 

I'm at a loss.

This is not perfect but a workaround that seems to prevent most of the hangs when loading FSX with this problem.

 

Edit the dll.xml in the folder where your fsx.cfg file resides and change the <ManualLoad> option for any Squawkbox related option from False to True.

 

If FSX does put up a dialog box as a above, make sure to answer Yes every time. If you do get a hang, kill fsx, restart it and when it displays the above prompt answer yes. This dialog box is a result from having to kill the FSX process the last time you loaded. Not sure what happens if you answer no.

 

This workaround doesn't elminate FSX hangs at load time but does reduce them significantly for my system. Let me know if it works for you.

 

The following is a copy of the relevant section in my dll.xml file:

 

<Launch.Addon>

<Name>SquawkBox Transponder</Name>

<Disabled>False</Disabled>

<ManualLoad>True</ManualLoad>

<Path>C:\Program Files (x86)\SquawkBox\sbtrans10.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>SquawkBox AI Control</Name>

<Disabled>False</Disabled>

<ManualLoad>True</ManualLoad>

<Path>C:\Program Files (x86)\SquawkBox\sbaicontrol10.dll</Path>

</Launch.Addon>

An update to this post - I think I've ultimately found the problem. I've removed the work-around listed above and instead modified the settings of the FSX executable in the compatibility tab. I checked the "Disable Visual Themes" and this seems to have fixed it for good.

 

Here's a screen shot:

 

 

A final update to this post. It appears the problem has been fixed in version 301.42 of the nvidia driver which was released on May 22nd, 2012. Make sure you are running this version and not the .24 version - they unfortunately shipped a released version that reverses the subversion number of the driver so it can be a bit confusing.