Windows 10: Rebooted from bugcheck, W10/pro x64 Solved

Page 2 of 2 FirstFirst 12
  1.    14 Oct 2015 #11

    I finally got around to running the tools (C:\ drive, properties\tools\error checking). It said it fixed errors.

    Then for good measure, I ran chkdsk /r from an elevated cmd prompt. By the time I took a look at it, the chkdsk had finished and it was back to the log-in screen.

    Here's is what was reported in the event log after I ran the error checking tool:



      My ComputersSystem Spec


  2. Posts : 13,351
    Windows 10 Pro
       14 Oct 2015 #12



    Please check your other hard drives too, to make sure they're fine too.
      My ComputersSystem Spec

  3.    14 Oct 2015 #13

    OK. I ran the error checking tool on my 2 other internal drives (d:\ and e:\, both spinners). No errors were found.

    I assume that is sufficient and equivalent to running chkdsk /r on them? If not, chkdsk wants to dismount those drives before running. I'm not sure of the implications of dismounting a drive.
      My ComputersSystem Spec


  4. Posts : 13,351
    Windows 10 Pro
       14 Oct 2015 #14

    Chkdsk /r scans the hard drives for bad sectors and in case there are bad sactors it recovers the readable data.
    Yes, it is sufficient to run it.
      My ComputersSystem Spec

  5.    14 Oct 2015 #15

    Thanks a lot for your help. I'm not sure exactly what we found, other than the memory tests good and the C:\ drive (SSD) did a successful repair... whatever that issue was. Oh, and by run it, I assume you mean the windows tool found in the drive properties, not the specific chkdsk /r command?

    Shall I mark this solved?
      My ComputersSystem Spec


  6. Posts : 13,351
    Windows 10 Pro
       14 Oct 2015 #16

    speedlever said: View Post
    Thanks a lot for your help. I'm not sure exactly what we found, other than the memory tests good and the C:\ drive (SSD) did a successful repair... whatever that issue was. Oh, and by run it, I assume you mean the windows tool found in the drive properties, not the specific chkdsk /r command?

    Shall I mark this solved?
    Both do the same thing, but the property utility has a UI.

    If you don't get any BSOD within the next few days, please mark this thread as solved :)
    If you do get any BSOD within the next few days, please use the tool again and upload the zip file.
      My ComputersSystem Spec

  7.    14 Oct 2015 #17

    The reason I wonder if there's a difference is that the UI command seems to operate quicker than the chkdsk /r command does. Or maybe I didn't watch long enough to notice.
      My ComputersSystem Spec


  • Posts : 13,351
    Windows 10 Pro
       14 Oct 2015 #18

    I'm not sure what command the UI uses and if it even really checks every sector.
    Usually a used sector cannot be accessed twice as that could cause trouble.
      My ComputersSystem Spec

  •    17 Oct 2015 #19

    No more BSODs. I don't know if the original was a fluke or just what.

    Let's called it fixed, but not really solved. I consider it solved when I know what caused the issue and apply the appropriate fix!
      My ComputersSystem Spec


  •  
    Page 2 of 2 FirstFirst 12

    Related Threads
    Hello, I have had this problem since day one with windows 10 and its about to force me back to windows 7. Random times when working on my laptop it will just freeze. If there is something playing be it music or youtube it will make a god awful...
    Dear all, I have an odd issue with my laptop since upgrading to Windows 10. The first time I boot I cannot connect to my home Wifi, however when I reboot I can. It is always the same every time I switch it on in that it will only connect on the...
    Solved Help needed in debugging bugcheck: 0xC000021a' in BSOD Crashes and Debugging
    My Windows 10 system continues to 'blue screen' with the bugcheck: 0xC000021a at startup and then will come up after a subsequent press of the restart button (I turned off 'automatic restart'). I installed Whocrashed to provide me with some...
    BSOD on Startup. The bugcheck was: 0x0000001e in BSOD Crashes and Debugging
    Hi, I received a BSOD on startup on the 7th of August at 6:57 pm. I have been trying to look into why this has happened but couldn't find out. Could you please help me find out the cause of the BSOD and how to fix it?
    I couldn't find any tutorial or help in the search utility can anyone help me?
    Our Sites
    Site Links
    About Us
    Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

    Designer Media Ltd
    All times are GMT -5. The time now is 22:12.
    Find Us