Disable/Remove the plugin and wait until the crash appears again.
PS: I also have/use IsDotNET plugin and didn't have an issue with it so far. But I only use it to quickly check something, either in custom columns or TC search, and usually I do that in another TC instance which gets closed after I have the information. What I'm trying to say is that the plugin is used only for a short period of time.
Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
I would also try disabling IsDotNet.wdx and check if you still get any crashes. If yes, compare the address with the list of remaining plugins. But there shouldn't be any more crashes if IsDotNet.wdx was really the problem.
2ghisler(Author)
I deactivated it. But it won't last long. I'm not going to abandon the plugin. I need him. It is better to identify the problem that occurred in 10.50b1.
The plugin IsDotNET probably crashes when it sees a very specific file which looks similar to a.Net file but isn't one, or is a variation it doesn't recognize correctly. You should try finding a file which causes the crash, I can forward it to the developer of the plugin so he can fix it. The developer progman13 is a very active developer, he has developed many paid plugins for me.
2ghisler(Author)
I don't see any connection with the problem file. TC never crashed with such an error before switching to hybrid sleep.
And I am quite familiar with Progman13 myself. We corresponded more than once on various issues.