H all,i have a problem with the new fs2crew voice commander Level-D.I want to work through the tutorial.But every time I try to open the panel by clicking on the VSI, the FSX (with SP2 + Windows 7) crashes immediately.I dont know why.I hope someone can give me a hint?Greetings from GermanyAndi

Hi Andi,Please run a program that comes with Win 7 called "Event Viewer".Just type "Event Viewer" in the Windows Start Search box.That'll give you more info on what files are associated with the crash.Unfortunately without more information, I'm just guessing but do see this thread and try the suggestions from it.There are 8 suggestions listed there:http://forums1.avsim.net/index.php?showtopic=291685Cheers,

Hi Brian,thank you for the answer.Here isthe error message within FSXProblem signature:Problem Event Name: APPCRASHApplication Name: fsx.exeApplication Version: 10.0.61472.0Application Timestamp: 475e17d3Fault Module Name: ntdll.dllFault Module Version: 6.1.7600.16385Fault Module Timestamp: 4a5bdb3bException Code: c0000005Exception Offset: 00067315OS Version: 6.1.7600.2.0.0.768.3Locale ID: 1031My drivers are up to date (yesterday). I have also re-installed FS2Crew.Some details about my system:Core i7 920Windows 7 64 bit with english language pack for fs2crew (Vistalizator)6 GB RAMSound on board Realthek HDNvidia GTX 295

Hi,That Error Report is point to NTDLL.DLL as the problem.I think the NTDLL is usually associated with Internet Explorer.It's not an FS2Crew file.At any rate, run a full anti-virus sweep and I'd also clean your registry.Also, please see this for more info on NTDLL.DLL errors.http://pcsupport.about.com/od/fixtheproblem/a/ntdlldll.htmBest,

okay guys,now i have a clean installation of FSX without any Addons. Only the Level-d + FS2crew.now displays the following errorProblemsignatur:Problemereignisname: APPCRASHAnwendungsname: fsx.exeAnwendungsversion: 10.0.61472.0Anwendungszeitstempel: 475e17d3Fehlermodulname: FS2AUDIO.dllFehlermodulversion: 0.0.0.0Fehlermodulzeitstempel: 4bb01ad3Ausnahmecode: c0000005Ausnahmeoffset: 0004e130Betriebsystemversion: 6.1.7600.2.0.0.768.3Gebietsschema-ID: 1031and i havent this dll-file in my windows directorie. I have twice installed FS2Crew, without some changes

FS2Audio.DLL is my DLL; it's what handles the audio system.When you installed FS2Crew, did you let the installer go all the way to the end?Or did you click 'cancel' before it finished?It takes a few minutes for all the DirectX files to be updated, and my Audio DLL needs those DirectX files or it won't work.Some people get impatient and click "cancel" before the installer finishes.Please try re-installing FS2Crew 767 again, and confirm for me that you waited for the installer to finish.Cheers,

Hallo,the Installer was complete finished.I have installed FS2Crew twice again. Without success. The dll is not here.Andi

Ah yes its true. The DLL was in the syswow64 folder. But if i make a copy and take this into system32 folder it dont work again:The same error:Problemsignatur:Problemereignisname: APPCRASHAnwendungsname: fsx.exeAnwendungsversion: 10.0.61472.0Anwendungszeitstempel: 475e17d3Fehlermodulname: FS2AUDIO.dllFehlermodulversion: 0.0.0.0Fehlermodulzeitstempel: 4bb01ad3Ausnahmecode: c0000005Ausnahmeoffset: 0004e134Betriebsystemversion: 6.1.7600.2.0.0.768.3Gebietsschema-ID: 1031

Please load the 767 in "Windowed" mode... that's important... hit alt-enter prior to opening the FS2Crew Main Panel.You need to be in Windowed mode in order to see any error messages.You should get some kind of error message...Please email me a screen shot of that error message to:admin *at* FS2Crew.comEDIT: That same DLL is used is numerous different FS2Crew products, and SYSWOW64 is the appropriate folder for your OS.From experiences, problem with that DLL usually suggest a damaged or corrupt Direct X install.Please download the latest version of Direct X from Microsoft, and install it.Best,

send...

An update to this:The user solved the problem by doing a clean re-install of Win 7.There was probably a virus or corrupt system file that was causing the problem before.So if this happens to you, you might want to consider doing a fresh install of your OS.Cheers,