repeated event ID 52

Question

for the last two or three months i have been seeing multiple Event ID 52 (source: Disk) events in the windows event logs (System). the nature of the event is very concerning. the details are as follows: The driver has detected that device \Device\Harddisk0\DR0 has predicted that it will fail. Immediately back up your data and replace your hard disk drive. A failure may be imminent.

the drive in question is a WD_Back SN850X

naturally i was alarmed to see such a message, however..... the drive in question is less than two years old, and all diagnostic data i can get from the drive from WD (WD Dashboard) and from CrystalDiskInfo app all seem to say that there is nothing wrong with the drive. All indications are the that drives health still very good, with the drive condition at 99%. there are no reassigned sectors or bad blocks. the spare blocks reserved for when sectors do go bad is still at 0 used. I even ran 'Chkdsk /v/ /x /f /r /b' which took forever, but found no errors (when i looked at the results in the event log)

am i seeing erroneous errors? do i need to be concerned?

from the checkdsk i ran:

Checking file system on C:

The type of the file system is NTFS.

Volume label is Windows.

A disk check has been scheduled.

Windows will now check the disk.

Stage 1: Examining basic file system structure ...

4381184 file records processed.

File verification completed.

Phase duration (File record verification): 40.13 seconds.

175645 large file records processed.

Phase duration (Orphan file record recovery): 56.92 milliseconds.

0 bad file records processed.

Phase duration (Bad file record checking): 1.84 milliseconds.

Stage 2: Examining file name linkage ...

353433 reparse records processed.

4906868 index entries processed.

Index verification completed.

Phase duration (Index verification): 1.02 minutes.

0 unindexed files scanned.

Phase duration (Orphan reconnection): 30.17 seconds.

0 unindexed files recovered to lost and found.

Phase duration (Orphan recovery to lost and found): 2.35 seconds.

353433 reparse records processed.

Phase duration (Reparse point and Object ID verification): 752.28 milliseconds.

Stage 3: Examining security descriptors ...

Cleaning up 111 unused index entries from index $SII of file 0x9.

Cleaning up 111 unused index entries from index $SDH of file 0x9.

Cleaning up 111 unused security descriptors.

Security descriptor verification completed.

Phase duration (Security descriptor verification): 60.56 milliseconds.

262843 data files processed.

Phase duration (Data attribute verification): 1.76 milliseconds.

CHKDSK is verifying Usn Journal...

39199344 USN bytes processed.

Usn Journal verification completed.

Phase duration (USN journal verification): 155.65 milliseconds.

Stage 4: Looking for bad clusters in user file data ...

4381168 files processed.

File data verification completed.

Phase duration (User file recovery): 1.90 hours.

Stage 5: Looking for bad, free clusters ...

49627654 free clusters processed.

Free space verification is complete.

Phase duration (Free space recovery): 35.32 seconds.

Windows has scanned the file system and found no problems.

No further action is required.

3814035 MB total disk space.

3614494 MB in 1496538 files.

1028584 KB in 262844 indexes.

     0 KB in bad sectors.

4791315 KB in use by the system.

 65536 KB occupied by the log file.

198510616 KB available on disk.

  4096 bytes in each allocation unit.

976393215 total allocation units on disk.

49627654 allocation units available on disk.

Total duration: 1.95 hours (7030870 ms).

Internal Info:

00 da 42 00 9b d8 1a 00 72 9f 31 00 00 00 00 00 ..B.....r.1.....

35 24 00 00 64 40 05 00 00 00 00 00 00 00 00 00 5$..d@..........

From Crystaldiskinfo:

Answer 1

Hello,

I checked the image you provided, and the SSD temperature is extremely high. This high temperature is likely the reason why Event ID 52 is being triggered.

The operating temperature range of the SN850X is 0°C to 85°C. However, in practice, thermal throttling can occur once the drive exceeds around 70°C, and this may cause Windows to mistakenly report a “predicted failure.”

Do you have a heatsink installed on the SSD? If you do, please review the airflow inside your PC, as insufficient airflow can prevent the SSD from cooling properly.

In addition, if the SSD is reaching temperatures near 80°C, your CPU or GPU may also be running hotter than expected. I recommend checking the overall cooling performance of your system.

Once you improve the cooling and the SSD temperature stabilizes around 50°C, please check again to see whether Event ID 52 continues to appear.