|
Windows shows StackHash_HHHH as the faulting module as a fallback when it cannot identify a loaded module at the memory address of the instruction that was being executed when a DEP error is trapped. A hash code computed on the contents of the instruction stack is just a shorthand way of identifying what was on the address stack when the fault occurred--if multiple crashes occur with the same hash, then it points to a possibly deterministic and reproducible error. These sorts of errors are caused by the same sorts of faults that produce other memory addressing faults--it can be unstable or faulty hardware, or a host of programming or data errors, any of which can cause the CPU to try loading an instruction from a bad address.
|