Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. Dynatrace counts the number of pages read from disk to resolve page faults. This includes also pages read to satisfy faults in the file system cache (usually requested by applications) and in non-cached mapped memory files.
Window's Resource Monitor lists so-called "hard faults" per process. It seems that it counts page reads to satisfy faults in non-cached mapped memory files but it completely ignores pages read to satisfy faults in the file system cache. Since file system cache is global, a distinct assignment of page faults to single processes is not feasible. But instead of counting the faults for the virtual "System" process, Resource Monitor seems to ignore them completely.
I suggest to search for a process which either reads a very huge file (size > a standby memory) or reads a very high number of files within a short time period (e.g. to index all files on a local disk or a network share). The Disk Activity view in Window's Resource Manager may help here. Another helpful too could be RAMMap's File Summary tap (https://technet.microsoft.com/en-us/sysinternals/rammap.aspx)
@Shane K., thank you for answering! I take if from your answer that there isn't a 1 to 1 mapping with regards to the mapping of the metric HPF (in AppMon) and in perf.mon (Windows)? And that the metric HPF itself is comprised of several elements that are represented as different metrics in perf.mon?