wackel134Hey Folks,i´ve been also flashing your modded BIOSes to my 767 SLI3 never really had any bigger Problems until half a year ago, where i would be getting BSOD´s with IRQL_NOT_LESS_OR_EQUAL or UNHANDLED_EXCEPTION. Initially i thought the Problem would occur due to Overclocking or just because it was time to reinstall my System. But after upgrading to Windows 10 and upgrading the RST Drivers to 14.6. (also tried the 14.6.1. release) my System is suffering from very slow Boot times and BSOD again, so i can confirm that something is off with ICH0R and 14.6 drivers. 14.5 were working on most levels for me.
dmohebanHi, I've been having some trouble getting my JMB controller to recognize an eSata drive. I have the 12.9 intel and 1.08.1 jmb rom installed in my bios. Anyone encounter this?
henryvitsdmohebanHi, I've been having some trouble getting my JMB controller to recognize an eSata drive. I have the 12.9 intel and 1.08.1 jmb rom installed in my bios. Anyone encounter this?If I remember correctly, there were reported issues with that 1.08.1 ROM. Have you tried the one in my BIOS?
dmohebanhenryvitsdmohebanHi, I've been having some trouble getting my JMB controller to recognize an eSata drive. I have the 12.9 intel and 1.08.1 jmb rom installed in my bios. Anyone encounter this?If I remember correctly, there were reported issues with that 1.08.1 ROM. Have you tried the one in my BIOS? I actually tried pulling the one in your bios and incorporating it into my bios file but after flashing the option rom still displayed version 1.08.1! Is there no way to go backwards to an earlier version? Thanks
dmohebanI tried the one from that site last night and even though I verified the rom version in a hex editor the awdflash program is skipping that rom maybe because it's newer. Need to try a newer version of awdflash maybe.
cleancutSame issue here with upgrading past 18.104.22.1688, maybe it's time for a reformat? Anyone with this issue have a workaround?
henryvitscleancutSame issue here with upgrading past 22.214.171.1248, maybe it's time for a reformat? Anyone with this issue have a workaround?What's the issue you've been having again? Make sure that you set the BIOS option to RAID instead of AHCI, even if you have only one drive attached.
cleancuthenryvitscleancutSame issue here with upgrading past 126.96.36.1998, maybe it's time for a reformat? Anyone with this issue have a workaround?What's the issue you've been having again? Make sure that you set the BIOS option to RAID instead of AHCI, even if you have only one drive attached.Sorry I should be more specific. Whenever I attempt to upgrade beyond 14.5 for the intel rst software I BSOD on boot. System restore is required to get back to the old version and boot up. And yes I have been using RAID for the last 7+ years on this board. Henry your mods are god send. Thank you for your work on this aging platform. PS - do you keep older versions of your mods available? Fernando on the win-raid thread recommends the 11.2 combo for ICH10R. Cc_
rancer420ive used the bios on my e768 and it works. but i was reading through this and it said you cant get the intel rom drivers to work without using your computer in, raid mode? is it? when i try to set my computer to raid mode and boot up, it says no bootmgr or that error and i have to have it on ahci. I am only able to use drivers 11.7 and my ssd's performance is less than it was on my ich9r, im using the intel sata channels. I can use the device manager to update the drivers and theres 2 inf files in the x64bit folder of the 14.8 drivers i tried. an achic and a stora file. then it loads up options, and it has 6th gen, 8th, 8th c220, 9 series intel chipset ahci controller, and a 100 series c230. I know this is ich10r, theres not really a 10 in the selection but id guess, the 100 c230? i dont know where the c230 comes from or if this matches. I think it says it if i pick either inf. I would think achi would be for achi mode and stora would be for ? raid? does that matter? and then windows says we cant verify if this is compatible with your hardware, after I click the 100 one and click next. doing the whole, manual, have disk thing. and it says my computer will stop working if i use it. Which driver should I use, should I do this? I cant switch to raid mode cause my computer won't boot, and if i try to run the setup it says this is not compatible with this machine. Id format and just set the settings but im having some bluray drive reading problem so i dont even have a dvd drive. and if i can ask real quick, anyone know of a marvell maybe chip update that will make it boot up with my ide dvd burner installed? theres a couple of things listed under the ide atapi controllers to do, maybe one will swap them all over to another section, ata 1 ata 2 ide primary and secondary ide. the ide 1 says intel ich10
jayvaughan08Hmm, been having issues with Intel RST v.188.8.131.522 which supports Win 10 x64 TH2 (which I'm currently running.) When installed, Win 10's boot time is like 60s long post boot (at the windows icon screen with the circling dots). On top of that, my OS drive displays, but non of my other drives show up under disk management. The OS drive is 2 SSD's running in Raid0 via the Marvell controller on the board. Uninstalling Intel RST and reverting to the Windows 10 generic drivers rectifies this problem. Previous version Intel RST v. 184.108.40.2063 doesn't support Win 10 and I get a BSOD on boot. Googled the issues and found that maybe Intel RST v.14+ isn't compatible with the intel ROM on my board so I flashed to henryvits modded bios including Intel RAID Option ROM 220.127.116.117 but still the hang at boot and the missing drives. I want to get intel RST running because I'm trying to run 2 HDDs in raid0 and I want the RST health monitoring. Will I notice a performance decease without RST? Does anyone have any suggestions? edit: fwiw I am using the AHCI-Raid option in bios. intel raid0 works, just not Intel RST.edit #2: going back to Intel RST 18.104.22.1680 presents the same issues as 22.214.171.1242, but no BSOD on boot like 126.96.36.1993edit #3: an OS reinstall didn't fix the boot time/disk drive issue, anyone else on the E770 get these drivers to work?edit #4: both pre and post OS reinstall, I wasn't able to bring up the intel rst UI except once (though, don't know how I did it - I think that might have been using an older RST prior to the ROM update.) Now whenever I try to load it I get an unknown error.
henryvitsYou need to switch from AHCI to RAID in the BIOS. Then the IRST should work.
First RST(e) v14.8 Series drivers:>32bit Intel RST(e) AHCI/RAID Drivers v188.8.131.522 WHQL< (>MIRROR<)>64bit Intel RST(e) AHCI/RAID Drivers v184.108.40.2062 WHQL< (>MIRROR<)>Intel RST(e) AHCI/RAID Drivers & Software Set v220.127.116.112 WHQL< (>MIRROR<)Notes: These drivers are dated 11/04/2015, WHQL certified by Microsoft and usable with all Windows Operating Systems from Win7 up. Only Intel Chipsets from the 8-Series up (incl. X99) are supported by these new drivers. Thanks to Station-Drivers for the source files.Best matching Intel RAID ROM/EFI BIOS modules: v18.104.22.1687Important remarks regarding the use of the 32/64bit RST(e) Drivers or the complete RST(e) Drivers and Software Set:The Intel RST/RST(e) Software may require .NET Framework v3.0 or v3.5 for a proper installation and function.Note: None of the Windows Operating Systems (not even Win8 and Win8.1) have the needed .NET Framework version working after a clean OS install! To prevent any problems and error message after having installed the complete Intel RST/RST(e) package the first time, it is a good idea to make sure, that the needed .NET Framework version is already running, and to install the required .NET Framework version, if it's not already done. Users, who forgot to install the needed .NET Framework version before they run the installer of the complete RST/RST(e) Set, will not be able to get access to the Intel RST Console, not even after having catched up the previously missed .NET installation. Tip: This problem can be solved by just rerunning the installer of the RST(RST(e) Drivers & Software Set.Because of the big structural and functional differences between the "classical" Intel RST driver (just using the iaStor.sys) and the newer Intel RST(e) drivers (using iaStorA.sys and additionally the SCSI driver iaStorF.sys), users should be very restrictive regarding the switch from one driver sort to the other. Extra dangerous is the "downgrade" from any RST(e) drivers (from v11.5 up) to any "classical" RST driver (latest: v22.214.171.1246). Before you are going to do that, a backup of the complete system partition is strongly recommended (in case that you are not able anymore to boot into the OS after the reboot).RAID resp. AHCI users, who had installed the RST software, should uninstall it, before they are going to install any other Intel AHCI or RAID driver or another complete RST/RST(e) package.Users, who want to install any of the Intel RST(e) drivers (from v11.5 up) the first time, should unplug all removable devices, before they start with driver installation. Otherwise it is possible, that these devices will not be recognized anymore by the OS with the consequence, that the related drivers and software have to be reinstalled as well. This is not a bug of Intel's RST(e) drivers or of the RST software, but a consequence of the completely new hardware detection procedure by the additional SCSI filter driver.Due to the severe changes of the complete storage device system by adding the SCSI filter driver, the first installation of the Intel RST(e) drivers comes up in 2 steps. That means, that the installation will be completed not until the user has done a second reboot.After the successful installation of Intel's RST(e) drivers you will recognize some changes within the Device Manager. They are caused by the installed Intel RST(e) SCSI filter driver.Example: The Intel(R) SATA AHCI Controller may not be listed anymore as "IDE ATA/ATAPI Controller", but now as "Storage Controllers".Warning: After having switched from any RST driver (iaStor.sys) to any of the RST(e) drivers (iaStorA.sys+iaStorF.sys) or vice versa you should never try to delete any of them from within the Windows\System32\Drivers folder (although they will not be in use anymore). If you do it nevertheless, you will get a BSOD during the next reboot. These drivers are needed by the OS.
jayvaughan08So the software issue with the Intel RST control center not loading was related to not having .net installed. Since this was a clean OS, I installed .net and that rectified the issue. However, I'm still getting terribly slow boot times and missing all drives but my main OS which is located on the marvel SATA III/6gbs. I'm honestly wondering if my OS was located on the intel controller if it would even load under these conditions or BSOD. I checked windows even log and could find nothing out of the ordinary. I closely followed the install instructions located here: But I haven't noticed any difference. Is the issue because I don't have an 8 series board and intel RST v.14 is not supported on our boards? I thought that was all of us, that's why updated the ROM. I've looked in driver view and only see iaStorA.sys, no iaStorF.sys. Unplugging/plugging the drives while off or running makes no difference. I could try uninstalling antivirus and acronis to see if they're causing an issue but I doubt it at this point. Norton shows nothing in the logs that it might be preventing anything.
rancer420anyone who can help me get my motherboard going