Check Scanning Queue Size & Frequency
Too many scan tasks queued and running simultaneously can lead to excessive memory use or database load.
- High-frequency scan schedules (e.g. every 5 mins)
- Repeating schedules with overlapping scans
- Very broad IP ranges
Check Performance scanning is enabled if so try disabling to see if that helps. It's possible there are performance scanning targets hogging up the queue since these run in the background and are not visible on the scanning queue
Are you scanning more than just errors with the event scanning.
SQL Database Performance (if on-prem)
A bloated or underperforming database can trigger memory spikes on the scan server indirectly.
Run database cleanup tool : C:\Program Files (x86)\Lansweeper\Tools
- Stale assets
- History size
- tblNtlog, tblSoftware, tblEventlog