Was the blue screen machine check error?
Printable View
Was the blue screen machine check error?
Believe it or not ASUS release BIOS 1702 for the Blitz Forumla which is much older than the Rampage Formula yesterday.....
Still no Rampage Formula or Rampage Extreme BIOS with fixed MSR :(
John
Result is;
Summary of impact: observed maximum latency = 519us
Summary: 4707 passed, 5 failed
I think this time i have found the cause of Blue Screen - Machine Check Error and is ATI driver 11.x.
So, i will reinstall soon SoLoR modded sound drivers along with ATI 11.3/11.4, which have been uninstall in order to track down the problem.
Bad news; random BSOD came again :(
I didn't look at the BSOD log but I think this time it is all about room temperature.
I couldn't figure out the problem exactly but now I know that Asus Maximus/Rampage Formula motherboards are not as they should be.
Try using Bar-Edit to set the MCH ODT timing to 11 (detailed in a post by A-Grey)
Quote:
Originally Posted by JohnZS
WoW!!! Nice.
:confused:
The latest instalment from ASUS:
:shrug:Code:Dear Valued Customer,
Thank you for contacting ASUS Customer Service.
Our related department told me Intel has not supply specifi defination about BWG.
Some devices need to use SMI in DOS, so SMI latency is normal.
Any specific problem when you use this BIOS except for the error?
Best Regards,
XXXX
ASUS Customer Service
Same question was asked before - for specific problem. Tell them you have in order to release BIOS :)
Yeah I had exactly the same answer from ASUS, since then, nothing :-|
The question is why other boards don't have these errors and SMI latency issue? :shrug:Quote:
Originally Posted by leo27
Correct me if I'm wrong but aren't these MSR errors a compatibility problem and isn't this the reason why there should be a BIOS update? :confused:
That was pretty much my reply. It seems ASUS has no idea so instead of asking Intel they said its normal
Today i found new RapidStorageTechnology ROM 10.5.0.1034 at StationDrivers (http://station-drivers.com/page/intel%20raid.htm). Could someone (SoLoR?) include this to the latest BIOS? :)
Better wait for WHQL
Nice find beesee.:up: Where have you been all this time? :DQuote:
Originally Posted by beesee
There should be a newer ROM version that might work and maybe it's this one.
I'm thinking of buying an OCZ Vertex III 120GB SDD and a Western Digital Caviar 2TB Black Edition. Anyone using one of these on the ASUS Rampage Formula?
I had this option rom for a while and it wasnt compatible with x48/ich9 (none from 10.5.0.xxxx branch where)...however today there was new option rom 10.5.1.1070 that works! so here is a bios: http://hotfix.chris123nt.com/Asus.Ra...D/1002b-R1.zipQuote:
Originally Posted by beesee
i temporarly upload it here since my original hosting of other rampage formula related things FTP crashed and i cant access it... anyway this bios have intel option rom 10.5.1.1070 and jmb 1.07.28 (i droped 1.08 branch since it seems they dont developt it). Also since now on ill mark bioses as revisions, this is R1 so if you see R2 it means something got changed :)
Hi SoLor, thanks for your great job!Quote:
Originally Posted by SoLoR
Only one question:
slp included as previous release?
yes everything stayed the same... just intel and jmb option roms got changed... also one more thing jmb option rom is not tested, since i dont have any IDE devices anymore... so if anyone gets any problems let me know (but there shouldnt be since 1.07 branch of JMB worked fine a year ago....).Quote:
Originally Posted by akirait
Thanks!!!!!Quote:
Originally Posted by SoLoR
I have the option rom 9.6.0.1014 with a RAID 1.
I had to disable the write back cache because I had to rebuild the raid one/two time per month (one hd randomly disappears while I use the system), now i'll try the cache with this option rom.
Hi. Got this motherbord 2nd hand and want to try to get an e8400 stable at 5ghz. What is the best bios for this?
I have 2x 1TB Caviar Black connected to mine... I'm assuming the 2TB and the 1TB models are similar. Haven't had any issues with them.Quote:
Originally Posted by Alien Grey
Thank you SoLoR, works fine! :-)
Thanks SoLoR.:up: I'll give it a try tomorrow.Quote:
Originally Posted by SoLoR
SoLoR's MOD BIOS. Everything else isn't worth flashing.:DQuote:
Originally Posted by kamieldehond
OK, thanks.Quote:
Originally Posted by DrTeal
Thanks SoLoR!!
About the JMicron ROM is the 1.07.28 version newer than the 1.08.XX that was in your previous BIOS??
Cheers
yes 1.08.01 is from 2009 and 1.07.28 is from 2011 :)Quote:
Originally Posted by leo27
So have Intel ratified a 10.5.x ICH9R firmware?
The latest ASUS provided me with for my RE was 10.1.x?
Must admit I am curious to see how they perform with the new 10.6 WHQL Matrix Storage Manager.
John
I have no idea if 10.5.1 rom is offical for ICH9R, but it works... and yes latest rom that worked before this was 10.1., no 10.5.0 worked on ICH9R and i tryed 3 different roms...Quote:
Originally Posted by JohnZS
Weird it doesnt work form me, it hungs on intel orom after few sec and some artifacts appear on the screenQuote:
Originally Posted by SoLoR
It works just fine for me. How did you flash the BIOS?Quote:
Originally Posted by pajda
Clear CMOS -> Load Setup Defaults -> Flash BIOS -> Clear CMOS -> Load Setup Defaults
That's the way I do it and I never had any problems flashing the BIOS.
AFAIK, the most reliable updated O-ROM to date is 9.6. Newer versions on X38/48/P45 chipsets just don't seem to work right.
works fine for me as well, or i wouldnt upload rom at all. Intel Raid ROM i always test since im using RAID0, jmb one is never tested (no IDE devices and i have it disabled anyway).Quote:
Originally Posted by Alien Grey
Than we must be very lucky because it seems to work fine with Windows 7 X64 and Ubuntu 64 bit.Quote:
Originally Posted by Ket
You know a lot about modding a BIOS. Is there anyway we can fix the BITS MSR fails or are we screwed when ASUS doesn't want to fix it?
I tried both configured as IDE and AHCI and I didn't have any problems.Quote:
Originally Posted by SoLoR
Same way i did it, i could even get into the config witch ctrl+l, setup raid, etc, but just 1 sec after i exit it hangsQuote:
Originally Posted by Alien Grey
Tried with ezflash and afudos /pbnc /n
I will try again - removed oem logo and nic oroms, i suspect that my lsi 9260 could intefere with this new intel orom coz its size is bigger than 10.0.x
Quote:
Originally Posted by Alien Grey
I can confirm that BIOS update from SoLoR works for me, no issues here. I am using RAID0 aswell. But I haven't tried to edit/change my RAID0 array in the BIOS.Quote:
Originally Posted by pajda
I'm also using the newest Intel Chipset & RST drivers in Win7 x64.
Have you tried to reflash?
Alien,Quote:
Originally Posted by Alien Grey
I'm using the OCZ Vertex II 240 GB SSD and Seagate Momentus XT 2TB with the X48 RF. Used Acronis to image my W7 Prof 64 to the SSD and have cold boot error ever since. OCZ said the only solution is to do a clean install, no imaging. Got a replacement from Amazon and it did the same thing. If you're willing to reboot on cold startup everytime, it's very fast, otherwize I'd pass unless I was doing a clean install. Also, Vertex III is a waste on X48 since it only supports SATA 2.
JBJ
I'm using Ghost to make my backup images and I didn't have a problem to restore my backup images on my OCZ Vertex 3. I don't think that an OCZ Vertex 3 is a waste. I see it as a good investment for the future.:DQuote:
Originally Posted by jbjsm
A waste is buying a cheaper SATA 300 drive to use on a SATA 600 board.
I've tested both drives with EVEREST Disk Benchmark.
http://i431.photobucket.com/albums/q...kBenchmark.jpg
Since i see you still try to access moded bios on that address i gave before, i want to tell you i moved it to here
@Alien Grey
Aida64 is "new" Everest...
My first experiences with the OCZ Vertex 3 and the ASUS Rampage Formula.
Getting the drive to work on the ASUS Rampage Formula isn't a problem. A big minus is trying to update the firmware. It isn't possible to update the OCZ Vertex 3 firmware when it's your primary drive.:confused: That's a big problem because for most users if not all users it's the primary drive.
I've tried a few Windows boot cd's but it didn't make much difference. Then I've found on the OCZ forum a set of Linux tools to make an USB boot drive with everything necessary to update the firmware. With these tools it was possible to update the firmware but it wasn't easy. When I tried to update the firmware it wasn't possible because the drive is locked. Unlocking the drive isn't difficult you would think because there's also a tool available to let the computer go in to sleep mode. Than you wait a few seconds to make the computer wake up again by pressing the power button. A big problem on the ASUS Rampage Formula because when the board tries to wake up from sleep mode it fails to do that and reposts.
If that doesn't work than there's always the hard way. Disconnecting the power from the drive and wait a few seconds before reconnecting it again to unlock the drive. This sucks when it's hard to reach the power cable.
Finally. It's now possible to update the firmware. Great but not so great. To update the drive with the latest firmware you've got to edit a file so you don't end up with an older firmware like me. Great now you can do the whole hassle again.
After a few hours, I'm using the latest firmware which results in a performance decrease and a broken side panel fan that can't be fixed from all the hassle trying to update the firmware.:shakes:
Hello everyone,
please, what's the difference between 1002b-R0.zip and 1002b-R1.zip ROM files?
I have appreciation for SoLoR's work since his Creative X-Fi modded drivers!
Thank you :clap:...
LE: Think it's the old BIOS, judging by it's build date...
R0 is old, with jmb 1.08.01 and intel 10.1.xxxx, R1 is new with jmb 1.07.27 and intel 10.5.1.xxxxx
Would be cool if there was someway to fix the BITS errors and the SMI Latency as ASUS support really just do not care.
I appreciate that our boards (Rampage Forumla and Rampage Extreme) are long in the teeth now and are perhaps just out of the 3 year support period... BUT surely it is not unreasonable for ASUS to release the source code when products reach EOL.
That way developers can address any bugs which may still be in the code, or develop custom BIOSes which get the best out of our boards.
It just feels "selfish" that we spend out on the hardware, only for the firmware to let us down.
John
Can you sum up what the problem is (to the end user noticeable), when BITS errors and SMI Latency present?
My 0x124 BSOD are still here and i will low my overclock once more (CPU only), unless BSOD is related to these 2 things.
i'm getting the same thing. strange.Quote:
Originally Posted by pajda
And nothing attached to the ich9r is visible as a bootable drive.
Hey guys, wanted to get your input on this BSOD (code 0x124) I got yesterday...
Less than one year ago I moved into my current apartment which isn't air conditioned besides my crummy window unit. Due to the heat in the US right now my A/C unit is barely able to keep ambient temps below 80F (27C). I seem to recall reading somewhere that the rampage formula will randomly BSOD once the ambient temps get up high enough, and I was wondering if anyone can confirm. I have passed hours of memtest, prime, linx, run heaven/3dmark, and the evga oc tool for stress and none of them have made me BSOD, but that was in the winter with ambient temps around 65-70F (18-21C). I've checked operating temps and even with the heat my CPU tops out around 55C under gaming load - lapped and have push-pull washermod TRUE. My gfx cards top out around 60-65C.
Basically is this just crashing due to the freak heat wave or is it possible I'm seeing some processor degradation? Is it likely that the component failing is infact the motherboard since my cpu and gpu temps are pretty well under control? I've been running 3.6 GHz for about two years at this point but I did upgrade from 4GB to 8GB ram this past winter and upgraded from gtx 280 to gtx 470 sli. If it is just due to heat am I better off not using the computer for gaming until after it passes (do I risk degradation due to more extreme operating conditions)? Any suggestions?
Thanks in advance.
EDIT: more details:
CPU: 400x9, 1.525V bios, 1.504V real, LLC enabled
other settings: CPL 7, FSB strap 333, nb: 1.41V, vtt: 1.34V, 100ps delay on cpu and nb
DRAM: DDR2800, 4-4-4-12, 2.2V bios
gfx cards at stock speeds atm
It's possible that the MSR fails and bad SMI Latency are causing these 0x124 BSOD. To know that for sure you would need a BIOS without the MSR fails and better SMI latency and that's impossible because ASUS doesn't want to fix it although it's a compatibility issue. It's the ASUS support at it's best. They also promised a few times on the XS forum to update the Option ROMs in their BIOSes but that was also a long time ago.Quote:
Originally Posted by Spyrus
Very strange. I'm doing great with that BIOS. No issues with Windows 7 X64 or Ubuntu 64 Bit.Quote:
Originally Posted by spy2520
Ubuntu Disk Benchmark
http://i431.photobucket.com/albums/q...-Benchmark.jpg
The OCZ Vertex 3 likes this board and BIOS. The drives speed is limited because of SATA 2 but it runs without issues and that can't be said by everyone with different boards.:D
Don't worry it's probably because of the higher room temperature. I also had to go back to CPU Clock Skew Delay 200ps and NB Clock Skew Delay 100ps and bump the NB Voltage a notch to keep everything stable. I would also need more CPU Voltage to keep Prime95 running without BSOD but I don't care much about it as long as she's running BOINC stable in Ubuntu.Quote:
Originally Posted by DrTeal
But all Bioses have these issues,right? 0902 had no issue for almost a year with higher clocks than i am using now with latest SoLoR modded.Quote:
Originally Posted by Alien Grey
I will lower once more Core MHz and keeping same voltages, because once i did that the BSOD were less frequent. (9x450 went to 9x445)
i cant even make it that far. My boot drive is an array of 3 intel 40GB ssds. The raid controller is crapping out on boot so no OS for me. it appears that it could still boot from an external device, but all the internal drives just wont show up. But they are listed when the raid initializes. Thats when it locks up though.Quote:
Originally Posted by Alien Grey
Yes, all BIOSes have these issues but all BIOSes also trigger the 0x124 BSOD. The 0x124 BSOD is a genuine MACHINE_CHECK_EXCEPTION BSOD. It's a CPU malfunction. That's all what I could find with debugging the minidump.Quote:
Originally Posted by Spyrus
This is what Intel has to say about this issue.
Hmm... "Missing proper microcode...".:rolleyes:Quote:
Potential Causes for Machine Check Exceptions
MCEs are difficult to debug mostly because of the large number of potential
causes. Some of the potential factors are:
• Violations to board design guidelines. For example, routing traces over
power and ground planes may cause unwanted noise and inadequate
signal spacing may cause signal integrity issues.
• Operating the processor out of specification. Examples include over-
clocking of the CPU and front-side bus speeds. The behavior of the system
cannot be predicted when the processor operates out of specification.
• Environmental factors, such as: alpha particles or cosmic ray hits,
extremely hot, and cold temperatures.
• Improperly fitted heat sinks or fans and incorrect hardware installation.
• Missing proper microcode updates that could contain fixes for known
processor errata.
• BIOS setup issue or OS issue may cause MCE handling scheme to behave
differently.
• Faulty components, such as: add-in cards, DIMMs, etc., can also cause
system errors that may eventually lead to a MCE.
Maybe this raid isue is already fixed in version 10.6.x.Quote:
Originally Posted by spy2520
maybe... however we cant find out right now, since currently 10.6 rom is not working with rampage formula... tryed it few days ago.Quote:
Originally Posted by Alien Grey
I have done myself minidump debug also.
Sometimes it is VGA related or so (dgmms something at stack) and other times no possible explanation.
All are VISTA_DRIVER_FAULT for sure, but no particular process is repeated at stack trace
What do you mean with not working?Quote:
Originally Posted by SoLoR
Do you mean that you couldn't replace it with the 10.6.x or do you mean that it doesn't work with your configuration?
If you mean that it doesn't work for you maybe it does work for someone else.:shrug:
VISTA_DRIVER_FAULT is also something that I noticed but I still think that it has something to do with the CPU implementation in the BIOS because the time before I run in to a 0x124 BSOD is longer when I give the CPU more voltage. I wish there was a way to try it with a BIOS that doesn't have these MSR fails to see if it fixes the 0x124 BSOD issue.:(Quote:
Originally Posted by Spyrus
not working as not booting... it never gets past intel raid rom in boot procedure... I can even enter in raid setup but it will never gets past, so i doubt it would work for anyone else, its just some incompatibility like i saw them before... i have a feeling that they slowly stop bothering with ICH9R/X48 support. For example: between option roms 8.0-10.0 there was like 80% of intel option roms (the ones that i tryed) working with our mobo without issues, now from 10.0-10.6 there where like 2 out of 8 or 9....Quote:
Originally Posted by Alien Grey
The reason that I'm asking this is that maybe they only work if you use a RAID card. Maybe it's worth a try for those who can't use your latest BIOS MOD.:shrug:Quote:
Originally Posted by SoLoR
Maybe I've found some help after all.
http://www.bios-mods.com/forum/Thread-ASUS-Rampage-Formula-BIOS-MOD
While you're there have a look on that forum you'll be amazed what these guys are able to do with a BIOS.:D
Great find Alien Grey! Lets hope they can work some magic!
Maybe you want to upload the BIOS into your post, so they can take a look at the code.
Only a suggestion, since others have gotten help this way....
I leave that for SoLoR. It's his MOD BIOS and he can add a link to his BIOS if he wants to do that and maybe also add a link to his Supreme FX II drivers.Quote:
Originally Posted by Senator
just feel free to do it if you want. I know i wont be messing with things like this on my own because you can easly brick your mobo....Quote:
Originally Posted by Alien Grey
Interesting site Alien
I am curious to see how you get along. I have not got anywhere in my quest to resolve the MSR errors on my Rampage Extreme.
So far I have incorporated the latest Microcode revision (60F) for my QX9650 and this did not resolve the MSR issue.
Have also tinkered with the BIOS ASUS provided me with (the one with the manual multiplier fix for QX9650 and 10.1 Option ROM). The 10.6 Option ROM appears to work on my board, HOWEVER DPC latency is increased so I rolled back to the original BIOS ASUS provided me with, but modded with the latest microcode for the QX9650 (60F as opposed to 60C)
I am pretty much at my wits end with latency and MSR test results and I think this is not going to be fixed by BIOS mods as we need the source code.
I have Option ROM 11.x for ICH10R however I have not tried putting this on my board yet as I am not confident it will work properly as these new 10.5+ ROMS seem to be optimised for Z68 series boards as include a lot of things for Performance features (caching) which rely on board features our systems just do not have.
In my mind the last proper ROM for our boards is the one ASUS provided me with inside a BIOS (10.1) However your milage may vary on the 10.5+ ROMS, however I fear you may encounter memory mapping issues with other Option ROM's as the size is quite big (119KB Vs 85KB).
So some users may have luck as they have more onboard devices disabled.
SoLoR is a BIOS mod expert and I think he maybe referring to those sorts of issues with the 10.6 ROM where offset hacking etc might be requried to even get it to work on some boards.
:(
As unXtreme as this sounds if it ain't broke, don't try to fix it. The 10.1 ROM is very good for my SSD's :P
John
Maybe I do that and make a new thread in the AMI BIOS Unlocking Request forum. Posting in the General help forum seems to lead to nowhere.Quote:
Originally Posted by SoLoR
Today I've flashed my BIOS back to 1002 R0 to see if there's any difference in performance of my SSD. The performance is almost the same with a very small gain with BIOS 1002 R1 (Option ROM 10.5.x). I also checked my HDD and SSD for errors after a few weeks with Option ROM 10.5.x and everything looks fine. Maybe it's just like you're saying. I've got a few things disabled in the BIOS and maybe that's why it's possible to use Option ROM 10.5.x.Quote:
Originally Posted by JohnZS
Did you notice any difference in performance or stability with updating the Microcode?
Good idea on that post in the AMI forum Alien :)
Well I have not noticed anything, but the good news is I have not had any issues. Seeing as Intel released the update officially on their site and it was incorporated into the latest XEONS on the 775/771 platform I think it is probably worth implementing as microcodes from their very definition are bug fixes.Quote:
Did you notice any difference in performance or stability with updating the Microcode?
Sadly I cannot find a changelog :(
(Will see if it is on a document anywhere). Needless to say the 60F revision was the last microcode for C0 QX9650 CPU and Quad Core Xeon.
Out of curiosity I tried that latest Option ROM 11.x I cannot BOOT with this as the RAID Option ROM does not work :(
It appears my "theory" is true, BIOS released for X58 you can use the Option ROM for ICH9/10R however BIOS released for 6 series motherboards are highly unlikely to play nicely with our boards (unless the Option ROM has also been ratified for X58).
10.6.1091 is an X58 ROM as is the only 10.5 ROM which works on our boards...
John
BTW this is the official Microcode File I used
Oh and this Tool here to extract the microcode
BE VERY VERY VERY VERY CAREFUL
Well you have rampage extreme right? for rampage formula 10.6. is not working, but 10.5.1.xxxx is.... i didnt try 11 version yet since i was working until whole day and didnt find a time.... i will tomorrow....Quote:
Originally Posted by JohnZS
about that microcode update, i dont feel like updating that if it doesnt fixes anything, because if something goes wrong and you cpu doesnt get recognised anymore you can brick your mobo...
Yep, I do have the Rampage Extreme.Quote:
Originally Posted by SoLoR
The early 10.5 Option Roms (which were released for the Z68 exclusively) did not work, however 10.6.0.1091 does work and one of the later revision 10.5 Option Roms does work, however I am using 10.1.1008 as this is what ASUS provided me with in a BETA BIOS, and I found this seems to (for me) work slightly better than 10.6.0.1091.
Oh yes Microcode is VERY risky business, I only tried it myself as I knew the revision of CPU I had and where to patch it and that the patch was compatible (I tested the patch via software using BITS as you can test your microcode in a software environment there and it was only then after booting from BITS into Windows and messing around for an hour or so that I felt confident in patching the code into the BIOS). AND only then...because I have a spare BIOS chip which I can fallback to if all goes wrong.
I would not be taking such a risk if I did not have so many countermeasures.
Attachment 118231
I am curious to see if you have any luck with the 11 Option ROM as I had no luck at all :(
Either way you are very much the expert in this field and I am sure like many of us on the forum I would like to thank you for your persistence in keeping the Option Rom's updated where ASUS have failed. (I only dabble, you are an artist!)
John
1002b-R2 with working intel raid option rom v11.0.0.1124.
Kudos on getting Option ROM 11 to work, I could never get it working :(
(perhaps I messed up my extraction).
John
Anyone test it yet?
Thanks SoLoR. I can confirm that it works for me.Quote:
Originally Posted by SoLoR
I also updated the Microcode for my Q9650 E0 from A07 to the latest A0B.
http://i431.photobucket.com/albums/q...ode-Update.jpg
I did this for my cpu as well... from 705 to 70A.... however i dont just want to go and replace all... so if anyone have any request what CPU microcode to update for R3, write here and ill do it (you need to give me cpuid), but i wont just go update all 36 microcodes....Quote:
Alien Grey;4914310I also updated the Microcode for my Q9650 E0 from A07 to the latest A0B.
I tried that but it's almost impossible to do it without the AIDA64 CPUID information. Some of them are easy to match with the old ones but others are almost impossible to find the updated microcode without the CPUID. Maybe there's an easy or logical way to update them all but I don't see it.:confused:Quote:
Originally Posted by SoLoR
if possible please update for E8500 (SLB9K) CPUID : 01067Ah
E8400 for me if you can to update microcode but what the reason to do it?
I hope you do not mind me asking, but are you using RAID0?
If I get the time this evening I will try and repatch my BIOS with the 11 Option ROM as I think I may have messed up my extraction :(
(seem to have difficulty extracting the new Z68 BIOS compared to the X58SO2 BIOS).
I am such a n00b compared to you guys :P
John
i have already done on my local copy for 01067Ah and 010677h... i also went thrue all updated microcodes and here is the list:Quote:
Originally Posted by papatsonis
Attachment 118259
if you see you cpuid among listed ones i can update microcode and you should poke me... but i wont just update all, since there is always risk of bricking mobo for that cpu...
honestly no idea, tryed to find somekind of changelog but i couldnt... but im sure there was a reason intel released new version of microcodes.... what exactly microcode does you can read on wiki...Quote:
Originally Posted by Spyrus
thing is, on some efi bioses some header is added in this option roms that needs to be removed. I didnt extract this 11 version my self, so i dont know what was original format.... but im my bios there is "clean" version so if you extract from my bios it should work unless its really incompatible with your mobo...Quote:
Originally Posted by JohnZS
I think that I've found a bug with the new Option ROM. It won't let me use the Official Intel WHQL RST driver Version 10.6.0.1002.
Don't ask me what's wrong but trying to install the drivers fails with an error telling me that some stuff couldn't be installed.:confused:
Anyway I could fix it with using the Intel WHQL RST driver Version 10.5.1.1001. This one can be downloaded from Station-Drivers.:)
are you trying to install whole package or just drivers? because i never install whole package...Quote:
Originally Posted by Alien Grey
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