Deadlock from select statements
Deadlock happens when one query acquires a lock on a object (rows, data pages, extent, tables etc) and other resource tries to access it. Smallest unit in SQL Server is data pages and SQL holds a lock on page while working on it. So, yes it is possible that two select statement can create deadlock.

Solution:


WITH(NOLOCK) - If your data is fine to be read dirty
Use Read committed snapshot or Snapshot isolation
Try to keep transaction small and in batches
Use bound connection - it will allow two connection to use same transaction &amp; lock


This answer is based on your question, as your screenshot doesn't contain any information.