Help! RST creating RAID1 caused BSOD

Memory & Storage Intel® Rapid Storage Technology (Intel® RST)
1

Help! RST creating RAID1 caused BSOD

Recently I upgraded my 10 years old PC with I5-3450 CPU and 2 RAID1 arrays (one 4 TB and one 3TB). The new one’s configuration -

Intel I7 13700;

ASUS ROG Strix Z690-E Gaming WiFi 6E LGA 1700 ATX gaming motherboard;

G.SKILL Ripjaws S5 Series 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6400;

SAMSUNG E 1TB 870 EVO 2.5 SATA SSD;

The Windows 11 prof 64 bit

The install was good and the 1st RAID1 (3TB) array was migrated smoothly; but the 2nd RAID1 (4TB) array was nightmare. The BIOS and RST recognized the 2 disks separately, but when RST try to create RAID1 array Windows crashed with BSOD error message ‘System thread exception not handled’. I tried to use BIOS RST and Optine under Win11 but none of them worked. Nevertheless to say I lost all the data on the array. If I remove the 2 disks Windows will back to normal. These 2 disks was RAID1 array on the old PC so they should be fine. I even got a 3rd 4TB disk just to prove the issue was not with the disk. I attached log file here. Please help! Thanks.

2023:07:30 14:30:35:617:
2023:07:30 14:30:35:617: >>>Dumping deffered logs
2023:07:30 14:30:35:608: Adding Windows8-x64 (0x90000602 == 0x80000602)
2023:07:30 14:30:35:608: Adding W2K12-x64 (0xA0000602 == 0x80000602)
2023:07:30 14:30:35:608: Adding Windows8.1-x64 (0x90000603 == 0x80000603)
2023:07:30 14:30:35:608: Adding W2K12R2-x64 (0xA0000603 == 0x80000603)
2023:07:30 14:30:35:608: Adding Windows10-x64 (0x90000A00 == 0x80000A00)
2023:07:30 14:30:35:608: Adding W2K16-x64 (0xA0000A00 == 0x80000A00)
2023:07:30 14:30:35:611: Banned Applications loaded
2023:07:30 14:30:35:613: Checking .NET version…
2023:07:30 14:30:35:613: Expected version: v2.0.50727
2023:07:30 14:30:35:613: Found registry key for the expected .NET version.
2023:07:30 14:30:35:613: Checking .NET version…
2023:07:30 14:30:35:613: Expected version: v3.0
2023:07:30 14:30:35:613: Found registry key for the expected .NET version.
2023:07:30 14:30:35:613: Checking .NET version…
2023:07:30 14:30:35:613: Expected version: v3.5
2023:07:30 14:30:35:613: Found registry key for the expected .NET version.
2023:07:30 14:30:35:613: Checking .NET version…
2023:07:30 14:30:35:613: Expected version: v4\Client
2023:07:30 14:30:35:613: Found registry key for the expected .NET version.
2023:07:30 14:30:35:613: Checking .NET version…
2023:07:30 14:30:35:613: Expected version: v4\Full
2023:07:30 14:30:35:613: Found registry key for the expected .NET version.
2023:07:30 14:30:35:613: Checking .NET version…
2023:07:30 14:30:35:613: Expected version: v4.5\Client
2023:07:30 14:30:35:613: Found registry key for the expected .NET version.
2023:07:30 14:30:35:613: Looking for .NET version 4.5 or above
2023:07:30 14:30:35:613: Found version: 4.8.09032
2023:07:30 14:30:35:613: Checking .NET version…
2023:07:30 14:30:35:613: Expected version: v4.5\Full
2023:07:30 14:30:35:613: Found registry key for the expected .NET version.
2023:07:30 14:30:35:613: Looking for .NET version 4.5 or above
2023:07:30 14:30:35:613: Found version: 4.8.09032
2023:07:30 14:30:35:614: Loading saved properties
2023:07:30 14:30:35:616: W VC2015++ 32bit detected, skip it
2023:07:30 14:30:35:616: W VC2015++ 64bit detected, skip it
2023:07:30 14:30:35:616: Effective command line: “C:\Users\dxr\Downloads\SetupRST (3).exe”
2023:07:30 14:30:35:617: >>> Log start
2023:07:30 14:30:35:617: Mutex with given name doesn’t exist. Creating new one.

2023:07:30 14:30:35:617: Obtained mutex succesfully.
2023:07:30 14:30:35:617: Single-instance mutex has been obtained
2023:07:30 14:30:35:618: Core version: 2.5.55
2023:07:30 14:30:35:618: Setup version: 16.8.0.5
2023:07:30 14:30:35:618: Command line: “C:\Users\dxr\Downloads\SetupRST (3).exe”
2023:07:30 14:30:35:618: OS data: 10.0 64-bit
2023:07:30 14:30:35:618: System up time: 13487 sec
2023:07:30 14:30:35:618: Reboot pending: No
2023:07:30 14:30:35:618: Current UI language: 0409
2023:07:30 14:30:35:618: Language folder: C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp
2023:07:30 14:30:35:628: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\ar-SA\IntelCommon.dll. Lang 0401. Rank 0
2023:07:30 14:30:35:634: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\cs-CZ\IntelCommon.dll. Lang 0405. Rank 0
2023:07:30 14:30:35:640: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\da-DK\IntelCommon.dll. Lang 0406. Rank 0
2023:07:30 14:30:35:645: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\de-DE\IntelCommon.dll. Lang 0407. Rank 0
2023:07:30 14:30:35:651: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\el-GR\IntelCommon.dll. Lang 0408. Rank 0
2023:07:30 14:30:35:656: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\en-US\IntelCommon.dll. Lang 0409. Rank 3
2023:07:30 14:30:35:662: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\es-ES\IntelCommon.dll. Lang 0C0A. Rank 0
2023:07:30 14:30:35:667: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\fi-FI\IntelCommon.dll. Lang 040B. Rank 0
2023:07:30 14:30:35:672: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\fr-FR\IntelCommon.dll. Lang 040C. Rank 0
2023:07:30 14:30:35:678: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\he-IL\IntelCommon.dll. Lang 040D. Rank 0
2023:07:30 14:30:35:683: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\hu-HU\IntelCommon.dll. Lang 040E. Rank 0
2023:07:30 14:30:35:689: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\it-IT\IntelCommon.dll. Lang 0410. Rank 0
2023:07:30 14:30:35:694: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\ja-JP\IntelCommon.dll. Lang 0411. Rank 0
2023:07:30 14:30:35:699: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\ko-KR\IntelCommon.dll. Lang 0412. Rank 0
2023:07:30 14:30:35:704: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\nb-NO\IntelCommon.dll. Lang 0414. Rank 0
2023:07:30 14:30:35:709: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\nl-NL\IntelCommon.dll. Lang 0413. Rank 0
2023:07:30 14:30:35:715: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\pl-PL\IntelCommon.dll. Lang 0415. Rank 0
2023:07:30 14:30:35:722: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\pt-BR\IntelCommon.dll. Lang 0416. Rank 0
2023:07:30 14:30:35:728: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\pt-PT\IntelCommon.dll. Lang 0816. Rank 0
2023:07:30 14:30:35:735: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\ru-RU\IntelCommon.dll. Lang 0419. Rank 0
2023:07:30 14:30:35:741: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\sv-SE\IntelCommon.dll. Lang 041D. Rank 0
2023:07:30 14:30:35:747: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\th-TH\IntelCommon.dll. Lang 041E. Rank 0
2023:07:30 14:30:35:753: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\tr-TR\IntelCommon.dll. Lang 041F. Rank 0
2023:07:30 14:30:35:759: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\zh-CN\IntelCommon.dll. Lang 0804. Rank 0
2023:07:30 14:30:35:765: Found C:\Users\dxr\AppData\Local\Temp\IIFCC63.tmp\zh-TW\IntelCommon.dll. Lang 0404. Rank 0
2023:07:30 14:30:35:766: Loading language 0409
2023:07:30 14:30:35:774: Setup mode: Installation
2023:07:30 14:30:35:774: === Device Enumerator: Starting enumerating all devices of type PCI
2023:07:30 14:30:35:775: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_A703&SUBSYS_86941043&REV_01
2023:07:30 14:30:35:775: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AC8&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:775: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AA3&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:775: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AF0&SUBSYS_00948086&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_09AB&SUBSYS_00000000&REV_00
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_10DE&DEV_0FB8&SUBSYS_8C981462&REV_A1
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7ACE&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AB9&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7ABA&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_1B21&DEV_0612&SUBSYS_858D1043&REV_02
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AD0&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7ABC&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_A77F&SUBSYS_86941043&REV_00
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AA7&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AB0&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7ACD&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_A77D&SUBSYS_86941043&REV_01
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AB8&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AA4&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_10DE&DEV_1D01&SUBSYS_8C981462&REV_A1
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AE0&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:776: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AE8&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:777: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_15F3&SUBSYS_87D21043&REV_03
2023:07:30 14:30:35:777: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7ACC&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:777: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7A84&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:777: === Device Enumerator: Found device with first hardware id: PCI\VEN_8086&DEV_7AC0&SUBSYS_86941043&REV_11
2023:07:30 14:30:35:777: Setting min supported .NET version (4.5 for < RST_15.0 | 4.6 for >= RST_15.0)
2023:07:30 14:30:35:777: Product version is: 16.8.5.1014
2023:07:30 14:30:35:777: .NET 4.6 is not required
2023:07:30 14:30:35:777: Looking for OS: 6.2 6.3 10.0
2023:07:30 14:30:35:777: OS check passed
2023:07:30 14:30:35:777: Checking .NET version…
2023:07:30 14:30:35:778: Expected version: v4.5\Client
2023:07:30 14:30:35:778: Found registry key for the expected .NET version.
2023:07:30 14:30:35:778: Looking for .NET version 4.5 or above
2023:07:30 14:30:35:778: Found version: 4.8.09032
2023:07:30 14:30:35:778: .NET version check passed
2023:07:30 14:30:35:778: Resolving driver source
2023:07:30 14:30:35:778: Using embedded driver(s). Temp source is ‘C:\Users\dxr\AppData\Local\Temp\IIFCD00.tmp’
2023:07:30 14:30:35:827: Using folder ‘C:\Users\dxr\AppData\Local\Temp\IIFCD00.tmp’ as the driver source
2023:07:30 14:30:35:828: Scanning all active devices
2023:07:30 14:30:35:843: Scanning x64\iaAHCIC.inf (Name: AHCI64, Version: 16.8.5.1014)
2023:07:30 14:30:35:843: Section with the best match: INTEL.NTamd64.6.2
2023:07:30 14:30:35:843: Device: PCI\VEN_8086&DEV_9D03&CC_0106 (Intel(R) 6th Generation Core Processor Family Platform I/O SATA AHCI Controller)
2023:07:30 14:30:35:843: Device: PCI\VEN_8086&DEV_A102&CC_0106 (Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller)
2023:07:30 14:30:35:844: Device: PCI\VEN_8086&DEV_A103&CC_0106 (Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller)
2023:07:30 14:30:35:844: Device: PCI\VEN_8086&DEV_A282&CC_0106 (Intel(R) 300 Series Chipset Family SATA AHCI Controller)
2023:07:30 14:30:35:844: Device: PCI\VEN_8086&DEV_9DD3&CC_0106 (Intel(R) 300 Series Chipset Family SATA AHCI Controller)
2023:07:30 14:30:35:844: Device: PCI\VEN_8086&DEV_A352&CC_0106 (Intel(R) 300 Series Chipset Family SATA AHCI Controller)
2023:07:30 14:30:35:844: Device: PCI\VEN_8086&DEV_A353&CC_0106 (Intel(R) 300 Series Chipset Family SATA AHCI Controller)
2023:07:30 14:30:35:844: MUP OS bits: 0x1B6000
2023:07:30 14:30:35:849: Scanning x64\iaStorAC.inf (Name: RAID64, Version: 16.8.5.1014)
2023:07:30 14:30:35:849: Section with the best match: INTEL.NTamd64.6.2
2023:07:30 14:30:35:849: Device: PCI\VEN_8086&DEV_2822&CC_0104 (Intel(R) Chipset SATA/PCIe RST Premium Controller)
2023:07:30 14:30:35:850: Device: PCI\VEN_8086&DEV_282A&CC_0104 (Intel(R) Chipset SATA/PCIe RST Premium Controller)
2023:07:30 14:30:35:850: Device: PCI\VEN_8086&DEV_9D07&CC_0104 (Intel(R) Chipset SATA/PCIe RST Premium Controller)
2023:07:30 14:30:35:850: Device: PCI\VEN_8086&DEV_A107&CC_0104 (Intel(R) Chipset SATA/PCIe RST Premium Controller)
2023:07:30 14:30:35:850: Device: PCI\VEN_8086&DEV_A106&CC_0104 (Intel(R) Chipset SATA/PCIe RST Premium Controller)
2023:07:30 14:30:35:850: Device: PCI\VEN_8086&DEV_A28E&CC_0104 (Intel(R) Chipset SATA/PCIe RST Premium Controller)
2023:07:30 14:30:35:850: Device: PCI\VEN_8086&DEV_A286&CC_0104 (Intel(R) Chipset SATA/PCIe RST Premium Controller)
2023:07:30 14:30:35:850: Device: PCI\VEN_8086&DEV_9DD7&CC_0104 (Intel(R) Chipset SATA/PCIe RST Premium Controller)
2023:07:30 14:30:35:850: Device: PCI\VEN_8086&DEV_A356&CC_0104 (Intel(R) Chipset SATA/PCIe RST Premium Controller)
2023:07:30 14:30:35:850: Device: PCI\VEN_8086&DEV_A357&CC_0104 (Intel(R) Chipset SATA/PCIe RST Premium Controller)
2023:07:30 14:30:35:850: Device: PCI\VEN_8086&CC_0108 (Intel(R) NVMe Controller)
2023:07:30 14:30:35:850: MUP OS bits: 0x1B6000
2023:07:30 14:30:35:854: Scanning x64\iaStorSW.inf (Name: X64_IASTORSW, Version: 16.8.5.1014)
2023:07:30 14:30:35:854: Section with the best match: INTEL.ntamd64
2023:07:30 14:30:35:855: Device: SWC\VID8086&PID2822&SID0001 (Intel(R) Pinning Shell Extensions)
2023:07:30 14:30:35:855: MUP OS bits: 0x1B6000
2023:07:30 14:30:35:858: Scanning x64\iaStorSwExt.inf (Name: X64_IASTORSWEXT, Version: 16.8.5.1014)
2023:07:30 14:30:35:858: Section with the best match: INTEL.ntamd64.10.0
2023:07:30 14:30:35:859: Device: PCI\VEN_8086&DEV_2822&CC_0104 (Intel(R) RST Software Components Extension)
2023:07:30 14:30:35:859: Device: PCI\VEN_8086&DEV_282A&CC_0104 (Intel(R) RST Software Components Extension)
2023:07:30 14:30:35:859: Device: PCI\VEN_8086&DEV_9D07&CC_0104 (Intel(R) RST Software Components Extension)
2023:07:30 14:30:35:859: Device: PCI\VEN_8086&DEV_A107&CC_0104 (Intel(R) RST Software Components Extension)
2023:07:30 14:30:35:859: Device: PCI\VEN_8086&DEV_A106&CC_0104 (Intel(R) RST Software Components Extension)
2023:07:30 14:30:35:859: Device: PCI\VEN_8086&DEV_A28E&CC_0104 (Intel(R) RST Software Components Extension)
2023:07:30 14:30:35:859: Device: PCI\VEN_8086&DEV_A286&CC_0104 (Intel(R) RST Software Components Extension)
2023:07:30 14:30:35:859: Device: PCI\VEN_8086&DEV_9DD7&CC_0104 (Intel(R) RST Software Components Extension)
2023:07:30 14:30:35:859: Device: PCI\VEN_8086&DEV_A356&CC_0104 (Intel(R) RST Software Components Extension)
2023:07:30 14:30:35:859: Device: PCI\VEN_8086&DEV_A357&CC_0104 (Intel(R) RST Software Components Extension)
2023:07:30 14:30:35:859: MUP OS bits: 0x180000
2023:07:30 14:30:35:861: E Win32 exception occurred!!
2023:07:30 14:30:35:861: Error code: 0x4E24 (20004)
2023:07:30 14:30:35:861: Error text: ‘’
2023:07:30 14:30:35:861: Extended error text: ‘Error in device matching’
2023:07:30 14:30:35:861: Debug info: ‘Setup.cpp (919)’
2023:07:30 14:30:35:861: Node is not valid. Failed to resolved error string from config file error: 20004
2023:07:30 14:30:35:861: propertyId: 8095, serror: This platform is not supported. errorCode: 20004
2023:07:30 14:30:35:875: Reading storyboard
2023:07:30 14:30:35:875: Page count: 15
2023:07:30 14:30:35:875: Added: Welcome
2023:07:30 14:30:35:875: Added: Modify
2023:07:30 14:30:35:875: Added: OptaneEnabledError
2023:07:30 14:30:35:875: Added: CpuAttachedStorageError
2023:07:30 14:30:35:875: Added: CpuAttachedStorageSystemVolumeError
2023:07:30 14:30:35:875: Added: SataPort6Or7UsedError
2023:07:30 14:30:35:875: Added: Warning
2023:07:30 14:30:35:876: Added: License
2023:07:30 14:30:35:876: Added: Readme
2023:07:30 14:30:35:876: Added: Destination
2023:07:30 14:30:35:876: Added: Confirm
2023:07:30 14:30:35:876: Added: Progress
2023:07:30 14:30:35:876: Added: InjectionFailedWarning
2023:07:30 14:30:35:876: Added: Finish
2023:07:30 14:30:35:876: Added: Error
2023:07:30 14:30:35:876: Reading string map
2023:07:30 14:30:35:876: No string map present
2023:07:30 14:30:35:896: Showing page: Error
2023:07:30 14:34:04:457: Copied to clipboard: ‘C:\Users\dxr\Intel\Logs’

2

Hello @dxr9

Thank you for posting on the Intel️® communities. We would be more than glad to help you with your issue.

In order to have a better understanding of your issue, please provide me with the following:

1.      Did you use in the OLD PC the BIOS configuration or Optane to create the RAID?

2.      Which driver are you using to create the RAID. We suggest using the RST driver from the motherboard manufacturer instead of our driver.

3.      How did you do the process of the migration from the old computer to the new one? Please provide us with all the details.

Best regards,

Isaac Q.

Intel Customer Support Technician

3

Hi Isaac,

Thanks for the response.  Please see my answer below -

1.      Did you use in the OLD PC the BIOS configuration or Optane to create the RAID?

Actually I used Intel RST app to create the 2 RAID1 arrays in my old PC. Looks like that app is replace by Optane.

2.      Which driver are you using to create the RAID. We suggest using the RST driver from the motherboard manufacturer instead of our driver.

I tried both RST drivers from the MB manufacture also from Intel. What puzzled me is that the 3TB RAID1 array was migrated np issue but the 4TB array was never be able to migrate.

3.      How did you do the process of the migration from the old computer to the new one? Please provide us with all the details.

I initialize and format the 2 4TB (both from Seagate 4000DM000) disks on another PC, then add them to my new PC and make sure they are recognized by TRS in BIOS also by Win11 disk management. Next I open Optane and see both disks there as non RAID disks, then I create RAID1 in Optane, a moment later the Win11 crashed with BSOD with error message ‘System thread exception not handled’.

4

Hello @dxr9

Thank you for the information provided.

I’ll look into the issue from within our team and get back to you soon with additional information.

Best regards,

Isaac Q.

Intel Customer Support Technician

5

Hello @dxr9

Thank you for your patience.

According to our research, the only recommendation we can offer is to create a new RAID volume in case the steps on the User Guide page 110 do not work.

Best regards,

Isaac Q.

Intel Customer Support Technician

6

Hi Isaac,

My problem is I can’t create a new RAID1 (the old one is gone and I accept that). RST caused Windows crash with BSOD when creating RAID1. You can see it in the log I posted in the original post. Here is the exert during RAID1 creation -

2023:07:30 14:30:35:859: MUP OS bits: 0x180000
2023:07:30 14:30:35:861: E Win32 exception occurred!!
2023:07:30 14:30:35:861: Error code: 0x4E24 (20004)
2023:07:30 14:30:35:861: Error text: ‘’
2023:07:30 14:30:35:861: Extended error text: ‘Error in device matching’
2023:07:30 14:30:35:861: Debug info: ‘Setup.cpp (919)’
2023:07:30 14:30:35:861: Node is not valid. Failed to resolved error string from config file error: 20004
2023:07:30 14:30:35:861: propertyId: 8095, serror: This platform is not supported. errorCode: 20004
2023:07:30 14:30:35:875: Reading storyboard
2023:07:30 14:30:35:875: Page count: 15

7

Hello @dxr9

Thank you for your reply.

We understand how frustrating this issue can be, but we are going to do our best to help you.

I will investigate the issue internally and promptly share additional details with you.

Best regards,

Isaac Q.

Intel Customer Support Technician

8

Thank you for your patience.

We would like to know some information, just to have all the details possible. Please provide us with the following information:

1.     When is the issue occurring?

2.     Is it when you are trying to make the migration?

3.     Have you tried to create the RAID from zero as we suggested you?

4.     Are you having any issues at the time of the RAID creation?

Also fee free to check this article related to the ERROR code you are experiencing:

Why does the error message SYSTEM_THREAD_EXCEPTION_NOT_HANDLED appear and how to resolve it?

Best regards,

Isaac Q.

Intel Customer Support Technician

9

Hi Isaac thanks for the following up.

Please see my answers below -

1.     When is the issue occurring?

After windows 11 was installed on a new PC and the 1st RAID1 array was created successfully. The issue occurred during  the 2nd RAID1 array creation.

2.     Is it when you are trying to make the migration?

The 2nd array migration has already failed and I was trying to create a new array from scratch.

3.     Have you tried to create the RAID from zero as we suggested you?

Yes I did and and the issues was in creating RAID from zero

4.     Are you having any issues at the time of the RAID creation?

The 1st array was created fine but I was never be able to create 2nd array

BTW, I post a a video on YouTube so you can see it -

https://youtu.be/REwbpuJ9zPM

Thanks again for your help!

10

Thank you for the information provided.

I will investigate the matter internally and will provide you with further details shortly.

Best regards,

Isaac Q.

Intel Customer Support Technician

11

Hello @dxr9

Thank you for your reply.

We need more information to give you a solution. Sorry to take so long to find a solution to your problem, but we are trying to do the best we can.

In this occasion please, provide us with the following:

·      Please, enable memory dump settings so we can get a full memory dump in order to identify the root cause.

·      Section: Enable memory dump settings> Generate a kernel or complete crash dump - Windows Client | Microsoft Learn

·      Once you have been able to create the MEMORY.dmp file, share that file with us.

Once we have that file we will evaluate that information and will be back with you once we have more details.

Best regards,

Isaac Q.

Intel Customer Support Technician

12

Hello @ dxr9

We hope you are doing fine.

Were you able to check the previous post?

We requested before the MEMORY.dmp file for more investigation.

Let us know if you still need assistance.

Best regards,

Isaac Q.

Intel Customer Support Technician

13

Greetings, dxr9,

Trust all is well on your end.

We wish to inform you that we have not received any further updates from your side. Consequently, we are in the process of concluding this particular discussion thread. Should you find the need for additional information or support, we kindly suggest initiating a new inquiry. Please be aware that this thread will no longer be subject to active monitoring.

Warm regards,

Isaac Q.

Technician, Intel Customer Support