The availability of direct dump modification raises the possibility of such memory dumps specifically modified to alter structural and behavioral diagnostic patterns. For example, to suppress certain module involvement or introduce fictitious past objects and interaction traces such as Execution Residue (Volume 2, page 239) and Module Hints (Volume 6, page 92). There can be 2 types of such artifacts: strong tampering with new or altered information completely integrated into memory fabric and weak tampering to confuse inexperienced software support engineers and memory forensics analysts.
For example, in one such experimental process memory dump we see Exception Stack Trace (Volume 4. Page 337) pointing to a problem in calc