Windows 10: Event 55, 137, 98 NTFS errors on SSD

Windows 10, 1803. Today I got a message I needed to restart to repair corruption. After the reboot and repair I found those three events (actually 98 was twice). The corruption occurred on my 3 month old Intel SSD and on the F: drive, which is the reserved drive. I have the latest firmware of this drive and did a quickscan from Intels toolbox which does not find any problems. I also looked at the SMART records and everything looks good.

Is this something I need to be concerned about?

Thank!

:)

 

computer failed to boot - disk error event id 153 + 98


Hi, suggest you try Hard Disk Sentinel (trial) - gives a great quick analysis (SSDs too).

Please post the results.

Event ID 153:
This event may be an indication that the specified drive may be failing soon. This is especially true if the event is recorded regularly. The first step is to run the maintenance utilities related to hard drives, starting with CHKDSK and the utilities available from the manufacturer for that specific brand.

Event ID 98:
Event ID: 98

 

Event ID 98, Ntfs (Microsoft-Windows-Ntfs)

Hi All,

One of my server keeps getting this error message and I believe the reason why my Altaro VM Backup are giving me a warning message everyday. Below are the event ID which I think is causing this warning message:

Event ID 98, Ntfs (Microsoft-Windows-Ntfs)

Volume ?? (\Device\HarddiskVolume19) 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.

Below is the warning message I got everyday from our backup software. I have already raised this issue to our vendor but they told me that this is basically a warning from the OS and I need to fix this on OS level.





Does anyone encounter this issue or any knows how I can remove this warning message? I am running on Windows Server 2012 R2.

 

Event IDs 55 and 98 request chkdsk /F but \Device\HarddiskVolume# does not exist when doing diskpart => list volume

Very recently (November 7, 2017 and November 13) has issued a notification and event logs that *SEEM* to indicate a problem.

The sequence is:

(Event ID 98): Volume D: (\Device\HarddiskVolume6) 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.

(Event ID 55)

A corruption was discovered in the file system structure on volume D:.

The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.

(Repeat of Event ID 98 ).

In the first of the two cases, I also immediately (2 seconds later) got Event ID 130, which indicated it has been repaired, even though I had NOT run CHKDSK at that point.

The thing is, the Volume it identifies as being associated with drive D: DOES NOT EXIST:

------------------------------------------------------

C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.15063.0

Copyright (C) Microsoft Corporation.

On computer: JAYW7

DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info

---------- --- ----------- ----- ---------- ------- --------- --------

Volume 0 I DVD-ROM 0 B No Media

Volume 1 Z STORAGE NTFS Partition 3725 GB Healthy

Volume 2 System Rese NTFS Partition 100 MB Healthy System

Volume 3 C NTFS Partition 222 GB Healthy Boot

Volume 4 NTFS Partition 858 MB Healthy Hidden

Volume 5 D RAID-D NTFS Partition 924 GB Healthy

DISKPART>

-------------------------------------------------------------

The only thing I can think of is that "D:" is mapped to a Intel ICH10R RAID array, and that somehow it is getting confused at times, and trying to access a physical drive directly for some reason.

(Volume 1 , Z: is one physical drive. Volumes 2, 3 and 4 are a second physical drive, and Volume 5 is the RAID array)

After the first one, I did run a CHKDSK /F, and it ran the check and there did not seem to be any errors.