- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm a tech. (make captain obvious assumptions) Had a nice intel RAID 5 for well over a decade in one form or another. Intel RST has always worked as expected, but this build I can't get it to install, (or uninstall without using a 3rd party uninstalling app). The APP will not open, no flash screen, nothing. Tried all ALL compatibility modes. Tried over versions. RAID works fine, but I'd like to change some settings that RST will permit me too.
Windows 10.0.17763 Build 17763
8700K
ASrock Z390 Phantom Gaming 4 (latest bios, v4.0)
64GB RAM
Samsung NVMe 970 Evo 500GB
10TB WD X 3 in a working RAID 5. (Tried another RAID 5 too, same problems, not related to RAID)
Every time I try to open it, reinstall it, uninstall it (without 3rd party uninstaller) there is an event log, here are the various ones associated with it. Googled my heart out.
Help.
Faulting application name: IAStorDataMgrSvc.exe, version: 17.2.0.1009, time stamp: 0x5c62d515
Faulting module name: KERNELBASE.dll, version: 10.0.17763.592, time stamp: 0xaee8f822
Exception code: 0xe0434352
Fault offset: 0x0000000000039129
Faulting process id: 0x38e4
Faulting application start time: 0x01d5291837064ef3
Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: dbe7e00c-1e0e-4db2-ae0b-8e6f19a7e969
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: HfcDisableService.exe, version: 17.2.0.1009, time stamp: 0x5c62d568
Faulting module name: HfcDisableService.exe, version: 17.2.0.1009, time stamp: 0x5c62d568
Exception code: 0xc0000005
Fault offset: 0x00000000000517a3
Faulting process id: 0x1124
Faulting application start time: 0x01d52917ee61b5cb
Faulting application path: C:\Windows\System32\DriverStore\FileRepository\iastorac.inf_amd64_5d83605e8696144c\HfcDisableService.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\iastorac.inf_amd64_5d83605e8696144c\HfcDisableService.exe
Report Id: 80f689ab-0f7b-4037-a475-d7766e48c385
Faulting package full name:
Faulting package-relative application ID:
Application: IAStorUI.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at <Module>.IsiSessionOpen(UInt32*)
at PsiData.PsiDataSource.Load(System.Collections.Generic.Dictionary`2<Int32,System.Object> ByRef, Boolean)
at PSI.PsiSystemDataModel.LoadDriverData(Int32)
at PSI.PsiSystemDataModel.CreateStaticDataModel()
at PSI.PsiSystemDataModel..cctor()
Exception Info: System.TypeInitializationException
at PSI.PsiSystemDataModel.get_Readiness()
at PSIClient.PsiClient.Init()
at IAStorUI.App.Application_Startup(System.Object, System.Windows.StartupEventArgs)
at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(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.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 IAStorUI.App.Main()
Application: IAStorUI.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at <Module>.IsiSessionOpen(UInt32*)
at PsiData.PsiDataSource.Load(System.Collections.Generic.Dictionary`2<Int32,System.Object> ByRef, Boolean)
at PSI.PsiSystemDataModel.LoadDriverData(Int32)
at PSI.PsiSystemDataModel.CreateStaticDataModel()
at PSI.PsiSystemDataModel..cctor()
Exception Info: System.TypeInitializationException
at PSI.PsiSystemDataModel.get_Readiness()
at PSIClient.PsiClient.Init()
at IAStorUI.App.Application_Startup(System.Object, System.Windows.StartupEventArgs)
at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(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.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 IAStorUI.App.Main()
- Tags:
- UserName
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well since we weren't getting anywhere, I decided to really tackle this and use all my mad tech skillz. After much troubleshooting, it appears Intel RST is no longer compatible with DataRam's RAMDisk.
This is the latest version I am using: Dataram_RAMDisk_4_4_0_RC36.msi
They haven't released anything since 2016: http://memory.dataram.com/products-and-services/software/ramdisk/ramdisk-releases
But I can fresh install windows, install Intel RST, it works. Then install Dataram's Ramdisk, and Intel RST has all of the described problems. I UNinstall DataRam's Ramdrive, and Intel RST starts working again.
Now, is this a Dataram incompatibility, or a Ramdisk problem in general? Well I installed SoftPerfect RAM Disk v 3.4.8 and both work just fine as intended. So it's Dataram.
Link Copied
- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Klepper,
Thank you for patiently waiting.
The order in which the drivers and Intel® Rapid Storage Technology must be installed are as follows:
Windows > Necessary drivers > Intel® RST
With that order, there should be no error present when installing it, please confirm if you have tried the installation process as mentioned.
David V
Intel Customer Support Technician
A Contingent Worker at Intel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Klepper,
Were you able to check my previous post?
Let me know if you need more assistance.
David V
Intel Customer Support Technician
A Contingent Worker at Intel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Fresh install of windows. Any ideas (besides trying different versions, re-re-re-re-reinstalling windows?)
Faulting application name: IAStorUI.exe, version: 17.5.2.1024, time stamp: 0x5d23994d
Faulting module name: KERNELBASE.dll, version: 10.0.18362.356, time stamp: 0x7083db20
Exception code: 0xe0434352
Fault offset: 0x000000000003a839
Faulting process id: 0x1a10
Faulting application start time: 0x01d56903385921ac
Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorUI.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 2e0a6ecf-c43c-450c-bb88-aeb35edb4e5d
Faulting package full name:
Faulting package-relative application ID:
Application: IAStorUI.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at <Module>.IsiSessionOpen(UInt32*)
at PsiData.PsiDataSource.Load(System.Collections.Generic.Dictionary`2<Int32,System.Object> ByRef, Boolean)
at PSI.PsiSystemDataModel.LoadDriverData(Int32)
at PSI.PsiSystemDataModel.CreateStaticDataModel()
at PSI.PsiSystemDataModel..cctor()
Exception Info: System.TypeInitializationException
at PSI.PsiSystemDataModel.get_Readiness()
at PSIClient.PsiClient.Init()
at IAStorUI.App.Application_Startup(System.Object, System.Windows.StartupEventArgs)
at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(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.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 IAStorUI.App.Main()
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well since we weren't getting anywhere, I decided to really tackle this and use all my mad tech skillz. After much troubleshooting, it appears Intel RST is no longer compatible with DataRam's RAMDisk.
This is the latest version I am using: Dataram_RAMDisk_4_4_0_RC36.msi
They haven't released anything since 2016: http://memory.dataram.com/products-and-services/software/ramdisk/ramdisk-releases
But I can fresh install windows, install Intel RST, it works. Then install Dataram's Ramdisk, and Intel RST has all of the described problems. I UNinstall DataRam's Ramdrive, and Intel RST starts working again.
Now, is this a Dataram incompatibility, or a Ramdisk problem in general? Well I installed SoftPerfect RAM Disk v 3.4.8 and both work just fine as intended. So it's Dataram.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Klepper,
Thank you for your response and feedback.
I'm glad to know that you have been able to use Intel ® Rapid Storage Technology properly, I appreciate you taking the time to provide us with this feedback. Since Intel ® Rapid Storage Technology works with the other software then it would seem like a compatibility issue between the version of software installed and Intel ® Rapid Storage Technology as you mentioned.
Let's hope other community peers can find this thread and find this information helpful!
David V
Intel Customer Support Technician
A Contingent Worker at Intel
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »