Should I just run Memtest86 to make sure? It's gonna take a few hours and we will be set....just to know if the Ram is actually the issue try only running 1 stick, no xmp and do a stress test
I dont have any important data on this computer.I still think you should backup your data and do a fresh windows installation
The FireCuda 540 is a PCIe 5.0 drive. Maybe thats the issue? In theory, it should be downwards compatible.Now I need to understand what happened to the M2 drive and why it's still not showing up.
What happen is that I was trying to primarily install Win 11 on it with all my softwares but it would fail everytime I would try.The FireCuda 540 is a PCIe 5.0 drive. Maybe thats the issue? In theory, it should be downwards compatible.
Is it being displayed in the BIOS, or is it just not bootable?
If its not even appearing in the bios, I'd suggest testing the Firecuda in another PC (one with PCIe 4.0, too), and if that fails .. well. Then it might be toast = broken from the begin. That means time for RMA.
cu, w0lf.
What happen is that I was trying to primarily install Win 11 on it with all my softwares but it would fail everytime I would try.
So I used an old 2'5'' SSD instead and its obviously working on that one.
Have you tried using another m2 drive yet? Because using a 2.5" SSD means its using a different connection (SATA), and therefore, is not the same.
I'd just buy a cheap but solid 1 TB PCIe 3.0 or 4.0 drive, and if that one doesnt give you any troubles, i'd stick to that.
Obv. look at specs and esp. tests / reviews, but for a literal test drive, it should be not the fastest or "best" but more like a robust and uncomplicated option. Geizhals shows eg. the TeamGroup MP33 (Pro) (PCIe 3.0) or the Kioxia Exceria Plus G3 (PCIe 4), all below or around 60 Euro.
After that, you can still try to get the FireCuda running in the second m2 slot. Potential options to try out:
In terms of "writes 2 GB and then stops working" - did you format it with the correct file system? That reminds me of an issue with FAT32 / NTFS or so. Could also be wrong partition type, eg. MBR vs. GPT. And also, maybe Fast Boot is part of the troubles (should be disabled in the BIOS).
As a final option, you could also write to the Asrock support - they list the FireCuda 540 in their official supported storage document, so maybe there are known issues or circumstances, that may lead to not being able to use the drive.
And if all those options should fail, I'd either RMA it, or sell it (before that, testing it for failure in a system that isnt giving any issues).
cu, w0lf.
Ok so I decided to install Seatools. A diagnistic tools for Seagate HDD and SDD's.Have you tried using another m2 drive yet? Because using a 2.5" SSD means its using a different connection (SATA), and therefore, is not the same.
I'd just buy a cheap but solid 1 TB PCIe 3.0 or 4.0 drive, and if that one doesnt give you any troubles, i'd stick to that.
Obv. look at specs and esp. tests / reviews, but for a literal test drive, it should be not the fastest or "best" but more like a robust and uncomplicated option. Geizhals shows eg. the TeamGroup MP33 (Pro) (PCIe 3.0) or the Kioxia Exceria Plus G3 (PCIe 4), all below or around 60 Euro.
After that, you can still try to get the FireCuda running in the second m2 slot. Potential options to try out:
In terms of "writes 2 GB and then stops working" - did you format it with the correct file system? That reminds me of an issue with FAT32 / NTFS or so. Could also be wrong partition type, eg. MBR vs. GPT. And also, maybe Fast Boot is part of the troubles (should be disabled in the BIOS).
As a final option, you could also write to the Asrock support - they list the FireCuda 540 in their official supported storage document, so maybe there are known issues or circumstances, that may lead to not being able to use the drive.
And if all those options should fail, I'd either RMA it, or sell it (before that, testing it for failure in a system that isnt giving any issues).
cu, w0lf.