Everything except the extra stuff that can be installed together if you enable it.
The driver was broken. Noticed that while running a disk benchmark. I uninstalled the driver and tried to reinstall it after a reboot but no go.
Printable View
Everything except the extra stuff that can be installed together if you enable it.
The driver was broken. Noticed that while running a disk benchmark. I uninstalled the driver and tried to reinstall it after a reboot but no go.
Are you trying to install this package here?
Would you suggest I rollback to a previous driver if this driver is broken?
Thanks
BTW have you had any luck on your MSR quest Alien?
John
No, I was talking about Intel RST 10.6.0.1002. However I tried Intel RST 10.6.0.1022 and it still fails the installation process.Quote:
Originally Posted by JohnZS
http://i431.photobucket.com/albums/q...gy-Failure.jpg
This is a screenshot trying to instal Intel RST 10.6.0.1022. It fails to install the SATA AHCI Controller driver. I also noticed that it still uses version 10.6.0.1002. I think that it's better to be safe than sorry so trying to reinstall (uninstall->reboot->reinstall) the Intel RST 10.6.0.10xx is a good idea, and if it fails the installation proces, roll back to a previous version.
Oops... double post. The forum is acting strange.:D
Ok when I extract the 11.0.1124 Option ROM from the Intel .BIO it fails :(
Yet when I extract the same option ROM from SoLoR's BIOs and put it into my RE it works?
The Option ROM's are completely different in HEX land :(
My extraction method no longer works!
:(:(:(:(
112,257 difference(s) found.
John
hey SoLoR could you update the microcode for Q6600 G0, I'll post the microcode later when I'm not at work.
BTW A-Grey i had a similar problem with the RST driver to re-installing, i had to install it via the have disk method and pointing to the inf that is extracted to a temp folder during the RST install. Let me know if you want a more detailed description.
I decided to just update all microcodes so here it is ...
EDIT broken bios!
That's great but it looks like something went wrong.Quote:
Originally Posted by SoLoR
http://i431.photobucket.com/albums/q...ocodePatch.jpg
hm... well i removed the ones that are updated and added them to the end.... order shouldnt matter... and bios works for me, tested on Q9450. About those 00000 microcodes they are in original bios as well.... so dunno i know this bios is working on Q9450 :) and what microcodes are updated i posted few posts back....Quote:
Originally Posted by Alien Grey
The 000... ones aren't in the original 1002b-R2. Maybe something went wrong when you updated some of them the first time and saved it.:shrug:Quote:
Originally Posted by SoLoR
Edit: Maybe it's better to stick with your first plan and only update the ones that are needed. If someone wants the microcode to be updated for his CPU he should post a CPUID screenshot. If it's done like that, it's easy to find out if the update was succesful or not.
well ill check again when i get home but im kinda sure there shouldnt be anything wrong :) keep in mind that 3,7,8,10,11,12 are removed so postions are bumped and "new" ones are added to end.... but ill check again...Quote:
Originally Posted by Alien Grey
I think that I've found the problem. The ones that are all with 0 are probably added twice. Some of them like number 7 don't need an update and others may have been added twice by misstake. Did MMTOOL gave you a few times the warning "The CPU MicroCode Patch data is existing in target ROM image"?Quote:
Originally Posted by SoLoR
no it didnt.... but look comparision of backup and current r-3.Quote:
Originally Posted by Alien Grey
as you see in current R3 microcodes with 0000 are 7,9,11,14,15,16,17,20 and in backup microcodes with 0000 are 13,15,17,20,21,22,23,26 in both cases there is 8 microcodes with 0000 they are just on different postions so i think its fine :)Code:D:\Downloads>AMIMMWIN.exe 1002b-R3.ROM /cp
Intel CPU MicroCode Patch Data Information
==============================================
MicroCode Platform Update Date Size
NO ID Type CPU ID Revision YYYY/MM/DD (Hex.)
-- --------- -------- ------ -------- ---------- --------
01 0016F005 01 06F0 05 2005/08/18 00001000
02 0276F111 27 06F1 11 2005/10/10 00001000
03 0F56F426 F5 06F4 26 2006/03/12 00001000
04 0016F533 01 06F5 33 2006/05/01 00001000
05 0506F533 50 06F5 33 2006/05/01 00001000
06 0016F982 01 06F9 82 2006/09/03 00001000
07 00000000 00 0000 00 0000/00/00 00000800
08 01DF3417 1D 0F34 17 2005/04/21 00002000
09 00000000 00 0000 00 0000/00/00 00000800
10 0BDF4117 BD 0F41 17 2005/04/22 00001800
11 00000000 00 0000 00 0000/00/00 00000800
12 09DF4406 9D 0F44 06 2005/04/21 00001000
13 09DF4703 9D 0F47 03 2005/04/21 00001000
14 00000000 00 0000 00 0000/00/00 00000800
15 00000000 00 0000 00 0000/00/00 00000800
16 00000000 00 0000 00 0000/00/00 00000800
17 00000000 00 0000 00 0000/00/00 00000800
18 004F620F 04 0F62 0F 2005/12/15 00001000
19 034F6404 34 0F64 04 2005/12/23 00001000
20 00000000 00 0000 00 0000/00/00 00000800
21 00366004 03 0660 04 2006/06/12 00001000
22 00167106 01 0671 06 2007/03/29 00001000
23 01067106 10 0671 06 2007/03/29 00001000
24 00167404 01 0674 04 2007/06/08 00001000
25 01067404 10 0674 04 2007/06/08 00001000
26 0016F25D 01 06F2 5D 2010/10/02 00001000
27 0016F6D0 01 06F6 D0 2010/09/30 00001000
28 0106F76A 10 06F7 6A 2010/10/02 00001000
29 0016FBBA 01 06FB BA 2010/10/03 00001000
30 0106FBBA 10 06FB BA 2010/10/03 00001000
31 0016FDA4 01 06FD A4 2010/10/02 00001000
32 00166143 01 0661 43 2010/10/04 00001000
33 0016760F 01 0676 0F 2010/09/29 00001000
34 0106760F 10 0676 0F 2010/09/29 00001000
35 0106770A 10 0677 0A 2010/09/29 00001000
36 01167A0B 11 067A 0B 2010/09/28 00002000
0 Warning, 0 Error occurred.
Done.
D:\Downloads>AMIMMWIN.exe 1002b-R3-backup.ROM /cp
Intel CPU MicroCode Patch Data Information
==============================================
MicroCode Platform Update Date Size
NO ID Type CPU ID Revision YYYY/MM/DD (Hex.)
-- --------- -------- ------ -------- ---------- --------
01 0016F005 01 06F0 05 2005/08/18 00001000
02 0276F111 27 06F1 11 2005/10/10 00001000
03 0016F25A 01 06F2 5A 2007/09/26 00001000
04 0F56F426 F5 06F4 26 2006/03/12 00001000
05 0016F533 01 06F5 33 2006/05/01 00001000
06 0506F533 50 06F5 33 2006/05/01 00001000
07 0016F6CB 01 06F6 CB 2007/09/16 00001000
08 0106F768 10 06F7 68 2007/09/16 00001000
09 0016F982 01 06F9 82 2006/09/03 00001000
10 0016FBB6 01 06FB B6 2007/07/13 00001000
11 0106FBB6 10 06FB B6 2007/07/13 00001000
12 0016FDA3 01 06FD A3 2007/08/13 00001000
13 00000000 00 0000 00 0000/00/00 00000800
14 01DF3417 1D 0F34 17 2005/04/21 00002000
15 00000000 00 0000 00 0000/00/00 00000800
16 0BDF4117 BD 0F41 17 2005/04/22 00001800
17 00000000 00 0000 00 0000/00/00 00000800
18 09DF4406 9D 0F44 06 2005/04/21 00001000
19 09DF4703 9D 0F47 03 2005/04/21 00001000
20 00000000 00 0000 00 0000/00/00 00000800
21 00000000 00 0000 00 0000/00/00 00000800
22 00000000 00 0000 00 0000/00/00 00000800
23 00000000 00 0000 00 0000/00/00 00000800
24 004F620F 04 0F62 0F 2005/12/15 00001000
25 034F6404 34 0F64 04 2005/12/23 00001000
26 00000000 00 0000 00 0000/00/00 00000800
27 00366004 03 0660 04 2006/06/12 00001000
28 00166138 01 0661 38 2007/09/19 00001000
29 00167106 01 0671 06 2007/03/29 00001000
30 01067106 10 0671 06 2007/03/29 00001000
31 00167404 01 0674 04 2007/06/08 00001000
32 01067404 10 0674 04 2007/06/08 00001000
33 0016760F 01 0676 0F 2010/09/29 00001000
34 0106760F 10 0676 0F 2010/09/29 00001000
35 0106770A 10 0677 0A 2010/09/29 00001000
36 01167A0B 11 067A 0B 2010/09/28 00002000
0 Warning, 0 Error occurred.
Done.
This is strange. Have a look at the one that I build. I don't have these 0000. All 36 Microcodes should have the latest revision. If you want you can verify it and if you find no mistakes in the one that I've build you can use this one as R3. I've flashed my board with it and everything is fine.Quote:
Originally Posted by SoLoR
Edit: I've compared the one that I build with yours and every microcode revision looks the same so I think that every microcode has the latest revision in my build.
now i see... you have a point, not sure where it went wrong :< just checked original 0001 and there is no 0000 microcodes in it... so DONT use my r3 right now:)
Are still using the Intel RST version 10.6.0.1002 with R3?Quote:
Originally Posted by SoLoR
If this is the case than maybe it's corrupting DATA when you save it to your disk. Try with the older driver and see if it fixes the 0000.
well no dunno whats wrong. it gets messed up when i try to replace all microcodes... tryed again and i got same mess :) not sure what ill do...Quote:
Originally Posted by Alien Grey
For example try to extract first microcode 15, then remove it and try to import it again.... and you see it will fail and i think that when you remove some microcode before 15 that 15 gets 000000.
here is fixed 1002b-R3. Someone please check if i missed anything... they are also in correct order so just check cpuid and platofrms :) problem was in new mmtool i was using (3.26)
edit: also a note, i didnt test this bios yet since im at work... :)
I didn't flash it with your fixed 1002b-R3 but I compared it with the one that I build. I don't see any differences so I think it should be fine to flash it with the fixed 1002b-R3.Quote:
Originally Posted by SoLoR
I'll give it a try tomorow.:up:
just flashed... it didnt brick my mobo so... hope it will work for everyone ;)Quote:
Originally Posted by Alien Grey
Thanks A-grey and SoLoR for the effort of updating the BIOS.
Now have you noticed any form of improvement??
nope... however microcode updates can improve preformance or fix errors (blue screens etc) so i guess it cant be bad thing :)Quote:
Originally Posted by leo27
I also flashed it with the 1002b-R3.:up:
Edit: I removed the BIOS download links to my builds. They aren't necessary anymore with the release of 1002-R3.
Glad to see you got the microcode sorted in the end.
You may find that slightly less vcore is required with the new microcode as apparently GTL improvements for QX9650 C0 was one of the fixes. I found this :)
Anyway with regards to the MSR issues I know that there are some people who believe that errors are expected.
Well I have done this test today on a DELL at work.
Attachment 118336Attachment 118337
Both pass with flying colours.
If Dell can do this, why can't ASUS?
John