Solved BSOD random 0xF4, no dumps; stuck on "initializing disk"

[axe0]

RAID & AHCI configuration could cause a lot of problems, including BSODs as you may read. I cannot confirm nor deny that it may have anything to do with the issue, but it is a possibility.

 

[luckycharms]

I just wanted to get back with what finally solved this vexing issue. I tried reinstalling the entire OS, and went with Windows 10 to see if there was some sort of NVMe support issue with Windows 7. But, the same BSOD occurred with Win 10.

After trying some other things, I did two things that actually, finally, gratefully, fixed the issue.

First, I switched from Intel RAID to AHCI. I had to boot into windows safe mode with AHCI enabled first, and then I could boot regularly into AHCI. That fixed a number of problems. Notably, apps such as CrystalDiskInfo could not see the NVMe drive when Intel RAID was enabled. I'm not sure if that's normal or not... but once booting into AHCI, CrystalDiskInfo could see the NVMe drive just fine. After I did this, I didn't get a BSOD at all, for a day or two.

After running like that for a day or two, I also replaced the 1TB Toshiba NVMe drive with a 1TB SK Hynix NVMe drive (having cloned from one to the other first).

I have now been running for over a week with AHCI and the SK Hynix drive, and no BSODs. I'm quite sure the issue is solved now. Whether the root of it was Intel RAID (which I suspect), or the drive itself, I can't be sure. But I did want to report back in case anyone else was having similar issues!

Thanks again for your attention, axe0.