Stopped VM from raidport/0 after NVMe reset via StornVME during gaming, leads to crashes until PC restarts.
Stopped VM from raidport/0 after NVMe reset via StornVME during gaming, leads to crashes until PC restarts.
Hello, I’m facing a really annoying problem with my PC. Recently, I installed a new Samsung 990 Pro 2TB NVMe drive and started playing games on it. In the last few months, I’ve encountered frequent crashes. When trying to launch games on Steam, they won’t open, and even after accessing the game files, Windows displays an error saying the path doesn’t exist. Interestingly, the drive is visible through normal methods, but it seems locked until I restart the computer, which then resolves the issue temporarily. Occasionally, I can see more details in Event Viewer, but the same errors keep appearing—like a reset event and controller errors. Sometimes CPU usage hits 100%. This only happens when playing games on the NVMe drive (such as GTA, Helldivers, Fortnite). I’ve checked online and found this issue strange, but no solution seems to work for me yet. I’ve tried updating drivers, ensuring sufficient power, running Samsung Magician, changing RAM settings, formatting the device, reseating it, and even sending it in for an RMA. Nothing has helped. This situation is becoming increasingly frustrating, and I’m starting to think there might be a hardware problem or a deeper software conflict. My system runs an I7-9700k processor with ASUS components, and I have 16GB of RAM, 2666MB of memory, and the graphics card is GTX 3080 FE. If anyone has any insights or fixes for this, it would be greatly appreciated.
Changing from RAID to AHCI in BIOS could be beneficial. Configure Windows to start in Safe Mode via msconfig, enter Safe Mode just once after the adjustment, turn off Safe Mode again, and then restart the system.
This problem appears to stem from several factors. I initiated an RMA on the drive, they confirmed it was in good condition but later sent a replacement instead of the original. While waiting, I updated my BIOS settings—including one highlighting improved Windows 11 support—and made some adjustments, though I’m unsure if these resolved anything. Once I returned the drive and reinstalled it carefully, the issue has been resolved for over a week. I’m fairly confident the BIOS update fixed the matter, at least for me.