What makes you think Couatl "CAUSED" this ?
As explained, so many times in this forum, Couatl CANNOT CRASH THE SIM, because it's an .EXE and by definition, an .EXE CANNOT cause a crash in the sim. In your case, the crash is not even happening in the sim, it's something more low-level, see here:
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
I can see what you are being mislead it's a "Couatl fault", because you then see PROCESS_NAME: couatl.exe but that doesn't mean Couatl CAUSED the crash, what caused the crash was the driver, since ONLY a driver can cause a BSOD, normal applications runs on different privilege level so, unless they also install a diver ( which surely isn't the case ), it's technically impossible for a normal application to cause a BSOD.
I think Couatl.exe was reported only because it might be the running application while the BSOD report was generated, so it's misleading you.
The only thing that's been updated is the new NVIDIA drivers, do we think it's not playing nice with couatl?
Couatl it's just a Python interpreter, and doesn't have any relationship with anything related to video drivers, and doesn't do anything graphic-related. It just use Simconnect to send orders to the sim to create objects, which the sim will create on its own.
So yes, it's technically possible that, if there's a video driver problem, or bug, or wrong tweak or wrong settings that, when an otherwise perfectly legal object is created, for some reason the video driver crashed, you might easily mislead it's either GSX or Couatl, because they sent the order to the sim.
However, is quite puzzling you see this in that location. I assume you were cruising at high altitude ? If yes, GSX is completely disabled over 10K feet, that's to prevent a known bug in P3D4 that, when nearby airports are queried in remote areas, the simulator *itself* crashes, so we just don't do any queries when cruising to prevent this.
However, this used to cause ( before we stopped GSX over 10K feet ) a crash in just the sim, never a BSOD because, even P3D itself, cannot cause a BSOD, since it's a standard application. Only a driver can do that.
Again, the location seems strange because, if it were a video driver bug crashing because GSX tried to create an otherwise perfectly correct object, it shouldn't happen *there* because GSX only creates object with you are on ground.
Basically, over 10K feet, they only thing our software does, is to read your position, and see if you go lower to 10K feet, to eventually reactivate GSX, which will also not do much, other than checking the nearby airports, to allow you to select a gate while in flight. It's only after you select a gate, that "graphic" things will start to happen, which could potentially involve the video driver.
