AFavors

HIGH 1M'S maybe 2, but with current setup I shouldn't get OOM's till around 3.5M. Anyway I haven't been able to reproduce the black screens. I'm still having issues at this point, but don't think its PMDG's problem. Thanks as always, and I'll let you know if anything else (like this) pops up. Only other concern...(i think I responded to someone else's post) is having to "allow" Navigraph access with every load of the B747-8. I'm heading to check if there's a remedy in the other topic now.

The only AV i run is microsoft security essentials, and its never been a problem before. But I will try it! As for FSX, I always run it as admin

Hello all, Just this evening I had a CTD while vacating the rwy in Anchorage after a flight from MYNN. I tried to get the whole error report but it was quite lengthy, and I couldn't copy or past it. I'll give you guys all the info I was able to receive and relocate through the event viewer and last problem reports. I was flying the 747-8F. Weird thing was, after the crash I tried to restart the flight and and screens were black and controls unresponsive. I was able to push any buttons or click any knobs. Here's everything I could retrieve... AppName: fsx.exe AppVer: 10.0.61472.0 AppStamp:475e17d3 ModName: pmdg_747qotsii.dll ModVer: 1.0.0.0 ModStamp:5c328a23 fDebug: 0 Offset: 004376b3 - System - Provider [ Name] Application Hang - EventID 1002 [ Qualifiers] 0 Level 2 Task 101 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2019-02-03T00:05:00.000000000Z EventRecordID 1645783 Channel Application Computer Aaron-PC Security - EventData fsx.exe 10.0.61472.0 2a0c 01d4bb51c60f199b 0 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe e4903953-2746-11e9-b204-74f06de8d275 55006E006B006E006F0077006E0000000000 Binary data: In Words 0000: 006E0055 006E006B 0077006F 0000006E 0008: 0000 In Bytes 0000: 55 00 6E 00 6B 00 6E 00 U.n.k.n. 0008: 6F 00 77 00 6E 00 00 00 o.w.n... 0010: 00 00 .. Source Microsoft Flight Simulator® Summary Stopped responding and was closed Date ‎2/‎2/‎2019 7:01 PM Status Not reported Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Problem signature Problem Event Name: AppHangB1 Application Name: fsx.exe Application Version: 10.0.61472.0 Application Timestamp: 475e17d3 Hang Signature: 7416 Hang Type: 0 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Hang Signature 1: 74167c54b519e3d44b2dc8d4b03b5f77 Additional Hang Signature 2: 7449 Additional Hang Signature 3: 74499b888e28fd75fe7a0a3a9661d3e4 Additional Hang Signature 4: 7416 Additional Hang Signature 5: 74167c54b519e3d44b2dc8d4b03b5f77 Additional Hang Signature 6: 7449 Additional Hang Signature 7: 74499b888e28fd75fe7a0a3a9661d3e4 I could not get the rest of the info from the PMDG one that was part of the error report from FSX. Thanks in advance

Same problem for me as well. I checked the option to remember, updated operation center, and 748 to the latest versions. I run the FSX version of the QOTSII, and have a full chart/fms service with Navigraph.

Issue seems to be resolved. (Or), a one-time fluke.

This is so weird! Sitting on the ramp at EHAM, configuring the plane for departure. Its new to me, until recently(before update), I had not had 1 issue with this aircraft. Not even the Caution light! I just did the research on that while here, so my next plan is to try it again, and change the panel state in the process. I'll report back in about an hour.

Hello All, Been having a problem since the latest update to QOTS. So far all the info I have on the problem is this: APPNAME: FSX.EXE APPVER: 10.0.61472.0 APPSTAMP:475E17D3 MODNAME: PMDG_747QOTSII.DLL MODVER: 1.0.0.0 MODSTAMP:5955CDCA FDEBUG: 0 OFFSET: 00337393 From the error report (it attempted) to send to Microsoft. I'm in the process of gathering more Info, But was wondering if this has been seen, as of yet? Aaron

thanks

Not a Hardware problem. I have the same issue at times. Its like someone is intentionally turning the sound off and on. I'm waiting on the fix for it myself. Disregard...Having different issue

Yes, I use ASN. But while I was checking multiple aircraft to research the failure. It was not active, and I tried different locations. But thanks for that tip. I will look further into that as well.

New twist to the weirdness... I just went back and attempted to load an older saved flight, and it loaded with the doors open and fully operable. The standby FD works and I've been able to cycle through the door commands, successfully, numerous times. So apparently I can't start a new flight but might can fly an old one!

Already did, Thanks a lot for your help Dan. I'll be sure to post the resolution when/if we find it. This has to be the weirdest problem I've come across to date. Monday and Tuesday, I flew this aircraft and I had no problems. Late Tuesday night, however, (on my return flight from Rio to Heathrow) I was delayed on departure due to not being able to open the doors. I initially thought it was because ground ops were automatic and I was trying to open the doors after the FO armed them all and was prepping the plan for dep. I ignored the problem and just took off anyway. During the fight is when I noticed the problem with the standby flight display, and realized something else must be wrong. All day yesterday and today have been spent trying to figure this thing out. Hopefully, with any luck, this great tech team here @PMDG will have me back up and flying in no time. I'll be sure to keep you posted.

I was actually in the process of doing that. No luck! I even turned the ground operations to auto. Shut down engines and set chocks. When the T7 tried to open the doors, I did get the message from fsx saying the main exit was opening. But it didn't open. Its almost like the open command was wiped from the system. Even still the fmc command never changed.

Yes. I just selected the aircraft from the selection screen and placed it at the gate. By default my panel state will load in the same condition. Engines off and gpu connected. I don't have any pre-SP1 saved panel states or flights.

YES