Hello,
This is really up to you, if you want to go through the bother of finding where this issue lies or if you are satisfied with the explanation that the DisplayLink driver is technically unable to be the source of a BSoD.
As we know it can't be a DisplayLink issue, I will not try to reproduce it locally (I don't play much). This needs to be handled by the company whose code trips the BSoD.
Here is an article on how to manage the
Windows dump creation settings with location.
Kind regards,
Alban