Author Topic: CHKDSK occasionally runs on SSD at startup (Read 17627 times)

Still_Game · « **on:** July 15, 2019, 05:28:44 am »

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 · « **Reply #1 on:** July 15, 2019, 06:11:06 am »

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 · « **Reply #2 on:** July 15, 2019, 06:35:58 am »

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 · « **Reply #3 on:** July 15, 2019, 06:49:03 am »

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 · « **Reply #4 on:** July 15, 2019, 07:59:26 am »

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.

Boggin · « **Reply #5 on:** July 15, 2019, 08:24:49 am »

Yeah - that's the thing

Does Event Viewer have anything recorded for the days that chkdsk ran ?

Reliability history may also have something.

Still_Game · « **Reply #6 on:** July 15, 2019, 10:22:01 am »

I've done some forensics to see if there's any smoking gun, but nothing jumps out at me. I'm just running a backup now before I dabble further 😬

Still_Game · « **Reply #7 on:** July 15, 2019, 10:43:11 am »

Managed to stop hibernation after the backup, checked Dirty Bit (OK). rebooted (no auto CHKDSK occured (all OK)), re-started hibernation, checked Dirty Bit again (OK) - so, on the principle that it's not wise to make too many changes at once, I'll leave well alone for the moment and see if the problem returns..................

Boggin · « **Reply #8 on:** July 15, 2019, 02:18:15 pm »

Well with a clean Hiberfil file, perhaps chkdsk won't find anything that worries it.

The thing is though that if you've created a back up with a corrupt Hiberfil file then you could be storing a problem.

What do you use for backing up ?

I use Macrium Reflect Free for creating system images which has the advantage of creating separate images which I can go back through if needed.

Still_Game · « **Reply #9 on:** July 16, 2019, 12:42:05 am »

I've used Future Systems Solutions Casper for years, now on version 10,x, to create clones which are backed up incrementally. Currently, I do that to 3 HDDs in 2.5 inch USB enclosure on a rotating basis - roughly weekly. I occasionally make a system image as well, using the same software. I also make regular backups of my Outlook PST files to DVD - I've got stuff going back YEARS in the PST archive file. I know that Macrium Reflect free seems to be the software of choice for most people but I've used Casperso long, it's reasonably priced and it's been very reliable, aside from the occasional quirk - and their support is first class.

I take your point about a currupt hyberfil.sys file perpetuating, though. I guess I could use powercfg -h off and then reboot, then powercfg -h on and I should have a new file? I think!

Boggin · « **Reply #10 on:** July 16, 2019, 01:08:21 am »

I thought you had already turned Hibernation off/on ?

I have Hibernation turned off on all three of my laptops - two Win 10 and one Win 7.

I noticed on my Win 7 that turning off Hibernation freed up about 6GB on the HDD which is something to keep in mind if you are running short of space.

Still_Game · « **Reply #11 on:** July 16, 2019, 02:01:11 am »

No, got stacks of space on the drive - but will toggle hyberfil.sys anyway.

Still_Game · « **Reply #12 on:** July 16, 2019, 02:09:30 am »

I'm an idiot - I have toggled hyberfil! It's the heat............

Boggin · « **Reply #13 on:** July 16, 2019, 02:26:29 am »

powercfg -h off

Still_Game · « **Reply #14 on:** July 25, 2019, 11:45:46 pm »

Don't know whether it's coincidence or not but have not seen had any further incidences of CHKDSK running at boot since toggling hyperfil.sys.So thanks for the suggestion, Tom. Have a good day.

Boggin · « **Reply #15 on:** July 26, 2019, 12:15:44 am »

That's good news and thanks for the update.

Boggin · « **Reply #16 on:** July 26, 2019, 03:13:11 am »

I forgot to ask - did you turn Hibernate back on ?

Still_Game · « **Reply #17 on:** July 26, 2019, 03:36:18 am »

Oh yes, I'm only using about 25% of my 1TB SSD so not short of space! I also forgot to say that no further anomalies have shown up in SMART - although the temperature did creep up to a max of 61 C - not surprising with the temperatures we've been getting here in France.

Boggin · « **Reply #18 on:** July 26, 2019, 03:40:12 am »

This one has been running up to 63ºC this morning in the UK but it seems to be a bit cooler today.

EDIT - I've just checked it again and it's currently running at 68 and has been up to 70 although the fan doesn't seem to be working overtime.

Still_Game · « **Reply #19 on:** July 26, 2019, 02:03:56 pm »

I think 70 C is suggested max operating temperature for this Crucial MX500 SSD.

Boggin · « **Reply #20 on:** July 26, 2019, 02:42:00 pm »

I was talking about the CPU which has a max temp of 100ºC which has integral graphics.

The HDD seems to run between 30 and 40ºC.

Still_Game · « **Reply #21 on:** July 26, 2019, 09:41:57 pm »

Ah, thought that was a little warm for an SSD!

Still_Game · « **Reply #22 on:** August 24, 2019, 09:05:22 am »

Just an update:- I've had no further incidents of Windows needing to run CHKDSK since toggling hyperfil.sys a few weeks ago, so looks as if a a corrupt file WAS at the root of the problem. Thanks once again for your help.

Boggin · « **Reply #23 on:** August 24, 2019, 09:07:16 am »

Your welcome and thanks for the update.