My sincere apologies if I seem to be coming on a bit strong, but it’s just a mark of my frustration over this matter. Your patience and persistence is admirable as is your apparent unwillingness to lock this thread until we find the solution, and I thank you for that.
Same here. I sent a PM earlier, but my outbox isn't showing it so I have no idea if it sent. Long story short, I'm not against participating in a session but at the same time I'm not sure what value such intervention could provide. Same situation as Cruachan, with the added nuance of a completely fresh installation. My schedule is also a bit restricted - especially end-of-week. At this point I'm left with tweaking BIOS settings to hope for the stupid issue to go away, or that a future Live Update mysteriously fixes it.
In any event I'm of two minds on this issue. Thinking in my day job mindset as an engineer, I'm not usually the one to have such problems nor do I often have to concede defeat. On the other hand, I just want to use the darn thing for what it's for - flying. The crash on exit doesn't bother me so much from an operational standpoint (in all reality it's quite inconsequential), it's just that I see that as a potential harbinger of other problems (i.e. well, it's obviously causing an issue somewhere, so is this going to manifest itself somewhere else down the line?) I'm an engineer - I abhor loose ends. As I've mentioned before, I've had occasional seemingly random crashes periodically, so in my mind they
could be related. Yes, I know there is no evidence to prove it. But neither is there evidence to
disprove it. That's what's so vexing and frustrating about it. (I say I don't usually have tech problems, but in another example to the contrary, I think I'm the one-in-a-million case where I still maintain an FSX installation that I would contend is still more stable than P3D4. At least when FSX does crash it's usually apparent why.)
If nothing else, I was expecting a complete system reinstall once I no longer require FSX, so that would theoretically clear up the hardware/Windows question. Not quite ready for that yet. I'm actually contemplating building a new rig anyway, so who knows.
UPDATE: I reset my BIOS to "Optimized Defaults" (I typically run a modest overclock) and as seems to be the pattern, first time did not CTD but all subsequent exits bombed out. I'm sure it's coincidence but it's almost as if there's some kind of cache somewhere getting corrupted.