F5F Stay Refreshed Hardware Desktop Exception in System Thread not addressed NTFS.SYS

Exception in System Thread not addressed NTFS.SYS

Exception in System Thread not addressed NTFS.SYS

C
CatandDani
Member
58
07-10-2022, 09:09 PM
#1
Windows seems to be targeting me for being a Linux user. I've tried numerous solutions, explored all the discussions online, but nothing helps. I'm seeking guidance on what to do next. The main issue is loading Windows 11, Hiren's Boost CD, or Windows PE without issues. On both installations, Linux functions perfectly. Accessing recovery causes BSODs, and the Windows disk scan fails to load properly. I'm trying to fix the BSOD by restarting and restarting repeatedly, but it just loops. The system details are: MSI B550 MPG Gaming Plus CPU, Ryzen 5800 X3D GPU, 8GB RAM, Samsung 980 Pro drives (unused since purchased), and I'm using Endeavour OS with MBR. I've also tried various recovery methods and troubleshooting steps.

Some attempts included:

- Unplugging the Windows SSD
- Disconnecting both SSDs that use UEFI, including Windows SSD
- Loading Windows PE ISO
- Pressing any F key during BSOD attempts for recovery or safe mode
- Installing Windows in CSM mode instead of UEFI
- Removing AMD chipset drivers and Comodo Firewall (after fixing a kernel security BSOD)
- Disabling memory XMP profiles
- Clearing BIOS settings, updating BIOS to latest version, and turning off Memory XMP
- Using a different SSD (removed the Windows 11 one)

Despite these efforts, I still face the same problems. Linux works without issues, but I can't share crash dumps since Windows won't load.

Off topic: The Samsung 980 Pro in M2_2 was previously in M2_1, but it couldn't reach Gen 4 speeds, which I thought was due to the NVMe drive. I bought a second 980 Pro for a discount, yet it still only gets Gen 3 speeds. The BIOS set PCI_E1 to Gen 4, which is intended for video cards, but the 980 Pro doesn't exceed Gen 3 speeds. What should I do next?
C
CatandDani
07-10-2022, 09:09 PM #1

Windows seems to be targeting me for being a Linux user. I've tried numerous solutions, explored all the discussions online, but nothing helps. I'm seeking guidance on what to do next. The main issue is loading Windows 11, Hiren's Boost CD, or Windows PE without issues. On both installations, Linux functions perfectly. Accessing recovery causes BSODs, and the Windows disk scan fails to load properly. I'm trying to fix the BSOD by restarting and restarting repeatedly, but it just loops. The system details are: MSI B550 MPG Gaming Plus CPU, Ryzen 5800 X3D GPU, 8GB RAM, Samsung 980 Pro drives (unused since purchased), and I'm using Endeavour OS with MBR. I've also tried various recovery methods and troubleshooting steps.

Some attempts included:

- Unplugging the Windows SSD
- Disconnecting both SSDs that use UEFI, including Windows SSD
- Loading Windows PE ISO
- Pressing any F key during BSOD attempts for recovery or safe mode
- Installing Windows in CSM mode instead of UEFI
- Removing AMD chipset drivers and Comodo Firewall (after fixing a kernel security BSOD)
- Disabling memory XMP profiles
- Clearing BIOS settings, updating BIOS to latest version, and turning off Memory XMP
- Using a different SSD (removed the Windows 11 one)

Despite these efforts, I still face the same problems. Linux works without issues, but I can't share crash dumps since Windows won't load.

Off topic: The Samsung 980 Pro in M2_2 was previously in M2_1, but it couldn't reach Gen 4 speeds, which I thought was due to the NVMe drive. I bought a second 980 Pro for a discount, yet it still only gets Gen 3 speeds. The BIOS set PCI_E1 to Gen 4, which is intended for video cards, but the 980 Pro doesn't exceed Gen 3 speeds. What should I do next?

P
Pyrotecha
Junior Member
13
07-11-2022, 03:33 AM
#2
The problem has been resolved temporarily. The cause was a stuck mechanical drive that blocked data writing. After isolating the drive, the Kernel Thread Exception Not Handled disappeared.
P
Pyrotecha
07-11-2022, 03:33 AM #2

The problem has been resolved temporarily. The cause was a stuck mechanical drive that blocked data writing. After isolating the drive, the Kernel Thread Exception Not Handled disappeared.