NTFS_FILE_SYSTEM Error, can’t boot

[gmrush04]

My computer was experiencing sever stability issues until it wouldnt boot. I fixed this by reinstalling Win10 from a USB and this worked for about an hour until the system locked up. Not even an error screen. Upon restart the system throws up a NTFS_FILE_SYSTEM error. Attempting to reinstall does not work either. Also cannot access advanced troubleshooting options. Is the drive dead? or is my whole system gone? Please help.

Thanks.

 

[Colif]

NTFS = New Technology File System. ITs the format used on the hard drive to store your information.

Does hard drive show up in the BIOS? It is likely its just the hdd at this stage.

 

[gmrush04]

Yes, the drive is recognized in the BIOS

I just might buy a smaller drive and take the corrupted one out.

 

[Colif]

try running chkdsk on it, might help

boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command prompt
type chkdsk C: /f and press enter
if its a hdd you can type chkdsk C: /f /r and press enter

this will also tell us if the hdd is actual cause though if its just after a fresh install, it shouldn't be the os yet. Likely hardware.

 

[gmrush04]

Alright, I picked up a 500GB HDD from SeaGate, and installed Windows 10 on the new one. The system can now boot into Windows perfectly fine. The old boot drive is now D:, the new one is C:, and the storage one is still E:. However, if the E: drive is plugged into the system, the Windows will not boot, and instead BSODs with the same NTFS_FILE_SYSTEM error. If both the C: and the D: drives are plugged in, the system works fine. The problem appears to have jumped to my storage drive. Any ideas?

Also my memory is bad, constant errors from my current sticks. Going to buy some new ones.

 

[Colif]

File system obviously includes the ram as PC cannot do anything without ram. Corrupted ram can cause random errors but this is same error twice.

One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted hard drive (SATA/IDE) drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

MS LInk

lets see if replacing ram fixes it, we can also look at the memory.dmp file since its a fresh install, it shouldn't be that big yet (can be several tb)

Can you go to C:/windows folder
set view to show hidden files and folders
copy the memory.dmp file to another folder
upload the copy from the other folder to a file sharing site like Onedrive or Google Drive or Dropbox, to name a few, and share a link to file here and I will ask someone to convert it for me.

I suspect its hardware as the unlikelihood of 2 installs on 2 hdd getting same error are slim.

Do you have the latest BIOS?

 

[gmrush04]

RAM is showing up tommorrow, and that should fix the stability issues. As for the HDD, I enabled hot-swapping on the SATA connection that it uses, and if I plug in the SATA connector to the HDD while on the desktop, Windows will recognize it correctly as the E: drive, but then after about half a second, the NTFS_FILE_SYSTEM occurs again, again the BSOD is shown.

 

[Colif]

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

might as well look and see what windows is seeing

 

[gmrush04]

MEMORY.dmp, 1.6 GB: https://mega.nz/#!ANMBAZoY!KaPGEuIfzdGAfzqPYqkAi7vAUvsmHKHPRE2IicMHgOY
Installed new RAM, system stable now.

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/V5Gj.html

File: MEMORY.DMP (Apr 18 2018 - 21:29:39)
BugCheck: [SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (C1)]
Probably caused by: memory_corruption (Process: MsMpEng.exe)
Uptime: 0 Day(s), 0 Hour(s), 32 Min(s), and 11 Sec(s)

Motherboard: https://www.gigabyte.com/us/Motherboard/GA-B250M-DS3H-rev-10#kf
You are using BIOS v7. The latest BIOS available for your system is v9e. Note: Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

Colif, there's many errors. I didn't see them before uploading.

I can't help you with this. Wait for additional replies. Good luck.

 

[gmrush04]

Haven't crashed since I installed the new RAM. E: drive is still throwing up NTFS_FILE_SYSTEM when it's plugged in. Don't think the hard drive issue is related to the RAM corruption, but at least the system is stable. At this point I'm just trying to get the drive back. There was 1.5 TB of data on it, but if it needs to be wiped in order for it to be back working that is fine.

 

[Colif]

Strange dump doesn't include that error you keep getting but another one instead. The Special pool error is caused by Defender of all things.

have you got another PC you can plug E into? It could be the hdd was the problem all along and it wasn't C? (since we haven't got any dumps for the NTFS file system errors, it has been guessing).

initial set up
C & D

changes
New hdd becomes C
C replaced and became D
D became E

MY only guess if the drive works fine in another PC is its something to do with sockets used on motherboard for the HDD. As the NTFS error points at failing or corrupt hdd.

 

[gmrush04]

Don't have access to another PC unfortunately. Replace ntfs.sys but that didn't do anything. Here is a minidump after a NTFS_FILE_SYSTEM BSoD: https://mega.nz/#!0J12WDDR!YqZ1xFXuaYQA6m1XfvQZ9R9WTYkronxZU6jfLoy7TKE

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/wg89.html

File: 042318-40437-01.dmp (Apr 23 2018 - 15:28:38)
BugCheck: [NTFS_FILE_SYSTEM (24)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 6 Hour(s), 37 Min(s), and 41 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

 

[gmrush04]

Update: Updated BIOS to latest version. Issue persists.

 

[Colif]

Whats Acronis on there for? can you update it as its all from 2014-15, and could be the cause of the NTFS errors. Anything prior to JUly 2015 isn't a windows 10 driver

Sep 04 2014 file_tracker.sys File Tracker Minifilter driver (Acronis International GmbH)
Nov 11 2014 fltsrv.sys Acronis Storage Filter Management driver http://www.acronis.com/
Nov 12 2014 snapman.sys Acronis Snapshots Manager from Acronis Snapshots Manager or Seagate DiscWizard
Jul 17 2015 tib.sys Acronis Backup Archive (TIB) Explorer
Jul 17 2015 tib_mounter.sys Acronis Backup Archive Mounter driver (Acronis International GmbH)

replacing file wouldn't help, its a dangerous idea (especially if you download a new one from a web site)

What make is the 3rd hdd its now having problems with? Did we ever run hdtune free version on it and check the health tab

 

[gmrush04]

Didn't even know the drive had Acronis on it. The HDD is a SeaGate FireCuda Part Number: 2DV164-300. I have never run HDTUNE on it.

Going to try SeaTools for DOS real quick.