1) Open dxdiag > allow each page to load > post a share link into the thread
.
2) Increase the free space on the Windows drive to > 30 GB
.
3) For any BSOD
a) run the administrative command prompt command > post a share link into the newest post
b) post a separate share link for C:\windows\memory.dmp
.
4) Post images or share links for:
a) startup and recovery system failure settings
b) virtual memory / page file settings
c) disk management (widen these columns: status and disk 0) (make sure that all characters within the parenthesis are visible)
.
4) Open administrative command prompt and type or copy and paste: (post an image of the results into the thread)
sfc /scannow
.
5) Run HD Tune (free version) (all drives)
https://www.hdtune.com/
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan
.
6) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
http://www.seagate.com/support/downloads/seatools/seatools-win-master/
http://knowledge.seagate.com/articles/en_US/FAQ/202435en
.
7) Open the website for the computer or motherboard manucturer > support > enter the product or serial number or model > select the operating system >display drivers and BIOD > post a URL or link into the thread
.
8) Update:
WDC_SAM WD SCSI Pass Thru driv WD SCSI Pass Thru driv 4/16/2008 1:39:08 AM C:\Windows\system32\DRIVERS\wdcsam64_prewin8.sys
nvstor 3/19/2010 1:45:11 PM C:\Windows\system32\drivers\nvstor.sys
https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1
.
9) Open device manager > click view > click show hidden devices > manually expand all rows > look for any row displaying a yellow triangle with black exclamation mark or unknown device > post images into the thread
.
.
------------------
System Information
------------------
DxDiag Previously: Crashed in system information (stage 1). Re-running DxDiag with "dontskip" command line parameter or choosing not to bypass information gathering when prompted might result in DxDiag successfully obtaining this information
.
.
There were multiple log entries displaying possible drive problems.
.
.
The memory dump was partially corrupt:
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
.
.
Event[54215]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2020-06-19T12:57:06.000
Event ID: 1018
Task: N/A
Level: Information
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Matthew-PC
Description:
The dump file at location: C:\Windows\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.
.
.
Event[53944]:
Log Name: System
Source: Microsoft-Windows-StartupRepair
Date: 2020-06-19T02:54:51.486
Event ID: 1121
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Matthew-PC
Description:
The following file necessary for Windows startup was corrupt: e:\windows\system32\kdcom.dll
.
.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.
On the bottom of each post there is:
Propose as answer = answered the question
On the left side of each post: Vote = a helpful post
.
.
.
.
.
