***BUG REPORT*** DSA corrupt message with NUC9i9QNX 905P

[BHarr8]

I get the following message from DSA on my NUC9i9QNX with a 905P SSD:


I do not need support, I am just reporting a bug.

[BHarr8]

Looks like a few things are currently corrupted:

[BHarr8]

The more I look into this the worse it gets. According to Intel's own documentation this software should not even be provided for the 905P or 800P yet in my NUC9i9QNX (905p) and my NUC8i7HVK (2 800P) it is being offered via DSA:

Customer Support Service Changes for NAND SSDs during Solidigm™... (intel.com)

Click "Show all" to see all supported drives. Best I can tell this tool is designed to support NAND based Intel SSDs now being supported by SK Hynix. The fact that DSA is recommending this tool at all for Optane drives seems to also be a bug.

[Steven_Intel]

Hello BHarr8,

Thank you for posting on the Intel® communities.

We are going to review the information you have provided. As soon as I have an update, I will let you know.

Best regards,

Steven G.

Intel Customer Support Technician.

[Steven_Intel]

Hello BHarr8,

Even though you are not asking for support, are you willing to help us check further this issue? If you are willing to, please help us with the following steps:

• If those apps are installed in your PC, please send us a screenshot of the apps and features showing all Intel apps you have.
• Perform a clean installation of IDSA and then get the IDSA folders after the installation.

Best regards,

Steven G.

Intel Customer Support Technician.

[BHarr8]

Pretty easy, wont take too long.

[BHarr8]

The 3 attached zips are from the 3 systems I am receiving this erroneous DSA recommendation on. Inside each zip is also a screenshot of the other installed Intel apps.

While I have you here, I am also posting a screenshot of what happens when you try to use the Intel Memory and Storage tool on an NUC8i7HVK with 2 800p drives in RAID 0. I reported this bug before but since Intel uses simulated systems for testing they were unable to replicate this problem. It has persisted across multiple driver builds, multiple Memory and Storage tool builds, multiple OS reinstalls and multiple OS builds. It is a real bug.

[Steven_Intel]

Hello BHarr8,

We highly appreciate the information provided.

We are going to review all the information and I will let you know as soon as I have an update.

Please feel free to reply if you have any concerns.

Best regards,

Steven G.

Intel Customer Support Technician.

[Steven_Intel]

Hello BHarr8,

By any chance, could you please try installing the latest IDSA version 22.3.20 and try again?

If the issue persists, and you are still willing to help us, please perform a clean installation of IDSA by using the uninstaller https://www.intel.com/content/www/us/en/download/19333/intel-driver-support-assistant-uninstaller.ht... and get the IDSA folders.

Best regards,

Steven G.

Intel Customer Support Technician.

[BHarr8]

Nothing has changed including the bug that has existed for more than a year now.

DSA folder also attached. I will not be able to provide any further assistance unless you can provide a picture of the NUC8i7HVK with 2 118GB 800P drives installed. Support can easily replicate both bugs I am reporting on actual physical hardware.

[Steven_Intel]

Thank you for the information provided.

We will keep working on this and let you as soon as we have an update.

We appreciate your help.

Best regards,

Steven G.

Intel Customer Support Technician.

[BHarr8]

You can add an additional problem to this list. V2.0 of Intel Memory and Storage Tool instantly crashes on this system.

This is due to mishandling of the error I posted above (and have been posting about for a year).

In V.1X Intel Memory and Storage Tool would fail to enumerate the 2 800p Optane drives in RAID 0 but in V2.X the tool outright crashes when it hits the same enumeration failure.

[BHarr8]

I just checked and 2 p1600x drives in RAID 0 also cause Intel Memory and Storage Tool to crash. Here are the 2 errors that I get:

Application: IntelMAS.UI.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at System.Linq.Enumerable.First[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable`1<System.__Canon>)
at IntelMAS.UI.Devices.DeviceList+<Scan>d__11.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at IntelMAS.UI.MainPanelViewModel+<>c__DisplayClass0_0+<<-ctor>b__4>d.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at MvvmHelpers.Utils+<SafeFireAndForget>d__2.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at IntelMAS.UI.App.Main()


Faulting application name: IntelMAS.UI.exe, version: 2.0.330.0, time stamp: 0x9e124772
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1737, time stamp: 0xa76f6e7b
Exception code: 0xe0434352
Fault offset: 0x0000000000034fd9
Faulting process id: 0x1230
Faulting application start time: 0x01d86eaff77f9725
Faulting application path: C:\Program Files\Intel\Intel(R) Memory and Storage Tool\IntelMAS.UI.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 11dd0a14-b883-4cc3-8c51-97b509f7c5f2
Faulting package full name:
Faulting package-relative application ID: