System is reporting drive errors

[KeyboardDemon]

I have twice seen an error come up for my main system drive, a 250Gb Samsung 840 Series SSD. I can't remember the exact error but it said it needed the system to be restarted so the drive could be repaired. The second time I got this error I ran AdvancedSystemCare 7 DiskDoctor and in the report on the drive it said:

Windows 8
English (United Kingdom)

C:\ Volume Label: Local Disk, File System: NTFS

Stage 1: Examining basic file system structure ...
418048 file records processed.
File verification completed.
2610 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
519130 index entries processed.
Index verification completed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
50542 data files processed.
Advanced SystemCare Ultimate is verifying Usn Journal...
37545232 USN bytes processed.
Usn Journal verification completed.
The master file table's (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect.
Advanced SystemCare Ultimate has checked the file system and found problems.
Please run chkdsk /scan to find the problems and queue them for repair.
243837951 KB total disk space.
140488424 KB in 269239 files.
144820 KB in 50543 indexes.
531351 KB in use by the system.
65536 KB occupied by the log file.
102673356 KB available on disk.
4096 bytes in each allocation unit.
60959487 total allocation units on disk.
25668339 allocation units available on disk.

I have highlighted the error. What's the normal course of action with this?

[herulach]

have you run chkdsk /scan?

Have you checked the status using samsungs utilities? Magician should show you the health status and is on the disk it came with or can be downloaded from the samsung ste.

Either way back anything up now.

[peterb]

The volume bitmap is (in simple terms) a record of free/unused clusters on the volume (or in the case of a single partition/drive, the drive)

Googling shows this is not an uncommon event.

Have you looked at the SMART data for the drive to check that the drive itself is OK?

Provided it is, then run chkdsk. Some reports say that there is a bug in chkdsk that will not correct this.

As always, it is advisable to backup any critical data before running any potentially destructive operations on a file system.

[KeyboardDemon]

Thanks, I'll give the utilities a go first then take it from there, though if this is something that is quite common then maybe I just need to check the basics for now.