Dump files created on Win10 v1703 Build 15063.250 issues?

[cwsink]

Hi everyone,

I was wondering if anyone else is having trouble with dump files generated on computers with the configuration in the title. I'm using windbg 10.0.15063.137 which is the latest from the Windows SDK available online. The most obvious problem is the module timestamps are completely nonsensical. For example, executing "lm t" on a dump shows timestamps from the 1970s, 1980s, 2059 and most showing "Invalid". Having trouble attaching a file to the post so please download it from here to see what I'm talking about. It was generated on my own computer but I've seen a number of people asking for help analyzing dump files showing the same issue. Is it a symbol server issue, perhaps?

Thank you,
cwsink

 

[writhziden]

re: Dump files created on Windows 10 1703 15063.250 issues?

Yes, and with my symbols path set to srv*c:\Symbols*[NO-PARSE]https://msdl.microsoft.com/download/symbols[/NO-PARSE], I have to run .dmps twice most times to get the symbols to load. It did not used to take two runs for that.

 

[jcgriff2]

Re: Dump files created on Windows 10 1703 15063.250 issues?

Same here.

 

[Mr Happy]

Windows 10 1703 dmp files point to memory corruption and driver dates wrong

I opened a thread about the same on the TechNet forum, and somebody brought this to my attention. Nice to know its not just me! I will update here if I get any answer on the TechNet thread.

 

[cwsink]

If anyone is still wondering what is going on with the timestamps in dumps generated on Windows 10 1703 systems and later I have it on good authority (Andrew Richards at Microsoft) that Microsoft have changed the timestamp to a checksum for internal use at Microsoft. He and Chad Beeder have added it to a list of topics to discuss in a future episode of Defrag Tools on Channel 9 which they both host.