New
#41
In the logs were file drive problems.
There were also hibernation failures.
Open administrative command prompt and type or copy and paste:
1) powercfg.exe /hibernate off
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
5) In the left lower corner search type reliability and post an image into the thread.
6) Download and install Whocrashed:
http://www.resplendence.com/whocrashed
7) Above analyze click on tools > crash dump test > type: ACCEPT
8) After the dump click analyze > post a report into the thread.
Code:Event[2081]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-06-30T11:07:49.968 Event ID: 16 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-MBCUAVH Description: Windows failed to resume from hibernate with error status 0xC000009A.Code:Event[1124]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-06-29T13:38:56.956 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-MBCUAVH Description: Windows failed fast startup with error status 0xC00000D4.Code:Event[1589]: Log Name: System Source: volmgr Date: 2017-06-29T14:19:27.985 Event ID: 49 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-MBCUAVH Description: Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.Code:Event[9221]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-07-31T21:11:13.589 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-MBCUAVH Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume9.(The I/O device reported an I/O error.)Code:Event[16372]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-09-04T21:58:26.923 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-MBCUAVH Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\karl\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost.Code:Event[16261]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-09-04T16:12:49.829 Event ID: 98 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-MBCUAVH Description: Volume F: (\Device\HarddiskVolume9) requires an Online Scan. An Online Scan will automatically run as part of the next scheduled maintenance task. Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.