Hello.
I have a problem with my mortherboard when useing raid.
Setup:
3950x
Asus Crosshair VII Hero Bios version: 1105
Samsung 970 EVO 256GB
2x Cruial P1 1TB M.2 - They run in a Asus Hyper M.2 PCI .
So, I install the M.2, setup the Raid Arrary in bios for M.2. Chose the 2x Curial P1 1TB to be Raid 0 for max speed, as is only going to be a game Drive.
The problem is, when I install Windows 10 with the Raid drivers AMD_RAID_Driver_V9.2.0.00105 in the Windows 10 Setup, that my Samsung 970 EVO that is not even in a raid is so sloooow. but do I reinstall Windows 10 again without the Raid drivers, so are the 970 M.2 lightning fast again. But then again I cant use the 2x P1 as Windows cant see the Raid setup without the drivers.
When Raid drivers are installed, even Samsung Magician cant see drive information about the 970 M.2 Evo. But without the drivers, it can see it fine.
So I bet that the Raid drivers are the problem.
NOTE: The 970 IS NOT EVNE IN A RAID ARRAY IN BIOS even thoug this say so.
Here is a little speed test before and after raid drivers so you can see.... both fresh windows 10.
Without Raid drivers:
With Raid DRIVERS:
Is there a way to install the RAID drivers that you load in the windows 10 Setup AFTER the windows 10 is installed? mabye it will help the problem..
Really hope you can fix the problem!!
I have a problem with my mortherboard when useing raid.
Setup:
3950x
Asus Crosshair VII Hero Bios version: 1105
Samsung 970 EVO 256GB
2x Cruial P1 1TB M.2 - They run in a Asus Hyper M.2 PCI .
So, I install the M.2, setup the Raid Arrary in bios for M.2. Chose the 2x Curial P1 1TB to be Raid 0 for max speed, as is only going to be a game Drive.
The problem is, when I install Windows 10 with the Raid drivers AMD_RAID_Driver_V9.2.0.00105 in the Windows 10 Setup, that my Samsung 970 EVO that is not even in a raid is so sloooow. but do I reinstall Windows 10 again without the Raid drivers, so are the 970 M.2 lightning fast again. But then again I cant use the 2x P1 as Windows cant see the Raid setup without the drivers.
When Raid drivers are installed, even Samsung Magician cant see drive information about the 970 M.2 Evo. But without the drivers, it can see it fine.
So I bet that the Raid drivers are the problem.
NOTE: The 970 IS NOT EVNE IN A RAID ARRAY IN BIOS even thoug this say so.
Here is a little speed test before and after raid drivers so you can see.... both fresh windows 10.
Without Raid drivers:
With Raid DRIVERS:
Is there a way to install the RAID drivers that you load in the windows 10 Setup AFTER the windows 10 is installed? mabye it will help the problem..
Really hope you can fix the problem!!
Hello.
I now tried DISABLE Nvme Raid and not installing AMD Drivers.
And now does my 970 EVO run perfekt again, and builed a Raid 0 op in WIndows 10 in instead, it runs 1000x better. Look before and after.
Cruial P1 1TB Raid 0 Setup:
With Nvme Enable in Bios - Arry lavet/AMD Drivers:
Crystal Mark:
Atto:
Nvme Disable in Bios / Ren Windows 10 Raid 0:
Crystal Disk mark:
Atto:
But please AMD/Asus, fix this, it cant be right I need to make a Raid 0 in Windows 10 that is WAY better than your own drivers...
I now tried DISABLE Nvme Raid and not installing AMD Drivers.
And now does my 970 EVO run perfekt again, and builed a Raid 0 op in WIndows 10 in instead, it runs 1000x better. Look before and after.
Cruial P1 1TB Raid 0 Setup:
With Nvme Enable in Bios - Arry lavet/AMD Drivers:
Crystal Mark:
Atto:
Nvme Disable in Bios / Ren Windows 10 Raid 0:
Crystal Disk mark:
Atto:
But please AMD/Asus, fix this, it cant be right I need to make a Raid 0 in Windows 10 that is WAY better than your own drivers...
Run the whole test on crystal diskmark
Sequential speeds of large files is the least of your worries and means squat in actual performance. Its the bottom number that matters. Q1T1 shows what speed 90% of your responsiveness is related to. Loading all those tiny 4kb dll files. If that number sucks then the large sequential number is just fun to look at and thats where it ends.
Under 100 is not preferable.
Under 50 is horrendous.
Raid only adds latency making that worse.
Also once you raid it up you can uuninstall the Samsung software and NVME drivers as it does nothing. Samsungs software or drivers cannot see past a raid controller. Been that way since inception.
Sequential speeds of large files is the least of your worries and means squat in actual performance. Its the bottom number that matters. Q1T1 shows what speed 90% of your responsiveness is related to. Loading all those tiny 4kb dll files. If that number sucks then the large sequential number is just fun to look at and thats where it ends.
Under 100 is not preferable.
Under 50 is horrendous.
Raid only adds latency making that worse.
Also once you raid it up you can uuninstall the Samsung software and NVME drivers as it does nothing. Samsungs software or drivers cannot see past a raid controller. Been that way since inception.
