September 30, 20178 yr Hi Bryan, Just bought your 747 qots II. After installation when I click on the icon I get this message: FS2Crew_747_configurator has stopped working. My p3d folder is excluded from my avast and I've uninstalled FS2Crew and reinstalled using administrator rights but to no avail. Alex Rui Laureano Lisboa, Portugal
October 1, 20178 yr Commercial Member Question: The 747 Config Manager will not load. Answer: 1. Delete and Reinstall the Riva Tuner Statistics Service. That worked for one user. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
October 1, 20178 yr Author Hi Bryan thank you, but I don't have Rivatuner installed. I am using windows 7 with service pack 1. I'm installing into P3D4. Rui Rui Laureano Lisboa, Portugal
October 1, 20178 yr Commercial Member You're running something on your system that's mucking with the Config Manager. It's a guessing game. Ensure your anti virus is excluding the P3D folder. Sometimes they run interference. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
October 1, 20178 yr Author It shouldn't be the antivirus either, I've excluded the p3d folder and have just tried reinstalling and starting fs2crew with avast offline. I'm going to try to find out what I have running in the background. Rui Laureano Lisboa, Portugal
October 1, 20178 yr Author Bryan I couldn't find any obvious cause. Can you give me any clues at to what kind of software could be preventing your configurator from running? I am not supposed to have any unusual software here unless you count the oculus rift software. Rui Laureano Lisboa, Portugal
October 1, 20178 yr Author Could I try to reinstall .NET? What version does FS2crew require? Should it be of any help, my fs2crew start center where I can configure my FSX MD11 starts up fine. Edited October 1, 20178 yr by alex extra info Rui Laureano Lisboa, Portugal
October 1, 20178 yr Commercial Member The MD11 Start Center and the 747 Start are totally different; they have nothing in common code-wise. Long shot, but try this: https://www.microsoft.com/en-us/download/details.aspx?id=30135 B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
October 1, 20178 yr Author Thanks Bryan. Unfortunately it did not solve it. damn. Rui Laureano Lisboa, Portugal
October 1, 20178 yr Author Bryan, this is the stack list from the configurator failing taken with process explorer. Perhaps this can provide a clue to you: ntoskrnl.exe!memset+0x61a ntoskrnl.exe!KeWaitForMultipleObjects+0xd52 ntoskrnl.exe!KeWaitForMutexObject+0x19f ntoskrnl.exe!PoStartNextPowerIrp+0xba4 ntoskrnl.exe!PoStartNextPowerIrp+0x1821 ntoskrnl.exe!KeWaitForMultipleObjects+0xf5d ntoskrnl.exe!KeWaitForMutexObject+0x19f ntoskrnl.exe!NtWaitForSingleObject+0xde ntoskrnl.exe!KeSynchronizeExecution+0x3a23 ntdll.dll!NtWaitForSingleObject+0xa KERNELBASE.dll!WaitForSingleObjectEx+0x9c mscorwks.dll!ClrCreateManagedInstance+0x5c29 mscorwks.dll!ClrCreateManagedInstance+0x5e1e mscorwks.dll!CopyPDBs+0x1dcf8 mscorwks.dll!PreBindAssembly+0x7eaef mscorwks.dll!CorDllMain+0xa857 mscorwks.dll!CorLaunchApplication+0x1ac7b mscorwks.dll!CorLaunchApplication+0x1cc69 KERNEL32.dll!UnhandledExceptionFilter+0x160 ntdll.dll!EtwEventSetInformation+0x1d74 ntdll.dll!_C_specific_handler+0x9c ntdll.dll!RtlDecodePointer+0xad ntdll.dll!RtlUnwindEx+0xbbf ntdll.dll!RtlRaiseException+0x248 KERNELBASE.dll!RaiseException+0x3d mscorwks.dll!CreateApplicationContext+0x2d813 mscorwks.dll!Ordinal24+0xb927 mscorwks.dll!Ordinal24+0xdaf6 mscorwks.dll!StrongNameSignatureVerificationEx+0x2fb5 mscorwks.dll!StrongNameSignatureVerificationEx+0x2fcb mscorwks.dll!CreateAssemblyNameObject+0x2248a mscorwks.dll!PreBindAssembly+0x25c88 mscorwks.dll!PreBindAssembly+0x53a0d PresentationCore.ni.dll+0x93c1f5 PresentationFramework.ni.dll+0x3f6a58 PresentationFramework.ni.dll+0x3f6815 PresentationFramework.ni.dll+0x3f67a2 PresentationFramework.ni.dll+0x3f04cc PresentationFramework.ni.dll+0x3f043f PresentationFramework.ni.dll+0x3eeaf4 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x36fe82 PresentationFramework.ni.dll+0x374298 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3126d4 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3306e9 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x367ea2 PresentationFramework.ni.dll+0x36782e PresentationFramework.ni.dll+0x366a1f PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x367ea2 PresentationFramework.ni.dll+0x36782e PresentationFramework.ni.dll+0x3667f1 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x36fe82 PresentationFramework.ni.dll+0x374298 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.Classic.ni.dll+0x3295a PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3664e6 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x367ea2 PresentationFramework.ni.dll+0x36782e PresentationFramework.ni.dll+0x366a1f PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3306e9 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3664e6 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x36fe82 PresentationFramework.ni.dll+0x374298 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x314a29 PresentationFramework.ni.dll+0x373b3f PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3126d4 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x36eecf PresentationFramework.ni.dll+0x36ec66 PresentationFramework.ni.dll+0x31a722 PresentationCore.ni.dll+0x78a0ba PresentationCore.ni.dll+0x8452ef PresentationCore.ni.dll+0x847721 PresentationFramework.ni.dll+0x362fa6 PresentationFramework.ni.dll+0x3f2d03 PresentationFramework.ni.dll+0x361d4b PresentationFramework.ni.dll+0x361817 WindowsBase.ni.dll+0x11b0fc WindowsBase.ni.dll+0x11afec WindowsBase.ni.dll+0x11edc0 mscorlib.ni.dll+0x30dd38 mscorwks.dll!IEE+0xdd36 Rui Laureano Lisboa, Portugal
October 1, 20178 yr Commercial Member Hi Rui, Send me a Support Ticket via the Contact us page at: www.fs2crew.com Thanks, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
October 1, 20178 yr Author With Bryan's fantastic support it was possible to work around this issue and I now have FS2Crew working in my QOTSII. If I ever discover what is keeping my manager from starting I'll post it here. Rui Laureano Lisboa, Portugal
Archived
This topic is now archived and is closed to further replies.