Last One To Post Wins [90]

Morning Keith, Paul, Mike.

Go ahead while I get more Wakeup Juice.........

f14tomcat said:

Morning Keith, Paul, Mike.

Go ahead while I get more Wakeup Juice.........

LoL ....ok since our last update, if I click on C-Drive properties menu, then tools, then error checking the drive, then SCAN THIS Drive. I get this new msg,
Attachment 144776

Ran chkdsk, Also used minitool to check for bad sectors .....they all report no errors found, This shows up on ALL 3 of my drives too. This has to be a bug, I'm thinking....

COMPUTIAC said:

Mornin' Gents, 68 'n sunny.

Good Morning Bob, your up early this morning. :)

f14tomcat said:

Morning Keith, Paul, Mike.

Go ahead while I get more Wakeup Juice.........

Morning TC.

COMPUTIAC said:

Mornin' Gents, 68 'n sunny.

Morning Bob.

2nd coffee always tastes better than my 1st ...Attachment 144777

OldMike65 said:

LoL ....ok since our last update, if I click on C-Drive properties menu, then tools, then error checking the drive, then SCAN THIS Drive. I get this new msg,
Attachment 144776

Ran chkdsk, Also used minitool to check for bad sectors .....they all report no errors found, This shows up on ALL 3 of my drives too. This has to be a bug, I'm thinking....

No nausea here:

Attachment 144778

At command, check the "dirty" bit. See if it's lying to ya.

Code:

C:\Users\dhubb\Desktop> fsutil dirty query C:
Volume - C: is NOT Dirty

C:\Users\dhubb\Desktop>

Chkdsk

ok TC
fsutil dirty query C:
reports its not dirty ....nothing I've tried reports or finds any errors

OldMike65 said:

ok TC
fsutil dirty query C:
reports its not dirty ....nothing I've tried reports or finds any errors

This is all clear as mud, but may help.....dunno:

---

https://answers.microsoft.com/en-us/windows/forum/all/chkdsk-false-positive-file-errors-sanity-check/cf1e3121-bcf2-42f5-821c-7e6d0086a080

Here is how Microsoft explains this observation:

"...CHKDSK may report that a disk is corrupted even when there is no
real corruption present. This can happen if NTFS happens to modify
areas of the disk on behalf of some program activity that CHKDSK is
examining at the same time. To verify a volume correctly, the volume
must be in a static state, and the only way to guarantee that state is
to lock the volume. CHKDSK only locks the volume when /F or /R (which
implies "F") is specified. Thus, you may need to run CHKDSK more than
once to get it to complete all stages in read-only mode."

Read the entire article here:

http://support.microsoft.com/kb/187941

f14tomcat said:

This is all clear as mud, but may help.....dunno:

---

https://answers.microsoft.com/en-us/windows/forum/all/chkdsk-false-positive-file-errors-sanity-check/cf1e3121-bcf2-42f5-821c-7e6d0086a080

Here is how Microsoft explains this observation:

"...CHKDSK may report that a disk is corrupted even when there is no
real corruption present. This can happen if NTFS happens to modify
areas of the disk on behalf of some program activity that CHKDSK is
examining at the same time. To verify a volume correctly, the volume
must be in a static state, and the only way to guarantee that state is
to lock the volume. CHKDSK only locks the volume when /F or /R (which
implies "F") is specified. Thus, you may need to run CHKDSK more than
once to get it to complete all stages in read-only mode."

Read the entire article here:

http://support.microsoft.com/kb/187941

Yeah I've run "chkdsk C: /f /r /x" 3 times yesterday, during bootup, nothing found. Only thing I have not done is run it from a USB drive .....also this error is reported on ALL My drives, not just C: drive.