- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
[Edited]
Dear Intels's developers!
I want tell you about problems with newer version of Intel RST drivers for old chipset:
- Intel X58 + ICH10R (Intel(R) Desktop/Workstation/Server Express Chipset SATA (PCI\VEN_8086&DEV_2822))
Last good worked version of Intel RST drivers for old chipsets is 13.6.0.1002.
If you have installed newer version of Intel RST drivers (14 or 15), you will get BSOD after OS's a restart. But I know the solution for this the problem.
Please, check the registry value:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_8086&DEV_2822&SUBSYS_82D41043&REV_00\3&11583659&0&FA\Device Parameters\Interrupt Management\MessageSignaledInterruptProperties]
"MessageNumberLimit". Please, change it for old chipset to from decimal "80" to "1".
For old chipsets it must be:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_8086&DEV_2822&SUBSYS_82D41043&REV_00\3&11583659&0&FA\Device Parameters\Interrupt Management\MessageSignaledInterruptProperties]
"MessageNumberLimit"=dword:00000001
Or, may be, for old chipsets you can change the string in iaStorAC.inf file:
"HKR, Interrupt Management\MessageSignaledInterruptProperties, MessageNumberLimit, %REG_TYPE_DWORD%, 1"
Thank you.
For users, who have got BSOD, after newer version of Intel RST derivers (14 or 15) were installed for Intel(R) Desktop/Workstation/Server Express Chipset SATA (PCI\VEN_8086&DEV_2822).
Method A (BEFORE RESTARTING):
1. If newer version of Intel RST drives have been intalled already, you must edit the registry value, before OS's a restart:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_8086&DEV_2822&SUBSYS_82D41043&REV_00\3&11583659&0&FA\Device Parameters\Interrupt Management\MessageSignaledInterruptProperties]
"MessageNumberLimit"=dword:00000001
Caution! "PCI\VEN_8086&DEV_2822&SUBSYS_82D41043&REV_00\3&11583659&0&FA" this the part of a registry path must be equivalent to your Intel RAID controller hardware ID.
Method B (if you got BSOD after restarting PC):
1. Load from working OS_rescue_DVD disk to load OS. You must see all your disks and partitions.
2. Select "Use command shell"
3. Run "regedit"
4. Check "HKEY_LOCAL_MACHINE" key
5. Use "Load Hive" from menu
6. Select your OS location. For an example C:\Windows. Select "your OS location"\System32\Config. For an example C:\Windows\System32\Config. Select "SYSTEM" file.
7. Enter a random_name. For an example: edit_system
8. Edit [HKEY_LOCAL_MACHINE\"random name"\ControlSet001\Enum\PCI\VEN_8086&DEV_2822&SUBSYS_82D41043&REV_00\3&11583659&0&FA\Device Parameters\Interrupt Management\MessageSignaledInterruptProperties]
"MessageNumberLimit" from decimal "80" to "1".
For an example, it may be: [HKEY_LOCAL_MACHINE\edit_system\ControlSet001\Enum\PCI\VEN_8086&DEV_2822&SUBSYS_82D41043&REV_00\3&11583659&0&FA\Device Parameters\Interrupt Management\MessageSignaledInterruptProperties]
"MessageNumberLimit"=dword:00000001
Caution! "PCI\VEN_8086&DEV_2822&SUBSYS_82D41043&REV_00\3&11583659&0&FA" this the part of a registry path must be equivalent to your Intel RAID controller hardware ID.
9. Use "Unload Hive" from menu.
10. Restart PC.
Beware, all registry changes in your OS you will do for your own risk.
This worked for my configuration:
*MB with Intel X58 + ICH10R (Intel(R) Desktop/Workstation/Server Express Chipset SATA (PCI\VEN_8086&DEV_2822))
*RAID configuration (1,0)
*Windows 10 Pro x64 1607 14393.1066
*Intel RST 15.2.0.1020 Installed
Registry was modified after OS have falled in BSOD. All are working after BSOD have been got and registry was changed.<...
- Tags:
- PCIe
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello igmikor,
Thank you for sharing you fix with the community, I am pretty sure this will help other users in the community.
Regards,
Amy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After updating my DG45ID w/ICH10R system running Windows 10 x32 today to the Win10 Creator's Update (1703), I noticed that the RAID driver had been updated from the Intel RST 12.9 version I had installed (the highest reve that worked for me in Win10) to the 14.8.0.1042 version that's now included by default. The registry edit mentioned above was already present, but there's no longer any Intel Raid Software present in the Start Menu, even though there's still an entry for the RST 12.9 software in Programs & Features.
I intend to run the RSTsetup.exe program for version 14.8.0.1042 with the -Nodrv option to only install the software, no drivers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It was very wisly to use -Nodrv options to prevent modify the registry after UI of Intel RST were intalled. Thank you for the advice for users, who updated Windows 10.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So yesterday when I attempted to update this same machine to the Fall Creators Update (1709), the system failed to boot after the first restart of the update process after spending about a minute twirling on the initial Win10 boot screen with no disk activity progress. Eventually I was taken to the Win10 boot troubleshooting screen where I had the option to troubleshoot or shutdown. I chose the shutdown. After restarting the system, Win10 reverted to the 1703 version with no issues. (Just in case there were unrecoverable issues, I had previously disabled the continuous update feature of the RAID recovery mode setup, the 2nd disk now offline).
I can only assume that the 1709 update is attempting to upgrade the 14.8.0.1042 driver to something more recent that's not compatible with my DG45ID's ICH10R chipset, or it's attempting to use it with the incorrect registry settings again. I plan to downgrade the RST driver to version 12.9 and try the Fall Creators Update again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FINALLY! After years and years, I was able to update my X58 based RST drivers! Thanks for the heads-up! I made the modifications to the registry before I rebooted after the driver installation. Also, I updated the iaStorAC.inf files (all occurrences that I found) to use 1 instead of 80. Note, to do that, I had to take ownership and also add my user account to the permissions list so that I could save the file (otherwise, no write permissions). MANY THANKS TO YOU igmikor!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OMG! This worked. Thank you so much! There was a little learning curve in the fact that I didn't remember right away how to check hardware ID's. For those less computer literate, you go into the device manager. Go down to the storage controllers, and highlight the raid controller. Right click, go to properties, and then select the "details" tab. There will be a drop down box for "hardware id's".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1. For Windows 10 Fall Creators Update:
Before the update will do start, you must install 13.6.0.1002 driver. Or use Method B from my post.
If your Windows update hang up after reboot, use Method B.
2. Windows 10 Fall Creators Update setup 15.7.0.1014 driver. That drives are working uncorrect on old chipsets (for an example, X58 gets disk errors with operations on big size files.).
You must use 15.5.0.1051 or older for a correct work. I installed 15.5.0.1051 driver and it working correct with Fall Creators Update.
3.The correction for my first post.
Method A: You must check not only CurrentControlSet branch, but CurrentControlSet1 too.
It's pity, but you can not change the string in iaStorAC.inf file, because all files have a hash and Windows do check the hash in time load drivers and do not load driver files with changed hash.
We must ask Intel developers to prepare a version of drivers for old chipset, where "MessageNumberLimit, %REG_TYPE_DWORD%, 1" will be in iaStorAC.inf file
<span style="display: inline !important; float: none; background-color: transparent; color: # 3d3d3d; font-family: 'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif; font-size: 14px; font-style: normal; font-variant: normal;...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The latest version of the Intel RST drivers is 15.8.1.1007 released on 12-Sep-2017.
Can you try this version with the Fall Creators Update 1709 and see if it fixes the problems you mention on older chipsets?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
15.7.0.1014, 15.8.1.1007 - This drivers are working uncorrect on old chipsets with Fall Creators Update.
X58 have disk errors with operations on big size files. May be, 15.7.0.1014 and 15.8.1.1007 issue some cache problems.
15.5.0.1051 are working correct with Fall Creators Update.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
igmikor: Do you know if drivers 15.9.0.1015 works correctly on X58?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page