G
Guest
Hi!
I have been describing this problem already on another thread on a more wide
context, but now got it maybe somehow more focused.
The problem is, that a manually requested, and probably also by system
requested, Disk Check is not got performed but just passed with some text
rows at the next and also all the sub-sequent coming start-ups.
The behaviour is as follows:
1. Regular start-up behaviour until the light blue screen for Disk Check
2. On the screen appearing in some two-three-four seconds the following
text rows
The file system of the drive C: will be checked
File system type NTFS
The drive cannot be opened into use directly
Windows has checked the hard drive
....... (yes, some dots appearing one by one)
3. When system is got on upon checking the statuses
- the DirtyBit is seen still on
- BootExecute key is seen still remaining "ready" for chkdsk /r for
the drive C:
So, this "no Disk Check for C:" symptom may have been caused somehow like this
a) a Disk Check incl. the phases 4 and 5 is requested for the disk C: and
due to this the DirtyBit of that disk is set on and the BootExecute key set
for chkdsk /r
b) due to the DirtyBit is set on, on the next start-up the Disk Check
chkdsk.exe /r is started automatically for the disk C: by the autochk.exe
c) now, a good guess for the reason is -> due to a fact that the disk C:
has during the start-up just for a few seconds before already been taken in
use i.e. locked by some unknown program the chkdsk.exe is failing to begin
it's process and thus the Disk Check for the disk C: is not done even
requested to be done
d) and, all this will be valid and repeated constantly on all subsequent
start-up's due to the DirtyBit remaining on all the time until set off by the
fulfillment of the chkdsk.exe ...
So, the solution for this could be to locate which program is the mysterious
unknown one locking the disk just before the chkdsk.exe ... please, is there
any good guesses for the mysterious program, or hints how to trace/debug it
up?
Best regards,
Pete V.
I have been describing this problem already on another thread on a more wide
context, but now got it maybe somehow more focused.
The problem is, that a manually requested, and probably also by system
requested, Disk Check is not got performed but just passed with some text
rows at the next and also all the sub-sequent coming start-ups.
The behaviour is as follows:
1. Regular start-up behaviour until the light blue screen for Disk Check
2. On the screen appearing in some two-three-four seconds the following
text rows
The file system of the drive C: will be checked
File system type NTFS
The drive cannot be opened into use directly
Windows has checked the hard drive
....... (yes, some dots appearing one by one)
3. When system is got on upon checking the statuses
- the DirtyBit is seen still on
- BootExecute key is seen still remaining "ready" for chkdsk /r for
the drive C:
So, this "no Disk Check for C:" symptom may have been caused somehow like this
a) a Disk Check incl. the phases 4 and 5 is requested for the disk C: and
due to this the DirtyBit of that disk is set on and the BootExecute key set
for chkdsk /r
b) due to the DirtyBit is set on, on the next start-up the Disk Check
chkdsk.exe /r is started automatically for the disk C: by the autochk.exe
c) now, a good guess for the reason is -> due to a fact that the disk C:
has during the start-up just for a few seconds before already been taken in
use i.e. locked by some unknown program the chkdsk.exe is failing to begin
it's process and thus the Disk Check for the disk C: is not done even
requested to be done
d) and, all this will be valid and repeated constantly on all subsequent
start-up's due to the DirtyBit remaining on all the time until set off by the
fulfillment of the chkdsk.exe ...
So, the solution for this could be to locate which program is the mysterious
unknown one locking the disk just before the chkdsk.exe ... please, is there
any good guesses for the mysterious program, or hints how to trace/debug it
up?
Best regards,
Pete V.