New
#31
That's good.
Do one more thing, let us see a screenshot of all your discs using Crystaldiscinfo.
CrystalDiskInfo - Software - Crystal Dew World
Also, report us for any further BSOD.
It also looks good.
One more thing ... dont let the SSD to sleep. Follow Power Plan Settings - Change. At point 5 (B), you will get the way to set the Disc sleep time to Zero or Never.
Let us know how the computer is running after doing it.
Shocking. Another BSOD on Startup. Do you think this issue is hardware related or driver related (maybe i didnt install all the drivers I needed to on accident, I have no idea)? This issue is so turbulent in when it occurs and I find that to be extremely strange.
Two more BSODs are there. Both reports some sort of NTFS issue.
It would be good to see how it goes when windows is installed on the HDD and the SSD with an unknown health status is not connected.Code:BugCheck 24, {1904fb, fffff88009cf8bb8, fffff88009cf8410, fffff880012fa6c7} Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe ) Followup: MachineOwner ---------
I already had windows installed on the hdd at one point and it yielded the same issue. its too much of a hassle for me right now to put it on my hdd again. Though I have a question. I'm only really using my HDD for storage and Im assuming that it has an issue since my SSD is brand new. Even if the HDD is only for storage and the SSD is the one actually running the OS, would the HDD's issues still cause a problem even if its not the drive running windows?
Multiple problematic storage drive is possible, if you are very unlucky.
Otherwise, some other thing is throwing the issue, say a failing SATA port as an example.
But, till now I dont have anything based on which I can point it to anything other than the primary storage, that is the SSD, with an unknown health status.
If I had a crash report with the HDD as the primary storage, there would have been more room to think on, but not right now.