• Opera Pms Version 5.0
• Android Version 5.0

I have a trouble with a mobo that has a pci-e ssd from ocz: if i set the ichr10 in raid mod then the card is not bootable.message about problem size i have a module intel for raid and ahci plus one module adaptec for raid. I booted today win10x64 with intel ahci loaded and was able to use old driver and get the drive but tool for windows was not able to get card 'drive' while the bootable linuxtool can in bios of card there is an option to solve trouble but i did not found it in tools. If i change intel rom that is v10.6.0.1091, will that solve my bug or i should do something else? I add a pic of the bios: there are 5 modules with index 20, i exchanged it and try to upload result file.

Opera Pms Version 5.0

I wonder how i can update my cpu microcode, topic is not clear for the way to do well. Latest cpucode is from march 2011, cpu are xenon x5660. If i can do others update, i am ready to try. Zitat von im Beitrag if i change intel rom that is v10.6.0.1091, will that solve my bug or i should do something else? I doubt, that the Intel RAID ROM version is responsable for your problem. Nevertheless I recommend to update it to v11.2.0.1527 and to use the Intel RST driver v11.2.0.1006 for your Intel SATA RAID Controller. Zitat i wonder how i can update my cpu microcode, topic is not clear for the way to do well.

You are right, the CPU Microcode update procedure is missing within my guide. Simple reason: I do not write any instructions about something, which I have never done myself. So if I would get a step-by-step instructions about how to do it by someone, who has successfully updated the CPU Microcode of an AMI non-UEFI BIOS, I would add it to my guide (with credits to the author). Zitat von im Beitrag Stumbled upon this page while trying to figure out why my new Win10 installation gives me BSOD's once in a while with the latest RST installed. Ended up realizing I have an antique ROM for my old ICH8R (running RAID 1) dating back to 2008! Updated Intel RAID ROM to version 11 with the help of your guide. Dunno whether that will solve my BSOD problem, but it feels good to be running on newer firmware for my RAID chipset.

Note - Updating ROM alone will not be enough it seems! I learned it the hard way - continued sporadic BSOD's that eventually crippled the entire system. If you have an older chipset (I have ICH8R) and you want RAID enabled, you will probably need to modify your Win10 installation image to include a legacy Intel RAID driver also before anything else. Details here. Did it while ago, but as an ungrateful bastard, never come back to say thanks or give feedback.

Using your guide I successful modded my P6TD Deluxe BIOS. One caveat, this BIOS, like some others Asus P6T., doesn't support modules bigger than 100kb, so the latest one that fits is the classic Intel RST v10101008. Even removing another stuff from bios, bigger ROM's can't be added, seems like there is a fixed space allocated for these ROM modules. I don't have SSD, but 2 mechanical drives in RAID 0.

RAID is pretty solid, system is snappier as it can be. I also updated intel microcodes with latest I7 and Xeon support, Marvell Yukon PXE and Marvell E-Sata rom. Windows 8.1 install imaged edited with NTlite, removed iastorav.inf (Intel RST v12.0.1.1019), and replaced by Intel RST v11.2.0.1006. : Thanks for your feedback!

Android Version 5.0

Zitat von im Beitrag One caveat, this BIOS, like some others Asus P6T., doesn't support modules bigger than 100kb, so the latest one that fits is the classic Intel RST v10101008. Even removing another stuff from bios, bigger ROM's can't be added, seems like there is a fixed space allocated for these ROM modules.

No, it is not a space problem. The problem of BIOSes like yours is, that bigger sized Intel RAID ROM modules canned be loaded while booting. So the BIOS would need another Option ROM loader, but this can only be done by the mainboard manufacturer. Hello everyone. Sorry for the long post, but it was necessary in order for me to fully explain my problem. So here's the story, my 9500 M GS on my Asus M50SV died a few weeks ago and I just bought a 9300 M GS to replace it. The laptop turns on and I can hear the bios chime, but there is no video signal sent to the screen or via the dsub port.

I know from exploring my bios in AMI MMTool (3.26) that the original bios version 207 can only recognize 8600M gt and 9500m gs as well as an ati graphics card. That being said, I wanted to add a module to my bios, so I started by extracting the 9300M gs module from the M50VA's bios (same age laptop that came with the 9300M GS). So far, everything was going well. When I tried to insert the module I extracted into thz m50sv bios, things got complicated. Easycap driver windows 10. In fact, it would appear in the list with «POST» as module name, is that normal?

So all that beng said, here are my questions -how do I add the 9300M GS module to my bios? -once this module is added, how can I flash my bios with the modded rom?

I heard about blind bios flash, booting while holding ctrl+home etc, but didn't work for me. Is there another way? Keep in mind I have no video signal, and that all the work I'm doing on MMTool is being done on another pc Thanks a lot for your help Best regards. : As I have already written, I cannot help you, because I don't know, which BIOS modules have to be replaced or modified. Zitat von im Beitrag So here's the story, my 9500 M GS on my Asus M50SV died a few weeks ago and I just bought a 9300 M GS to replace it. I know, that this question doesn't help you at all, but I ask it nevertheless: Why didn't you buy a 9500 M GS? The problem you have now is not only the modification of the BIOS.

Much riskier is it to get a modded BIOS properly flashed into the BIOS chip of a Mobile system.