Print Page | Close Window

Samsung 950 pro m.2 raid 0 sleep problem

Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=2459
Printed Date: 08 Aug 2025 at 11:47am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com


Topic: Samsung 950 pro m.2 raid 0 sleep problem
Posted By: nme
Subject: Samsung 950 pro m.2 raid 0 sleep problem
Date Posted: 16 Apr 2016 at 9:38am
Hey guys and gals! I have an interesting dilemma that I have not been able to figure out. I have a pretty interesting system with an even more interesting problem. Here is what happens:

benchmarks:
http://imgur.com/a/VEXVd" rel="nofollow - http://imgur.com/a/VEXVd

After a clean boot I run ATTO disk benchmark or samsung magician on my samsung 950 pro 512 GB m.2 raid and get about 3 GB read and 3 GB write speeds. Great you say! Here is the problem... If i put the computer to sleep, and wake it back up then run the test I get about half of that speed at 1.5-1.6 GB read and write. Its like clockwork. Nothing to do with heat throttling because i can repeat this and it happens every time. There are also 4x 120mm fans on the side of my case lol.

It seems to me that there may be some sort of power setting or sleep setting that limits throughput. I haven't found a bios setting that makes sense though. All of the power settings i can think of (besides speedstep) are disabled. Also not sure if there is a setting for the type of sleep in this bios (s3, s4, s5 or whatever they are)

 Here is a list of things i have done:

-Disconnected all my other hard drives and CD drives leaving the raid as my only storage
-disconnected my only other pci device (7.1 sound card)
-disabled  hybrid sleep in windows power settings (computer wont actually wake after doing this, so it just makes it worse)
-updated bios to newly released 3.0 from 4/13/16. I believe i was at 2.6 or 2.8 before.
-disabled write caching buffer

Here are my specs

Windows 10 Pro 64-bit
Intel Core i7 6700k stock @ 4.00GHz 17 °C (im in a basement.. cpu has corsair h100i water cooler)
RAM 32.0GB DDR4 3200
ASRock Z170 Extreme7+ 26 °C
NVIDIA GeForce GTX 970 (Gigabyte) 25 °C
2x samsung 950 pro nvme m.2 drives in intel raid 0
uefi install, csm disabled
intel rst version 14.8.0.1042
1x 3 tb samsung hdd 
1x 3 tb wd greed backup drive
1x blu ray
1x dvd burner
asus xonar 7.1 sound card (pcie 1x)
12 total fans (4x120 side, 1x140 front, 1x120back, 1x120mm psu, 2x120mm on cpu radiator, 3 on video card)
seasonic 750 watt gold psu
corsair 600t white case

I use the sleep mode regularly and had no problems with my old setup (i7 3770k sata raid 940 pros).

any questions, comments or helpful feedback? I also take criticisms, sarcasm, and negativity!

Hope you guys can help!

Thanks
Mike



Replies:
Posted By: Grant Rogers
Date Posted: 10 Jul 2016 at 9:35pm
Hi Mike,

I have just stumbled across this message in search for an answer and have exactly the same problem as you and a similar system set-up.

My specifications:
Windows 10 Pro V1511
Intel Core i7 6700K stock @ 4.00Ghz H100i GTX
64GB RAM
ASRock Z170 OC Formula
2x Samsung 950 Pro NVME m.2 Intel Raid 0
CSM disabled
2x 6TB Hdds
1x Bluray writer
1600 watt PSU
Corsair 500R case

Fresh boot:
http://imgur.com/xc1sP3r" rel="nofollow - http://imgur.com/xc1sP3r

After sleep:
http://imgur.com/H4RCF9N" rel="nofollow - http://imgur.com/H4RCF9N

I have a strong suspicion this is being cased by the intel raid drivers.  They just don't seem to handle sleep properly.  I have also noticed in the event viewer I am getting event ID 129 storahci (Reset to device, \Device\RaidPort0, was issued.) when waking up from sleep.  I am going to report this to Intel and ASRock although I am not holding my breath.


Posted By: parsec
Date Posted: 10 Jul 2016 at 11:11pm
A curious but obvious issue, I can't say I ever checked the performance of two 950 Pro's in RAID 0 after waking from Sleep when I had that setup a while ago.

I couldn't stand the failure of the RAID 0 array if the UEFI/BIOS was cleared, or the same failure after a UEFI update. Which is why I stopped using RAID 0 with these SSDs.

I don't know what is going on after waking from Sleep, but one thing I want you both to check is the following... Hmm, just remembered the Magician software does not like RAID mode, and I can't remember if this will work when the SSDs are in a RAID 0 array. I'll mention it anyway... Confused

On the main, Disk Drive screen of the Magician software, with one of the 950 Pro's selected (if possible) in the System Information area, the PCIe Slot information, looks like this with a single 950 Pro:



We want to confirm the Link Speed Current, and the Link Width Current, after waking from Sleep. 10Gbps is DMI3/PCIe 3.0 speed, and x4 is the lane connections, as you know.

If the Link Speed or Link Width changes, we then have a hint about what is happening.

I had a thought, put my Z170 Exteme7+ PC, with my single 256GB 950 Pro into Sleep mode, wake it, and see what I get. This is the result:



That's what it should be, so no problem after waking from Sleep on my system. You'll have to trust me on this, I would have posted the result regardless of what it was. I'm using RAID mode, but this is a single drive, no RAID array.

Since I imagine you both are using the M.2 slots, and Z170 systems use the chipset DMI3 lanes for the M.2 slots, you cannot try the UEFI option available for the PCIe slots. That is, setting the PCIe slots to Gen3 (PCIe 3.0) in Chipset Configuration. Z97 and X99 boards use the CPU's PCIe 3.0 lanes for the M.2 slots.

Originally posted by Grant Rogers Grant Rogers wrote:

Hi Mike,

I have just stumbled across this message in search for an answer and have exactly the same problem as you and a similar system set-up.
.
.
.
I have a strong suspicion this is being cased by the intel raid drivers.  They just don't seem to handle sleep properly.  I have also noticed in the event viewer I am getting event ID 129 storahci (Reset to device, \Device\RaidPort0, was issued.) when waking up from sleep.  I am going to report this to Intel and ASRock although I am not holding my breath.


That's an interesting event, but something is strange about it. storahci is the native Windows 10 AHCI driver. The Intel IRST driver is iaStorA.sys, which you can confirm in the Device Manager entry, under Storage Controllers.

Regardless, the reference to \Device\RaidPort0 seems to be related to this situation. You should check the Event Log for anything about iaStorA.sys, if you manually installed the IRST 14.6 or 14.8 version driver, which I believe you must have done.

We also have the Samsung NVMe driver to potentially add to the list of reasons for this issue. A question that I am unsure about is, when using these SSDs in RAID 0, is the Intel IRST driver in complete control, and the only one that is used? The Samsung NVMe driver not being used at all?

Or, is the Windows 10 native NVMe driver, whose name I cannot recall right now.

OHH great, more Windows Sleep issues... why am I one of the few that does not have any... Confused

I'll be thinking about this, and watching this thread.



-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: parsec
Date Posted: 11 Jul 2016 at 11:33am
If you are feeling adventurous, you can try one of the Intel IRST beta drivers that this website somehow manages to get. I've used other non-officially released versions of IRST from this website, and they were fine.

http://www.station-drivers.com/index.php?option=com_remository&Itemid=353&func=select&id=103&lang=en" rel="nofollow - http://www.station-drivers.com/index.php?option=com_remository&Itemid=353&func=select&id=103&lang=en

Notice they have IRST version 15 drivers for current chipsets like our Z170. Right now, Intel has an IRST version 15 driver available for the NUC mini board PC. Must be a big demand for that... Confused

Frankly, although I like Intel and IRST, the IRST software is loaded with bugs. I've seen several officially released versions going back to IRST 11 that were subsequently removed by Intel due to problems.

If we check the Relase Notes for IRST version 14.8.0.1042, we can find a few known issues related to your situation. For example:

4938878  PCIe link speed information is not updated in RST UI after exiting S3

May be a bit more than link speed information is not updated.

4938246  PCIe NVMe SSD 2DR0 (2-disk RAID 0) performance lower than pass-through single SSD

That inspires confidence. This is an old bug, that is also included in the Resolved Issues section.

We can also see other bugs related to NVMe SSD use.

Currently, if I attempt to install the IRST Windows software, the IRST UI will not install, the installation program just hangs indefinitely at the point (I assume) when the IRST UI is installed. I must kill the installation process. I get the 14.8.0.1042 driver installed, but no IRST UI. The... "SATA" mode is set to RAID in the UEFI, from day one of the Windows 10 installation, using a 950 Pro as the OS drive. Perhaps my configuration of the 950 Pro, an SM951 (AHCI version), and an 840 Pro, is a tortuous combination. Cool

I must give Intel credit, they have given us RAID with NMVe SSDs, which is a different protocol than SATA, and uses a different driver. IMO it is a miracle it works at all. Can we find such a capability anywhere else?

https://downloadmirror.intel.com/25165/eng/Release_Notes_14_8_PV.htm" rel="nofollow - https://downloadmirror.intel.com/25165/eng/Release_Notes_14_8_PV.htm



-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: clubfoot
Date Posted: 11 Jul 2016 at 12:37pm
I don't use sleep modes on my system but will test it later to see if I have the issue and report back tomorrow.

Parsec that clear CMOS is really f'd on this board,...that's why I stay away from it and have no issues with my RAID or bios updates.Smile


-------------
https://valid.x86.fr/1tkblf" rel="nofollow">


Posted By: clubfoot
Date Posted: 12 Jul 2016 at 9:23am
I concur with your findings.  IRST version 15. write back cache disabled, BIOS loaded with defaults and balanced power plan in Os. I don't use sleep on my computer as it is used for gaming,...but good to know.

Before sleep:
CrystalDiskMark 5.1.2 x64 (C) 2007-2016 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 1) :  3192.719 MB/s
  Sequential Write (Q= 32,T= 1) :  1916.382 MB/s
  Random Read 4KiB (Q= 32,T= 1) :   820.143 MB/s [200230.2 IOPS]
 Random Write 4KiB (Q= 32,T= 1) :   640.631 MB/s [156404.1 IOPS]
         Sequential Read (T= 1) :  3062.996 MB/s
        Sequential Write (T= 1) :  1923.757 MB/s
   Random Read 4KiB (Q= 1,T= 1) :    45.345 MB/s [ 11070.6 IOPS]
  Random Write 4KiB (Q= 1,T= 1) :   162.830 MB/s [ 39753.4 IOPS]

  Test : 1024 MiB [C: 36.8% (158.4/430.5 GiB)] (x5)  [Interval=5 sec]
  Date : 2016/07/11 20:38:37
    OS : Windows 10 Professional [10.0 Build 10586] (x64)

After sleep:
CrystalDiskMark 5.1.2 x64 (C) 2007-2016 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 1) :  1637.564 MB/s
  Sequential Write (Q= 32,T= 1) :  1575.108 MB/s
  Random Read 4KiB (Q= 32,T= 1) :   824.710 MB/s [201345.2 IOPS]
 Random Write 4KiB (Q= 32,T= 1) :   662.792 MB/s [161814.5 IOPS]
         Sequential Read (T= 1) :  1606.940 MB/s
        Sequential Write (T= 1) :  1380.449 MB/s
   Random Read 4KiB (Q= 1,T= 1) :    51.131 MB/s [ 12483.2 IOPS]
  Random Write 4KiB (Q= 1,T= 1) :   140.071 MB/s [ 34197.0 IOPS]

  Test : 1024 MiB [C: 36.8% (158.4/430.5 GiB)] (x5)  [Interval=5 sec]
  Date : 2016/07/11 20:57:59
    OS : Windows 10 Professional [10.0 Build 10586] (x64)


-------------
https://valid.x86.fr/1tkblf" rel="nofollow">


Posted By: parsec
Date Posted: 12 Jul 2016 at 10:26am
Originally posted by clubfoot clubfoot wrote:

I concur with your findings.  IRST version 15. write back cache disabled, BIOS loaded with defaults and balanced power plan in Os. I don't use sleep on my computer as it is used for gaming,...but good to know.

Before sleep:
CrystalDiskMark 5.1.2 x64 (C) 2007-2016 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 1) :  3192.719 MB/s
  Sequential Write (Q= 32,T= 1) :  1916.382 MB/s
  Random Read 4KiB (Q= 32,T= 1) :   820.143 MB/s [200230.2 IOPS]
 Random Write 4KiB (Q= 32,T= 1) :   640.631 MB/s [156404.1 IOPS]
         Sequential Read (T= 1) :  3062.996 MB/s
        Sequential Write (T= 1) :  1923.757 MB/s
   Random Read 4KiB (Q= 1,T= 1) :    45.345 MB/s [ 11070.6 IOPS]
  Random Write 4KiB (Q= 1,T= 1) :   162.830 MB/s [ 39753.4 IOPS]

  Test : 1024 MiB [C: 36.8% (158.4/430.5 GiB)] (x5)  [Interval=5 sec]
  Date : 2016/07/11 20:38:37
    OS : Windows 10 Professional [10.0 Build 10586] (x64)

After sleep:
CrystalDiskMark 5.1.2 x64 (C) 2007-2016 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 1) :  1637.564 MB/s
  Sequential Write (Q= 32,T= 1) :  1575.108 MB/s
  Random Read 4KiB (Q= 32,T= 1) :   824.710 MB/s [201345.2 IOPS]
 Random Write 4KiB (Q= 32,T= 1) :   662.792 MB/s [161814.5 IOPS]
         Sequential Read (T= 1) :  1606.940 MB/s
        Sequential Write (T= 1) :  1380.449 MB/s
   Random Read 4KiB (Q= 1,T= 1) :    51.131 MB/s [ 12483.2 IOPS]
  Random Write 4KiB (Q= 1,T= 1) :   140.071 MB/s [ 34197.0 IOPS]

  Test : 1024 MiB [C: 36.8% (158.4/430.5 GiB)] (x5)  [Interval=5 sec]
  Date : 2016/07/11 20:57:59
    OS : Windows 10 Professional [10.0 Build 10586] (x64)


It looks like we have another data point where the wake from Sleep changes something that causes a performance loss for the 950 Pro in RAID 0.

But I find your before and after Crystal results (in text mode) easier to read than the screenshots, and I can analyze them better. Thanks for posting this Thumbs Up

Clearly the sequential, large file read and write speeds (with one file, or with a Queue depth of 32 files) are reduced by almost 50% for the Read speed, but not as bad for Write speed.

What is curious is the 4K small file results, (with one file, or with a Queue depth of 32 files) are either virtually identical for Q=32, and actually improved for single file 4K reads! The 4K random write takes a small hit in performance.

I'd really like to know what happens here, given these results. Confused

The reduced sequential file speeds imply a bandwidth reduction, but to not have that reflected in the 4K results is strange.

The increase in the 4K random read speed (Q=1) reminds me of the difference between one of these drives and two in RAID. In RAID 0, you loose some 4K random performance, which is normal and the biggest downside of RAID 0 performance. But a single 950 Pro should not be able to match the Q=32 4K results. So that is again, strange.

Do you see any difference in your CPU speed after waking from Sleep? Reduced CPU speed, or the loss of an OC is a classic wake from Sleep bug that many boards have. I do NOT see that on my ASRock Z170 Extreme7+ board, with an i5-6600K at 4.4GHz. I also do not see that happen on my ASRock X99 board.

So what is happening? Are the DMI3 lanes changing to DMI2 speeds? Are we loosing a DMI3 lane for some reason?

clubfoot, if you run the Magician software after waking from Sleep, what do you see about your 950 Pros, as I asked about in my earlier post with the Magician screenshot?

Also, I am not blaming the UEFI clear for the problem with the failure of the RAID 0 array of the PCIe NVMe SSDs. A RAID 0 array of SATA III SSDs will not be in a failed state after a UEFI clear. That has always been that way.

IF the PCIe Remapping option must be enabled, or the PCIe SSD RAID 0 array will fail when the PC POSTs, I also cannot call that a UEFI bug. The PCIe Remapping option is not something that should be enabled by default for the majority of users. If it was enabled by default, most users would need to disable it before normal operation of their SATA drives would happen.

Again, IF the PCIe Remapping option must be enabled, or the PCIe SSD RAID 0 array will fail during POST, that is a bad situation that may not be able to be solved with an IRST driver update. I have more theories, but they are no worth mentioning.


-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: vacaloca
Date Posted: 12 Jul 2016 at 10:26am
My only guess would be to change the PCI Express Link State Power Management Settings in the power plan being used to off, perhaps try the same in BIOS if there is such an option to see if the issue is resolved. Otherwise, then yes, it sounds like faulty drivers.


Posted By: clubfoot
Date Posted: 12 Jul 2016 at 11:07am
There is an option to lock the buses at GEN3,...but I'm thinking that is only for the PCI graphics bus as changing it to GEN3 lowers the graphics scores :( Is there a UEFI option to lock the DMI for the m.2s?

I've always enabled the remapping for my two m.2s,...are you saying I do not need to?

In my "normal" setup i.e. o/c at 4.5Ghz with C States disabled, Speed Step disabled,...my comp will not sleep :) Tomorrow I can retest the cpu speed drop from sleep to see if that is what is causing it.


-------------
https://valid.x86.fr/1tkblf" rel="nofollow">


Posted By: parsec
Date Posted: 12 Jul 2016 at 5:43pm
Originally posted by vacaloca vacaloca wrote:

My only guess would be to change the PCI Express Link State Power Management Settings in the power plan being used to off, perhaps try the same in BIOS if there is such an option to see if the issue is resolved. Otherwise, then yes, it sounds like faulty drivers.


Good idea, if that would also apply to the DMI3 buss in the chipset, who knows if it does. A worthwhile experiment for this issue and in general. But, would the setting in the Power Plan match the actual setting in Windows after waking from Sleep. Confused

My Z170 Extreme7+ board and the Z170 OC Formula has two UEFI options that are similar to this Windows Power Plan setting.

One is the PCH DMI ASPM Support (speaking in acronyms.) PCH is the chipset, ASPM is Active State Power Management.

The other is DMI ASPM Support, which is ASPM support on the CPU side of the DMI link.

Both of these options are Disabled by default. I enabled them as a test, and the PCH temperature was reduced relative to being enabled, so they do seem to do what they should do.

Checking if they were enabled after waking from Sleep would not be simple, if even possible. The difference in PCH temperature would be a clue indicating they were enabled IMO.



-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: parsec
Date Posted: 12 Jul 2016 at 6:03pm
Originally posted by clubfoot clubfoot wrote:

There is an option to lock the buses at GEN3,...but I'm thinking that is only for the PCI graphics bus as changing it to GEN3 lowers the graphics scores :( Is there a UEFI option to lock the DMI for the m.2s?

I've always enabled the remapping for my two m.2s,...are you saying I do not need to?

In my "normal" setup i.e. o/c at 4.5Ghz with C States disabled, Speed Step disabled,...my comp will not sleep :) Tomorrow I can retest the cpu speed drop from sleep to see if that is what is causing it.


OMGosh, NO!

When the UEFI/BIOS is cleared, or after an update, the PCIe Remapping options are Disabled.

My theory, and it is just a theory, is the failure of a PCIe NVMe RAID 0 array after a UEFI/BIOS clear or update is caused by the PCIe Remapping options being disabled. I don't know if that is true, but it is the only thing I can think of that causes this to happen.

If C States and Speed Step are disabled, your PC will not Sleep? Interesting, never tried that since I normally have those options enabled.


-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: clubfoot
Date Posted: 13 Jul 2016 at 5:42am
I don't think it is the remapping being disabled as I can F9, save and reboot, and enable raid and remap and not lose my array. I can also flash between 2.6? and 3.0 without losing my array,.... The earlier BIOSES,... No!

Magician doesn't give any vital info of a raid array, unlike IRST where you can see the individual attached drives.

Clear CMOS is allot "harsher" on an m.2 raid setup,... It must be the way it totally disconnects power from it and may be a "flaw" in the m.2 design,.... Re sleep mode.




-------------
https://valid.x86.fr/1tkblf" rel="nofollow">


Posted By: parsec
Date Posted: 13 Jul 2016 at 10:37am
Originally posted by clubfoot clubfoot wrote:

I don't think it is the remapping being disabled as I can F9, save and reboot, and enable raid and remap and not lose my array. I can also flash between 2.6? and 3.0 without losing my array,.... The earlier BIOSES,... No!

Magician doesn't give any vital info of a raid array, unlike IRST where you can see the individual attached drives.

Clear CMOS is allot "harsher" on an m.2 raid setup,... It must be the way it totally disconnects power from it and may be a "flaw" in the m.2 design,.... Re sleep mode.




Interesting about the new UEFI versions that don't loose the 950 Pro RAID 0 array, I was not aware of that. Or is that the non-loss of power during an F9 and restart that is the key?

If the RAID 0 arrays are not lost ONLY in the scenario that you described, then there is a difference between that and a restart after a shutdown. POST is not always the same on a cold (after shutdown) startup, then it is on a restart of the PC. That may be a factor too.

Waking from Sleep issues that are common include loosing over clocks, and core multipliers being set to throttled values (such as 8 or 12). That is caused by the internal CPU registers that contain that data, not being reset correctly, or other registers used to signal thermal and power throttling being set to the throttle value, and the CPU's internal logic sees that and sets the core multipliers accordingly. The same thing may be happening with the DMI3 buss in the Z170 chipset. We don't know if that is happening.

I could swear I am seeing a few options in the UEFI that are not reset after a UEFI update, that are not default values. Such as RAID for the "SATA" Mode. There are also "background" setting in a UEFI/BIOS, that we are not aware of, or don't match certain option settings. Turbo Boost can behave that way, being set to Disabled by some users for over clocking, but is really enabled, since it must be for any OC multiplier OC from Sandy Bridge processors forward. I'm hinting here that PCIe Remapping might remain enabled even when it seems it isn't.

The ASRock OC Formula boards have switches on the board that can turn the PCIe x16 lanes off and on. It would be nice if the M.2 slots had such a switch in the UEFI update/shutdown situation. But that is a unique situation, and would be like a switch to turn off a SATA port, which is not needed for any reason.

I've always wondered about the option to disable the SATA Controllers in the UEFI, Storage Configuration screen. Would that also disable the M.2 slots on a Z170 board?


-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: clubfoot
Date Posted: 13 Jul 2016 at 11:23am
I came across another interesting discovery while testing power plans,...default balanced power plan produces higher disks scores >3200 than default high performance plan >2900! Using balanced plan with HDD turn off = never, Link state = off, and UEFI APCI suspend to ram = disabled,...C states and Speed step disabled.

balanced power plan:
CrystalDiskMark 5.1.2 x64 (C) 2007-2016 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 1) :  3207.355 MB/s
  Sequential Write (Q= 32,T= 1) :  1912.526 MB/s
  Random Read 4KiB (Q= 32,T= 1) :   860.171 MB/s [210002.7 IOPS]
 Random Write 4KiB (Q= 32,T= 1) :   552.720 MB/s [134941.4 IOPS]
         Sequential Read (T= 1) :  3057.911 MB/s
        Sequential Write (T= 1) :  1919.841 MB/s
   Random Read 4KiB (Q= 1,T= 1) :    56.030 MB/s [ 13679.2 IOPS]
  Random Write 4KiB (Q= 1,T= 1) :   188.692 MB/s [ 46067.4 IOPS]

  Test : 1024 MiB [C: 37.7% (162.2/430.5 GiB)] (x5)  [Interval=5 sec]
  Date : 2016/07/12 23:00:44
    OS : Windows 10 Professional [10.0 Build 10586] (x64)


-------------
https://valid.x86.fr/1tkblf" rel="nofollow">


Posted By: Grant Rogers
Date Posted: 14 Jul 2016 at 4:20am
Hi guys,

I have just noticed I didn't have notifications ticked when there was a reply so sorry for the late response.

@Parsec, yeah I know I am taking my chances with RAID 0, the reason I did it is so I don't have worry about where the data is going, using them as two separate drives mean I would have to start using Windows mount points.  It also has the added benefit of making the performance even better than a single m.2.

Regarding the check in the Samsung Magician software I checked, but it doesn't know anything about the RAID:




It is correct at least for me that I am using the m.2 sockets.

Originally posted by Parsec Parsec wrote:

That's an interesting event, but something is strange about it. storahci is the native Windows 10 AHCI driver. The Intel IRST driver is iaStorA.sys, which you can confirm in the Device Manager entry, under Storage Controllers.

Regardless, the reference to \Device\RaidPort0 seems to be related to this situation. You should check the Event Log for anything about iaStorA.sys, if you manually installed the IRST 14.6 or 14.8 version driver, which I believe you must have done.


Yeah I was wondering about this, but the drivers look correct so I don't think I am using the base Microsoft ones.



Originally posted by Parsec Parsec wrote:

We also have the Samsung NVMe driver to potentially add to the list of reasons for this issue. A question that I am unsure about is, when using these SSDs in RAID 0, is the Intel IRST driver in complete control, and the only one that is used? The Samsung NVMe driver not being used at all?


I don't think the samsung driver is being used by Windows which is why Samsung magician doesn't recognise them.  It is all hidden by the Intel drivers.

Thanks for finding those notes about the bugs I hadn't seem them before, it is interesting.

Is there any particular reason you chose RAID when you are not using RAID configuration?

@clubfoot, thanks for confirming it is useful to know how many people are affected by this.

It is a shame that version 15 of the driver doesn't fix this issue either.

I will let you know if I get anything back from Intel / ASRock, and thanks for all the research it has been interesting reading.

One thing I will say about Intel's bug list is plenty of people had a problem with hdds not spinning down (not my problem), and one year later it still hasn't been fixed.  It doesn't give me much confidence they will fix the known issues quickly.

Lastly regarding the sleep thing, I have used it a lot on my other machines as wake up time is near instant and I can resume my work (mainly programming) without having to open all of the apps up again, an added benefit is that dropbox doesn't keep indexing on startup.  It is an inconvenience rather than a show stopper, but annoying none the less.

Grant


Posted By: clubfoot
Date Posted: 14 Jul 2016 at 9:19am
Have you found anyway to correct the half speed on wake?

Did you notice if your cpu is locking itself down at a lower speed?


-------------
https://valid.x86.fr/1tkblf" rel="nofollow">


Posted By: parsec
Date Posted: 14 Jul 2016 at 11:40am
@Grant Rogers, You don't need to justify your use of 950 Pros in RAID 0 to me! LOL

I update and clear the UEFI too often, which is one reason I don't use RAID 0 for my 950 Pros. I have one not being used currently, which is ridiculous! Confused

About the Magician software, it cannot recognize RAID mode. Been that way since it was introduced.

Early on, it could not work with AMD SATA chipsets using AMD drivers, in AHCI mode!

I have RAID selected in the UEFI, but no RAID arrays created. This is what Magician shows me when I have my Samsung 840 Pro selected:



Notice the Storage controllers in Device Manager. Regardless of what it states above about AHCI mode, RAID mode has EVERY feature that is provided by AHCI mode.

Changing to my 950 Pro, I see this in Magician:



While the Intel RAID software (IRST) must provide the NVMe interface to the SSDs (Intel has their own NVMe driver for their NVMe SSDs), I don't see any reason why it would hide the Samsung NVMe driver.

Regarding the Microsoft storahci driver, your 950 Pro RAID 0 array is not using the storahci driver, but notice in your Device Manager picture, you have an IDE ATA/ATAPI controllers entry.

If I select my Samsung SM951 AHCI PCIe M.2 SSD in Magician, I see this:



In your PC, that Device Manager entry is for your BD drive. It isn't for your HDDs, since they would be controlled by the Intel RAID controller, even as single drives. That Event Log entry should be related to the BD drive.

The Samsung SM951 is unusual in that is has its own storage controller chip as part of the SSD. It uses the Windows AHCI driver by default.

I always use RAID mode, whether I'm using a RAID array or not. I prefer to use the Intel storage driver (which can be used in AHCI mode.) Intel calls that "RAID ready", and the Intel IRST driver only supports PCIe SSDs in RAID mode. Plus I create a RAID array on this PC occasionally, I did that to test something for someone in this forum a while ago, can't recall exactly what it was. That was a crazy one, a RAID 0 of a Samsung 840 Pro and an older Crucial M4 SSD. Did it work? It sure did.

Intel knows IRST has issues. That software is provided as is, without any guarantees. If you want perfect (or closer to perfect), you must use the Intel RSTe driver, Rapid Storage Enterprise. That driver is not supported on the Z170 chipset, you must use a server board with a server chipset. The first HEDT platform, X79, supported RSTe. It's performance was less than IRST (reduced benchmark performance)

Wake from Sleep work fine for me on this PC. clubfoot said if he has C States disabled in the UEFI, waking from Sleep fails. I have C States enabled.



-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: clubfoot
Date Posted: 15 Jul 2016 at 10:37am
In further testing of sleep IRST still shows PCIe link speed:4000MB/s and PCIe link width x4 for both m.2s after waking. So I don't think the driver is falling back to single drive.

However, the cpu on the other hand drops the core voltage to >.6xx and the multiplier is at 8x. If I run Crystaldisk the core increases to 1.3xx and the multiplier varies between 42 and 8 and everything in between as it should.

What is a little disturbing is that it never throttles up!? Stays at half speed as if has not fully awakened.

Parsec does this happen on your single m.2 with the raid driver? Because that would tell us if it is the IRST!


-------------
https://valid.x86.fr/1tkblf" rel="nofollow">


Posted By: parsec
Date Posted: 15 Jul 2016 at 12:12pm
Originally posted by clubfoot clubfoot wrote:

In further testing of sleep IRST still shows PCIe link speed:4000MB/s and PCIe link width x4 for both m.2s after waking. So I don't think the driver is falling back to single drive.

However, the cpu on the other hand drops the core voltage to >.6xx and the multiplier is at 8x. If I run Crystaldisk the core increases to 1.3xx and the multiplier varies between 42 and 8 and everything in between as it should.

What is a little disturbing is that it never throttles up!? Stays at half speed as if has not fully awakened.

Parsec does this happen on your single m.2 with the raid driver? Because that would tell us if it is the IRST!

I want to be sure I understand what is happening in your description of your CPU before and after Sleep. I'll go through that in a bit.

First, CPU speed, an over clock, and CPU power saving options enabled and disabled (mainly SpeedStep and C States) will affect the benchmark results of a SSD. When I've seen that with SATA III SSDs, it's not that much of a difference, compared to the reduced 950 Pro RAID 0 results, which are reduced a lot more.

The SATA III SSD sequential read and write speeds will lose about 25MB/s from the usual ~500MB/s Read, and ~450MB/s Write speeds, when SpeedStep and C States are enabled. The benchmark test does not put enough of a load on the CPU to take it out of the SpeedStep CPU speed of 800MHz, for any Mainstream/Performance CPU (all Intel CPUs except the HEDT 6, 8, and now 10 core processors, whose SpeedStep speed is 1,200MHz.)

Add C States (C3, C6) to the situation, at idle the CPU will be in the C6 state (cores virtually off) ~90% of the time. When an IO request finally wakes up a core or two, it takes time for the core to get going again. That should be no time compared to the slow IO of our storage drives, but it adds up and the benchmark result difference is real, small but real for SATA III SSDs at least.

Back to your CPU description before and after waking from Sleep.

Your signature specs show an OC of 4.6GHz on your i7-6700K. You might use a manual, constant VCore. No SpeedStep or C States, both disabled?

Is that right, and what you used when you noticed your 950 Pro RAID 0 performance problem, after waking from Sleep?

You wrote this:

However, the cpu on the other hand drops the core voltage to >.6xx and the multiplier is at 8x. If I run Crystaldisk the core increases to 1.3xx and the multiplier varies between 42 and 8 and everything in between as it should.

Does the above happen after waking from Sleep? You loose your OC to 4.6, and the CPU is back to stock speeds, Turbo up to 4.2, and SpeedStep seems to be enabled, since you are down to 800MHz, depending on CPU load.

Then you wrote:

What is a little disturbing is that it never throttles up!? Stays at half speed as if has not fully awakened.

Is this referring to the 950 Pro RAID array? Or your CPU speed? I think you mean the RAID array.

Does that happen to my single 950 Pro? Check my first post on page 1 of this thread, third post from the top. Here it is again, after waking from Sleep, a 256GB 950 Pro:



Exactly what it should be given the specs. Plus this is the OS drive.

Does this really tell us if it is the IRST driver? It could be, but I'm not ready to say that yet.

Why? Because of what might be happening to your CPU speed after waking from Sleep. BTW, I do NOT loose my OC on my i5-6600K when I wake from Sleep. It's still at 4.4GHz, which I've been using lately.

If YOU are loosing your OC settings, and other weirdness like SpeedStep being enables, for the 800MHz CPU speed, then it is possible that OTHER settings somewhere are off too, that affect the RAID 0 array. Changes to CPU multipliers are a classic wake from Sleep failure of a BIOS. Why mine are fine and yours are not (if true) is even more weird. Pinch

That is why I need to understand what happens to your CPU speed when you wake from Sleep!! I could not be sure given what you wrote. Confused




-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: clubfoot
Date Posted: 15 Jul 2016 at 11:45pm
>> Your signature specs show an OC of 4.6GHz on your i7-6700K. You might use a manual, constant VCore. No SpeedStep or C States, both disabled? - Yes.

>>Is that right, and what you used when you noticed your 950 Pro RAID 0 performance problem, after waking from Sleep? - No. To duplicate the OP's bug I F9 default BIOS settings, rebooted, set up UEFI RAID and remap,...no o/c, no other changes and tested sleep. From wake,...half speed :(

>>However, the cpu on the other hand drops the core voltage to >.6xx and the multiplier is at 8x. If I run Crystaldisk the core increases to 1.3xx and the multiplier varies between 42 and 8 and everything in between as it should.

Does the above happen after waking from Sleep? You loose your OC to 4.6, and the CPU is back to stock speeds, Turbo up to 4.2, and SpeedStep seems to be enabled, since you are down to 800MHz, depending on CPU load. - No,...everything BIOS defaults, no o/c.

>>What is a little disturbing is that it never throttles up!? Stays at half speed as if has not fully awakened.

Is this referring to the 950 Pro http://www.ebay.com/sch/i.html?_nkw=raid+array" rel="nofollow - RAID array ? Or your CPU speed? I think you mean the RAID array. - 950 Pro RAID array same as the OP,...after extended desktop use you would think everything would be fully awake and drives at full speed but no :(

>>Does this really tell us if it is the IRST driver? It could be, but I'm not ready to say that yet. - There is one way to find out,...use the default Microsoft raid driver, but we can't because we load the floppy IRST during install to get the m.2s recognized in RAID :( As your single drive is working full speed from wake I'm going to point my finger at the ASRock BIOS implementation of m.2 because the z170 chip set support for m.2 cannot be at fault. LOL :)

P.S. Like you I am also using the default 4,4GHz built in o/c with XMP for 24/7 daily use instead of 4.6GHz because I really can't tell the difference in gaming, I can turn my fans to silent, the cpu runs cooler and I really only benchmark to uncover issues and check to make sure everything is working as it should. All the Crystaldisk results previous posted are default C states & Speedstep enabled.

This is my result today at 4.4GHz F9 default BIOS settings with XMP, with write back cache enabled (for benching/testing only) and Link Power Management Disabled in IRST.  I have my PC plugged into a server UPS,...just to be safe.

CrystalDiskMark 5.1.2 x64 (C) 2007-2016 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 1) :  3312.495 MB/s
  Sequential Write (Q= 32,T= 1) :  1923.209 MB/s
  Random Read 4KiB (Q= 32,T= 1) :   908.839 MB/s [221884.5 IOPS]
 Random Write 4KiB (Q= 32,T= 1) :   665.851 MB/s [162561.3 IOPS]
         Sequential Read (T= 1) :  3295.103 MB/s
        Sequential Write (T= 1) :  1921.093 MB/s
   Random Read 4KiB (Q= 1,T= 1) :    53.841 MB/s [ 13144.8 IOPS]
  Random Write 4KiB (Q= 1,T= 1) :   399.944 MB/s [ 97642.6 IOPS]

  Test : 1024 MiB [C: 35.0% (150.8/430.5 GiB)] (x5)  [Interval=5 sec]
  Date : 2016/07/15 10:17:12
    OS : Windows 10 Professional [10.0 Build 10586] (x64)





-------------
https://valid.x86.fr/1tkblf" rel="nofollow">


Posted By: parsec
Date Posted: 16 Jul 2016 at 2:27am
You might be able to manually update the IRST driver to the native Windows version. Doing a Browse for drivers on the PC, and select from a list on the PC.

I get to the point in the manual update where I think I see the native Windows IRST driver, but no idea what version it is. All it says is Intel Desktop/Workstation/Server Express Chipset SATA RAID Controller.

If it is NOT an IRST version 14 version, in your case with the 950 Pro RAID 0 array, since ONLY IRST version 14 drivers support PCIe NVMe SSDs in RAID, you should NOT try that! Unless you feel like installing Windows again on a most likely dead RAID 0 array. Ouch  Friends don't let friends kill their RAID 0 arrays. LOL

I don't know if the ASRock UEFI is having a problem with the M.2 system after waking from Sleep. IMO, if it did we would see it with a single 950 Pro, which we don't. That is, if the DMI3 bandwidth in the chipset was reduced after waking from Sleep, would it not happen to all M.2 ports?

Speaking of which, my 950 Pro is in the M2_3 slot. Which M.2 slot do you use?

Add the IRST RAID driver to the mix, but the question still becomes WHAT is changing, IF it was a wake from Sleep UEFI issue?

Just for fun, this is yet again my single 950 Pro after waking from Sleep, Crystal test version:

CrystalDiskMark 5.1.2 x64 (C) 2007-2016 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 1) :  2187.658 MB/s
  Sequential Write (Q= 32,T= 1) :   955.658 MB/s
  Random Read 4KiB (Q= 32,T= 1) :   767.589 MB/s [187399.7 IOPS]
 Random Write 4KiB (Q= 32,T= 1) :   334.638 MB/s [ 81698.7 IOPS]
         Sequential Read (T= 1) :  2036.506 MB/s
        Sequential Write (T= 1) :   957.743 MB/s
   Random Read 4KiB (Q= 1,T= 1) :    59.438 MB/s [ 14511.2 IOPS]
  Random Write 4KiB (Q= 1,T= 1) :   244.274 MB/s [ 59637.2 IOPS]

  Test : 1024 MiB [C: 12.1% (24.2/200.0 GiB)] (x5)  [Interval=5 sec]
  Date : 2016/07/15 13:05:14
    OS : Windows 10  [10.0 Build 10586] (x64)
    950 Pro After Wake From Sleep



-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: gtharea
Date Posted: 17 Jul 2016 at 3:23am
Hello all, I am also having sleep issues with RAID, but they seem to be much worse than others on here. 

I have two SM951 AHCI drives in the M2_1 and M2_3 ports (im not using port 2 because the gfx card is on top of it and affects cooling)

With the 3.00 BIOS and Intel RST 14.8 installed on windows 10, I am unable to successfully wake up from sleep. Sometimes I can unlock the computer, but then it freezes at the windows desktop. Other times my monitors turn on but there is just a blank screen. I have to hold down the case power button and cold boot in order to get back to windows. 
Clearing CMOS does nothing except destroy my RAID array.

However, when I switch to BIOS B, which is version 1.80, I am able to sleep and wake properly. I notice that the RAID driver in UEFI is 14.5, while the windows driver is 14.8. 

The only issue I see is half speeds after wake, like the others in this thread. 

If I downgrade to windows Intel RST 14.5 (from the extreme7+ download page) so that it matches the UEFI version, then I cant wake from sleep....

So frustrating. I hope ASRock can provide some insight to these issues. 

EDIT; I figured out what was causing the freezing... DVD drive connected to the ASMedia controller. Once I disconnected the drive, no more freezing. However I'm still getting half speed after waking from sleep. BIOS 3.00, Windows 10 x64 Intel drivers 14.6.0.1029, I dont have RST installed


Posted By: clubfoot
Date Posted: 17 Jul 2016 at 10:08am
>>EDIT; I figured out what was causing the freezing... DVD drive connected to the ASMedia controller. Once I disconnected the drive, no more freezing. However I'm still getting half speed after waking from sleep. BIOS 3.00, Windows 10 x64 Intel drivers 14.6.0.1029, I dont have RST installed

Interesting about the ASMedia as I have a hot swap bay connected to those ports, however it is not powered On. Are you running the latest ASMedia drivers?

Unless you plan on reinstalling Windows do not clear CMOS :(

Did you lose your array when you switched to BIOS version 1.8?

No need to downgrade the IRST driver to match the BIOS version. If 14.8 works use it. Are you running an o/c or Speedstep and C States disabled?

During installation you used a floppy driver version of IRST,...you just don't have the GUI installed so you can view information and make changes.


-------------
https://valid.x86.fr/1tkblf" rel="nofollow">


Posted By: gtharea
Date Posted: 17 Jul 2016 at 10:08pm
Interesting about the ASMedia as I have a hot swap bay connected to those ports, however it is not powered On. Are you running the latest ASMedia drivers?

Dont think so, I was using whatever windows defaults to... Would you be kind enough to share a link to them?

Did you lose your array when you switched to BIOS version 1.8?

When I switched from BIOS 3.00 to BIOS 1.80 using the switch on the MB I did not lose the array. However clearing CMOS ruins the array, as we all know. I imaged my windows install, no big deal.

No need to downgrade the IRST driver to match the BIOS version. If 14.8 works use it. Are you running an o/c or Speedstep and C States disabled?

During installation you used a floppy driver version of IRST,...you just don't have the GUI installed so you can view information and make changes.

I am not currently running an OC, but when I do OC to 4.7, the same behaviors are present. I did not change any speedstep or C states settings, so whatever the BIOS default is.

I was paranoid about different IRST driver versions for some reason. Now that I figured out it was the ASMedia DVD drive, i'll probably update to 14.8

Thanks for your help.


Posted By: clubfoot
Date Posted: 18 Jul 2016 at 1:58am
>>Don't think so, I was using whatever windows defaults to... Would you be kind enough to share a link to them?

Station Drivers usually has the latest (select english flag) as well as IObit Driver Booster.
http://www.station-drivers.com/index.php?option=com_content&view=article&id=1483:z170-extreme7&catid=171&Itemid=169&lang=fr

>>When I switched from BIOS 3.00 to BIOS 1.80 using the switch on the MB I did not lose the array. However clearing CMOS ruins the array, as we all know. I imaged my windows install, no big deal.
If you do not require any "special" features in 3.00 and 1.80 works well with sleep,...than use 1.8,...without clearing CMOS :)


-------------
https://valid.x86.fr/1tkblf" rel="nofollow">


Posted By: Grant Rogers
Date Posted: 19 Jul 2016 at 2:53am
Just thought I would update you guys, I have created two tickets, one with ASRock and another with Intel.  They are both investigating; I will let you know when I have an concrete answers.

Grant


Posted By: nme
Date Posted: 02 Aug 2016 at 5:42am
OP here, i don't get the notification in my email either! going to enable them now lol.... 

I didn't get any responses from here for months so I went about my way. I still have the same set up and all i have been doing is using hibernate instead of sleep. It takes a little longer to boot but the drives work at full speed after waking from hibernate so I've just been dealing with it.

Interesting to see so many responses though! I guess i'll hop back on the train and try some things and post back soon. Hopefully we can figure something out.




Posted By: parsec
Date Posted: 02 Aug 2016 at 11:25am
Originally posted by nme nme wrote:

OP here, i don't get the notification in my email either! going to enable them now lol.... 

I didn't get any responses from here for months so I went about my way. I still have the same set up and all i have been doing is using hibernate instead of sleep. It takes a little longer to boot but the drives work at full speed after waking from hibernate so I've just been dealing with it.

Interesting to see so many responses though! I guess i'll hop back on the train and try some things and post back soon. Hopefully we can figure something out.




What is the difference between Hibernate and Sleep? The only difference (supposedly) is the "snapshot" of the state of the OS that is stored in DRAM memory when Sleep or Hibernate are started is written to disk in Hibernate mode.

But one more important detail about Hibernate: The snapshot of the OS written to disk is ONLY used to restore the PC upon waking if power to the PC is removed or lost while in Hibernate mode.

If the "Sleep" indication of the power LED on your PC case (mine blinks on and off) is active, obviously power to the PC was not lost. But you said coming out of Hibernate is slower than Sleep, meaning the disk image is being used to restore the desktop.

Is power removed from your PC when you use Hibernate?

If Hibernate is truly only Sleep with the addition of the OS image saved to disk, then how does it work fine when Sleep doesn't?

Also, why does the disk OS image apparently work to restore the desktop perfectly, including the RAID 0 array, but the OS image in DRAM does not?

Yet another example of the strange nature of Windows Sleep and Hibernate.

The following is not directed at you personally, nme, but in general to those whom have this issue:

Don't forget that Sleep and Hibernate are 100% Microsoft Windows features, provided by and running in a Microsoft OS.

So explain to me why the first complaints go to the mother board manufacture, and Intel? What about Samsung too?

Have you contacted Microsoft about this?

FYI, the IRST software is provided as is with nothing about it guaranteed whatsoever. The following is taken from this file:

https://downloadmirror.intel.com/25165/eng/F6flpy_ReadMe.txt" rel="nofollow - https://downloadmirror.intel.com/25165/eng/F6flpy_ReadMe.txt

EXCEPT AS PROVIDED ABOVE, THE SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED
 WARRANTY OF ANY KIND, INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT,
 OR FITNESS FOR A PARTICULAR PURPOSE. Intel does not warrant or assume responsibility
 for the accuracy or completeness of any information, text, graphics, links or other
 items contained within the Software. LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS SUPPLIERS BE LIABLE FOR ANY
 DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION
 OR LOST INFORMATION) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN
 IF INTEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS
PROHIBIT EXCLUSION OR LIMITATION OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR
 INCIDENTAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE
 OTHER LEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION.
My actual point is, Intel will just put this issue, IF it is really the fault of the IRST driver, on the list of IRST issues (plenty already in the list), which may or may not be fixed in the future.



-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: Grant Rogers
Date Posted: 21 Aug 2016 at 6:59pm
Hi all,

It has been a while to post, but I got a BIOS from support that fixes this issue!  The BIOS was version 2.5 (I guess this was a BETA version) where the latest BIOS is 2.6 (this problem is not fixed in this version).

I can upload the BIOS somewhere if people are interested in trying it out.  I have made support aware of this forum post too.

Grant


Posted By: parsec
Date Posted: 21 Aug 2016 at 7:31pm
Originally posted by Grant Rogers Grant Rogers wrote:

Hi all,

It has been a while to post, but I got a BIOS from support that fixes this issue!  The BIOS was version 2.5 (I guess this was a BETA version) where the latest BIOS is 2.6 (this problem is not fixed in this version).

I can upload the BIOS somewhere if people are interested in trying it out.  I have made support aware of this forum post too.

Grant


For your Z170 OC Formula, there is a standard 2.50 UEFI version, but the latest Beta is 1.92. So the UEFI version file you got is 2.50, or something else? Apparently not.

So you actually cleared the UEFI with the UEFI version ASRock sent you, and your RAID 0 array survived? Great, and thanks for trying that for us and ASRock. Kinda scary to do that, wasn't it?

You should make it clear that the UEFI version ASRock sent you with the fix is ONLY for the Z170 OC Formula. Not that it should cause problems with other boards, it won't install, but you know what I mean.

Is there anything you noticed about that UEFI version regarding UEFI options or settings that is different than the others, that prevents the failure of the RAID array?


-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: Grant Rogers
Date Posted: 21 Aug 2016 at 8:21pm
Ah ok, I guess 2.5, I didn't see anything identifying in the name of the file.  I will check the BIOS for version numbers when I am back home at that PC.

I didn't explicitly clear anything, I don't know what the upgrade / downgrade does to settings.  I did need to enable the m.2 mapping (I can't remember the exact name) and go back into the BIOS to check the RAID array was still there, everything booted fine after that Smile.  I wasn't that worried, I would have just rebuilt the machine again.

Yes very true, it is only compatible with my board.  I hope the support staff that sent me the BIOS update will comment here on what the problem was and fixes to the other motherboards.

Um that is a good question, no I haven't noticed anything special about this BIOS.  I haven't seen my RAID array being trashed through any BIOS changes, the only thing I noticed was that I needed to change a couple of settings to get the BIOS to recognise the array again.

I should have written them all down for future reference.  I will check tonight to see if I can remember the steps and list them here.


Posted By: Grant Rogers
Date Posted: 22 Aug 2016 at 4:01pm
Here is a quote from the support staff themselves:

Hello,

Thank you for the feedback. Maybe good to know the BIOS version: 2.52C

I will ask my colleague in Taiwan if this fix will be implemented in the next regular BIOS version, and ask him to have a look at that thread.

Thanks,

ASRock Support



Posted By: Grant Rogers
Date Posted: 23 Aug 2016 at 12:04am
For reference

Hello,

The fix will also be implemented in the next regular BIOS release (after 2.60). I have no information about when a new version is planned.

I expect it will also be used in the next regular BIOS release for Z170 Extreme7+ and Z170 Professional Gaming i7.

Thanks,
ASRock Support




Posted By: gtharea
Date Posted: 24 Aug 2016 at 2:56am
Hi all, support has provided be with a beta BIOS for the Extreme7+:

https://1drv.ms/u/s!AlIuWeCO2Mqakil342R4ICN8Xqqo

Its a modification of BIOS 3.10C

Haven't tried it yet, not at home

Great support tho, I emailed them yesterday. Hope it works!

edit: The fix works, there is no more decrease in speed after waking from sleep. However, it seems like sequential reads have decreased by about 400mb/s. Used to be around 3200, now its 2800


Posted By: clubfoot
Date Posted: 24 Aug 2016 at 9:16am
Good to know a fix is coming.


-------------
https://valid.x86.fr/1tkblf" rel="nofollow">


Posted By: parsec
Date Posted: 24 Aug 2016 at 12:42pm
Originally posted by gtharea gtharea wrote:

Hi all, support has provided be with a beta BIOS for the Extreme7+:

https://1drv.ms/u/s!AlIuWeCO2Mqakil342R4ICN8Xqqo

Its a modification of BIOS 3.10C

Haven't tried it yet, not at home

Great support tho, I emailed them yesterday. Hope it works!

edit: The fix works, there is no more decrease in speed after waking from sleep. However, it seems like sequential reads have decreased by about 400mb/s. Used to be around 3200, now its 2800


Thanks for the download link. It worked for me, I have the file.

OS drives, including RAID volumes as OS drives, can loose some performance over time. But that seems a bit much to be related to that.

Did you ever run the trimcheck tool on that RAID array? I know I did at one time, but don't have a RAID 0 or 950's anymore. TRIM worked at that time. Just a thought, might not be the cause.

http://files.thecybershadow.net/trimcheck/" rel="nofollow - http://files.thecybershadow.net/trimcheck/

Also, CPU power saving options, and the chipset ASPM power saving options can affect performance of drives. Just going over other possible causes.

So you don't see any loss in performance in other areas, like 4K Read and Write, etc? What benchmark test did you run? What version of IRST are you using, just for the record.


-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: gtharea
Date Posted: 30 Dec 2016 at 11:26pm
The latest BIOS, 7.30 has the half speed wake from sleep issue


Posted By: nme
Date Posted: 24 Jul 2018 at 5:34am
OP here. A year later lol. Thanks for all the responses. I lived with using hibernate for the whole time. I did just upgrade my computer with some more SSD love but i still have the main 950s  in RAID 0. I tried the above 3.10c bios and it indeed works. I will stick with this one. Thanks gtharea and the rest of you for your research! 

FYI I still have this set up and I do overclock. My 4.6 Ghz overclock went away when i did the bios update, and i can't load my profile anymore. I will be recreating it and overclocking again. If anyone with the same board has any questions or would like to compare, feel free to give me a shout!

Thanks.


Posted By: clubfoot
Date Posted: 24 Jul 2018 at 9:44pm
You could also try the latest 3.60 UEFI.


-------------
https://valid.x86.fr/1tkblf" rel="nofollow">



Print Page | Close Window

Forum Software by Web Wiz Forums® version 12.04 - http://www.webwizforums.com
Copyright ©2001-2021 Web Wiz Ltd. - https://www.webwiz.net