[MKANET]

Im curious, how did you determine that? There is a problem in the dsplayer code; but theres something our system configurations share that the dsplayer code doesn't account for (something that other Kodi DSplayer users don't have that don't have this issue at all)... whether it's a piece of software or hardware or respective software setting... or combination of them. It may not be possible for us to prevent it if the offending component we share is hardware configuration related. We should still try to find what we share in common to help Aracnoz know where to poke around in the Dsplayer code to fix it.

...let me put it this way... if we were to zip up our entire Kodi folder and all its contents... then let someone who doesn't have the issue test it on their PC, it is most likely not going to have the issue anymore.

No, it's not the driver. After taking my system apart one day, I figured out the freezing most likely has something to do with code for the player that can't be fixed by any external tinkering. That is frustrating to the user, but likely true.

If you click on any of the items in the changelog in the first post, you can see the actual code that makes the player work. It is fairly complex, and I'm sure one line could make the whole thing crash.

The only hint as to what could be wrong, for me at least, is that turning on madVR debugging seems to help considerably. Something engaged by debug mode is causing the player to be more stable. This is probably causing a headache for aracnoz because he can't replicate this issue on his test system. But hopefully he can piece together what parts of the player might be impacted by debug mode, which could cause such a crash. I also provided some crash logs, which may or may not contain some information about the crash.

I would advise turning on madVR debugging. You will end up with a bunch of debug logs on your desktop, but the player will behave normally with no performance hit.