Discussion New PC running EXTREMLY Slow. Please help !!

Gidilo

Caliper Novice
Nov 23, 2022
33
11
just to know if the Ram is actually the issue try only running 1 stick, no xmp and do a stress test
 

martel80

Caliper Novice
Original poster
Sep 13, 2024
29
11
Oh, I just got a Windows update issue with a code when trying to install KB5043178.

0x800736cc.


Microsoft refer to it as a Windows System files issue on my computer.

I think we got something
 

martel80

Caliper Novice
Original poster
Sep 13, 2024
29
11
I just ran a scannow and it found multiple issues.

I was now able to download the update.

The computer is a bit better now. There<s still some sort of lag but I dont know if its the normal Win 11 animation lag.

I<m not used to that coming from Win 10.
 

martel80

Caliper Novice
Original poster
Sep 13, 2024
29
11
Ok, I reinstalled everything and ran Geekbench 6.


Single core score higher the the highest in the chart.

Multi core score about equal to a 7945HX or a 14600K.

Core temp now read 105W peak. That is great improvement.

I think I'm back in business here.

Thank you so much for your support. I really appreciate.

Now I need to understand what happened to the M2 drive and why it's still not showing up.
 

hrh_ginsterbusch

King of Cable Management
Silver Supporter
Nov 18, 2021
714
279
wp-devil.com
Now I need to understand what happened to the M2 drive and why it's still not showing up.
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.
 

martel80

Caliper Novice
Original poster
Sep 13, 2024
29
11
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.

Now I've installed it as an extra drive and everytime I would write or read something bigger then 2 GB on it, it would fail and disapear.

So then I would reboot and in the bios it would not show up.

So I would reboot again and if I unplug and replug the Power Supply then it would show up again.

I would try to transfer a big folder on it for quick access and it would fail again and disappear.

And so on and so forth.

Funny thing is that I did install it on my old laptop and it work flawlessly so I don't understand what the issue is.

Now I got it mounted in the M2_1 slot PCIe Gen 5( the 128 gbps one ) and as I said, it appear and disappear randomly.

When I first started to try to install Windows 11 on it, It was sloted in the M2_2 slot PCIe Gen 4 ( 64gbps one ) .

So both M2 slots are acting up the same way in the DeskMini x600.

But on my old Gigabyte Aero 15 OLED ( 11800H ) it work flawlessly. No issue at all.

So now I have a brand new PCIe Gen 5 M2 Blazing (FireCuda 540 2TB) mounted that I cannot use for anything as it fails randomly.

I'm wondering if the issue is not the BIOS or the Motherboard itself....

Is there a software that could help me pin point the issue ?
 

hrh_ginsterbusch

King of Cable Management
Silver Supporter
Nov 18, 2021
714
279
wp-devil.com
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.
 
Last edited:

martel80

Caliper Novice
Original poster
Sep 13, 2024
29
11
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.

Thanks for the ideas.

I'll send an email to AsRock. Maybe they can guide me.

Also, Fast Boot was always enabled so I'll try to disable it right now and transfer a big folder and see how it goes.

Will report back.

Best,
 
  • Like
Reactions: hrh_ginsterbusch

martel80

Caliper Novice
Original poster
Sep 13, 2024
29
11
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.

It reported that the S.M.A.R.T. had BAD sectors and therefor was unstable.

So I started a return process with the 3rd party Amazon seller but I'm not sure what will come out of it.

Anyways, the M2 was defective so that's why it was not working properly.

Time to move on.
 
  • Like
Reactions: hrh_ginsterbusch