February 3, 20197 yr 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 Edited February 3, 20197 yr by AFavors Best Regards, Aaron Favors i7-2600 Overclocked Turbo Boost to 3.9GHz 8GB Dual Channel DDR3 at 1333MHz Dual 1.5GB GDDR5 NVIDIA GeForce GTS 450 - SLI 1TB SATA 3Gb/s (7,200RPM) 32MB Cache High-Performance CPU Liquid Cooling 875W Multi-GPU Approved PSU Windows 7 Home Premium 64 bit SP1 FSX SP2 (no Acceleration)
February 3, 20197 yr 1 hour ago, AFavors said: 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 Have you tried disabling your AV and running the sim as a admin also don’t forget to restart your computer. Zdenek Cebis
February 3, 20197 yr Author 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 Best Regards, Aaron Favors i7-2600 Overclocked Turbo Boost to 3.9GHz 8GB Dual Channel DDR3 at 1333MHz Dual 1.5GB GDDR5 NVIDIA GeForce GTS 450 - SLI 1TB SATA 3Gb/s (7,200RPM) 32MB Cache High-Performance CPU Liquid Cooling 875W Multi-GPU Approved PSU Windows 7 Home Premium 64 bit SP1 FSX SP2 (no Acceleration)
February 3, 20197 yr Commercial Member What was your VAS? This looks like OOM issue. Chris Makris PLEASE NOTE PMDG HAS DEPARTED AVSIM You can find us at http://forum.pmdg.com
February 9, 20197 yr Author 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. Edited February 9, 20197 yr by AFavors Best Regards, Aaron Favors i7-2600 Overclocked Turbo Boost to 3.9GHz 8GB Dual Channel DDR3 at 1333MHz Dual 1.5GB GDDR5 NVIDIA GeForce GTS 450 - SLI 1TB SATA 3Gb/s (7,200RPM) 32MB Cache High-Performance CPU Liquid Cooling 875W Multi-GPU Approved PSU Windows 7 Home Premium 64 bit SP1 FSX SP2 (no Acceleration)
Archived
This topic is now archived and is closed to further replies.