The absence of error codes (edit: actually just noticed you're using a scan tool. Ideally check for codes with INPA, most of the DME low-level operation codes don't have external P-Codes linked to them) related to supply power, OS integrity, memory integrity, etc. make this seem like a very sudden event that is killing the DME immediately with no opportunity for it to log codes. It might be that the issue is happening fast enough that the thresholds aren't met for storage ofr the codes into the EEPROM before it fails completely. What doesn't align with that thinking though is your observation of several minutes of rough running before it fails completely.
I agree with Terra though that it would be worth replacing the DME with a known good unit and retesting, that will for sure tell you whether the issue is inside the DME or out.
I agree with Terra though that it would be worth replacing the DME with a known good unit and retesting, that will for sure tell you whether the issue is inside the DME or out.

Comment