New
#1
BSoD at random times, error 0x000000C4 (STOP): Ntfs.sys
Hello,
I have been encountering some BSoD trouble in the recent past.
In the most recent crashed, the Ntfs.sys filename appeared on the BSoD (it was previously some other one).
Following, the BSoD Analysis tutorial, I grabbed the following information during the inspection of the most recent DMP file:
- The initial 'Probably caused by' source was the ntoskrnl.exe binary
- No analysis was available through '!analysis -v'
- Having activated the 'Driver verifier', I restarted normally. The login screen appeared, but when I logged in, another BSoD appeared, but the dump didn't work (stuck, I rebooted forcefully). Still the Ntfs.sys file
- I restarted again in normal mode, letting the system finish to work on the HDD (the little light stopped flashing intensively). When I logged, BSoD as before. Still the Ntfs.sys file
- I restarted in Safe Mode, then I could log in without problem. No new DMP file existed in the Minidump directory, proof that the dump indeed didn't work at all.
- I downloaded, burned and rebooted on the MemTest86+ software, making only 1 pass on the whole RAM, without error. I stopped there because I already have enough suspicions about some other hardware component...
- Having rebooted under normal mode, I am now running Prime95, if by any chance that's useful...
Following what I encountered, I have strong evidence against my filesystem and maybe my HDD:
- The system's filesystem driver crashes (Ntfs.sys)
- When the verifier has been activated the system is unable to write to the disk (that's in coherence with a filesystem's crash: no access to it)
- Filesystem is one of the most immediate thing used, the crash at login time probably means that an early faulty action has been done
I am still unsure about what precisely caused the error. It doesn't appear at boot time, not even at logon but at login. The OS has already made plenty of accesses and loaded a lot of stuff. It would mean something happens/is loaded in user space to trigger the error.
Is the filesystem or one of the HDD the source of the problem? Does a format would be useless/usefull? That's kinda huge thing to do, I do not want to waste time if it doesn't change anything.
In case this comes from the filesystem, here is some new information:
I defragmented my whole disks a few days ago, and I ran a 'chkdsk /f' on them after the first following Ntfs.sys BSoD. It seems some little space were in error, but I never launched that command before.
Would it be more of some faulty system's HDD (or the other one's) segment? Or kind of corrupted files on it?
I'd take any help and carefully weight advice :)