Report problems, with logs, and suggest features, with the Feedback Hub

This blog post has moved to

Comments (12)

  1. David says:

    After latest update computer won’t boot keeps acting like it’s updating then goes to black screen sometimes with only a mouse cursor have to hard reset then it does it all over again. Was able to get into safe mode once but wouldn’t do anything in there very weird looks like I am going to have to restore from original disks windows 7.

  2. David says:

    Wish I could get back into safe mode found a possible fix in registry I really don’t want to have to erase computer. The built-in Windows 10 tools couldn’t fix and or said drive was locked.

  3. i had window 10 afther the reboot of my pc now i cant instal it and the program telsme im to late what can i do to donwn load it.

  4. Terri says:

    Since an auto-reboot of an update (evaluation copy build 14986.rs_prerelease.161202-1928) my computer keeps rebooting with stop codes. I get different codes all the time as the reboots happen over and over again. When I do get to the desktop, it doesn’t stay very long before it also reboots. I’m not sure what to try to fix it. I can’t stay in long enough to do much. If I try to stop using the preview build, will the computer be able to just do that, or will it need to boot up and download new things? (I’m not sure it will be able to.) I tried to restore to previous point, but it said there weren’t any within 10 days or something like that. What? Why such a short limit? I didn’t think not having a few restore points was even possible. I’m not sure what to try. I found a BIOS setting that referred to Plug and Play OS. It was set off. In the past I had Windows XP on the machine. I updated a year or so ago to Windows 10 64 bit. The machine has an i5 but it’s an older mother-board installed June 2012, ASUS P7P55 LX. I thought it might have PCI-Express 1.0 s;pts because a new video card had a lot less pins so I returned it, but the online info for the motherboard says PCI Express 2.0 so I’m confused now. I know my video card (quite old) and driver are not great with Windows 10, but I’m not sure if this preview build pushed that over the edge or there is something else with other drivers going on. Any ideas of what I can try since I have constant reboots but don’t want to reinstall from scratch yet?

    1. To help figure out what the bluescreen is, can you grab C:\Windows\memory.dmp and send it to me?

      You can roll back to a previous build by going to Settings | Update & Security | Recovery | Go back to an earlier build

    2. Tom Sussman says:

      I get the same error updating to 13986 from 13965 the stop code first said dxg error, when it rebooted it said pool handler error, I’m running Windows 10 Pro in Vmware workstation player 12.5, I think it maybe related to your 3D graphic changes. I’ve come so far with the windows insider experience, I would hate for this to end my journey.

  5. Dan Packard says:

    Numerous blue screen errors since loading build 14986. I cannot keep the computer up long enough to generate feedback on it.

  6. Bob blandin says:

    I installed build 14986 and now my laptop crashes after 1 minute. with a verity of different error messages such as “Attempted to write to read only area”, “page fault in non paged area”. also most of the message boxes are blank, kernel security is”. I have reset the laptop twice by downloading the ISO copy. Bob

  7. Domain Information
    Registration Date:
    Expiration Date:
    Updated Date:
    Name Servers:
    Registrant Contact
    Domain Administrator
    Go Daddy Operating Company, LLC
    14455 N Hayden Rd Suite 219
    Postal Code:
    Administrative Contact
    Domain Administrator
    Go Daddy Operating Company, LLC
    14455 N Hayden Rd Suite 219
    Postal Code:
    Technical Contact
    Domain Administrator
    Go Daddy Operating Company, LLC
    14455 N Hayden Rd Suite 219
    Postal Code:
    Raw Whois Data

    Domain Name: GODADDY.COM
    Registry Domain ID: 4013247_DOMAIN_COM-VRSN
    Registrar WHOIS Server:
    Registrar URL:
    Update Date: 2013-06-02T12:16:24Z
    Creation Date: 1999-03-02T05:00:00Z
    Registrar Registration Expiration Date: 2021-11-01T11:59:59Z
    Registrar:, LLC
    Registrar IANA ID: 146
    Registrar Abuse Contact Email:
    Registrar Abuse Contact Phone: +1.4806242505
    Domain Status: clientTransferProhibited
    Domain Status: clientUpdateProhibited
    Domain Status: clientRenewProhibited
    Domain Status: clientDeleteProhibited
    Registry Registrant ID: Not Available From Registry
    Registrant Name: Domain Administrator
    Registrant Organization: Go Daddy Operating Company, LLC
    Registrant Street: 14455 N Hayden Rd Suite 219
    Registrant City: Scottsdale
    Registrant State/Province: Arizona
    Registrant Postal Code: 85260
    Registrant Country: US
    Registrant Phone: +1.4805058800
    Registrant Phone Ext:
    Registrant Fax: +1.4805058844
    Registrant Fax Ext:
    Registrant Email:
    Registry Admin ID: Not Available From Registry
    Admin Name: Domain Administrator
    Admin Organization: Go Daddy Operating Company, LLC
    Admin Street: 14455 N Hayden Rd Suite 219
    Admin City: Scottsdale
    Admin State/Province: Arizona
    Admin Postal Code: 85260
    Admin Country: US
    Admin Phone: +1.4805058800
    Admin Phone Ext:
    Admin Fax: +1.4805058844
    Admin Fax Ext:
    Admin Email:
    Registry Tech ID: Not Available From Registry
    Tech Name: Domain Administrator
    Tech Organization: Go Daddy Operating Company, LLC
    Tech Street: 14455 N Hayden Rd Suite 219
    Tech City: Scottsdale
    Tech State/Province: Arizona
    Tech Postal Code: 85260
    Tech Country: US
    Tech Phone: +1.4805058800
    Tech Phone Ext:
    Tech Fax: +1.4805058844
    Tech Fax Ext:
    Tech Email:
    Name Server: CNS1.GODADDY.COM
    Name Server: CNS2.GODADDY.COM
    Name Server: CNS3.GODADDY.COM
    Name Server: A11-64.AKAM.NET
    Name Server: A1-245.AKAM.NET
    Name Server: A20-65.AKAM.NET
    Name Server: A6-66.AKAM.NET
    Name Server: A8-67.AKAM.NET
    Name Server: A9-67.AKAM.NET
    DNSSEC: unsigned
    URL of the ICANN WHOIS Data Problem Reporting System:
    >>> Last update of WHOIS database: 2017-03-01T05:00:00Z <<<

    For more information on Whois status codes, please visit

    The data contained in, LLC's WhoIs database,
    while believed by the company to be reliable, is provided "as is"
    with no guarantee or warranties regarding its accuracy. This
    information is provided for the sole purpose of assisting you
    in obtaining information about domain name registration records.
    Any use of this data for any other purpose is expressly forbidden without the prior written
    permission of, LLC. By submitting an inquiry,
    you agree to these terms of usage and limitations of warranty. In particular,
    you agree not to use this data to allow, enable, or otherwise make possible,
    dissemination or collection of this data, in part or in its entirety, for any
    purpose, such as the transmission of unsolicited advertising and
    and solicitations of any kind, including spam. You further agree
    not to use this data to enable high volume, automated or robotic electronic
    processes designed to collect or compile this data for any purpose,
    including mining this data for your own personal or commercial purposes.

    Please note: the registrant of the domain name is specified
    in the "registrant" section. In most cases,, LLC
    is not the registrant of domain names listed in this database.

    Soooooo; MS what's all that? :)

    Your using go.daddy servers? Huh.. isn't that the same ones you claim are so bad, or at least you did how many years back.
    Also notice Akamai Technologies, Inc.

    Who is that? I see them Amazon and :P, and a number of cloud servers all tied into you and yours. I think it's interesting to say the least. :)

    So many eyes MS. :) lol what's next?

    OH and google declared not too many days ago that CLOUD FLARE yet another cloud you all use for your well this very blog.. :) of course they as in google mentioned that those all the way to HAVE BEEN COMPROMISED.
    What say you? Hmm MS? Hello?

    I wonder what users who see this will think.

    1. Sorry, I don’t understand what you’re asking.

  8. Daniel J. Baugh says:

    I can’t thank you enough! I am still learning and I appreciate your help and tutelage.

Skip to main content