The we should add a note to the OP of an appropriate thread that windows 7 users need to set BtS to XP compatibility mode to avoid certain crashes with C2C.
At least if they experience a crash to try that before they send it to us. But at this point I will definitely not be losing sleep when I see these ntdll crashes anymore - between what @Anq showed me on how to get more heap info on a mini and an expanded understanding that crashes there that I can't duplicate are due to a difference in op systems, I at least now know what to say when these come up and I should mention it when I talk about troubleshooting in the v39 Player's Guide
I think it was Alberts2 who pointed out something was more forgiving in Win10 recently - might've had to do with this same kinda thing. I've forgotten more about all this stuff than I've learned sometimes. I have to wonder if somehow it's pulling up a Null message reference. The mini doesn't show the process step by step so some of the information the intellisense would give is not available, which is why it's often better to be able to run the attached debug dll. We'd certainly know where to put a breakpoint to evaluate things but we'd need to run the debugging on Win7 to see if there's anything more it could tell us as it enters the crash spiral. I have win7 on another system but I wouldn't be able to run VS on it now.
Right... because Fanatical has no equivalence. You'll get that on occasion with Complex traits - it really is more designed for use with Developing Leaders. The leaders themselves are not well updated to the slightly different list in Complex Traits and there are a ton of traits in Complex that no leader has been given any access to at all because they don't exist in the core. Leaders need a modular update with replacements to bring them in line with Complex if you're not going to play on Developing Leaders. It's not going to cause problems, per se, but it's a known deficiency that exists right now. I should've remembered this when you brought this up but I forgot there were a few that couldn't be equated when they were removed.
Apparently Windows XP compatibility mode slowsdown PPIO a lot....
It could also be that the actual bug is some wild pointer overwriting/corrupting page management data that happens to cause a crash on Windows 7 while being checked for in Windows 10. Unfortunately if that is the case it is very hard to find out which access did that in the first place.
Thanks. I didn't realize that it wasn't supposed to be taken alone.
It probably slows down BtS in general, not PPIO specifically, I would think.
Well you CAN, and it's supposed to be possible to do, but there's a few glitches in that approach and the full spectrum of it's design is largely ignored that way.
Most likely related to PPIO. You may have installed it wrong.
You have to delete your user settings
