Windows 10: 0x00000119 ntoskrnl.exe+16c310

Why do you want me to copy the browser HTML link? It is just a link to the file on my PC, unless you want something else done here: file:///C:/Windows/System32/sleepstudy-report.html. Also, I just started running the CPU test after I removed my OC so far after 15 minutes it is going fine with just temps being a lot higher than they ever were with the OC, but it is Prime95...

 

I kinda feel stupid now. So I went and ran the Prime95 test for a 1 hour and 36 minutes with out my OC and had no issues, screenshot attached, after the test was done I thought let's try sleep. It worked, and then I tried 4 more times and it worked each time... I think it was a CPU OC issue. I am going to try and lower the OC to 4.3Ghz with same voltage and see what happens when I put it into sleep mode.

 

Yep found it is 100% a OC issue, not matter the clock the sleep mode stuff fails with an OC but works with stock.

 

Glad to hear that *Smile

I would recommend to run chkdsk /r command in an admin command prompt, on all your disks/partitions, for the errors @BSODHunter posted.

 

I ran it and it finished quite quick with no error.

 

With 2 SSD of 240GB total it takes max 15min (my experience at least) *Smile

Though it sounds to me like you ran either chkdsk in read mode or through Windows Explorer (read mode again), which is not recommended to fix errors.

 

What I did is I copied "chkdsk /r" and pasted it and then typed "y" so it would do it the next time my PC rebooted, then I rebooted my PC. The check ran for 10 seconds and was done. Not sure what else I was meant to do.

 

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.

 

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.

 

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 *Smile

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 *Smile

 

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.

 

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.

 

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.