When Memory scan is invoked manually via Clam Sentinel, Clamscan does crash. (see below)
Memory scan does not crash, when Clam Sentinel starts with the Setting selected:
"Scan the memory when the program starts"
Scan Memory with Clam Win does also not crash.

I don't look for a solution. Just want to mention it.
Looked at the differences and noticed, that the Clamscan option "--archive-verbose"
does make the difference - in my case at least. With that option, it does crash.
____________________________________________________________________
Clam Sentinel - Memory scan
Loading virus signature database, please wait... done
*** Scanning Programs in Computer Memory ***
---Please login as an Administrator to scan System processes loaded in computer
memory---
*** Memory Scan: using ToolHelp ***

*** ClamWinDumper ***)\IN\ClamWin\bin\ClamTray.exe: [100%]
*** C:\Program Files (x86)\IN\ClamWin\bin\clamscan.exe Crashed
ExpCode : 0xc0000005
ExpAddress: 0x00401E33
scanning: [C:\Program Files (x86)\IN\ClamWin\bin\ClamTray.exe]

Clam Sentinel has not been updated for a couple of years now. It is basically an orphan.

Regards,