1. #1

    Join Date
    Apr 2017
    Posts
    2

    Dump files created on Win10 v1703 Build 15063.250 issues?

    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


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    writhziden's Avatar
    Join Date
    May 2012
    Location
    Colorado
    Posts
    2,328
    • specs System Specs
      • Manufacturer:
        Sony
      • Model Number:
        VPCF232FX/B
      • Motherboard:
        Sony Corporation VAIO
      • CPU:
      • Memory:
        8.00 GB Crucial CT2KIT51264BF1339 DDR3 1333
      • Graphics:
      • Sound Card:
        Realtek High Definition Audio/nVidia High Definition Audio
      • Hard Drives:
        TOSHIBA MK5061GSY 500 GB (465 GB actual)
      • Case:
        Laptop black matte case with backlit keyboard
      • Cooling:
        Air cooling via fan and heat exchanger heatsink
      • Display:
        Laptop display
      • Operating System:
        Windows 7 Home Premium 64 Bit

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

    Yes, and with my symbols path set to srv*c:\Symbols*https://msdl.microsoft.com/download/symbols, I have to run .dmps twice most times to get the symbols to load. It did not used to take two runs for that.
    Last edited by writhziden; 04-27-2017 at 06:29 PM.
    cwsink says thanks for this.

  3. #3
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    15,839
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

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

    Same here.
    cwsink and writhziden say thanks for this.

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015

  4. #4

    Re: Dump files created on Win10 v1703 Build 15063.250 issues?

    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.
    writhziden and jcgriff2 say thanks for this.

  5. #5

    Join Date
    Apr 2017
    Posts
    2

    Re: Dump files created on Win10 v1703 Build 15063.250 issues?

    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.
    jcgriff2 says thanks for this.

Similar Threads

  1. Replies: 0
    Last Post: 03-22-2017, 06:25 PM
  2. User account issues in Redstone 1 build 14393.5
    By SpartacusSystem in forum Windows 10
    Replies: 5
    Last Post: 08-10-2016, 10:10 PM
  3. Replies: 33
    Last Post: 09-14-2015, 01:22 PM

Log in

Log in