one more stab at this which feels promising (but so did the former).

I returned all the new/current HIPM/DIPM qwords to their defaults.

I had tried default, I had tried them all removed, I had tried them with only DIPM off and HIPM on as is windows default. All still had the soft hangs.

I was looking through the inf's and noticed a difference in the messaging signal interrupt setting. A drastic difference. Current IRST(e) have the MessageNumberLimit as 1. The old non-problematic IRST drivers also have it as one (including fernando's modded). Current problematic drivers have it set to 80!!

Now for testing im using the MSI mode utility, and MSI Is brand new to me. However its my understanding under most cases the higher the number, the more problematic it can become with one of the problems being hangs such as what many experience.

(oddly enough samsung sets their m.2 driver at 2048 lol)

its my last ditch effort before i give up on current irst completely.

towel tossed in. messing with the the MSI didnt save it. good luck to the next guy

found this during the endeavor which is interesting. naturally went unanswered but it provides at least some more technical info.

https://forums.intel.com/s/question/0D50...?language=en_US

Please dont toss anything else, do urself a favor start from scratch with a clean OS and drive by drive...im almost sure that the driver will be stable and wont freeze...if it does, then u have a hw i/o issue. Dont try get an answer in a pile of junk OS full of tryouts and modifications...hopping that a miracle fix will come out from it, u wont get any clear understanding of the issue. Troubleshooting steps is always the way. A simple i/o cable, voltage drain, disk surface, disk heads, firmware, bios...u name it

unfortunately it is a clean OS. actually in the midst of setting it up atm, hence why im revisiting this "problem"

the fact that it doesnt soft-hang with IRST pre ~15.x, doesnt soft hang with M$ standard ahci, and doesnt soft-hang with any irst(e) up to and including the newest - certainly puts it well beyond the particular OS install imo anyways.

its been present for ages. Ever since the migration from ~15x to higher irst.

its all over the web. Apparently the general consensus is ditch the irst drivers and use standard, but standard puts my drives all out of order. It puts my OS driver as Disk 7. Makes it a bit annoying every time i have to navigate to it in xxx software.

Others just avoid sleeping their disks. For me with 7 inside my PC and 6 outside, not an option either. My data is very important to me so i'd prefer not to run all my drives 24/7

having my OS drive not as the first disk is a deal breaker for me, as is the random hangs when disks spinup, so that leaves me with the 13.xx drivers fernando signed to make usable on current win10, or the irste.

the performance is marginally better with the old irst from win-raid, but probably within margin of error. Oddly enough that part is inconsequential to me. What is not (warning, im very ocd) is the fact that fernando's display in the proper area of device manager, but are named incorrectly and advertise as being "by fernando" (no offense fernando lol). The irste on the other hand, dont display under IDE ATA/ATAPI Controllers and instead display under Storage Controllers. Also named incorrectly but in a different way. They say theyre for C600/C220+ chipsets or something like that which is evidently what comes on the X99+ boards.

at least i know what it isnt. It isnt related to HIPM/DIPM in the sense that a particular mode is the problem. It isnt related to Message Interrupts or their limit. Its something revolving around APM and waking the drives though. It happens at random when the OS decides to spin one up for whatever reason which is what makes it especially taxing as it soft locks your pc for ~5 seconds at least.

im a glutton for punishment.

i noticed the non-offender drivers point to their relative driver, aka iastorE.sys or iastorA.sys. The irst (newer ones) point to iaStorAC.sys but also an RstMwEventLogMsg.dll and a RstMwService.exe

I wonder if one of those "extras" is the root of the issue.

I tried finding the service in services.msc to disable and test, but not seeing it.

I'm with you on this one, klepp0906.
My OS is freshly installed and obsessively clean and free of any extras whatsoever.
I was able to get rid of this problem only once, with a somehow perfect combination of official EFI update from Asus + right RST drivers.
As I said, disabling sleep on my spare drive is not much of a problem, but I'd love to solve the soft-lock annoyance nonetheless.
I appreciate all of your efforts to dig deeper into this and followed each one of them closely as you posted.
As I said, I suspect the culprit might even lie in one of the many Windows updates of the past year or so (been on my new system for a year now and have seen three or four OS installations).

I can tell you for sure that enabling/disabling the services installed by the RST package changed absolutely nothing on my system.

Please keep us posted on any of your findings. I've been pulling my hair on this for quite some time now.

Zitat von Lurk im Beitrag #21

---

I'm with you on this one, klepp0906.
My OS is freshly installed and obsessively clean and free of any extras whatsoever.
I was able to get rid of this problem only once, with a somehow perfect combination of official EFI update from Asus + right RST drivers.
As I said, disabling sleep on my spare drive is not much of a problem, but I'd love to solve the soft-lock annoyance nonetheless.
I appreciate all of your efforts to dig deeper into this and followed each one of them closely as you posted.
As I said, I suspect the culprit might even lie in one of the many Windows updates of the past year or so (been on my new system for a year now and have seen three or four OS installations).

I can tell you for sure that enabling/disabling the services installed by the RST package changed absolutely nothing on my system.

Please keep us posted on any of your findings. I've been pulling my hair on this for quite some time now.

---