Intermitent Boot Up Failure

Run Crystal Disk standard edition after completing the earlier steps:
CrystalDiskInfo – Crystal Dew World

kwgagel said:

Here's the chkdsk results:
Checking file system on C:
The type of the file system is NTFS.
Volume label is Drive.


A disk check has been scheduled.
Windows will now check the disk.


Stage 1: Examining basic file system structure ...
The attribute of type 0x80 and instance tag 0x0 should be after
attribute of type 0x80 and instance tag 0x1 in file 0x267.
Cleaning up instance tags for file 0x1aed7.
The attribute of type 0x80 and instance tag 0x0 should be after
attribute of type 0x80 and instance tag 0x1 in file 0x1162.
1275936 file records processed.
File verification completed.
14336 large file records processed.
0 bad file records processed.


Stage 2: Examining file name linkage ...
124354 reparse records processed.
1566242 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
124354 reparse records processed.


Stage 3: Examining security descriptors ...
Cleaning up 7688 unused index entries from index $SII of file 0x9.
Cleaning up 7688 unused index entries from index $SDH of file 0x9.
Cleaning up 7688 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
145154 data files processed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.


Stage 4: Looking for bad clusters in user file data ...
1275920 files processed.
File data verification completed.


Stage 5: Looking for bad, free clusters ...
252064211 free clusters processed.
Free space verification is complete.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.


Windows has made corrections to the file system.
No further action is required.


1950906364 KB total disk space.
940758752 KB in 764669 files.
459980 KB in 145157 indexes.
0 KB in bad sectors.
1430788 KB in use by the system.
65536 KB occupied by the log file.
1008256844 KB available on disk.


4096 bytes in each allocation unit.
487726591 total allocation units on disk.
252064211 allocation units available on disk.


Internal Info:
20 78 13 00 25 e1 0d 00 53 4b 18 00 00 00 00 00 x..%...SK......
2b a8 00 00 97 3d 01 00 00 00 00 00 00 00 00 00 +....=..........


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

- - - Updated - - -



And finally:


Now I'll do a complete back up and see how the next week goes. If this last week was any indication it'll fail to boot by the weeks end. If it's fixed it should startup reliably again.

Chkdsk results displayed:

Code:

Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.

Nice progress.

Use the computer as above and report stability / instability.

zbook said:

Chkdsk results displayed:

Code:

Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.

Nice progress.

Use the computer as above and report stability / instability.

That is my intent. Thanks for your help/insight so far. Once again I have missed doing some obvious steps first. That's OK, I've learnt a few things along the way. Once I determine that it is stable again I'll start looking at reducing the size of the MSR - but I'll do that in a seperate post. I will return to this thread to do an update next week.

That should be sufficient time to check for stability / instability.
If there is any uncertainty please upload a new V2.
If there are any hangs / freezes requiring power offs please make note of the date and time.

Anibor said:

The MSR partition is normally created automatically when a disk is initialized as GPT, or during a clean install. It´s not necessary to boot, neither to help Windows, and it´s not an NTFS partition, as appears in the Macrium image.

Normally it's created durring windows installation on a new storage medium. This installation has survived since Windows for Workgroups 3.11. Cloning from old hardware to new and upgrading windows to it's present state of Windows 10. The drive(s) of past years have given way to SSD now. When it existed as Windows 7 it was a few 500GB drives existing as a BIOS/MBR setup. When I went to Windows 10 I migrated the OS (via cloning) to a 2TB hard drive and then relocated the various folders back to the default Windows configuration. When I found the hard drive to be to slow I went out and got the SSD.

Before I cloned to the SSD I converted the system from MBR to GPT (new motherboard had UEFI) so it didn't have an MSR.

MSR's have two sizes, a 16MB and a 128MB (I didn't know that when I created them). Larger doesn't seem to be a problem except that I lose usable storage space. I'll reclaim that at a later date when I determine the system is again stable (this particular boot problem is gone).

I do know that 16 MB is to small as per https://docs.microsoft.com/en-us/pre...99232(v=ws.10) .

Thank you ZBook your help seems to have solved the puzzle of the intermittent boot failures. The file corruption and the MFT corruption appear to be the cause. Now that both are fixed the computer is starting up properly. Thanks again.

That's great news.

You're welcome.

If not yet done consider:
a) upgrading Windows
b) making free backup images

Repair Install Windows 10 with an In-place Upgrade


Macrium Software | Your Image is Everything
Backup and Restore with Macrium Reflect