Rebooted from bugcheck, W10/pro x64

Page 2 of 2 FirstFirst 12

  1. Posts : 83
    Windows 10 Pro x64
    Thread Starter
       #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 Computers

  2. axe0's Avatar
    Posts : 14,787
    Windows 10 Pro
       #12



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


  3. Posts : 83
    Windows 10 Pro x64
    Thread Starter
       #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 Computers

  4. axe0's Avatar
    Posts : 14,787
    Windows 10 Pro
       #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 Computers


  5. Posts : 83
    Windows 10 Pro x64
    Thread Starter
       #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 Computers

  6. axe0's Avatar
    Posts : 14,787
    Windows 10 Pro
       #16

    speedlever said:
    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 Computers


  7. Posts : 83
    Windows 10 Pro x64
    Thread Starter
       #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 Computers

  8. axe0's Avatar
    Posts : 14,787
    Windows 10 Pro
       #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 Computers


  9. Posts : 83
    Windows 10 Pro x64
    Thread Starter
       #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 Computers


 
Page 2 of 2 FirstFirst 12

  Related Discussions
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 00:02.
Find Us




Windows 10 Forums