Many files suddenly 0 bytes

[br0dy]

Hi guys, 

 

Currently running Windows 10 on an nVME as my boot drive, but I use my old Windows 7 larger drive just for storage of old files/media/large games/etc. I tried to watch some movies I had on that old drive and they wouldn't play. I realized they had all turned to 0kb! I did a search on everything and found many more (but not) all files also changed to 0kb. First thing I did was run a chkdsk , below are the results. Nothing really all that special and it didn't generate a FOUND folder. I read something about fastboot causing file system corruption... is this something  I disable in Win10 or through bios, or both? Also is there any possibility of recovering my files? Thanks.. chkdsk log below

 

Spoiler

 

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

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

Stage 1: Examining basic file system structure ...
  648704 file records processed.                                                         
File verification completed.
  16721 large file records processed.                                    
  0 bad file records processed.                                      

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

Stage 3: Examining security descriptors ...
Cleaning up 19 unused index entries from index $SII of file 0x9.
Cleaning up 19 unused index entries from index $SDH of file 0x9.
Cleaning up 19 unused security descriptors.
Security descriptor verification completed.
  66352 data files processed.                                            
CHKDSK is verifying Usn Journal...
  27606800 USN bytes processed.                                                            
Usn Journal verification completed.

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

Stage 5: Looking for bad, free clusters ...
  42860374 free clusters processed.                                                        
Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

 976657407 KB total disk space.
 804160008 KB in 552067 files.
    279700 KB in 66353 indexes.
         0 KB in bad sectors.
    776203 KB in use by the system.
     65536 KB occupied by the log file.
 171441496 KB available on disk.

      4096 bytes in each allocation unit.
 244164351 total allocation units on disk.
  42860374 allocation units available on disk.

Internal Info:
00 e6 09 00 ad 6f 09 00 61 35 11 00 00 00 00 00  .....o..a5......
df 46 00 00 2e 00 00 00 00 00 00 00 00 00 00 00  .F..............

 

 

[Kanna]

Is the windows 7 still on there?

[br0dy]

1 minute ago, Kanna said:

Is the windows 7 still on there?

Yes it's still on E: but I never boot from it.. I may have booted from it once as a troubleshooting step in the past.  Reading about the dual boot fast boot issue has led me to believe perhaps that was the cause of the corruption.

[Kanna]

10 hours ago, br0dy said:

Yes it's still on E: but I never boot from it.. I may have booted from it once as a troubleshooting step in the past.  Reading about the dual boot fast boot issue has led me to believe perhaps that was the cause of the corruption.

Well maybe that is the thing