Windows 10: 0x00000119 ntoskrnl.exe+16c310

Page 3 of 3 FirstFirst 123

  1. Posts : 20,076
    windows 10 professional version 1607 build 14393.969 64 bit
       24 May 2017 #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 ComputerSystem Spec

  2.    24 May 2017 #22

    zbook said: View Post
    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 ComputersSystem Spec


  3. Posts : 20,076
    windows 10 professional version 1607 build 14393.969 64 bit
       24 May 2017 #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 ComputerSystem Spec

  4.    24 May 2017 #24

    zbook said: View Post
    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 ComputersSystem Spec

  5. axe0's Avatar
    Posts : 13,620
    Windows 10 Pro
       24 May 2017 #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 ComputersSystem Spec


  6. Posts : 20,076
    windows 10 professional version 1607 build 14393.969 64 bit
       24 May 2017 #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 ComputerSystem Spec

  7.    24 May 2017 #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 ComputerSystem Spec


  8. Posts : 20,076
    windows 10 professional version 1607 build 14393.969 64 bit
       24 May 2017 #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 ComputerSystem Spec

  9. Ztruker's Avatar
    Posts : 6,264
    Windows 10 Pro X64 17134.191
       24 May 2017 #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 ComputersSystem Spec


 
Page 3 of 3 FirstFirst 123

Related Threads
Hi, new member here, I thought this looks like the place to try and get over a annoying problem. Every 1 or 2 days intermittently I am getting a BSOD, it usually happens when my PC wakes up from sleep, but I can't repeat it. (I have tried manually...
0x00000119 BSOD only in Fallout 4. in BSOD Crashes and Debugging
Hello, i have recently been getting the most inexplicable error when playing Fallout 4. For whatever reason sometimes when i am playing it my game will have a suddenly huge spike in fps, dropping from 60 to 5-10, and the audio will distort terribly....
Hello everyone. I have been having some problems with my windows 10. I upgraded from windows 7 about one and a half month ago. I had many problems all around with multiple BSOD per week. I took up the opportunity to format my HDDs and did a...
BSOD, Error 0x00000119, Playing Unturned in BSOD Crashes and Debugging
Hi Tenforums, After playing a bit of Unturned and watching Youtube, my PC made a BSOD. I have no idea what made happend and I would love some help. I have uploaded the dump file, like I was instructed, from this website. All tempetures...
I recently upgraded to Windows 10. Yesterday I experienced a red boot screen after restoring to a windwos restore point installing a new GeForce driver, that is probably related to this issue. That only happened once. I reinstalled my GPU drivers...
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 08:46.
Find Us