- Joined
- May 20, 2002
I've been thinking the same sad thing: Fresh install after the drive is wiped clean.
-
Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
PC unbootable
- Thread starter Time-Bandit
- Start date
I've been thinking the same sad thing: Fresh install after the drive is wiped clean.
OP
- Joined
- Jul 30, 2014
- Thread Starter
- #22
First chkdsk I ran that I was talking about in my earlier post running chkdsk with the /f command
Checking file system on C:
The type of the file system is NTFS.
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)...
Cleaning up instance tags for file 0x2a01.
Cleaning up instance tags for file 0x523f.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xea57a for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x145fc is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83452.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xf5472 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x14613 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83475.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x20ab9c for possibly 0x3d clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1472b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83755.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3f0398d for possibly 0x7 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x14786 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83846.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3b51ef for possibly 0x3d clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x15e27 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 89639.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3d64a8b for possibly 0xf clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1668c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 91788.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x20e546 for possibly 0x28 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x16e97 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 93847.
Attribute record of type 0x80 and instance tag 0x0 is cross linked
starting at 0x2182d0 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x0
in file 0x16fd0 is already in use.
The attribute of type 0x80 and instance tag 0x0 in file 0x16fd0
has allocated length of 0x24a000 instead of 0xb8000.
Deleted corrupt attribute list entry
with type code 128 in file 94160.
Unable to locate attribute with instance tag 0x0 and segment
reference 0xab0000000147ed. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 83949.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x4d000000014f73. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 85875.
Unable to locate attribute with instance tag 0x0 and segment
reference 0xd6000000014fb2. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 85938.
Cleaning up instance tags for file 0x1b528.
Cleaning up instance tags for file 0x1c1ed.
Cleaning up instance tags for file 0x1cfb3.
Cleaning up instance tags for file 0x1cfd3.
Cleaning up instance tags for file 0x1cfe2.
Cleaning up instance tags for file 0x1d975.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xb3141c8 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x21457 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 136279.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0x160c for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x5
in file 0x25d09 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 154889.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x5cb for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3bd9d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 245149.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x183508 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x40c51 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 265297.
595200 file records processed. File verification completed.
Deleting orphan file record segment 83949.
Deleting orphan file record segment 85875.
Deleting orphan file record segment 85938.
15802 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
The file reference 0x82c00000000e93a of index entry MSS.log of index $I30
with parent 0x653 is not the same as 0x83000000000e93a.
Deleting index entry MSS.log in index $I30 of file 1619.
The file reference 0x18800000000265a of index entry TMPA0201837E930FED7 of index $I30
with parent 0xe85 is not the same as 0x18700000000265a.
Deleting index entry TMPA0201837E930FED7 in index $I30 of file 3717.
The file reference 0x18800000000265a of index entry TMPA02~1 of index $I30
with parent 0xe85 is not the same as 0x18700000000265a.
Deleting index entry TMPA02~1 in index $I30 of file 3717.
The file reference 0x10000000014613 of index entry MBAMSwissArmy.cat of index $I30
with parent 0xe8d0 is not the same as 0xf000000014613.
Deleting index entry MBAMSwissArmy.cat in index $I30 of file 59600.
The file reference 0x120000000145fc of index entry MBAMSwissArmy.inf of index $I30
with parent 0xe8d0 is not the same as 0x110000000145fc.
Deleting index entry MBAMSwissArmy.inf in index $I30 of file 59600.
The file reference 0x14a0000000145f0 of index entry MBAMSwissArmy.sys of index $I30
with parent 0xe8d0 is not the same as 0x1490000000145f0.
Deleting index entry MBAMSwissArmy.sys in index $I30 of file 59600.
The file reference 0xcf000000014635 of index entry MBAMSwissArmy.tmf of index $I30
with parent 0xe8d0 is not the same as 0xce000000014635.
Deleting index entry MBAMSwissArmy.tmf in index $I30 of file 59600.
The file reference 0x10000000014613 of index entry MBAMSW~1.CAT of index $I30
with parent 0xe8d0 is not the same as 0xf000000014613.
Deleting index entry MBAMSW~1.CAT in index $I30 of file 59600.
The file reference 0x120000000145fc of index entry MBAMSW~1.INF of index $I30
with parent 0xe8d0 is not the same as 0x110000000145fc.
Deleting index entry MBAMSW~1.INF in index $I30 of file 59600.
The file reference 0x14a0000000145f0 of index entry MBAMSW~1.SYS of index $I30
with parent 0xe8d0 is not the same as 0x1490000000145f0.
Deleting index entry MBAMSW~1.SYS in index $I30 of file 59600.
The file reference 0xcf000000014635 of index entry MBAMSW~1.TMF of index $I30
with parent 0xe8d0 is not the same as 0xce000000014635.
Deleting index entry MBAMSW~1.TMF in index $I30 of file 59600.
Unable to locate the file name attribute of index entry ti-analytics.19.log.gz
of index $I30 with parent 0x14102 in file 0x150c8.
Deleting index entry ti-analytics.19.log.gz in index $I30 of file 82178.
Unable to locate the file name attribute of index entry ti-analytics.2.log.gz
of index $I30 with parent 0x14102 in file 0x150cd.
Deleting index entry ti-analytics.2.log.gz in index $I30 of file 82178.
Unable to locate the file name attribute of index entry ti-analytics.21.log.gz
of index $I30 with parent 0x14102 in file 0x14c9b.
Deleting index entry ti-analytics.21.log.gz in index $I30 of file 82178.
Unable to locate the file name attribute of index entry ti-analytics.23.log.gz
of index $I30 with parent 0x14102 in file 0x148a6.
Deleting index entry ti-analytics.23.log.gz in index $I30 of file 82178.
Unable to locate the file name attribute of index entry TI1F71~1.GZ
of index $I30 with parent 0x14102 in file 0x149bb.
Deleting index entry TI1F71~1.GZ in index $I30 of file 82178.
Unable to locate the file name attribute of index entry TI5758~1.GZ
of index $I30 with parent 0x14102 in file 0x150cd.
Deleting index entry TI5758~1.GZ in index $I30 of file 82178.
Unable to locate the file name attribute of index entry TI84CA~1.GZ
of index $I30 with parent 0x14102 in file 0x150c8.
Deleting index entry TI84CA~1.GZ in index $I30 of file 82178.
Unable to locate the file name attribute of index entry TI9890~1.GZ
of index $I30 with parent 0x14102 in file 0x148a6.
Deleting index entry TI9890~1.GZ in index $I30 of file 82178.
Unable to locate the file name attribute of index entry TIEA91~1.GZ
of index $I30 with parent 0x14102 in file 0x14c9b.
Deleting index entry TIEA91~1.GZ in index $I30 of file 82178.
Unable to locate the file name attribute of index entry ti_monitor.3.log.gz
of index $I30 with parent 0x14102 in file 0x149bb.
Deleting index entry ti_monitor.3.log.gz in index $I30 of file 82178.
Index entry ti_monitor.9.log.gz of index $I30 in file 0x14102 points to unused file 0x177a8.
Deleting index entry ti_monitor.9.log.gz in index $I30 of file 82178.
Index entry TI_MON~2.GZ of index $I30 in file 0x14102 points to unused file 0x177a8.
Deleting index entry TI_MON~2.GZ in index $I30 of file 82178.
685372 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file TIAF1A~1.LOG (1571) into directory file 93780.
Recovering orphaned file TibMounter-20201031-072823-147.log (1571) into directory file 93780.
Recovering orphaned file TN3A95~1.LOG (64919) into directory file 89975.
Recovering orphaned file tnd-20201031-072840-946.log (64919) into directory file 89975.
Recovering orphaned file 78B7EE~1.JSO (71289) into directory file 242647.
Recovering orphaned file 78b7eedb-1b49-11eb-8079-000000000000.json (71289) into directory file 242647.
Recovering orphaned file TI8208~1.GZ (84134) into directory file 82178.
Recovering orphaned file ti-analytics.24.log.gz (84134) into directory file 82178.
Recovering orphaned file TI984C~1.GZ (84411) into directory file 82178.
Recovering orphaned file ti_monitor.4.log.gz (84411) into directory file 82178.
Recovering orphaned file TIF03A~1.GZ (85147) into directory file 82178.
Recovering orphaned file ti-analytics.22.log.gz (85147) into directory file 82178.
Recovering orphaned file TI646C~1.GZ (86216) into directory file 82178.
Recovering orphaned file ti-analytics.20.log.gz (86216) into directory file 82178.
20 unindexed files scanned. Recovering orphaned file TI3272~1.GZ (86221) into directory file 82178.
Recovering orphaned file ti-analytics.3.log.gz (86221) into directory file 82178.
CHKDSK is recovering remaining unindexed files.
12 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
595200 file SDs/SIDs processed. Cleaning up 1398 unused index entries from index $SII of file 0x9.
Cleaning up 1398 unused index entries from index $SDH of file 0x9.
Cleaning up 1398 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 83452.
Inserting data attribute into file 83475.
Inserting data attribute into file 83755.
Inserting data attribute into file 83846.
Inserting data attribute into file 89639.
Inserting data attribute into file 91788.
Inserting data attribute into file 93847.
Inserting data attribute into file 94160.
Inserting data attribute into file 136279.
Inserting data attribute into file 154889.
Inserting data attribute into file 245149.
Inserting data attribute into file 265297.
45099 data files processed. CHKDSK is verifying Usn Journal...
34095912 USN bytes processed. Usn Journal verification completed.
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.
2147071996 KB total disk space.
1264529324 KB in 385040 files.
202200 KB in 45091 indexes.
0 KB in bad sectors.
766400 KB in use by the system.
65536 KB occupied by the log file.
881574072 KB available on disk.
4096 bytes in each allocation unit.
536767999 total allocation units on disk.
220393518 allocation units available on disk.
Internal Info:
00 15 09 00 46 90 06 00 3e 27 0c 00 00 00 00 00 ....F...>'......
54 03 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 T...,...........
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.
Ran a chkdsk overnight on c drive with the /r command and got this.
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
595200 file records processed. File verification completed.
15698 large file records processed. 0 bad file records processed. 2 EA records processed. 56 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
688970 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
595200 file SDs/SIDs processed. Cleaning up 1149 unused index entries from index $SII of file 0x9.
Cleaning up 1149 unused index entries from index $SDH of file 0x9.
Cleaning up 1149 unused security descriptors.
CHKDSK is compacting the security descriptor stream
46886 data files processed. CHKDSK is verifying Usn Journal...
34199000 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
595184 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
228614186 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
2147071996 KB total disk space.
1231594708 KB in 414479 files.
258176 KB in 46889 indexes.
0 KB in bad sectors.
762368 KB in use by the system.
65536 KB occupied by the log file.
914456744 KB available on disk.
4096 bytes in each allocation unit.
536767999 total allocation units on disk.
228614186 allocation units available on disk.
Internal Info:
00 15 09 00 41 0a 07 00 39 1c 0d 00 00 00 00 00 ....A...9.......
8b 02 00 00 38 00 00 00 00 00 00 00 00 00 00 00 ....8...........
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.
Based on this would this mean I am good?
Checking file system on C:
The type of the file system is NTFS.
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)...
Cleaning up instance tags for file 0x2a01.
Cleaning up instance tags for file 0x523f.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xea57a for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x145fc is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83452.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xf5472 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x14613 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83475.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x20ab9c for possibly 0x3d clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1472b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83755.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3f0398d for possibly 0x7 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x14786 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83846.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3b51ef for possibly 0x3d clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x15e27 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 89639.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x3d64a8b for possibly 0xf clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1668c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 91788.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x20e546 for possibly 0x28 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x16e97 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 93847.
Attribute record of type 0x80 and instance tag 0x0 is cross linked
starting at 0x2182d0 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x0
in file 0x16fd0 is already in use.
The attribute of type 0x80 and instance tag 0x0 in file 0x16fd0
has allocated length of 0x24a000 instead of 0xb8000.
Deleted corrupt attribute list entry
with type code 128 in file 94160.
Unable to locate attribute with instance tag 0x0 and segment
reference 0xab0000000147ed. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 83949.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x4d000000014f73. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 85875.
Unable to locate attribute with instance tag 0x0 and segment
reference 0xd6000000014fb2. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 85938.
Cleaning up instance tags for file 0x1b528.
Cleaning up instance tags for file 0x1c1ed.
Cleaning up instance tags for file 0x1cfb3.
Cleaning up instance tags for file 0x1cfd3.
Cleaning up instance tags for file 0x1cfe2.
Cleaning up instance tags for file 0x1d975.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xb3141c8 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x21457 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 136279.
Attribute record of type 0x80 and instance tag 0x5 is cross linked
starting at 0x160c for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x5
in file 0x25d09 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 154889.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x5cb for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3bd9d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 245149.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x183508 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x40c51 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 265297.
595200 file records processed. File verification completed.
Deleting orphan file record segment 83949.
Deleting orphan file record segment 85875.
Deleting orphan file record segment 85938.
15802 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
The file reference 0x82c00000000e93a of index entry MSS.log of index $I30
with parent 0x653 is not the same as 0x83000000000e93a.
Deleting index entry MSS.log in index $I30 of file 1619.
The file reference 0x18800000000265a of index entry TMPA0201837E930FED7 of index $I30
with parent 0xe85 is not the same as 0x18700000000265a.
Deleting index entry TMPA0201837E930FED7 in index $I30 of file 3717.
The file reference 0x18800000000265a of index entry TMPA02~1 of index $I30
with parent 0xe85 is not the same as 0x18700000000265a.
Deleting index entry TMPA02~1 in index $I30 of file 3717.
The file reference 0x10000000014613 of index entry MBAMSwissArmy.cat of index $I30
with parent 0xe8d0 is not the same as 0xf000000014613.
Deleting index entry MBAMSwissArmy.cat in index $I30 of file 59600.
The file reference 0x120000000145fc of index entry MBAMSwissArmy.inf of index $I30
with parent 0xe8d0 is not the same as 0x110000000145fc.
Deleting index entry MBAMSwissArmy.inf in index $I30 of file 59600.
The file reference 0x14a0000000145f0 of index entry MBAMSwissArmy.sys of index $I30
with parent 0xe8d0 is not the same as 0x1490000000145f0.
Deleting index entry MBAMSwissArmy.sys in index $I30 of file 59600.
The file reference 0xcf000000014635 of index entry MBAMSwissArmy.tmf of index $I30
with parent 0xe8d0 is not the same as 0xce000000014635.
Deleting index entry MBAMSwissArmy.tmf in index $I30 of file 59600.
The file reference 0x10000000014613 of index entry MBAMSW~1.CAT of index $I30
with parent 0xe8d0 is not the same as 0xf000000014613.
Deleting index entry MBAMSW~1.CAT in index $I30 of file 59600.
The file reference 0x120000000145fc of index entry MBAMSW~1.INF of index $I30
with parent 0xe8d0 is not the same as 0x110000000145fc.
Deleting index entry MBAMSW~1.INF in index $I30 of file 59600.
The file reference 0x14a0000000145f0 of index entry MBAMSW~1.SYS of index $I30
with parent 0xe8d0 is not the same as 0x1490000000145f0.
Deleting index entry MBAMSW~1.SYS in index $I30 of file 59600.
The file reference 0xcf000000014635 of index entry MBAMSW~1.TMF of index $I30
with parent 0xe8d0 is not the same as 0xce000000014635.
Deleting index entry MBAMSW~1.TMF in index $I30 of file 59600.
Unable to locate the file name attribute of index entry ti-analytics.19.log.gz
of index $I30 with parent 0x14102 in file 0x150c8.
Deleting index entry ti-analytics.19.log.gz in index $I30 of file 82178.
Unable to locate the file name attribute of index entry ti-analytics.2.log.gz
of index $I30 with parent 0x14102 in file 0x150cd.
Deleting index entry ti-analytics.2.log.gz in index $I30 of file 82178.
Unable to locate the file name attribute of index entry ti-analytics.21.log.gz
of index $I30 with parent 0x14102 in file 0x14c9b.
Deleting index entry ti-analytics.21.log.gz in index $I30 of file 82178.
Unable to locate the file name attribute of index entry ti-analytics.23.log.gz
of index $I30 with parent 0x14102 in file 0x148a6.
Deleting index entry ti-analytics.23.log.gz in index $I30 of file 82178.
Unable to locate the file name attribute of index entry TI1F71~1.GZ
of index $I30 with parent 0x14102 in file 0x149bb.
Deleting index entry TI1F71~1.GZ in index $I30 of file 82178.
Unable to locate the file name attribute of index entry TI5758~1.GZ
of index $I30 with parent 0x14102 in file 0x150cd.
Deleting index entry TI5758~1.GZ in index $I30 of file 82178.
Unable to locate the file name attribute of index entry TI84CA~1.GZ
of index $I30 with parent 0x14102 in file 0x150c8.
Deleting index entry TI84CA~1.GZ in index $I30 of file 82178.
Unable to locate the file name attribute of index entry TI9890~1.GZ
of index $I30 with parent 0x14102 in file 0x148a6.
Deleting index entry TI9890~1.GZ in index $I30 of file 82178.
Unable to locate the file name attribute of index entry TIEA91~1.GZ
of index $I30 with parent 0x14102 in file 0x14c9b.
Deleting index entry TIEA91~1.GZ in index $I30 of file 82178.
Unable to locate the file name attribute of index entry ti_monitor.3.log.gz
of index $I30 with parent 0x14102 in file 0x149bb.
Deleting index entry ti_monitor.3.log.gz in index $I30 of file 82178.
Index entry ti_monitor.9.log.gz of index $I30 in file 0x14102 points to unused file 0x177a8.
Deleting index entry ti_monitor.9.log.gz in index $I30 of file 82178.
Index entry TI_MON~2.GZ of index $I30 in file 0x14102 points to unused file 0x177a8.
Deleting index entry TI_MON~2.GZ in index $I30 of file 82178.
685372 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file TIAF1A~1.LOG (1571) into directory file 93780.
Recovering orphaned file TibMounter-20201031-072823-147.log (1571) into directory file 93780.
Recovering orphaned file TN3A95~1.LOG (64919) into directory file 89975.
Recovering orphaned file tnd-20201031-072840-946.log (64919) into directory file 89975.
Recovering orphaned file 78B7EE~1.JSO (71289) into directory file 242647.
Recovering orphaned file 78b7eedb-1b49-11eb-8079-000000000000.json (71289) into directory file 242647.
Recovering orphaned file TI8208~1.GZ (84134) into directory file 82178.
Recovering orphaned file ti-analytics.24.log.gz (84134) into directory file 82178.
Recovering orphaned file TI984C~1.GZ (84411) into directory file 82178.
Recovering orphaned file ti_monitor.4.log.gz (84411) into directory file 82178.
Recovering orphaned file TIF03A~1.GZ (85147) into directory file 82178.
Recovering orphaned file ti-analytics.22.log.gz (85147) into directory file 82178.
Recovering orphaned file TI646C~1.GZ (86216) into directory file 82178.
Recovering orphaned file ti-analytics.20.log.gz (86216) into directory file 82178.
20 unindexed files scanned. Recovering orphaned file TI3272~1.GZ (86221) into directory file 82178.
Recovering orphaned file ti-analytics.3.log.gz (86221) into directory file 82178.
CHKDSK is recovering remaining unindexed files.
12 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
595200 file SDs/SIDs processed. Cleaning up 1398 unused index entries from index $SII of file 0x9.
Cleaning up 1398 unused index entries from index $SDH of file 0x9.
Cleaning up 1398 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 83452.
Inserting data attribute into file 83475.
Inserting data attribute into file 83755.
Inserting data attribute into file 83846.
Inserting data attribute into file 89639.
Inserting data attribute into file 91788.
Inserting data attribute into file 93847.
Inserting data attribute into file 94160.
Inserting data attribute into file 136279.
Inserting data attribute into file 154889.
Inserting data attribute into file 245149.
Inserting data attribute into file 265297.
45099 data files processed. CHKDSK is verifying Usn Journal...
34095912 USN bytes processed. Usn Journal verification completed.
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.
2147071996 KB total disk space.
1264529324 KB in 385040 files.
202200 KB in 45091 indexes.
0 KB in bad sectors.
766400 KB in use by the system.
65536 KB occupied by the log file.
881574072 KB available on disk.
4096 bytes in each allocation unit.
536767999 total allocation units on disk.
220393518 allocation units available on disk.
Internal Info:
00 15 09 00 46 90 06 00 3e 27 0c 00 00 00 00 00 ....F...>'......
54 03 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 T...,...........
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.
Ran a chkdsk overnight on c drive with the /r command and got this.
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
595200 file records processed. File verification completed.
15698 large file records processed. 0 bad file records processed. 2 EA records processed. 56 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
688970 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
595200 file SDs/SIDs processed. Cleaning up 1149 unused index entries from index $SII of file 0x9.
Cleaning up 1149 unused index entries from index $SDH of file 0x9.
Cleaning up 1149 unused security descriptors.
CHKDSK is compacting the security descriptor stream
46886 data files processed. CHKDSK is verifying Usn Journal...
34199000 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
595184 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
228614186 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
2147071996 KB total disk space.
1231594708 KB in 414479 files.
258176 KB in 46889 indexes.
0 KB in bad sectors.
762368 KB in use by the system.
65536 KB occupied by the log file.
914456744 KB available on disk.
4096 bytes in each allocation unit.
536767999 total allocation units on disk.
228614186 allocation units available on disk.
Internal Info:
00 15 09 00 41 0a 07 00 39 1c 0d 00 00 00 00 00 ....A...9.......
8b 02 00 00 38 00 00 00 00 00 00 00 00 00 00 00 ....8...........
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.
Based on this would this mean I am good?
Last edited:
- Joined
- Feb 1, 2011
- Location
- Republic of Texas
Depends. Did you attempt restart yet? You should know at that point in time.
OP
- Joined
- Jul 30, 2014
- Thread Starter
- #24
System loaded as normal.
Do I need to check mbr or assume it's fine since I can boot and login without issue??
Do I need to check mbr or assume it's fine since I can boot and login without issue??
- Joined
- May 20, 2002
OP
- Joined
- Jul 30, 2014
- Thread Starter
- #26
how can I check the mbr?
Why do insist on checking it? Does it boot? Then you are all set!
I'm curious 'how' to check it (since it was mentioned to do so), but since you are clearly back up, I don't see a point (yet curious to know what that process is).
- Joined
- May 20, 2002
Storage Ultimate Sticky Thread:
It seems that you may not have seen the STICKY:
https://www.overclockers.com/forums...-Ultimate-Sticky-Thread?p=8153149#post8153149
It has all kinds of HDD and SSD information!
It seems that you may not have seen the STICKY:
https://www.overclockers.com/forums...-Ultimate-Sticky-Thread?p=8153149#post8153149
It has all kinds of HDD and SSD information!
Thanks for the link! Can't say I remembered it!Storage Ultimate Sticky Thread:
It seems that you may not have seen the STICKY:
https://www.overclockers.com/forums...-Ultimate-Sticky-Thread?p=8153149#post8153149
It has all kinds of HDD and SSD information!
That said, please link directly to where it says WHY we need to check the MBR and HOW. There are several links there, but not sure which will have the information we're looking for here.
OP
- Joined
- Jul 30, 2014
- Thread Starter
- #30
Why do insist on checking it? Does it boot? Then you are all set!
I'm curious 'how' to check it (since it was mentioned to do so), but since you are clearly back up, I don't see a point (yet curious to know what that process is).
Wanting to check since prior to my system going down MBR was said to be the problem, I figure the same if it boots it works. That being said my knowledge is minimal and wanting to ensure we are all good with no issues so I can create a new back up and remove the old one which was prior to my hardware swap/OS reinstall.
- - - Auto-Merged Double Post - - -
Storage Ultimate Sticky Thread:
It seems that you may not have seen the STICKY:
https://www.overclockers.com/forums...-Ultimate-Sticky-Thread?p=8153149#post8153149
It has all kinds of HDD and SSD information!
Please link where it has info about MBR checking/testing as I can't find this info would be great.
OP
- Joined
- Jul 30, 2014
- Thread Starter
- #33
EaseUS Partition Manager changes MBR to GPT.
I thought for Windows it had to be set to MBR for Win 7 install?
I have my windows installed on a 4TB HDD so I have 2 TB that is the OS and another unallocated 2TB. Don't think I can merge them right?
Also since the OS upgrade reinstall every seems to be working fine just need to confirm MBR on the HDD's.
One BSOD that I have had come up twice is memory_management BSOD. I am testing both Ram sticks now with memtest86 which has been going on for several hours and so far no errors coming up.
My GPU drive is updated as well and have seen on other forums pointing towards nvidia gpu driver. I was on AMD previously and used DDU to remove anything AMD related. So I am puzzled on this one.
Just had a thought, my card is an MSI card. I am using the drivers given to me from geforce experience. Should I be using the utility from the MSI for my cards driver and not geforce experience ???? I would have thought its fine to use these??
Last edited:
OP
- Joined
- Jul 30, 2014
- Thread Starter
- #35
So even if Ram checks out as clean in memtest86 it will still be the ram?
There was another error I got but can't remember if this was prior or after driver fixes/OS reinstall page file fault or something to that effect. Have not had it again so far just twice on the memory management error. Based on this would you say the drive is now Ok for cloning?
Don't have a great deal of space so have to delete the old backup that was pre hardware changes/drivers/OS reinstall.
Chkdsk comes up with nothing on all drives now with both /f and /r commands.
I stay away from GFE... it does nothing but get in the way. I set my games manually, and download new drivers when I feel like it/need to for a new game. You're an enthusiast....Uninstall GFE... set games and get drivers manually.
That said, mixed ram could very well be the issue....
OP
- Joined
- Jul 30, 2014
- Thread Starter
- #37
You guys might be right, RAM passed memtes86 no problems BUT... did 2 tests with windows memtest. Extended testwith cache on passed no problems. Did the test again cache off and has either frozen/not started at all 20min in at 0%.
OP
- Joined
- Jul 30, 2014
- Thread Starter
- #38
Update - Couple hours into this windows mem test running with cache off/extended testing. I was looking to do 8 passes as I did with the first test but this thing is going just extremely slowly never used windows mem test so not sure how quick it should be running this test in extended with cache off. Either way I am only at 5% completed on the first pass and 0% on overall.
If I let this complete 1 or 2 passes then hit escape to cancel out will windows tell me if there were any issues with the two passes once I load back into windows?
Or do I now have to complete all 8 passes to get an answer??
No error messages or errors have come up yet either just FYI.
If I let this complete 1 or 2 passes then hit escape to cancel out will windows tell me if there were any issues with the two passes once I load back into windows?
Or do I now have to complete all 8 passes to get an answer??
No error messages or errors have come up yet either just FYI.
OP
- Joined
- Jul 30, 2014
- Thread Starter
- #39
Left test going overnight, without cache on and extended test its only at 20% on first pass. Should it take this long or is there something wrong with the ram ??
Wouldn't the easiest way be to try running without the other set in? If it works, swap it out with the other. If they both work alone, then its clear together they arent playing nice. Artificial testing isn't The Gospel.
You fixed your MBR/boot issue, clone your drive, and run the kits alone.
You fixed your MBR/boot issue, clone your drive, and run the kits alone.
Similar threads
- Locked
