April 19, 201214 yr FSX was running and my default aircraft was displaying fine then I switched aircraft and the notice came up that FSX was stopping and here's the Problem signature: Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: Flight1_GarminG1000.GAU Fault Module Version: 1.0.0.0 Fault Module Timestamp: 4f606c02 Exception Offset: 000827f6 Exception Code: c0000417 Exception Data: 00000000 OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Additional Information 1: 3094 Additional Information 2: 3094e5f797103ef68651a7044df535cd Additional Information 3: 59c6 Additional Information 4: 59c692283360298edf30ca38f12f7fd5 I checked my entire disk and loaded a program to eliminated the Vundo virus and after a complete scanning it reported all clean so I re-downloaded the 182T and loaded it into FSX. On one hand I spent $48 for a plane I can't use but more than that, this is a really great plane and I enjoyed flying it. Can anyone tell me what is wrong? I thank you for any help.
April 19, 201214 yr Do you have flightsim installed to the default directory? Did you run the installer as administrator for this addon? if you did have a virus it may have messed up the operating system. have you run windows updates, directx, video card drivers? Flight1 also has their own forum and support email address.
April 19, 201214 yr Author FSX is installed to a non-default directory and after installing that is where it installed to. Yes, I install as administrator but I had a run in with the Vundo virus. I've cleaned and scoured everything and got all-clean notices from my virus protection as well as the Vundo fix software. That if means I may have some messed up files in the system that has to be looked at as well. I've also posted on the F1 forum but I know there's a lot of brain power over here at Avsim. Thank you for replying. good flights, Cal
April 19, 201214 yr Go into the FSX.cfg and delete the trusted modules (you'll have to trust them again when you restart FSX). If you can find just the one for the Flight1 gauge, then delete that line, save, and restart FSX. Make sure you trust these gauges when asked by FSX when you first start up. You may have hit the do not trust button instead of trust. Since you got a virus earlier you should do a file system integrity check by opening the CMD prompt as an Administrator and then entering sfc /scannow. Also run Windows update. Hope this helps. Best regards, Jim
April 20, 201214 yr Author Thanks Jim, I thought I could replace the 182T gauge with the one from Flight 1 Mustang but it has a different name. Your suggestions sound promising but I have never attempted anything quite that deep. I will try them and see what occurs after I have set up a reliable restore point. with your help I anticipate getting back a favorite, thank you. good flights, Cal
April 23, 201214 yr Author Hello Jim and all, I still think the Vundo virus was attached to the download wrapper but I got my plane back. I did all that you suggested and my comp is running well, thank you. Once I knew everything was clean and all related files removed, I downloaded and did a clean install but this time I allowed the program to install into the default locations. I was directing it to install in a different drive letter and directly into airplanes and it mis-installed. Using defaults it installed correctly and I have my plane back. If Vundo shows up I ignore it. Thanks again, Cal
Create an account or sign in to comment