by   June 01 2012   
Upgrading your system with the Intel Rapid Storage Technology. It is really easy to mess up your drive configuration if you've not looked into the fixes online for upgrading to a SSD caching system. If you have the Intel motherboard that supports the Intel Rapid Storage Technology you really need to purchase any SSD over 20Gb to experience a swifter computer. I mean it's quicker and doesn't have that hang effect when you are over your physical memory limits. I'm running 32Gb on the DZ68DB mainboard. i5 core, crucial memory etc.

Adding SSD RAID with Intel Rapid Storage Technology

1. BSOD visitors: If you are here regarding BSOD issues with the iaVStor.sys file read this from MS first. http://support.microsoft.com/kb/982018

2. Upgrading: Enable Rapid Storage Technology with SSD as an upgrade to OS installed on primary drive. If you have issues after you have completed the registry entries or you need the registry entry to merge you will need to set up a service ticket. I'm not going to charge you a dime but I need feedback if your system is having problems upgrading. I've done this upgrade on a few systems and each seemed to have it's own unique issue. BSOD was very common until you got it right, switch back in BIOS the drive type to a non raid drive, do the registry entries, reboot, enter BIOS set the drive type to RAID then save, exit. That's the order of things.

3. Install in fresh system follow the yellow page insert with your motherboard. I'll dig mine up and post it in the system builders section.

The issue might not apply to you but I would like to know the hardware to software issue which I am not finding directly with any of my test systems. If you have a BSOD related to the iaVStor.sys file read on and make sure everything is good before you send me a service desk ticket to work with you and find the answer. No, not all service tickets cost. Some often help other technicians which means we share data and exchange fixes. Kind of what the Community at XtremeComputer.Com does! It's your time to be part of the solution by helping create the solution.

I have all Intel based systems running the Rapid Store Technology that uses the iaVStor.sys file on Win7 Pro, Ult, Win8, Windows 2008 R2 and haven't seen this issue. I would like to see what is causing BSOD in Win7 systems. Are you using a brand name computer or a pure Intel system?

On with the Rapid Storage Technology upgrade from standard systen Non RAID to RAID.

I have some processes and procedures on several different methods of updating to use the Rapid Storage technology and I'll be updating this post as soon as I find the notepad again.

The key was installing the software, editing the registry and changing the boards BIOS to RAID configurations which might have started with changing the AHCI.

If this doesn't help you fix your upgrade using the Intel Rapid Storage Technology on any Intel RST rated mainboard with a good SSD drive of 40Gb or larger send me a service desk ticket. Click the Computer Help banner or the My Service Desk Account link and send me what you have done. I'm guessing this issue is completely resolved but I haven't search the topic much this year. Thanks, Murray.

The trick?
Not really a trick.
It's a Registry Modification (Hack).

  1. First, disable the drives except for the registry you are looking to use.
  2. Enable the RAID in the Registry will allow even the AHCI to boot so don't worry.
  3. Open your Intel Rapid software.

Showing 0gb drive sizes?
Reinstall the software and reboot.
You might have to update a few things and reboot a couple of times but it will start working.
I've worked with these drives and they can be a pain, but if you can boot to windows under any BIOS setting you
can then fix or setup your Rapid Store.

Registry Changes: BACKUP!!!!!

The Registry changes are from my testing system. I reworked many registry settings so you'll have to compare yours with mine. Not all will apply but I can tell you changes will not break your system. Be sure you follow the Intel Instructions as well. You'll find their BIOS settings guide can be handled after you change your registry in some cases. (If I recall it was last year).

Don't give up! It's a really good technology and if you're like me running 4 2TB drives with a master drive 1Tb and Vitural Machines you will really find the quickness something to write home about.

Registry = BACKUP the blocks prior to changes.

iaStorV

My Change

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorV]
"Start"=dword:00000000
"Type"=dword:00000001
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\
  72,00,69,00,76,00,65,00,72,00,73,00,5c,00,69,00,61,00,53,00,74,00,6f,00,72,\
  00,56,00,2e,00,73,00,79,00,73,00,00,00
"Group"="SCSI Miniport"
"DriverPackageId"="iastorv.inf_amd64_neutral_18cccb83b34e1453"
"Tag"=dword:00000019
"DisplayName"="Intel RAID Controller Windows 7"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorV\Parameters]
"queuePriorityEnable"=dword:00000000
"BusType"=dword:00000008

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorV\Enum]
"0"="Root\\LEGACY_IASTORV\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

iaStor

My Change

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor]
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"Tag"=dword:00000019
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,61,00,53,00,74,00,6f,00,72,\
  00,2e,00,73,00,79,00,73,00,00,00
"DisplayName"="Intel RAID Controller"
"Group"="SCSI Miniport"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters]
"BusType"=dword:00000008
"CSMI"=dword:00000003

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\oromVersion]
"MajorVersion"=dword:0000000a
"MinorVersion"=dword:00000006
"HotfixNumber"=dword:00000000
"BuildNumber"=dword:00000443

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Enum]
"0"="PCI\\VEN_8086&DEV_2822&SUBSYS_201B8086&REV_05\\3&11583659&0&FA"
"Count"=dword:00000001
"NextInstance"=dword:00000001

adpahci

My Change

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\adpahci]
"Start"=dword:00000003
"Type"=dword:00000001
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
  74,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,52,\
  00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,64,00,70,00,61,00,68,00,63,00,\
  69,00,2e,00,73,00,79,00,73,00,00,00
"Group"="SCSI Miniport"
"DriverPackageId"="adpahci.inf_amd64_neutral_b082e95ec9f8c3f9"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\adpahci\Parameters]
"BusType"=dword:00000008

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\adpahci\Parameters\Device]
"DriverParameter"="DisableIoctl=1;"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\adpahci\Parameters\PnpInterface]
"5"=dword:00000001

My Change

msahci

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci]
"Start"=dword:00000000
"Type"=dword:00000001
"ErrorControl"=dword:00000003
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\
  72,00,69,00,76,00,65,00,72,00,73,00,5c,00,6d,00,73,00,61,00,68,00,63,00,69,\
  00,2e,00,73,00,79,00,73,00,00,00
"Group"="SCSI Miniport"
"DriverPackageId"="mshdc.inf_amd64_neutral_a69a58a4286f0b22"
"Tag"=dword:00000040

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci\Enum]
"0"="Root\\LEGACY_MSAHCI\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001


I know not giving the before and after registry entries might have been nice but this was a work day for me and I just saved the configurations that worked.

I've tested converted VHD as well and using VHD registry changes prior to transfering to a physical drive does help speed things along.

The key is to not give up. You will get it to work. You will also notice the benefits when you start running applications like a bandit. I have my workstations all running the Rapid Storage Technology on Intel 320 SSD drives 40Gb and 80Gb (max is about 64Gb) and I really like it.

I've tested it by loading older IDE drives into the same system and the applications cached offer some great benefits.

The only issue I found was in the Maximized Mode. The system did Blue Screen a few times when I mixed drives and was running VHDs and really loading the system. My guess is was an OS issue which I avoided by not using the Maximized mode. It did make a noticable speed (quick) difference but the risk of a BSOD was enough to change back to the Enhanced Mode which I have not any any issues and quickness is much faster than the standard drives.

Matter of fact, between using 7200RPM drives and 5400 Green Drives I found a slight difference but not enough to warrant the cash for 7200RPM drives in the 2TB size range when it comes to working with the Rapid Store Technology it allowed me to load 4 2TB drives with a master OS drive of 500Gb 7200RPM. I'm impressed to say the least.

I'd like to hear from those that have had issues and corrected them. I can only test on so many systems and not them all.

 


Upgrading your system with the Intel Rapid Storage Technology. It is really easy to mess up your drive configuration if you've not looked into the fixes online for upgrading to a SSD caching system. If you have the Intel motherboard that supports the Intel Rapid Storage Technology you really need to purchase any SSD over 20Gb to experience a swifter computer. I mean it's quicker and doesn't have that hang effect when you are over your physical memory limits. I'm running 32Gb on the DZ68DB mainboard. i5 core, crucial memory etc.