If you've made backed up images or backed up files then you can use the drive until the terminal event.
Many OP will replace a Windows drive displaying any significant problems (for example recurrent logical errors or chkdsk problems).
The time cost for troubleshooting can be compared to a working drive.
Also before drive failure there can be performance problems such as slow read, slow write, hangs, freezes, BSOD, etc.
Once a drive has had bad blocks you can follow the event viewer to view the frequency of new reports:
Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using (howtogeek.com)
For chkdsk consider using these switches: chkdsk /b /v C:
This is the deepest switch, can take a long time, and makes sure if completed that bad blocks are no longer used.
Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10
The C: displayed; 4 KB in bad sectors
The D: displayed: 20 KB in bad sectors
S.M.A.R.T. Attribute: Current Pending Sector Count | Knowledge Base (acronis.com)
Current Pending Sector Count Warning: What You Need To Know (harddrivegeek.com)
What to Do When Encountering Current Pending Sector Count? (minitool.com)
How to Fix Current Pending Sector Count Warning | by Satyeshu Kumar | Medium
Run the crucial scanner to view replacement options:
Crucial System Scanner