Akarin

I finally got around to exploring this solution. I don't have Windows 10, I have 8.1, but I used Driver Easy to check if my Controller Driver was out of date. It turns out it was. I just updated to the newest version. I will monitor my log files and see if this was the issue. It is interesting to note some order of events here. Aside from the Disk Errors I listed above, there were two isolated cases of Disk Errors associated with the SSD in question in August and September of 2019. The first was 21 Event 51 Disk Errors in August and and 19 in September. In both cases, the errors had taken place during an ESET full system scan. They were isolated incidents and there were no more Event 51 Disk Errors until my recent issue back in May. The interesting part was that the newest Controller Driver was released in early August 2019, immediately preceding any disk errors associated with ESET.

OP here. I'm still having the issue, almost two months later. Nothings changed. I didn't replace my SSD and I'm glad I didn't. I have not experienced any other errors or performance issues with my SSD. And I have no reason to suspect my computer has been infected. However I would be happy to submit any logs if you want to investigate that angle. Unfortunately I no longer have the logs from when the issue first started happening, however the logs I submitted in my original ticket (#400433) may help. Please let me know what information may be needed.

I never claimed ESET destroyed my SSD and I already submitted a full set of logs using the ESET log collector program when I submitted my ticket.

I can't think of anything else it could be but either hardware or ESET and ESET already decided it isn't them.

Thanks for the tips. I looked through that folder and found no entries. I looked through the rest of the folders under Windows and found nothing relevant either. I tried looking into the corrupted Win page file angle, but couldn't find anything other than sfc /scannow which continues to find no errors. I had also run chkdsk and found no errors. Crucial's Storage Executive program is reporting the drive as healthy. Last night I uninstalled ESET again and ran CCleaner. I left the machine running all night without ESET. There were no disk warnings. I reinstalled ESET again this morning. The warnings returned again. This is not the first time AV software has been responsible for Event 51 diskwarnings (Win10 users of Bidefender reported such issues on startup that went away after Bitdefender pushed an update), but with no other option I guess I'll just plan on replacing my SSD.

Hello, I'm posting this here because tech support wasn't able to help me. Yesterday, I installed the Windows Security update KB4556846 for Windows 8.1. There was problem during installation that resulted in the update failing to install. During a second attempt, the update installed fine. Shortly after installing I noticed 27 warnings in Windows Event Viewer, marked as Event 51: An error was detected on device \Device\Harddisk0\DR0 during a paging operation. All 28 events were recorded over a range of two seconds. The device in question is my boot drive, a Crucial SSD. ESET is currently installed on that drive. These events are also reported as S.M.A.R.T. Reported UnCorrectable Errors, however multiple S.M.A.R.T. software suites continue to report the drive as healthy. The first thing I did was shut down the PC and made sure there was no issues with the cables. Later in the night, these series of warnings happened three more times in batches of 27, 27, and 12 events. At this point, I determined that every single event was proceeded several seconds by ESET installing a new version of the detection engine. I believe it started with detection engine 21316. It is written in my support ticket at least. I put in a support ticket #400433 - "Disk Errors during Detection Engine updates after Windows Update" While waiting, I performed some troubleshooting. I performed the following steps: 1. I uninstalled ESET Internet Security completely. Then I reinstalled it. Within a couple minutes of the installation coming to completion, including the installation of detection engine 21322, there was a new batch of Event 51 warnings. Since it had been a couple minutes this time between the warnings and the detection engine installation, I thought it might not be related to ESET after all so I moved on to Windows Update. 2. I uninstalled the update KB4556846 successfully and waited, however later on there was a new batch of Event 51 warnings. Once again, they were recorded within seconds of the installation of the ESET detection engine this time 21323. I briefly chatted with tech support regarding my ticket, however I was told the following: I know what Event 51 means, but I am at a loss over the specific cause and the only clue I have is the installation of ESET detection engines. Aside from one case after reinstalling ESET, every single series of warnings were reported within ten seconds of the ESET log Detection Engine was successfully updated to version 21322 (20200513). Unfortunately any current ESET logs will only go back to the reinstallation. I have my eis_logs.zip file made using the ESET log collector program (Default Collection profile, 5 day), but I'm not sure if I should be posting that in public.