Question BSOD after about 30 seconds when booting ?

boysomee

Honorable
Jan 13, 2018
19
0
10,510
stop code: "system thread exception not handled" what failed: ntfs.sys
No matter what I do I cant use any fix because my pc gets this bsod.
Tried to format pc from usb, safe mode, repair pc, restore previous version, erase disk with cmd.
But the problem is that before I manage to use any of these fixes my pc already bsods and I feel like I cant do anything.
The pc does not bsod when in bios or when using windows memory diagnostic tool, but when I do anything else it bsods in 30 seconds.
 
1. Remove the boot drive from your PC and plug it in to a different PC/a Laptop(Sata SSD/HDD - HD Cage | m.2 Nvme - m.2 Cage). Then from there, backup any files you need, format it and install fresh windows on it.

2. Do a CMOS reset on your PC motherboard you can find the instructions online.

3. Insert the drive with a fresh install of windows and boot using a single RAM stick and no other drives.
 
I
1. Remove the boot drive from your PC and plug it in to a different PC/a Laptop(Sata SSD/HDD - HD Cage | m.2 Nvme - m.2 Cage). Then from there, backup any files you need, format it and install fresh windows on it.

2. Do a CMOS reset on your PC motherboard you can find the instructions online.

3. Insert the drive with a fresh install of windows and boot using a single RAM stick and no other drives.
I have a laptop but not sure I can plug a pc hdd into a laptop
 
Update.
I used dban to erase the hdd and it seems to work without getting bsod, i'll come with an update after its done
 
The ntfs.sys driver that was noted in your BSODs is the Windows high-level NTFS filesystem driver, so it's entirely possible that erasing your HDD has solved the problem. I would however recommend running a chkdsk /r command on that drive to be sure it's good.
 
The ntfs.sys driver that was noted in your BSODs is the Windows high-level NTFS filesystem driver, so it's entirely possible that erasing your HDD has solved the problem. I would however recommend running a chkdsk /r command on that drive to be sure it's good.
I will right after its finished, its almost done.