Main Forum > General Computer Support

CHKDSK occasionally runs on SSD at startup

(1/5) > >>

Still_Game:
I recently replaced my 1 TB HDD on my Lenovo G560 laptop with a Crucial MX500 SSD of the same size. I cloned the old drive with Casper 10, which is my backup software of choice. All went swimmingly with the installation and the computer is transformed in terms of speed and usability. I have, however, had an ongoing quirk in that Windows sometimes decides there's a need to run CHKDSK on boot, although the results don't seem to show any errors found (see below). Crucial Storage Executive reports no errors.
S.M.A.R.T. all looks fine. See attached PDF.

I did raise a support request with Crucial but their advice was to return the drive for exchange - something I'm reluctant to do as I can't see any problems with the drive and I don't want to exchange it if it's performing correctly, never mind the hassle. Is there anything I've missed in the reports or can anybody shed any light on why SHKDSK is running? Windows shut down correctly yesterday (I have the VERBOSE option active as it helps me spot any problems on shutdown) and this morning CHKDSK ran at boot - but that's an infrequent occurrence, and I can't link it to any other activity. Reliability Monitor shows all has been fine for weeks...................


*******************************************************

Checking file system on C:
The type of the file system is NTFS.
Volume label is SYSTEM.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 3)...
  405504 file records processed.                                          File verification completed.
  2427 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              60 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 3)...
  507358 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 3)...
  405504 file SDs/SIDs processed.                                         Cleaning up 39 unused index entries from index $SII of file 0x9.
Cleaning up 39 unused index entries from index $SDH of file 0x9.
Cleaning up 39 unused security descriptors.
Security descriptor verification completed.
  50928 data files processed.                                            CHKDSK is verifying Usn Journal...
  208571360 USN bytes processed.                                             Usn Journal verification completed.
Windows has checked the file system and found no problems.

 930661375 KB total disk space.
 253872744 KB in 244267 files.
    155860 KB in 50929 indexes.
         0 KB in bad sectors.
    708447 KB in use by the system.
     65536 KB occupied by the log file.
 675924324 KB available on disk.

      4096 bytes in each allocation unit.
 232665343 total allocation units on disk.
 168981081 allocation units available on disk.

Internal Info:
00 30 06 00 a8 80 04 00 f0 ab 07 00 00 00 00 00  .0..............
b2 21 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  .!..<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

*******************************************************

Iain

Windows 7 Home Premium x64 SP1 - Microsoft Security Essentials - Malwarebytes Premium - CryptoPrevent Premium

Boggin:
See if this article helps - https://www.thewindowsclub.com/check-disk-runs-at-every-startup-windows but I noticed in the SMART log there had been an unexpected power loss.

I've seen the chkdsk running on boot caused by a corrupt Hibernation file which Windows blames for the corruption and runs the chkdsk on boot to correct the corruption as it sees it.

If the power loss occurred while it was writing to the Hibernation file, then that may have caused the corruption.

See if turning off Hibernation and then rebooting to see if that resolves chkdsk running on boot.

Run a cmd prompt as an admin and enter -

powercfg -h off

To turn Hibernation back on, repeat the cmd changing off to on

Still_Game:
Thanks, Tom, I'll give that a try when I'm back on the laptop. That unexpected shutdown in the Smart log showed up fairly early on and I'm not sure why - but most boots have been fine. Whenever I've done a random check to see if the DIRTY bit is set, it's not.

Boggin:
Intermittent problems may be more difficult to nail down, so not sure if changing the autochk bit in the registry would do it.

When you turn off Hibernation and then back on, it creates a new Hiberfil file which should resolve any corruption in there.

Anyway, see how it goes.

Still_Game:
It may be Wednesday before I get the chance to look at the laptop but I'll try the Hibernation thing - but, because it's intermittent, I may not know if it fixes it for a bit.

Navigation

[0] Message Index

[#] Next page

Go to full version