May 10, 20242 yr Here's from Windows Event viewer. Not sure if this will help you figure out issue. When I run without A&O's MSFS runs fine. Just thought you might like to know this info just in case there is an issue. I'm a paid user of A&O's Log Name: Application Source: Application Error Date: 5/9/2024 11:45:44 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Monza Description: Faulting application name: LorbyAxisAndOhs_MSFS.exe, version: 4.10.51.0, time stamp: 0x65ac0a23 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x000000002ba08848 Faulting process id: 0x4b3c Faulting application start time: 0x01daa28c7049dba6 Faulting application path: C:\Program Files\LorbyAxisAndOhs_MSFS\LorbyAxisAndOhs_MSFS.exe Faulting module path: unknown Report Id: 38095f44-b497-45e2-bacf-c47a991fe8fb Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2024-05-10T03:45:44.2945681Z" /> <EventRecordID>50592</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Monza</Computer> <Security /> </System> <EventData> <Data>LorbyAxisAndOhs_MSFS.exe</Data> <Data>4.10.51.0</Data> <Data>65ac0a23</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>000000002ba08848</Data> <Data>4b3c</Data> <Data>01daa28c7049dba6</Data> <Data>C:\Program Files\LorbyAxisAndOhs_MSFS\LorbyAxisAndOhs_MSFS.exe</Data> <Data>unknown</Data> <Data>38095f44-b497-45e2-bacf-c47a991fe8fb</Data> <Data> </Data> <Data> </Data> </EventData> </Event>
May 10, 20242 yr Commercial Member 2 hours ago, RadarNC said: I'm a paid user of A&O's Please send an email with your proof of purchase to the support address (it is on the last page of the manual). This is not a known issue. Please include all information that you can give about your computer, sim and AAO configuration in the email. Plus, all error messages from the Windows event logs that pertain to this matter (the error message above tells me nothing, only that "something went wrong". There should be another one with a stack trace in it?). LORBY-SI
October 9, 20241 yr I too am having issues. If I reboot and start from scratch it works for a while then A&O becomes unresponsive then stops altogether. killing it and relaunching it take FOREVER and even the it stops responding at every input. Reboot machine and all is good. It is not using excessive CPU or memory. It just stops working. My machjine is no slouch
October 9, 20241 yr Commercial Member 4 hours ago, Paladin569 said: It just stops working. Sorry, but this is not a known issue either. Can't say that I've even heard of this before. It is pobably not the app itself, but something you do with it. Sounds like something is flooding AAO, causing a massive amount of workload (errors?) in the app, like a script or input device. I can only give generic advice: - Go to Hardware->Device Blacklist and move everything into the list on the right with the "Ignore" button that isn't a game controller that you are actually using in AAO. Also ignore all mice and keyboards, AAO is talking to them through other means. - Maybe reinstall both of the VCRedist libraries (x86 and x64), just in case some other program has messed with them. - Check the AAO logfiles, if they are unusually big. Some exceptions will always be there in the logs, but if there are hundreds or thousands of them, that will be a problem. - AAO does not work properly with preview versions of Windows. So if you are in the Windows Insider Program and are running early bird Windows builds, the app will be in trouble. Edited October 9, 20241 yr by Lorby_SI LORBY-SI
October 17, 20241 yr The last one could be a hit. I am on an insider build of Win 11. I have not had this issue in the past either and have been away for some time from Simming. I had to update to the latest version of AAO so I though that might be the issue. but apparently not. Thanks for the generic pointers though they may yet be of assistance Brad
Create an account or sign in to comment