Blue Screen issues with your NTFS file system
Blue Screen issues with your NTFS file system
I have been struggling with a really annoying problem on an old computer that keeps giving me blue screens. Here are the details: Intel i5-10400F MSI B460M PRO-VDH TEAMGROUP T-Force Vulcan Z DDR4 16GB SK Hynix Gold S31 1TB SSD EVGA 600w PSU EVGA GTX 970. After switching from Windows 10 to Windows 11 recently, I keep getting blue screens while playing a game called Palworld. Since the upgrade, the PC won't start up at all or will not get into recovery mode. No matter what steps I take, it keeps hitting a Blue Screen with the error being NTFS FILE SYSTEM. I can enter BIOS settings fine, but even when I try to boot from a Windows 11 USB stick, the blue screen happens again. I tried turning off all other drives in the BIOS so that it only boots from the USB, but the problem is still happening. I am thinking the issue might be with my hard drive or SSD, but because disabling them doesn't stop the error, I don't know for sure what is broken. What else should I check? The user wants to replace whatever isn't working, but right now I'm not entirely sure which part is failing... Summary of what I've tried: Disable/enable secure boot Disable/enable TPM Enable XMP Tried to boot into safe mode (doesn't work) Boot from usb to reinstall windows 11 (doesn't work, still blue screens after a short while loading). My gut says to replace the SSD as a ntfs file system error is likely related to the disk, but I'm really not sure. Any thoughts or suggestions?
You probably won't see the same Blue Screen of Death (BSOD) when using a USB drive that doesn't seem to be booting off it, but rather your normal hard drive. Is this BIOS setting turned on or is there an option in the menu? If you don't find one in the manual, you might need to turn off boot override to make sure your PC uses the USB instead of the hard drive. Disabling secure boot can also help with that. I tried running the installer on my computer without using the SSD and just wanted to see if you get the same error message or not. Sure, it won't actually work but it is a test.
The problem seems to be that the files on your hard drive are damaged. You need to get a USB-to-SATA adapter. Plug the drive into a computer that works well and use the USB sata cable to connect them. Then run CHKDSK to check the drive, or clean it with DiskPart Clean.
Plug in your USB stick and try starting up your Linux distribution from there. Usually, most of these systems just work without needing anything else installed. If the first USB slot doesn't work, check each port until you find a working one.
Linux does not come with built-in support for Windows NTFS files.
That doesn't make sense right now. We need to figure out if one of his hard drives is making him unable to start, or if something else is wrong with the computer, or maybe it's just a problem with the operating system. If he can't boot up in Linux, then the basic parts are definitely broken. The fact that he can't even find his drives doesn't matter here because if Linux won't turn on at all, we know for sure that there is a hardware problem. But if Linux turns on and runs fine, then I should try putting him into Windows by removing all of his hard drives from the machine and running the Windows setup media again.
The problem is NTFS file system errors. If your Linux computer cannot read an NTFS drive, then it won't find out if there are any bad files on that disk.
I don't think we have proved it yet. It looks like our best idea so far.
I get that, but one thing I've learned is that error messages aren't always true. Sometimes an error in one spot might only show up later when something looks different. My idea was to check if the main hardware works by running Linux. If that works fine, then take out all drives and try booting just the Windows USB. If it boots successfully, I'll know for sure that a drive is causing the problem.