Login

**WinXPto10** · 06-19-2015, 06:24 AM

(06-18-2015, 11:22 AM)Britec Wrote: 0 KB in bad sectors.
0 bad file records processed.

The drive is healthy according to them logs. But I would check Event Viewer Log for Errors in System Events.

where i can find it in system events?

***Britec*** · (This post was last modified: 06-19-2015, 11:05 AM by Britec.)

Click Start button, in search box type Event Viewer, then click Windows Logs > System
Once there, look for any errors showing in red (example)

**WinXPto10** · 06-19-2015, 10:22 PM

(06-19-2015, 11:05 AM)Britec Wrote: Click Start button, in search box type Event Viewer, then click Windows Logs > System
Once there, look for any errors showing in red (example)

ok cool! i tried to find it but there's no error about disk

***Britec*** · 06-20-2015, 07:56 PM

Please make sure you have this installed
The Volume Bitmap is incorrect

**WinXPto10** · 06-21-2015, 04:33 AM

(06-20-2015, 07:56 PM)Britec Wrote: Please make sure you have this installed
The Volume Bitmap is incorrect

hi, i can't find the windows 8.1 download, i am using windows 8.1 with update 1 x64

**jmitservices** · 06-21-2015, 12:42 PM

You should already have it in Windows 8/8.1.

**WinXPto10** · 06-21-2015, 12:51 PM

(06-21-2015, 12:42 PM)jmitservices Wrote: You should already have it in Windows 8/8.1.

i did check in windows update history, it's not there

**jmitservices** · 06-21-2015, 12:56 PM

What Britec had linked you to was a hotfix.

It will be integrated into the operating system.

***Britec*** · 06-21-2015, 02:40 PM

Yeah forgot it was Windows 8. My bad.

Found this information

The volume bitmap is a metafile called $BITMAP. Its function is to keep track of ALL the clusters on your volume and if they are in use or not. So when a file needs more space, we query $BITMAP to see what's free. It is updated when clusters are brought into use and when they are 'freed'.

When CHKDSK runs, if it makes any changes to the volume such as correcting a problem or just consolidating security descriptors, a change has to be made to $BITMAP to reflect the newly in use clusters or freed clusters, thus the message.
The downside to this is that if you have anything changed by CHKDSK, you will also see a message about the volume bitmap. So it can mislead you to think there is an actual problem with it.

Source

**WinXPto10** · 06-21-2015, 06:47 PM

(06-21-2015, 02:40 PM)Britec Wrote: Yeah forgot it was Windows 8. My bad.

Found this information

The volume bitmap is a metafile called $BITMAP. Its function is to keep track of ALL the clusters on your volume and if they are in use or not. So when a file needs more space, we query $BITMAP to see what's free. It is updated when clusters are brought into use and when they are 'freed'.

When CHKDSK runs, if it makes any changes to the volume such as correcting a problem or just consolidating security descriptors, a change has to be made to $BITMAP to reflect the newly in use clusters or freed clusters, thus the message.
The downside to this is that if you have anything changed by CHKDSK, you will also see a message about the volume bitmap. So it can mislead you to think there is an actual problem with it.

Source

so, my hard disk is good?