I have a core dump that has been generated at a customer site. All I can find from the timestamp is which second the dump-file was opened. (Part of the filename.)
Is it possible to see at which millisecond the exception has occurred?
This would enable me to compare more accurately with the log file (which is in milliseconds).
As mentioned above, .time is how you get a dump occurrence timestamp. For user dumps, it's unlikely - from my observation it's always just second-level accuracy. For kernel dumps however I have found it's accurate to the millisecond.
However, I've found that the "System Uptime" in .time output is accurate to the millisecond for both kernel and user dumps. In the case that you are able to get the last boot time to millisecond accuracy (for instance by calling "wmic os get lastBootUpTime") you could add the uptime to the lastBootUpTime to get an accurate dump occurrence timestamp.