0x00000119 ntoskrnl.exe+16c310

Page 3 of 3 FirstFirst 123

  1. Posts : 41,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #21

    In administrative command prompt type chkdsk /x /f /r
    Then Y
    then reboot again

    It can take hours to complete.
    When it has completed open administrative Powershell and copy and paste:

    get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt
      My Computer


  2. Posts : 45
    Windows 10
    Thread Starter
       #22

    zbook said:
    In administrative command prompt type chkdsk /x /f /r
    Then Y
    then reboot again

    It can take hours to complete.
    When it has completed open administrative Powershell and copy and paste:

    get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt
    Okay, test is over and here is the file.
      My Computers


  3. Posts : 41,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #23

    1) run administrative command prompt: sfc/ scannow
    2) report whether there were any integrity violations
    3) reboot
    4) run chkdsk /x /f /r again
    5) report chkdsk results again

    Sometimes when chkdsk /x /f /r repairs the drive it can compromise the operating system. So always best to run sfc /scannow and or dism /online /cleanup-image /restore health after it completes.

    Most often the orphaned files that were found during the repair are no longer there after reboot.

    So after the dism restorehealth run chkdsk to confirm that there are no longer any errors or orphaned files.
      My Computer


  4. Posts : 45
    Windows 10
    Thread Starter
       #24

    zbook said:
    1) run administrative command prompt: sfc/ scannow
    2) report whether there were any integrity violations
    3) reboot
    4) run chkdsk /x /f /r again
    5) report chkdsk results again

    Sometimes when chkdsk /x /f /r repairs the drive it can compromise the operating system. So always best to run sfc /scannow and or dism /online /cleanup-image /restore health after it completes.

    Most often the orphaned files that were found during the repair are no longer there after reboot.

    So after the dism restorehealth run chkdsk to confirm that there are no longer any errors or orphaned files.
    There were no violations and I reran the other thing as well.
      My Computers


  5. Posts : 14,901
    Windows 10 Pro
       #25

    Why /x /f and /r?
    /f is included in /r and /x, I do understand /r and /x though.


    The chkdsk log looks good, many things have been repaired and deleted but haven't returned after another chkdsk :)

    Sometimes when chkdsk /x /f /r repairs the drive it can compromise the operating system. So always best to run sfc /scannow and or dism /online /cleanup-image /restore health after it completes.
    I've read about those kind of issues, but have never seen it happening to anyone I've (tried to) helped.
    If this would occur, however, often those commands wouldn't work for different reasons.


    Just a recommendation, it would be best to run both chkdsk and SFC every once in a while like every once in a month.
    Every month new updates are released, by running both chkdsk and SFC you keep the health of the OS as it should giving less issues :)
      My Computers


  6. Posts : 41,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #26

    In April after a clean install there were chkdsk problems. A chkdsk /f /r led to a nonbootable computer. Another clean install was then performed.
      My Computer


  7. Posts : 926
    Windows 10 Pro
       #27

    Then there was a big problem before chkdsk. I think the system was bad and chkdsk gave the rest. Chkdsk cannot break a system, thats nonsense, sorry.
      My Computer


  8. Posts : 41,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #28

    chkdsk did not break the system. chkdsk /f /r did. I was working on the computer with microsoft level III support in India. That is their research team. They recommended the next time to run only /f without /r and then send to them the results. That way a fix could have possibly been done. Again the chkdsk repair moved or removed files such that it was no longer bootable.
      My Computer


  9. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #29

    The /r basically does a surface scan of the entire drive which is why it takes so much longer to run. If it caused problems then it's quite likely you need to replace the drive.
      My Computers


 

  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 07:26.
Find Us




Windows 10 Forums