Windows 10: NTFS Corruption

Discus and support NTFS Corruption in Windows 10 BSOD Crashes and Debugging to solve the problem; I rebuilt my system in December. Only components I kept from my old build were PSU, case and HDDs. On December 30 I noticed chkdsk running on boot... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Sanatorious, Jan 11, 2019.

  1. NTFS Corruption


    I rebuilt my system in December. Only components I kept from my old build were PSU, case and HDDs.

    On December 30 I noticed chkdsk running on boot into Windows 10. Event Viewer since then has had numerous Ntfs (Ntfs) Errors and Warnings. Event IDs 55, 130, 131.


    55 - A corruption was discovered in the file system structure on volume C:.

    The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.


    130 - The file system structure on volume C: has now been repaired.


    131 - The file system structure on volume C: cannot be corrected.
    Please run the chkdsk utility on the volume C:.


    I tried multiple solutions from this and other forums but never found a solution. I have 2 other attached drives but only C: (my Windows install drive) ever had chkdsk errors. So I gave up hope and just "Reset" Windows.


    To my chagrin Ntfs errors appeared. This time event ID 98 showed up in addition to the other 3.


    98 - Volume C: (\Device\HarddiskVolume4) needs to be taken offline for a short time to perform a Spot Fix. Please run "CHKDSK /SPOTFIX" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.


    Chkdsk had these results:

    Chkdsk was executed in scan mode on a volume snapshot.

    Checking file system on C:
    Volume label is Samsug SSD 850 EVO 500GB.

    Stage 1: Examining basic file system structure ...
    Found corrupt basic file structure for "<0x4,0xe00>"
    ... repaired online.
    Attribute record of type 0x80 and instance tag 0x19 is cross linked
    starting at 0x4990ba for possibly 0x1 clusters.
    Found corrupt basic file structure for "\Users\nogre\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AC\#!001\MicrosoftEdge\User\Default\DOMStore\3FPW1URN\answers.microsoft[1].xml <0x3,0x2e05>"
    ... repaired online.
    File "\Users\nogre\AppData\Local\Packages\Microsoft.OneConnect_8wekyb3d8bbwe\LocalState\DiagOutputDir\OneConnect.DiscoveryNotificationTask01_11_14_55_28_7222.txt <0x3,0xdfe>" and file "\Users\nogre\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AC\#!001\MicrosoftEdge\User\Default\DOMStore\3FPW1URN\answers.microsoft[1].xml <0x3,0x2e05>" both own logical cluster 0x4990ba
    ... queued for offline repair.

    408576 file records processed. File verification completed.

    26154 large file records processed.
    0 bad file records processed.
    Stage 2: Examining file name linkage ...

    464 reparse records processed.
    478184 index entries processed. Index verification completed.
    Found missing Index entry for file "<0x4,0xe00>" from index "\??\C:\found.002" of directory "$I30"
    ... repaired online.

    464 reparse records processed.
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.

    34806 data files processed. CHKDSK is verifying Usn Journal...
    Usn Journal verification completed.
    Windows has found problems and some were fixed online;
    the remaining problems must be fixed offline.
    Please run "chkdsk /spotfix" to fix the issues.

    488384511 KB total disk space.
    51179552 KB in 123464 files.
    81392 KB in 34807 indexes.
    503435 KB in use by the system.
    65536 KB occupied by the log file.
    436620132 KB available on disk.

    4096 bytes in each allocation unit.
    122096127 total allocation units on disk.
    109155033 allocation units available on disk.

    ----------------------------------------------------------------------


    Stage 1: Examining basic file system structure ...
    Some clusters occupied by attribute of type 0x80 and instance tag 0x19
    in file 0x2e05 is already in use.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x2E05.

    Stage 2: Examining file name linkage ...
    CHKDSK is scanning unindexed files for reconnect to their original directory.
    0 unindexed files recovered to original directory.
    CHKDSK is recovering remaining unindexed files.
    Lost and found is located at \found.002

    Stage 3: Examining security descriptors ...
    Inserting data attribute into file 2E05.



    Winninit from boot:


    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is Samsug SSD 850 EVO 500GB.


    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.

    Stage 1: Examining basic file system structure ...
    The attribute of type 0x80 and instance tag 0x3 in file 0x4d6
    has allocated length of 0x1000 instead of 0x2000.
    Deleting corrupt attribute record (0x80, "")
    from file record segment 0x4D6.
    Attribute record of type 0xa0 and instance tag 0x4 is cross linked
    starting at 0xe473c7 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0xa0 and instance tag 0x4
    in file 0x55158 is already in use.
    Deleting corrupt attribute record (0xA0, $I30)
    from file record segment 0x55158.
    405760 file records processed.
    File verification completed.
    31740 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    429 reparse records processed.
    The file reference 0x49000000000259 of index entry REE263~2.SWI of index $I30
    with parent 0x754 is not the same as 0x4a000000000259.
    Deleting index entry REE263~2.SWI in index $I30 of file 754.
    The file reference 0xf00000002e3e9 of index entry CONTAC~1.TXT of index $I30
    with parent 0x15bc6 is not the same as 0x1200000002e3e9.
    Deleting index entry CONTAC~1.TXT in index $I30 of file 15BC6.
    The file reference 0x1910000000001fb of index entry USERPR~1 of index $I30
    with parent 0x1ca81 is not the same as 0x1920000000001fb.
    Deleting index entry USERPR~1 in index $I30 of file 1CA81.
    The multi-sector header signature for VCN 0x0 of index $I30
    in file 0x55118 is incorrect.
    00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? ................
    Correcting error in index $I30 for file 55118.
    The index bitmap $I30 in file 0x55118 is incorrect.
    CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 55118.
    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 ?? ?? ?? ?? ?? ?? ?? ?? ................
    Sorting index $I30 in file 55118.
    A downpointer (VCN 0x0) was found in index $I30 in file 0x55158 but the index has no index allocation attribute.
    Removing corrupt index $I30 in file 55158.
    Recreating deleted index $I30 in file 55158.
    604618 index entries processed.
    Index verification completed.
    CHKDSK is scanning unindexed files for reconnect to their original directory.
    Recovering orphaned file USERPR~1 (1FB) into directory file 1CA81.
    There is no NTFS file name attribute in file 0x1fb.
    Correcting minor file name errors in file 1FB.
    Recovering orphaned file REE263~2.SWI (259) into directory file 754.
    There is no NTFS file name attribute in file 0x259.
    Correcting minor file name errors in file 259.
    Recovering orphaned file 953316~1.INI (877) into directory file 152D6.
    Recovering orphaned file 95331605732da8f0.temp.ini (877) into directory file 152D6.
    Recovering orphaned file GLOBAL~1.INI (1C555) into directory file 152D6.
    Recovering orphaned file global.temp.ini (1C555) into directory file 152D6.
    Recovering orphaned file MICROS~1.DLL (1D06B) into directory file 55158.
    Recovering orphaned file Microsoft.VisualStudio.QualityTools.CommandLine.ni.dll (1D06B) into directory file 55158.
    Recovering orphaned file MICROS~1.AUX (55119) into directory file 55118.
    Recovering orphaned file Microsoft.VisualStudio.QualityTools.AgentProcessManager.ni.dll.aux (55119) into directory file 55118.
    Skipping further messages about recovering orphans.
    11 unindexed files scanned.
    7 unindexed files recovered to original directory.
    CHKDSK is recovering remaining unindexed files.
    4 unindexed files recovered to lost and found.
    Lost and found is located at \found.001

    429 reparse records processed.

    Stage 3: Examining security descriptors ...
    Cleaning up 110 unused index entries from index $SII of file 0x9.
    Cleaning up 110 unused index entries from index $SDH of file 0x9.
    Cleaning up 110 unused security descriptors.
    Security descriptor verification completed.
    Inserting data attribute into file 4D6.
    99431 data files processed.
    CHKDSK is verifying Usn Journal...
    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.
    No further action is required.

    488384511 KB total disk space.
    112112900 KB in 274400 files.
    208536 KB in 99432 indexes.
    0 KB in bad sectors.
    500091 KB in use by the system.
    65536 KB occupied by the log file.
    375562984 KB available on disk.

    4096 bytes in each allocation unit.
    122096127 total allocation units on disk.
    93890746 allocation units available on disk.

    Internal Info:
    00 31 06 00 53 b4 05 00 fd cc 0b 00 00 00 00 00 .1..S...........
    18 01 00 00 95 00 00 00 00 00 00 00 00 00 00 00 ................

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

    • I even replaced my SATA cable.
    • What else can I do here? Would a clean install (instead of a Reset) make a difference?
    • SMART data on my HDD says everything is good (Samsung Magician). Is it possible my HDD is shot?
    • I ran Windows Memory Diagnostic and Prime 95 with no issues. I feel this rules out my RAM.
    • What about issues with my motherboard/chipset? How can I rule these out?

    Frustrated.

    :)
     
    Sanatorious, Jan 11, 2019
    #1

  2. Corrupted NTFS Partition Table

    I have a 160GB drive that for some reason or another has a corrupted NTFS partition table.

    The NTFS partition (about 129GB) is inaccessible, (I get an error message stating that I need to format the drive inorder to use it.) and the remaining free space is in RAW format. For some reason the normal tools will not recognize the original NTFS partition and I cannot repair/recover the partition.

    Can anyone recommend any tools that they've used to repair/recover NTFS partition information?

    Part of me is thinking of just formatting the drive and then trying to recover what I can through recovery software.

    Any idea's?
     
    ex-dohctor, Jan 11, 2019
    #2
  3. zbook Win User
    Programs not working


    In post 26 there were steps listed to fix the operating system corruption.
    Are you able to follow them?
    In post 29 was the suggested dism repair command.
     
    zbook, Jan 11, 2019
    #3
  4. Eric Ber Win User

    NTFS Corruption

    windows 10 "the first ntfs boot sector is unreadable or corrupt raw"

    Hi,

    Corrupted boot system files is one of the possible reasons why you are having an error message, the first NTFS boot sector is unreadable or corrupt, when you run the Check disk (Chkdsk) tool. Since you already tried using DiskPart and it shows that the partition
    is RAW, we suggest that you perform a clean install of Windows 10. You can follow the steps in this

    Forum Article
    that was provided by Andre Da Costa to perform a clean install or reinstall of Windows 10.

    Should you need further assistance, don't hesitate to get back to us.
     
    Eric Ber, Jan 11, 2019
    #4
Thema:

NTFS Corruption

Loading...
  1. NTFS Corruption - Similar Threads - NTFS Corruption

  2. NTFS vs XFS

    in Windows 10 Support
    NTFS vs XFS: Hi folks transferring 2 X 2TB files to NAS server (SAMBA connection) - one encoded NTFS the other XFS over a 3GB Wifi network - identical file sizes and HDD's identical connected via USB3 port. My Max Wifi speed over network is approx 850 MB/s (not Mb/s) NTFS file transfer...
  3. BSOD NTFS ntoskrnl.exe+1b1b40

    in Windows 10 BSOD Crashes and Debugging
    BSOD NTFS ntoskrnl.exe+1b1b40: Hello all I just bought a new prebuilt computer as the way it goes I went to update everything on it (drivers wise) when I first got it, everything was going swimmingly until I mistakenly tried to update the bios (My version of Z390 Phantom Gaming 4 is the 'CB' version, I...
  4. NTFS or FAT32

    in Windows 10 Installation and Upgrade
    NTFS or FAT32: Hello. I have a copy of bootable Windows 10 on my 8gb flashdrive. The ISO was probably 4.7gb or 4.8gb and was from the April Update. I decided to delete it and download the October Update to use as a copy. I used Rufus but since the update has 5gb+ of files, and Rufus...
  5. Ntfs file system stop code (infinite boot looping)

    in Windows 10 BSOD Crashes and Debugging
    Ntfs file system stop code (infinite boot looping): I downloaded windows 10 on my Vostro 220. Everything was working perfectly fine for quite some time until a day my screen froze during startup and gave me the ntfs stopcode bluescreen. The computer would boot endlessly giving the same stopcode error. The pc would then try to...
  6. Ntfs file compression - how to remove from folders

    in Windows 10 Support
    Ntfs file compression - how to remove from folders: Hi. I just noticed on my small 32GB netbook that a folder on the desktop has the blue arrows on it signifying that Windows 10 has compressed the folder and its contents on its own I guess because I don't have a lot of space left on the netbook. I found this tutorial and...
  7. exFat vs NTFS

    in Windows 10 Network and Sharing
    exFat vs NTFS: ExFat can only save files up to 4 GBs. If you save a 20 GB file using it, you end up with at least 5 files instead of 1. Which would be the case if you were using NTFS format on your device. NTFS can handle any sized file intact. I only use Fat32 or exFat format on usb...
  8. Copying files from NTFS to NTFS drive result in different size in target location

    in Windows 10 Network and Sharing
    Copying files from NTFS to NTFS drive result in different size in target location: I have an external 512GB NTFS drive (which has ~450GB used) that I normally use mounted in linux. Now, in Windows, I'm trying to copy the contents of the drive to an NTFS partition on another drive of a similar size. I'm copying folder by folder and suddenly I get an error...
  9. NTFS Rights corrupted after chkdsk some Progs run only admin

    in User Accounts and Family Safety
    NTFS Rights corrupted after chkdsk some Progs run only admin: Hi, after an chkdsk runned from a cloned backup install some ntfs rights got corrupted and now some progs run only as admin (ITunes, Android Studio). Reinstallation of the Progs does not help. Any Idea what to do? Can I prompt ntfsrights somehow in detail, by script...
  10. windows 10 purposely corrupts ntfs partition on old disk, cannot mount

    in Windows 10 Drivers and Hardware
    windows 10 purposely corrupts ntfs partition on old disk, cannot mount: i am becoming quite pissed. a Western Digital hard drive i know is perfectly good, that was used as a windows 7 disk and had an automatic upgrade done on it but became problematic... I have had to grab a spare drive, install linux and boot on that, then mount my problem WD...