June 24, 201510 yr Anybody else getting CTDs out of the Mustang G1000? I did install some airports but I've turned them off and they're still happening. Looking for clues. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
June 24, 201510 yr I've had them off and on since the addon was released. Normally relating to a navigraph update I've done. What airac are you on? | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
June 24, 201510 yr Author The latest. Maybe I should go back one. Error handling could certainly be better. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
June 24, 201510 yr Author I sorted it out, I think, though, I don't know what caused it. I use SimStarter and I noticed that one profile worked and another didn't. I backed up my profiles and then copied over the one that wasn't working. Would be nice to know the cause, if only to help other folks. Everything seems to be back in greased grooves. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
June 25, 201510 yr What did the Windows Event Log state when this happened, Gregg? Point to some C++ stuff perhaps?
June 25, 201510 yr Author What did the Windows Event Log state when this happened, Gregg? Point to some C++ stuff perhaps? Here's the fault: Faulting module name: Flight1_GarminG1000_510.GAU, exception code: 0xc00000005, Fault offset: 0x0000daaf If I had the code, I'd be able to catch it in the debugger. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
June 26, 201510 yr Just assuming things but I think Ryan is closest with suggesting some (causal?) relation to the Nav data being read. Sorry for being no better help, Gregg.
June 26, 201510 yr Author I went back to the latest Airac and it's fine (so, it wasn't the NavData). Did some looking around yesterday to see if I could find what caused the issue. May try again over the next couple days. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
Create an account or sign in to comment