Chkdisk deleted files that I transferred

Hello everyone,

This forum has helped me so much with setting up my new system and I'm hoping to get an answer for my next issue.

First off, I purchased an HP system with a 2T hdd running Windows 7 Home Premium. I purchased a 128gb SSD drive since I'm a speed freak. I am running a dual boot with 2 separate drives with Windows 7 Ultimate on the SSD and keeping the same setup HP sent me. The 2T drive will pretty much be used for storage but I want to keep the OS on it in case I have a warranty issue. On another note, I am also running on UEFI.

After days figuring out how to load the Windows Ultimate on my SSD using UEFI, I thought everything was fine. Yesterday I loaded the OS from the SSD and transferred some movie files to the 2T HDD. Later on when I started the computer, chkdsk came on and it started deleting all the movie files I had transferred. Today I loaded into the 2T OS and noticed Norton Antivirus was corrupted. I uninstalled Norton on the 2T since I won't be using that OS much anyways. What I also did was go into the folder where I transferred the movie files into and changed the security to accept me as an Administrator.

I have then loaded the files back and chkdsk has not come back on. What I am scared of is if it does it again in the future, I may lose everything. What I am going to be doing is moving my user profile on the SSD to the 2T HDD since my SSD is only 128gb.

Is Norton the culprit? Is it because I changed the security in the folder that fixed this?

Thanks in advance and I apologize for the long post.

Click Start and type "eventvwr.msc" (no quotes). Expand "Windows Logs" and click on "Application" once to highlight it. Right click it and click "Find." In the find box, type in "Chkdsk" (no quotes). Now click "Find next." This will allow you to cycle through all of your CHKDSK instances that have occurred, starting with the most recent. They will appear at the bottom half of the window, and you might have to cancel out of the search dialog box to see it. Find the date of the scan that deleted your files, and look through it. If you don't know what you're looking at, copy and paste it here.

Ok here's a few of them.. First one

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)...
The attribute of type 0x80 and instance tag 0x8 in file 0x182cf
has allocated length of 0x890000 instead of 0x1a90000.
Deleting corrupt attribute record (128, $J)
from file record segment 99023.
199680 file records processed. File verification completed.
332 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 0x400000002325b of index entry {99F90~3 of index $I30
with parent 0x6a63 is not the same as 0x1d00000002325b.
Deleting index entry {99F90~3 in index $I30 of file 27235.
The file reference 0xa00000001f844 of index entry f_000475 of index $I30
with parent 0x229f4 is not the same as 0x600000001f844.
Deleting index entry f_000475 in index $I30 of file 141812.
The multi-sector header signature for VCN 0x1 of index $I30
in file 0x26522 is incorrect.
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 00 00 00 00 00 ................
Correcting error in index $I30 for file 156962.
The index bitmap $I30 in file 0x26522 is incorrect.
Correcting error in index $I30 for file 156962.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 07 5e 5e f2 af 7c cd 01 .........^^..|..
00 b0 06 00 00 00 00 00 30 a0 06 00 00 00 00 00 ........0.......
Sorting index $I30 in file 156962.
The multi-sector header signature for VCN 0x2 of index $I30
in file 0x26902 is incorrect.
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 00 00 00 00 00 ................
Correcting error in index $I30 for file 157954.
The index bitmap $I30 in file 0x26902 is incorrect.
Correcting error in index $I30 for file 157954.
The down pointer of current index entry with length 0xa8 is invalid.
1a 69 02 00 00 00 02 00 a8 00 8a 00 01 00 00 00 .i..............
02 69 02 00 00 00 02 00 de 0c ef ed af 7c cd 01 .i...........|..
de 0c ef ed af 7c cd 01 de 0c ef ed af 7c cd 01 .....|.......|..
de 0c ef ed af 7c cd 01 00 10 00 00 00 00 00 00 .....|..........
70 02 00 00 00 00 00 00 20 00 00 00 00 00 00 00 p....... .......
24 01 70 00 68 00 69 00 73 00 68 00 69 00 6e 00 $.p.h.i.s.h.i.n.
67 00 5f 00 74 00 61 00 6b 00 65 00 5f 00 6d 00 g._.t.a.k.e._.m.
65 00 5f 00 74 00 6f 00 5f 00 76 00 61 00 72 00 e._.t.o._.v.a.r.
5f 00 30 00 2e 00 72 00 63 00 64 00 6c 00 67 00 _.0...r.c.d.l.g.
2e 00 64 00 61 00 74 00 61 00 00 00 00 00 00 00 ..d.a.t.a.......
ff ff ff ff ff ff ff ff 00 00 00 00 00 00 00 00 ................
18 00 00 00 03 00 00 00 03 00 00 00 00 00 00 00 ................
Sorting index $I30 in file 157954.
The multi-sector header signature for VCN 0x3 of index $I30
in file 0x26a57 is incorrect.
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 00 00 00 00 00 ................
The multi-sector header signature for VCN 0xa of index $I30
in file 0x26a57 is incorrect.
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 00 00 00 00 00 ................
The multi-sector header signature for VCN 0xb of index $I30
in file 0x26a57 is incorrect.
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 00 00 00 00 00 ................
Correcting error in index $I30 for file 158295.
The index bitmap $I30 in file 0x26a57 is incorrect.
Correcting error in index $I30 for file 158295.
The down pointer of current index entry with length 0x78 is invalid.
73 6a 02 00 00 00 03 00 78 00 5a 00 01 00 00 00 sj......x.Z.....
57 6a 02 00 00 00 02 00 31 4f 60 f9 af 7c cd 01 Wj......1O`..|..
31 4f 60 f9 af 7c cd 01 31 4f 60 f9 af 7c cd 01 1O`..|..1O`..|..
31 4f 60 f9 af 7c cd 01 00 10 00 00 00 00 00 00 1O`..|..........
00 10 00 00 00 00 00 00 20 20 00 00 00 00 00 00 ........ ......
0c 02 30 00 44 00 37 00 38 00 33 00 30 00 7e 00 ..0.D.7.8.3.0.~.
31 00 2e 00 44 00 41 00 54 00 00 00 00 00 00 00 1...D.A.T.......
ff ff ff ff ff ff ff ff 7d 6a 02 00 00 00 02 00 ........}j......
78 00 5a 00 01 00 00 00 57 6a 02 00 00 00 02 00 x.Z.....Wj......
Sorting index $I30 in file 158295.
276270 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file _WC-US~1.XML (129092) into directory file 129091.
Recovering orphaned file _wc-USNY0996Fen-US_.xml (129092) into directory file 129091.
Recovering orphaned file {7DC4B~1 (155285) into directory file 27235.
Recovering orphaned file RAPPOR~1.SYS (156978) into directory file 156962.
Recovering orphaned file RAPPOR~1.EXE (156979) into directory file 156962.
Recovering orphaned file RAPPOR~2.SYS (156980) into directory file 156962.
Recovering orphaned file RapportKE64.sys (156980) into directory file 156962.
Recovering orphaned file RAPPOR~1.DLL (156982) into directory file 156962.
Recovering orphaned file RapportKoan_x64.dll (156982) into directory file 156962.
Recovering orphaned file RAPPOR~3.SYS (156985) into directory file 156962.
Recovering orphaned file RapportPG64.sys (156985) into directory file 156962.
Recovering orphaned file RAPPOR~2.DLL (157450) into directory file 156962.
Recovering orphaned file RapportUtil_x64.dll (157450) into directory file 156962.
Recovering orphaned file ROOKSB~1.DAT (157535) into directory file 156962.
Recovering orphaned file rooksbas_x64.dll.data (157535) into directory file 156962.
Recovering orphaned file ROOKSC~1.DAT (157538) into directory file 156962.
Recovering orphaned file rookscom_x64.dll.data (157538) into directory file 156962.
Recovering orphaned file ROOKSD~1.DAT (157540) into directory file 156962.
Recovering orphaned file rooksdol_x64.dll.data (157540) into directory file 156962.
Recovering orphaned file PAYMEN~1.DAT (157970) into directory file 157954.
Recovering orphaned file PENDIN~1.DAT (157971) into directory file 157954.
Recovering orphaned file pending_messages_notification_var_0.rcdlg.data (157971) into directory file 157954.
Recovering orphaned file PHARMI~1.DAT (157972) into directory file 157954.
Recovering orphaned file pharming_cached_ip_var_0.rcdlg.data (157972) into directory file 157954.
Recovering orphaned file PHARMI~2.DAT (157973) into directory file 157954.
Recovering orphaned file pharming_cert_error_var_0.rcdlg.data (157973) into directory file 157954.
Recovering orphaned file PHARMI~3.DAT (157974) into directory file 157954.
Recovering orphaned file pharming_detected_var_0.rcdlg.data (157974) into directory file 157954.
Recovering orphaned file PHARMI~4.DAT (157975) into directory file 157954.
Recovering orphaned file pharming_dns_error_var_0.rcdlg.data (157975) into directory file 157954.
Recovering orphaned file PH588D~1.DAT (157976) into directory file 157954.
Recovering orphaned file pharming_unknown_host_var_0.rcdlg.data (157976) into directory file 157954.
Recovering orphaned file phishing_confirm_learning_var_0.rcdlg.data (157977) into directory file 157954.
Recovering orphaned file ROOKSB~1.DLL (158063) into directory file 156962.
Recovering orphaned file rooksbas_x64.dll (158063) into directory file 156962.
Recovering orphaned file ROOKSC~1.DLL (158065) into directory file 156962.
Recovering orphaned file rookscom_x64.dll (158065) into directory file 156962.
Recovering orphaned file ROOKSD~1.DLL (158067) into directory file 156962.
Recovering orphaned file rooksdol_x64.dll (158067) into directory file 156962.
Recovering orphaned file 0A7BAD~1.DAT (158318) into directory file 158295.
Recovering orphaned file 0a7badcf250fe99d09a1e8f2625fb457_var_0.png.data (158318) into directory file 158295.
Recovering orphaned file 0AA00D~1.DAT (158319) into directory file 158295.
Recovering orphaned file 0aa00d8eb3e4f9e37f5baadedb8f2e18_var_0.png.data (158319) into directory file 158295.
Recovering orphaned file 0BEAC2~1.DAT (158320) into directory file 158295.
Recovering orphaned file 0beac214bd0efa5af78dad1b8b398d73_var_0.png.data (158320) into directory file 158295.
Recovering orphaned file 0BEFA9~1.DAT (158321) into directory file 158295.
Recovering orphaned file 0befa992b124aa3f95c1cbc33736e7d0_var_0.png.data (158321) into directory file 158295.
Recovering orphaned file 0C4F52~1.DAT (158322) into directory file 158295.
Recovering orphaned file 0c4f5291cb4c7786d45eb32bdb8dc873_var_0.png.data (158322) into directory file 158295.
Recovering orphaned file 0d7830e3dc1fbd73b9004758216e5611_var_0.png.data (158323) into directory file 158295.
Recovering orphaned file 0D28A9~1.DAT (158324) into directory file 158295.
Recovering orphaned file 0d28a93a282235b6ebc0e0c43d00f8e9_var_0.png.data (158324) into directory file 158295.
Recovering orphaned file 1EFB6A~1.DAT (158362) into directory file 158295.
Recovering orphaned file 1efb6a55d75a858bfab85a884732e430_var_0.gif.data (158362) into directory file 158295.
Recovering orphaned file 1F28EF~1.DAT (158365) into directory file 158295.
Recovering orphaned file 1f28ef3759660b61a30601ad01c1c4bc_var_0.gif.data (158365) into directory file 158295.
Recovering orphaned file 1FC5E4~1.DAT (158366) into directory file 158295.
Recovering orphaned file 1fc5e4e4c22e0657c6b42de0b5e5f191_var_0.png.data (158366) into directory file 158295.
Recovering orphaned file 2001D3~1.DAT (158367) into directory file 158295.
Recovering orphaned file 2001d375fc3878578eae1b6eae61c14e_var_0.png.data (158367) into directory file 158295.
Recovering orphaned file 207708~1.DAT (158368) into directory file 158295.
Recovering orphaned file 207708241a6347162502ae533973417c_var_0.png.data (158368) into directory file 158295.
Recovering orphaned file 208F19~1.DAT (158369) into directory file 158295.
Recovering orphaned file 208f19b646861c2863b6ba248c7dc58d_var_0.png.data (158369) into directory file 158295.
Recovering orphaned file 20a4d0b8efbc8b4129d6940a7ced7396_var_0.png.data (158370) into directory file 158295.
Recovering orphaned file 20FE2B~1.DAT (158371) into directory file 158295.
Recovering orphaned file 20fe2b0327249481d6c7b411ca39ccc0_var_0.png.data (158371) into directory file 158295.
Recovering orphaned file 22A1EC~1.DAT (158372) into directory file 158295.
Recovering orphaned file 22a1ecf4c6f4c8ea2fa16d6b9b395379_var_0.gif.data (158372) into directory file 158295.
Recovering orphaned file 22FF6B~1.DAT (158373) into directory file 158295.
Recovering orphaned file 22ff6baf1590704a452ad5f57a18a7c0_var_0.png.data (158373) into directory file 158295.
Recovering orphaned file 23584D~1.DAT (158374) into directory file 158295.
Recovering orphaned file 23584de4ed1d4eef62f9b60bb5b568b8_var_0.png.data (158374) into directory file 158295.
Recovering orphaned file 236816~1.DAT (158375) into directory file 158295.
Recovering orphaned file 236816ac4ccfb31d9dde943de334294c_var_0.png.data (158375) into directory file 158295.
Recovering orphaned file 237812~1.DAT (158376) into directory file 158295.
Recovering orphaned file 237812c901554ad195540544dfe4cccf_var_0.png.data (158376) into directory file 158295.
Recovering orphaned file 23d64678b157293083d739877d6a0016_var_0.gif.data (158377) into directory file 158295.
45 unindexed files scanned. Recovering orphaned file PCSHAR~1 (159358) into directory file 5.
Recovering orphaned file PCShareManagerUpload (159358) into directory file 5.
CHKDSK is recovering remaining unindexed files.
1 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
199680 file SDs/SIDs processed. Cleaning up 42 unused index entries from index $SII of file 0x9.
Cleaning up 42 unused index entries from index $SDH of file 0x9.
Cleaning up 42 unused security descriptors.
Security descriptor verification completed.
38296 data files processed. CHKDSK is verifying Usn Journal...
Creating Usn Journal $J data stream
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.

124799999 KB total disk space.
57085700 KB in 156116 files.
120776 KB in 38298 indexes.
0 KB in bad sectors.
270299 KB in use by the system.
65536 KB occupied by the log file.
67323224 KB available on disk.

4096 bytes in each allocation unit.
31199999 total allocation units on disk.
16830806 allocation units available on disk.

Internal Info:
00 0c 03 00 77 f7 02 00 fb 00 06 00 00 00 00 00 ....w...........
e9 00 00 00 2c 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.

Well, you certainly needed CHKDSK to run because you had some corrupt areas on your drive. What's strange is how they got corrupted. Your copy of Windows 7 Ultimate is legitimate, right? As in you purchased the license and everything? I'm only asking because I've heard of pirated copies pulling some nasty stuff on people after a month of hassle-free use. This session of CHKDSK fixed a lot of problems, especially with your MFT (master file table), the "header" that allows files to be accessed on NTFS (it's sort of like metadata). I doubt you'll have any more problems after such a thorough clean-up as this, but to be safe, ALWAYS back up your critical data on removable media (external HDD; you can get a 1TB Seagate for $99).

There's only 2 that looks abnormal. The first one I posted earlier is the SSD I'm booting into. This one is the drive where the files were deleted.

Checking file system on E:
The type of the file system is NTFS.
Volume label is OS.


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)...
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x7b96ff for possibly 0x1319 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x8e5 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 2277.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x8a0a3 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa7e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 2686.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xc2c for possibly 0x8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xb7a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 2938.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x125305 for possibly 0x200 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x14bc is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 5308.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xc34 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1971 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 6513.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xe6415 for possibly 0x25 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1c0b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 7179.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x48d for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1f5c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 8028.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x711573 for possibly 0x25 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1f88 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 8072.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xf1479 for possibly 0x7e9 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x1fc2 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 8130.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x125784 for possibly 0x160 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1fd1 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 8145.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x233 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x2107 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 8455.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x235 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x21a1 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 8609.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x1468 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x225d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 8797.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x2744 for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x227b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 8827.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x77e01 for possibly 0x10 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x234f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 9039.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x6fd2df for possibly 0xc clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x242a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 9258.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x711403 for possibly 0x14 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x2926 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 10534.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x116f63 for possibly 0x1e clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x2af1 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 10993.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x98ac for possibly 0x120 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x2b47 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 11079.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x7794a for possibly 0x3e0 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x2b4b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 11083.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x72cbaa for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x2c8a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 11402.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x8094a8 for possibly 0xae6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x2c9e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 11422.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xecde3 for possibly 0x45 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x3562 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 13666.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xf1f for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3b0f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 15119.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xf22 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa47b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 42107.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x171f124 for possibly 0x9544 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0xa54d is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 42317.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xeb0cc for possibly 0x42 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xa921 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 43297.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x28e80 for possibly 0x10 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xcced is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 52461.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xe4ce8 for possibly 0x80 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xccef is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 52463.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xa023f for possibly 0x48 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xccf0 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 52464.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x7580fe for possibly 0x351 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xd3a0 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 54176.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xd03e0 for possibly 0x13 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1349e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 79006.
Attribute record of type 0x80 and instance tag 0x12 is cross linked
starting at 0x29f47 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x12
in file 0x134b7 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 79031.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x10fa68 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x134e5 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 79077.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0x250 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x134ed is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 79085.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xcf5e4 for possibly 0x1f1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x134fd is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 79101.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xba8f for possibly 0x28 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x13519 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 79129.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xcf7d8 for possibly 0x5d8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x135cb is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 79307.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xcfdb1 for possibly 0xd6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x135d3 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 79315.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x712e0a for possibly 0x1a clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x137ed is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 79853.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x19ff8b for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1383f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 79935.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xcfe87 for possibly 0x1d1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x13842 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 79938.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xd0058 for possibly 0x1fd clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x13aed is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 80621.
Attribute record of type 0xa0 and instance tag 0x3 is cross linked
starting at 0xf2a for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
in file 0x13d0a is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 81162.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xe674b for possibly 0x1b3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x13d0c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 81164.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x7b8e5b for possibly 0x5d8 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x13fe8 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 81896.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xd0257 for possibly 0x122 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x14060 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 82016.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x7ad for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x1460b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83467.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x47810 for possibly 0x13 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x14651 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83537.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x582a for possibly 0xb clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x14658 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 83544.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x15b9a for possibly 0x65 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x14895 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 84117.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x552a0 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x14a0e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 84494.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x29e8f for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x152cd is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 86733.
Attribute record of type 0x80 and instance tag 0x1 is cross linked
starting at 0x2c4bd f

Yes, both copies are from HP and have legit licenses. My SSD drive is the primary boot. What I do notice is when I load into the 2T OS and it hibernates, it restarts into the SSD when I turn the computer back on. Is the Windows Boot for the 2T HDD in limbo when I boot into the SSD when I get out of hibernation. Is it confusing the start up or restart? I just don't know how it got so corrupted when the SSD is a clean install with only a few programs. The chkdsk for C: should have been for the SSD.