Between 11/16/2017 and 12/14/2017 there were 14 crashes.
One of the crashes had a problem creating a BSOD dump.
There were many problems with the drive reported in the files.
For all tests please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.
1) open administrative command prompt and type or copy and paste:
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) chkdsk /x /f /r
This may take many hours so plan to run overnight
6) Find the chkdsk report in the event viewer using the information in this link:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials
7) Run HDTune: http://www.hdtune.com/
to check the health,
scan for errors, no quick scan but full scan
run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 General Tips Tutorials
8) Run Sea tools for windows on your drive using SMART, short and long generic tests:
How to use SeaTools for Windows
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows
http://www.seagate.com/support/downloads/seatools/
9) If you use Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread10) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread
11) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
> on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
> on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread
12) In the left lower corner search type services > open windows error reporting service > scroll to the startup type column > right click > left click on properties > post an image into the thread
13) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
http://www.resplendence.com/whocrashed
14) Click analyze > look for dead or deaddead in the results > post the results into the thread
15) Run the DM log collector after all of the above steps and post a zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums
BSOD - Posting Instructions - Windows 10 Forums
16) Open device manager > click view > show hidden devices > expand all rows > look for any rows that have an icon with a yellow triangle and black exclamation mark > post images into the thread
17) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials
Code:
Event[1057]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-11-16T13:15:16.963 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: N/A User Name: N/A Computer: DESKTOP-R84D7AI Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume13.({Device Timeout}The specified I/O operation on %hs was not completed before the time-out period expired.)
Code:
Event[11864]: Log Name: System Source: Ntfs Date: 2017-12-15T13:06:54.631 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: LukeLaptop Description: A corruption was discovered in the file system structure on volume E:.The exact nature of the corruption is unknown. The file system structures need to be scanned online.
Code:
Event[12209]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-12-15T13:19:58.216 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: LukeLaptop Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume2.
Code:
Event[16391]: Log Name: System Source: Ntfs Date: 2017-12-16T00:17:31.997 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: LukeLaptop Description: A corruption was discovered in the file system structure on volume F:.A corruption was found in a file system index structure. The file reference number is 0x9000000000009. The name of the file is "<unable to determine file name>". The corrupted index attribute is ":$SII:$INDEX_ROOT". The corrupted index block is located at Vcn 0xffffffffffffffff, Lcn 0xffffffffffffffff. The corruption begins at offset 112 within the index block.
Code:
Event[341]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-11-14T15:18:05.815 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-R84D7AI Description: Windows failed fast startup with error status 0xC00000D4.
Code:
Event[1050]: Log Name: System Source: Disk Date: 2017-11-16T13:14:50.911 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-R84D7AI Description: The IO operation at logical block address 0xbc158c8 for Disk 2 (PDO name: \Device\00000085) was retried.Event[1051]: Log Name: System Source: Disk Date: 2017-11-16T13:14:50.911 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-R84D7AI Description: The IO operation at logical block address 0x83f3c8 for Disk 2 (PDO name: \Device\00000085) was retried.Event[1052]: Log Name: System Source: Disk Date: 2017-11-16T13:15:00.923 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-R84D7AI Description: The IO operation at logical block address 0x80e9e0 for Disk 2 (PDO name: \Device\00000085) was retried.Event[1053]: Log Name: System Source: Disk Date: 2017-11-16T13:15:00.923 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-R84D7AI Description: The IO operation at logical block address 0x80e5e0 for Disk 2 (PDO name: \Device\00000085) was retried.Event[1054]: Log Name: System Source: Disk Date: 2017-11-16T13:15:00.923 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-R84D7AI Description: The IO operation at logical block address 0x83f408 for Disk 2 (PDO name: \Device\00000085) was retried.Event[1055]: Log Name: System Source: Disk Date: 2017-11-16T13:15:04.931 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-R84D7AI Description: The IO operation at logical block address 0x80e5e0 for Disk 2 (PDO name: \Device\00000085) was retried.Event[1056]: Log Name: System Source: Disk Date: 2017-11-16T13:15:12.937 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-R84D7AI Description: The IO operation at logical block address 0x80e5e8 for Disk 2 (PDO name: \Device\00000085) was retried.
Code:
Event[2287]: Log Name: System Source: Disk Date: 2017-11-21T22:55:24.822 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: LukeLaptop Description: The driver detected a controller error on \Device\Harddisk2\DR2.
Code:
Event[2391]: Log Name: System Source: Disk Date: 2017-11-22T03:44:04.764 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: LukeLaptop Description: The driver detected a controller error on \Device\Harddisk2\DR6.
Code:
Event[8993]: Log Name: System Source: Disk Date: 2017-12-06T19:11:44.691 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: LukeLaptop Description: The driver detected a controller error on \Device\Harddisk2\DR3.
Code:
Event[1630]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-11-18T19:59:45.094 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-R84D7AI Description: Volume G: (\Device\HarddiskVolume83) 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.
Code:
Event[16890]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-12-16T00:27:18.129 Event ID: 98 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: LukeLaptop Description: Volume E: (\Device\HarddiskVolume1) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
Code:
Event[8084]: Log Name: System Source: volmgr Date: 2017-11-29T14:16:36.764 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: LukeLaptop Description: Dump file creation failed due to error during dump creation.
Code:
Event[2751]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-11-23T19:24:38.905 Event ID: 6 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: LukeLaptop Description: An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '
Code:
Event[785]: Log Name: System Source: BTHUSB Date: 2017-11-14T22:04:37.937 Event ID: 14 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-R84D7AI Description: A device with Bluetooth adapter address (b8:69:c2:4c:03:4c) has a bad service record (attribute identifier 13). The service will not be visible.
Code:
Event[9555]: Log Name: System Source: Disk Date: 2017-12-11T15:41:29.608 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: LukeLaptop Description: The device, \Device\Harddisk0\DR0, has a bad block.Event[9556]: Log Name: System Source: Disk Date: 2017-12-11T15:41:29.671 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: LukeLaptop Description: The device, \Device\Harddisk0\DR0, has a bad block.
Code:
Event[17284]: Log Name: System Source: storahci Date: 2017-12-16T00:44:10.091 Event ID: 129 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: LukeLaptop Description: Reset to device, \Device\RaidPort0, was issued.