Please help me with this subject considering that I am not a programmer but more of a power user. Let's say that I would like to contribute to a source-closed application where I find diverse issues by utilizing procdump for example. Obviously, the list of potential issues is huge : hangs, crashes, memory corruption, etc. What is intriguing is that, as user, I find a lot of hangs that normally do not provide an every time replication (eg appear in certain conditions such as low memory, cpu, driver interference and other "bizarre behavior").
I usually use WinDbg + Microsoft Symbols Server and check FOLLOWUP_IP. However, I have noticed that some issues get the same bug tracking number from devs which means that it's a possible duplicate.
Thus, the question: As a user - How do you tell based on dump file only that you experienced a different issue than you reported in the past? Is my method bad? Any other methods?