Hi all,
I recently upgraded my system with SSDs
I took the opportunity to upgrade my OS from Win7 to Win10 as well.
The system is based on a GIGABYTE 965P-DQ6 with ICH8R and a modded BIOS with updated OROM V8.5.0.1030
I have 3 SSDs setup in a Striped configuration.
Windows 10 has been unstable from day one, even the setup ran quite slow.
The system is running with windows built in driver.
I tried to install several original intel drivers but the system just becomes unbootable under Windows 10 after installing RST, I have to revert the driver to the original OEM from windows using DISM.
I tried to mod my BIOS and upgrade my OROM to the recommended v11.2.0.1527 but my Motherboard doesn’t seem to like it and the module does not load.
Do you have any suggestions? Either a driver that I can use or a way to make v11.2.0.1527 work in my system or both?
Help is highly appreciated, thank you very much.
Regards
Still struggling with this… any help is appreciated.
Thank you
@zone2097 - Did you ever test installing Intel drivers during OS Install, where you choose disk target, and test to see if they work better than Microcosoft ones, before you do anything else
On the BIOS mod, maybe you did the mod wrong, when you tried to put in orom v11? Or, maybe it’s too large? Where do you see this is suggested and compatible version to use for 965P?
You do have the 3 SSD connected to SATA_0-SATA_2 yellow, correct? If not, move them to those ports, best to use SATA_0-4/5 first for HDD/SSD, and the leave SATA_5 for CD/DVD, when possible.
When you did you test edit inserting V11 orom, did you mind the sensitive modules? If not, what cbrom version did you use, and was the BIOS bootable, just no RAID Rom loaded?
@Fernando - Before I do anything to a BIOS, I see you do recommend 11.2.0.1527 for ICH7-10R here, is that always the best choice and is always compatible, or would v10.1.0.1008 possibly be a better choice here?
If he did the mod correctly, and module is not loading, this means 11.2 was too large, so 10.x probably better choice. I’m not looking at either file now, so unsure of sizes of any of these as I reply, but I do remember that symptom being too large of a rom so it does not load
@Lost_N_BIOS :
According to my own tests the Intel RAID ROM v11.2.0.1527 in combination with the Intel RST RAID driver v11.2.0.1006 is the best choice for old Intel RAID systems (up to 100-Series chipsets).
Unfortunately the BIOS of some old Intel chipset mainboards is not able to load any Option ROM module, whose size exceeds 100 KB. Such big sized ROM modules cannot be loaded while booting. For details look >here<.
@Fernando - Thanks, I thought I remembered some old BIOS do have issue with larger roms. I’ve tested that myself and hit this issue even on X58 and P35 in testing for some users sometimes
I bet that is what happened here with his mod attempt, will have to wait on him to reply back about what cbrom he used, and then he can also just directly do same edit again but use smaller 85KB 10.1.0.1008_TRIM mod rom instead.
Hi Lost and Fernando and thank you very much for your replies
To answer to your questions @Lost_N_BIOS :
I didn’t actually test this during installation but does it matter now that the system is installed?
v11.2.0.1527 is suggested on this topic at the end of section 1 where it states this: best choice for Intel ICH7R/8R/9R/10R Chipset RAID systems (matching RAID driver: Intel RST v11.2.0.1006), best performant ROM for all RAID0 users.
SSDs are connected to the first 3 yellow slots. I used exactly the same procedure for orom v11 as I did for v8.5, tried several OROMs and everything above v8.5 does not work. (i.e. system posts but rom module is not loaded)
I used CBROM 1.55 as suggested in this post for Gigabyte Award Bios Motherboards. system posts and can boot to other devices but ICH8R rom is not loaded and devices connected to it are not detected.
At the moment I do not have access to the system, only later in the afternoon, I can try v10.1.0.1008 TRIM, but I think I recall trying the unmodded version some time ago with no luck. Could it be that the limit is 65KB and not 100KB on this motherboard?
I can also try to make a clean install loading the driver during setup but probably not until tomorrow.
EDIT by Fernando: Unneeded blank lines removed (for better readability and to save space)
You may be absolutely right.
After having done a Google Search for the "Intel RAID ROM v8.5.0.1030" I found >here<, what I had written more than 6 years ago:
@zone2097 - It may or may not matter, about the driver install pre-OS install, just tossing out things for you to try if you had not yet.
You said everything about 8.5 didn’t work, but then you said you will try 10.x, so you did not try 10.x previously??
Thanks, so 1.55 was OK and BIOS was bootable, good to know. Did you mind the sensitive modules, or just do /pci filename.bin?
Yes, maybe in some cases 64KB may be the limit, but I would test 10.x on your system first to be 100% sure. Then if still no RAID, do the 8.5_TRIM insert and see if all OK then
@Lost_N_BIOS I was not sure if I had tried 10.5 before as I had tried several versions.
Today I’ve tried v10.5 with TRIM unsuccessfully.
I did mind the MINIT module, is there any other module I should care about? You can find the CBROM displays for original gigabyte and modded
original with 10.5 below as well as HxD prints with MINIT locations.
I see some value changes after the MINIT is this relevant? v8.5 has different values from the original as well but works.
@Fernando I recall seeing the F6 drivers somewhere on the forum but I’ve searched the whole afternoon and could not find them… Do you remember where I can get these?
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
CBROM_155.EXE V1.55 [10/12/05 Release] (C)Phoenix Technologies 2001-2005
******** 965PDQ6.F13 BIOS component ********
No. Item-Name Original-Size Compressed-Size Original-File-Name
================================================================================ 0. System BIOS 20000h(128.00K)14D5Ah(83.34K)965pdq6.BIN
1. XGROUP CODE 0F200h(60.50K)0A9C4h(42.44K)awardext.rom
2. ACPI table 04C79h(19.12K)018CBh(6.20K)ACPITBL.BIN
3. EPA LOGO 0168Ch(5.64K)0030Dh(0.76K)AwardBmp.bmp
4. GROUP ROM[18] 027F0h(9.98K)01B49h(6.82K)ggroup.bin
5. YGROUP ROM 0BB70h(46.86K)05839h(22.06K)awardeyt.rom
6. GROUP ROM[ 0] 07720h(29.78K)02D01h(11.25K)_EN_CODE.BIN
7. PCI ROM[A] 0F400h(61.00K)0955Ah(37.34K)ICH8RAID.BIN
8. PCI ROM[B] 04000h(16.00K)02B46h(10.82K)AHCI.bin
9. PCI ROM[C] 07A00h(30.50K)04479h(17.12K)JMB59.BIN
10. PCI ROM[D] 0DA00h(54.50K)08579h(33.37K)8056B0.lom
11. LOGO1 ROM 00B64h(2.85K)00520h(1.28K)dbios.bmp
12. LOGO BitMap 4B30Ch(300.76K)06F80h(27.88K)DQ6.BMP
13. GV3 0182Dh(6.04K)00AA8h(2.66K)PPMINIT.ROM
14. OEM0 CODE 02F0Ch(11.76K)021B9h(8.43K)DBF.BIN
15. OEM2 CODE 01000h(4.00K)00079h(0.12K)AFSC_HDR.ROM
16. MINIT 07800h(30.00K)0782Ch(30.04K)ME_MRC.BIN
Total compress code space = 67000h(412.00K)
Total compressed code size = 557B1h(341.92K)
Remain compress code space = 1184Fh(70.08K)
** Micro Code Information **
Update ID CPUID | Update ID CPUID | Update ID CPUID | Update ID CPUID
------------------+--------------------+--------------------+-------------------
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
CBROM_155.EXE V1.55 [10/12/05 Release] (C)Phoenix Technologies 2001-2005
******** 965PDQ6_MOD.F13 BIOS component ********
No. Item-Name Original-Size Compressed-Size Original-File-Name
================================================================================ 0. System BIOS 20000h(128.00K)14D5Ah(83.34K)965pdq6.BIN
1. XGROUP CODE 0F200h(60.50K)0A9C4h(42.44K)awardext.rom
2. ACPI table 04C79h(19.12K)018CBh(6.20K)ACPITBL.BIN
3. EPA LOGO 0168Ch(5.64K)0030Dh(0.76K)AwardBmp.bmp
4. GROUP ROM[18] 027F0h(9.98K)01B49h(6.82K)ggroup.bin
5. YGROUP ROM 0BB70h(46.86K)05839h(22.06K)awardeyt.rom
6. GROUP ROM[ 0] 07720h(29.78K)02D01h(11.25K)_EN_CODE.BIN
7. PCI ROM[B] 04000h(16.00K)02B46h(10.82K)AHCI.bin
8. PCI ROM[C] 07A00h(30.50K)04479h(17.12K)JMB59.BIN
9. PCI ROM[D] 0DA00h(54.50K)08579h(33.37K)8056B0.lom
10. LOGO1 ROM 00B64h(2.85K)00520h(1.28K)dbios.bmp
11. LOGO BitMap 4B30Ch(300.76K)06F80h(27.88K)DQ6.BMP
12. GV3 0182Dh(6.04K)00AA8h(2.66K)PPMINIT.ROM
13. OEM0 CODE 02F0Ch(11.76K)021B9h(8.43K)DBF.BIN
14. OEM2 CODE 01000h(4.00K)00079h(0.12K)AFSC_HDR.ROM
15. MINIT 07800h(30.00K)0782Ch(30.04K)ME_MRC.BIN
16. PCI ROM[A] 1DC00h(119.00K)10EE1h(67.72K)ICH8RAID.BIN
Total compress code space = 67000h(412.00K)
Total compressed code size = 5D138h(372.30K)
Remain compress code space = 09EC8h(39.70K)
** Micro Code Information **
Update ID CPUID | Update ID CPUID | Update ID CPUID | Update ID CPUID
------------------+--------------------+--------------------+-------------------
Original Gigabyte ROM
Modded from Original with v10511070_TRIM
Backup currently running with v8501030_TRIM
EDIT by Fernando: Put the CBROM output into "spoilers" (to save space)
@zone2097 - You’re supposed to try 10.1.0.1008 w/ TRIM, not 10.5 that one is too large = same as 11.x - Sorry if my mention of 10.x directly above confused you, I was in a rush and didn’t have time to scroll back up to my original reply to see correct smaller 10.1.x version
Minit, GV3 and MeminitEntrypoint (x2 locations) should remain same always, same start offset and same module #, if that matters in this BIOS, which it most likely does.
However, maybe not in this case, due to your 10.5 test above, if this is bootable then maybe no sensitive modules here since that likely moved them all.
Cbrom is of zero use for checking mod BIOS, unless you really break something, or you just wanted to check module order #
Try 10.1.0.1008 now and see how you get along 
Which sort of F6 drivers do you mean?
@zone2097 :
To avoid the usage of the Win10 in-box Intel RST RAID driver v15.44.0.1015 I recommend to load the Intel RST driver v11.2.0.1006 WHQL.