Updating to the latest version (11.18) is recommended, just as a matter of course.
If you're not having any luck with VMMap (How to find components causing memory leaks), then disabling viewer plugins and shell extensions is the next thing to try: Crash, exit or high CPU when viewing certain directories. (The guide is about crashes, but the investigation steps also apply to memory leaks.)
If you can tie the leaks to a particular file, folder, or type of files, then that can narrow down the components which need considering.
It's also worth checking that you don't see the same leak when using File Explorer to view the same directory.