wrong estimation at Hash Match

SirWilliam 2017-07-14 09:29:52

In an inner join on a table with up-to-date full scan statistics the hash match estimated 2.760 rows (149K) , whereas the actuals are 544.700.285. This leads to a spill in the tempDB in a sort later on. How to investigate where this mismatch comes from and how to correct this?
alt text
Matak 2017-07-16 22:59:10
Pictures of execution plans dont help at all. Can you attach the actual plan ?