Intel RST v.20.0.0.1038 Windows Software Fails Every Time with 0xA00906B3, RstMWService always 1067

UserRH · ‎12-15-2024

Quite obviously Intel hasn't done any QA testing prior to rolling out v.20.0.0.1038 of Intel RST windows application (the "Intel Rapid Storage Application").

Set-up:

* Z790 chipset
* 14th generation CPU
* Intel RST VMD enabled for all three controllers (SATA and two PCIe NVMe M2)
* latest version of BIOS (with the latest Intel fixes)
* v.20.0.0.1038 drivers confirmed via Windows Device Manager for all three controllers
* RAID arrays successfully seen in BIOS, Windows boots and works successfully off the multiple RAID arrays

However, the issues are:

1. Intel RST application can never be started. Always error 0xA00906B3.
2. The RstMWService (Intel Storage Middleware Service) does not start automatically (it is set for "Automatic"). Nor can it be manually started. Every time I try to start it, it fails with 1067 error. Event Viewer provides no information as to why it doesn't start, just:

"The Intel(R) Storage Middleware Service service terminated unexpectedly. It has done this 8 time(s)."
(obviously the # goes up with every reboot and attempt to start it)
That is usually there in the log just a split second after it detects all the RAID arrays successfully (upon reboot).

3. Uninstall of application and reinstall does not work. I have tried numerous times, both using the Intel SetupRST.exe which reinstalls the drivers (which are already v.20.0.0.1038) and the app (though sometimes the app doesn't get installed, if I've previously uninstalled it), and just getting the app from the Microsoft Store as the Intel installer instructs one to do if it fails to install. App installs. Reboot. Still issues #1 and #2.

This is quite clearly a critical issue. Quite obviously someone at Intel rolled out totally untested v.20.0.0.1038 of the drivers and/or application where the Windows application fails to run, as the Intel(R) Storage Middleware Service cannot be started.

Intel reps: this is an urgent and critical issue. Please provide a hotfix version where this issue is fixed for download and install, OR provide an earlier last known version of RST drivers and Windows app known to work, for Windows 10, 14th generation.

Do NOT tell me to look at support articles like https://www.intel.com/content/www/us/en/support/articles/000056936/memory-and-storage/intel-optane-memory.html , since those presume that Intel has released and made available for download a functional version. Intel has not. Following those steps doesn't work, as RstMWService cannot be started. Uninstalling and reinstalling the application (rebooting after every step, of course) does not fix it. The RstMWService is clearly broken and needs to be either hotfix updated, or Intel must provide an earlier (last known working) version for download. Again, this is urgent, as it is imperative to be able to see the status of RAID, build new RAID, rebuild RAID, etc. within the OS - the functionality in BIOS is limited, and there is no way to know of a drive failure without the application. Therefore, Intel, please provide a resolution here, a known working version (later or earlier) than v.20.0.0.1038 where the RstMWService can successfully start on a standard Windows 10 install on a Z790 chipset, 14th gen CPU.

Note: this issue is like described here https://www.intel.com/content/www/us/en/support/articles/000056936/memory-and-storage/intel-optane-memory.html , but in v.20.0.0.1038 Intel RST application can be never started, as RstMWService cannot start upon system reboot and cannot be started manually. So, it is more severe. It is not that it stops working. It just does not work at all.

UserRH · ‎12-15-2024

Output from Even Viewer on the RstMWService 1067 error details (one of many):

System

-	Provider

[ Name]

Service Control Manager

[ Guid]

{555908d1-a6d7-4695-8e1e-26931d2012f4}

[ EventSourceName]

Service Control Manager

-

EventID

7034

[ Qualifiers]

49152

Version

0

Level

2

Task

0

Opcode

0

Keywords

0x8080000000000000

-	TimeCreated

[ SystemTime]

XXXX

EventRecordID

7738

Correlation

-	Execution

[ ProcessID]

1796

[ ThreadID]

14572

Channel

System

Computer

XXXX

Security

-	EventData

param1

Intel(R) Storage Middleware Service

param2

8

5200730074004D00770053006500720076006900630065000000

Binary data:

In Words

0000: 00730052 004D0074 00530077 00720065
0010: 00690076 00650063 0000

In Bytes

0000: 52 00 73 00 74 00 4D 00 R.s.t.M.
0008: 77 00 53 00 65 00 72 00 w.S.e.r.
0010: 76 00 69 00 63 00 65 00 v.i.c.e.
0018: 00 00 ..

UserRH · ‎12-15-2024

Note that I have also tried downgrading the driver to 19.5.7.1058, which is the version that the mb manufacturer's (Gigabyte) application lists under its driver versions.

Still the same, RstMWService cannot start (1067) and Intel RST application (Windows 10) always fails with 0xA00906B3.

The system used to work just fine with the latest version v.20.0.0.1038 (it's had that since install, and it was fine), until it just randomly stopped working and hasn't worked since. (Nothing new has been installed or changed, just some drives moved around.)

So, please don't tell me to go to the mb manufacturer's listed version. I have already tried that (19.5.7.1058). Windows still boots, all the RAID arrays are seen and can be used, but the critical Intel RST Application cannot be started, due to RstMWService being unable to start automatically or manually.

Intel: as both the hardware (Z790 chipset, the integrated RST) and software (RST drivers, RST Application) manufacturer, please provide an urgent fix here by the way of a version where RstMWService is able to be started and works, so that the application will work. Or please provide directions how to force start RstMWService and force it to keep running, as clicking "start" under windows Services cannot start it, nor does it start when set to "Automatic" upon reboot.

UserRH · ‎12-15-2024

Every time upon reboot or manually attempting to start RstMWService, there will be 12 entries where it successfully sees every RAID volume and its status. Then 0.01 seconds after the last entry always it fails, with an error like this.

This is regardless of v19 or v20 driver version.

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Channel>System</Channel>

</System>

- <EventData>

<Data Name="param1">Intel(R) Storage Middleware Service</Data>

</EventData>

</Event>

Note that it can start fine, it can detect all RAID volumes and status thereof. It just won't keep running for more than 0.01 seconds, it'll always stop after the 12th successful log entry of having seen all the RAID volumes on the system.

Need a solution to force it to keep running, or a version (compatible with Z790, 14th gen) where Intel has tested it and has found that RstMWService will keep running reliably.

UserRH · ‎12-15-2024

For what it's worth, here's one of the Windows crashlogs of the RstMWService.

(Does Intel have a non-crashing, stable version of the RstMWService available that could be installed?)

Note: this happens with every version, not just 20.0.0.1038. With earlier version also.

Fault bucket 1851802909889988451, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: RstMwService.exe
P2: 20.0.0.1038
P3: 65674a94
P4: RstMwService.exe
P5: 20.0.0.1038
P6: 65674a94
P7: c0000005
P8: 0000000000152998
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7E4E.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7E7E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7E9E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7EAC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7EBC.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_RstMwService.exe_c585d134ab6a472d34d7b143a3afa91333d705b_d86332ea_d93108be-3d35-44f1-961f-50fde7cb76dc

Analysis symbol:
Rechecking for solution: 0
Report Id: 26270db1-8018-481b-b8b9-83eb1d2e87d2
Report Status: 268435456
Hashed bucket: 74b23984f0df623a09b2ecef6e070763
Cab Guid: 0

and

Faulting application name: RstMwService.exe, version: 20.0.0.1038, time stamp: 0x65674a94
Faulting module name: RstMwService.exe, version: 20.0.0.1038, time stamp: 0x65674a94
Exception code: 0xc0000005
Fault offset: 0x0000000000152998
Faulting process id: 0x1460
Faulting application start time: 0x01db4f7b9b869a0a
Faulting application path: C:\WINDOWS\System32\DriverStore\FileRepository\iastorvd.inf_amd64_80dcb7b409148fed\RstMwService.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\iastorvd.inf_amd64_80dcb7b409148fed\RstMwService.exe
Report Id: 26270db1-8018-481b-b8b9-83eb1d2e87d2
Faulting package full name:
Faulting package-relative application ID:

Full details from the .wer file:

Version=1
EventType=APPCRASH
EventTime=133788006247432888
ReportType=2
Consent=1
UploadTime=133788006248526207
ReportStatus=268435456
ReportIdentifier=d93108be-3d35-44f1-961f-50fde7cb76dc
IntegratorReportIdentifier=26270db1-8018-481b-b8b9-83eb1d2e87d2
Wow64Host=34404
NsAppName=RstMwService.exe
OriginalFilename=RstMwService.exe
AppSessionGuid=00001460-0000-002c-0a9a-869b7b4fdb01
TargetAppId=W:00068981d0f42843a4da6ce97f34a2fd5f3300000904!00004a6f04d5373ec17790e80254ebe3f9f3afbe7fa2!RstMwService.exe
TargetAppVer=2023//11//29:14:28:36!207f6f!RstMwService.exe
BootId=4294967295
TargetAsId=313
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=74b23984f0df623a09b2ecef6e070763
Response.BucketTable=4
Response.LegacyBucketId=1851802909889988451
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=RstMwService.exe
Sig[1].Name=Application Version
Sig[1].Value=20.0.0.1038
Sig[2].Name=Application Timestamp
Sig[2].Value=65674a94
Sig[3].Name=Fault Module Name
Sig[3].Value=RstMwService.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=20.0.0.1038
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=65674a94
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000152998
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19045.2.0.0.256.4
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=1606
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=16062703410c07199910e34af7a621a1
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=d288
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=d2889f2c7dcbcf889da0babef63de4a1
UI[2]=C:\WINDOWS\System32\DriverStore\FileRepository\iastorvd.inf_amd64_80dcb7b409148fed\RstMwService.exe
UI[5]=Close
UI[8]=Intel(R) Rapid Storage Technology Management Service stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\WINDOWS\System32\DriverStore\FileRepository\iastorvd.inf_amd64_80dcb7b409148fed\RstMwService.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[5]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[6]=C:\WINDOWS\System32\sechost.dll
LoadedModule[7]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[8]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[9]=C:\WINDOWS\System32\SETUPAPI.dll
LoadedModule[10]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[11]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[12]=C:\WINDOWS\System32\ole32.dll
LoadedModule[13]=C:\WINDOWS\System32\combase.dll
LoadedModule[14]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[15]=C:\WINDOWS\System32\win32u.dll
LoadedModule[16]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[17]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[18]=C:\WINDOWS\System32\USER32.dll
LoadedModule[19]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[22]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[23]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[24]=C:\Windows\System32\SspiCli.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=19045
OsInfo[3].Key=ubr
OsInfo[3].Value=5247
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=4
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=222977120
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.3636.19041.0-11.0.1000
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32530
OsInfo[19].Key=svolsz
OsInfo[19].Value=930
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=191206
OsInfo[22].Key=bldtm
OsInfo[22].Value=1406
OsInfo[23].Key=bldbrch
OsInfo[23].Value=vb_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.19041.5247.amd64fre.vb_release.191206-1406
OsInfo[30].Key=buildflightid
OsInfo[30].Value=8ed686bc-8db4-4694-8e5b-8446ac532c4f
OsInfo[31].Key=edition
OsInfo[31].Value=Enterprise
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=MD:283BAEF,ME:3037091,ME:3038C64,ME:3038CEC,MD:3039059,MD:30390AF
OsInfo[34].Key=fconid
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Intel(R) Rapid Storage Technology Management Service
AppPath=C:\WINDOWS\System32\DriverStore\FileRepository\iastorvd.inf_amd64_80dcb7b409148fed\RstMwService.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=C4DE118BFEDFE1779D4170FC4D72E3D8
MetadataHash=-1083109393

UserRH · ‎12-15-2024

The only workaround I've found is to set the RstMWService to continually keep restarting.

Services setting on Recovery tab:
Restart after First, Second and Subsequent failures.

Restart after 0 minutes (has to be, as it runs at most for 2-3 seconds at a time)

This way the service continually keep restarting, several 100 times per minute (at times every millisecond). But after a few tries RST Application can be started (it'll give both the 0xA00906B3 error in one dialog box, while actually starting) and used... though not sure how reliable it is, esp. if building new RAID, rebuilding RAID, etc., with the background service being a continual stop-and-go. It is also quickly filling up the Windows logs with the application crash logs.

Intel: there has to be a better solution than setting RstMWService to keep constantly restarting almost every second. Please provide a solution/workaround. This is clearly a widely experienced problem, as it's been reported here in multiple other posts, while Intel has done nothing to provide a fix (release a new more stable version of RstMWService that doesn't need to be continually restarted).

This solution to keep RST running is not sustainable, as it takes up about 20% of CPU and makes the system run extra hot, with Service Host: Windows Error Reporting writing the log files constantly. It is also very quickly wearing out SSD drives with the non-stop writing of the Intel RstMWService crash dumps (many hundred every minute).

UserRH · ‎12-18-2024

Still no response and any solutions or workaround?

I've found that the event that causes this irreparable error is putting in a drive that was previously part of an RST RAID array in a different system, removing it from RAID (at BIOS), and then doing anything with it (such as reformat, check for health, etc.). While it's there RST still works. Once that non-RAID drive is removed (after format or what not was done), RST stops working and always has this error for the rest of eternity. In other words, this is a very common error easily replicable in a test lab with just four drives and two RAID1s. And it is quite severe. Just doing so once effectively bricks the RST Middleware Service for good, with no workaround (uninstalling RST app [can't outright remove drivers, of course - then couldn't boot], downgrading drivers to later version, reinstalling drivers and/or RST application, nothing works - whatever is making it fail right after reading and recognizing all the arrays, drives and volumes is still there and doesn't get removed; I am guessing some registry or config file entry somewhere that RST MW Svc doesn't know how to handle and chokes on, due to not being QA tested prior to release).

espcs · ‎04-04-2025

Same thing. Was intermittent in the beginning, then could never get it to run.

Windows 10

Asus TUF Z790

Raid 1 on sata ssd's

Raid 1 on sata hdd's

Removed everything, reinstalled everything, latest drivers from Asus for my board, 20.2.1.1016.

Latest Storage Manager from Intel in MS Store... 20.0.1019.0

Tried every driver version I had from install. Would not run!

Removed Norton 360 totally! Works like a champ!

I will try to reinstall later, but this seems to have fixed my Storage Manager issues and should fix the DNS issues Norton is causing as well.

I can stop and start it over and over and RST runs like a champ.

espcs · ‎04-05-2025

Update.

Reinstalled Norton360. Problem exists again. RstMwService.exe will not run.

I turned off both Product Tamper Protection settings. Disabled every thing I could possibly disable. Auto scan, safe web, firewall, email protection, everything.....

Even added it to the scan exclusions.

RstMwService.exe will not run.

As soon as I removed Norton 360 again, RstMwService.exe started working again. Did not even need to reboot.

So... who's problem is this, Norton's or Intel's? Some one let me know so I know where to find resolution.....

UserRH · ‎04-05-2025

Thanks for sharing!

So glad that you found a workaround - removing Norton 360 in your case.

I am not running anything Norton, and have never had any Norton bloatware installed on my system. I even Ctrl-F'ed regedit to search for any traces of "norton" - none to be had in registry, so I'm quite sure my system is clean of the Norton taint. Yet just like you: At first would work. Then get more intermittent. Then stop entirely, fail a few milliseconds after start to be precise. If I restored back to a few days earlier system (when it was still working), it would work again. For a while, then stop. (Not related to any windows updates or any software installed. I literally make no changes to the system, and over a few days it just stops working again.) I kept restoring back to previous system disk version, but after a few weeks couldn't keep doing that every few days.

I think the problem is still Intel, as part of any basic QA they should have tested the software on systems with popular antivirus programs, such as Norton. Though in your case, you have a workaround - just stop using Norton (it's huge bloatware that'll cause all sorts of problems, IMHO at least). For me, alas, no such luck. I tried disabling my AV program, but still no go on RST. Though I guess I can try to totally uninstall it (while so, of course having the system completely disconnected from the Internet), to see if it's not just Norton but any AV program specific...though if the AV was stopping it, it should be in the logs, and it's not.

Here's what I suggest you do: open a trouble ticket with Intel. Send them your system crash logs. They will investigate, set-up a test station with same environment as yours to try to replicate the problem, and hopefully release a new version that is actually working. I've had an Intel TT on this open for several months, had one new supposedly "fixed" release (non-public) sent to me, but that still doesn't work. Now am waiting for them to go through yet more logs and have the developers fix their buggy code (again, for real this time I hope) and release another new version to try. The more customers open tickets with Intel, the more aware Intel will be of just how serious this problem is and that they can't keep dilly-dallying around and need to push their developers to fix this without further delay.

espcs · ‎04-05-2025

It would be interesting to know if removing your AV completely made a difference. I have the Windows stuff enabled for what it is worth.

I totally agree on the bloat and bs marketing Norton does. It is the most cost effective and low support method for me to provide license to 7 other users (family members) who are not technical. This issue and since they have messed the back-up stuff so much... I just need to find a suitable replacement.

I am preparing to try McAfee trial just as a test.

UserRH · ‎04-05-2025

First I tried stopping my AV (Avira) real-time protection. No go.

Then I tried adding IntelRstMWService to the services not scanned list. Still no go.

Then I uninstalled it completely. Rebooted. Made sure it's fully gone.

Still no go. IntelRstMWService (set to auto start) is not running. Trying to start it, as always, results in "Error 1067" every time. In the logs it shows it only runs for a few milliseconds before crashing. (Same as before.)

So, while in your case removing Norton 360 helped, in my case removing my AV (Avira) did not.

I suspect there is something, may be some common element, in Norton 360 that is also present in some other (unknown) software installed on my end (though my system is rather lean and clean) that may be conflicting with the Intel RST MW Service. Just a guess.

I suggest you open an official ticket on this with Intel. The more users have active tickets open on this, the more development resources they are likely to dedicate to fixing their buggy code and making this critical service work.

In the meanwhile, if you need to use the Intel RST Windows software, for the Intel RST MW Service under the Recovery tab (in Windows Services), if you set it to restart after first/second/subsequent failures (always), with a restart counter at 0 minutes, it'll keep restarting instantly the moment it crashes. Then at least you can run the RST software. But, it'll keep flooding your system logs with countless entries every second (as it restarts too many times to count, each and every second) and add a good 30% to your CPU load due to the constant crashes and restarts. So, that is not something to keep so permanently. Just as a rather poor workaround if you need to use the RST software, such as to check on your RAID status. Bit of a warning, though: I wouldn't go making any changes with the Windows RST software while the MW service is like this (constantly crashing and restarting, many times each second), as if that call to the middleware happens while the software is crashing or has crashed, it may totally nuke your RAID, or worse. To make any changes to your RAID arrays, you have to make do with the very limited options in the BIOS. That is, until Intel finally fixes this absolutely critical, major bug.

espcs · ‎04-09-2025

Sorry that did not change your situation, at least it is now ruled out. McAfee installed and ran ok and RstMWService/IRST operated with McAfee. But McAfee presented other issues that made it undesirable.

I did open a case with Intel as you recommended, let's see where this goes. Currently I am running on the Windows out of box stuff.