Cannot flash Intel MEI firmware on p67a-gd65

well, since the first thread was locked up https://forum-en.msi.com/index.php?topic=144484.0 I think there should be another one to point out this problem. MSI knows of it (here: https://forum-en.msi.com/index.php?topic=144484.msg1080605#msg1080605) but we still haven't seen official responce or a fix to it. Maybe the fix should come from intel itself? p67 revised anyone?
Post your comments here if you cannot flash the firmware.

HU16E, you made the following statements in your first reply to pepe123's initial posting:
First:
Quote
If you have attempted to load the ME driver off your install disc & it fails, the chipset does not have the firmware installed.
Second:
Quote
This can be verified by the absence of the Intel Management Engine Interface not showing up in the Device Manager.
Third:
Quote
The 6 series chipset must be replaced. With almost 100% certainty
When I asked questions and commented on these statements I was not "attacking" you or "provoking" you into some sort of "debate".  Stop projecting that and please refrain from taking such comments personally as this will intoxicate any kind of discussion.  I was asking honest questions about the premises of your propositions.  
Your first statement implicates a connection between "the ME driver" on an "install disc", the failure of installing that driver and the absence of the ME firmware as a consequence of that failure.  That is a connection that I simply did not understand (and still do not understand).  
Your second statement interpretes the fact that the Intel ME Interface does not show up in device manager as a 'verification" of what is implied in the second half of your first proposition (absence of firmware).  Again, I do not believe that the former necessarely verifies the latter. And if you think so, please elaborate on that.  It is not clear to me what premise that assumption is based upon.
Your third statement posits a chipset replacement as the only solution, and again, I did not (and still do not) understand the reasoning behind that conclusion in regard to statement 1 & 2.
Quote
I know very well driver & firmware are not the same thing, & can't believe that was brought up.
I brought it up because you drew a connection between a (Windows) driver on a disk and the ME firmware in your first statement:
Quote
If you have attempted to load the ME driver off your install disc & it fails, the chipset does not have the firmware installed.
Quote
A recent interpreted statement about 'all' the mainboards not being affected is believed to be incorrect on your part.
I am not entirely sure what you are referring to, but I am assuming that you are talking about something I said regarding the Intel Statement that only systems that were shipped since January 9th were affected.  Under the conditions of the information available at the time I made that statement, it was not an unreasonable one.  However, I have no idea what that has to do with the ME Firmware question.
Quote
Rather than brow beat me
Again, you need to stop taking comments as personal assaults.  It was not my intention to "brow beat" you.
I am interested in trying find shed light onto the problem in question here without hastening to early conclusions.  Based on the facts available at the moment I simply not willing to settle with an "absence of ME firmware" explanation that can only be solved with a chipset replacement.  Even if that turns out to be true, there is no sufficiant information available at the moment to infer that or make it the only/necessary conclusion.  Let's keep a room for the possibility of other explanations as well.  That is all I am saying.
Quote
educational respectful correction with confirmed facts is always a good thing for everybody concerned.
Svet has made some tests in conjunction with someone from MSI to determine where exactly the ME Firmware is actually "stored".  He found out that (at least in the case of P67 systems) that firmware is stored in respective area of the BIOS Chip, the same chip that holds the actual BIOS/UEFI Code. The following paper also indicates this as well:
http://webcache.googleusercontent.com/search?q=cache:mi50f3Vy534J:web.it.kth.se/~maguire/DEGREE-PROJECT-REPORTS/100402-Vassilios_Ververis-with-cover.pdf+Intel+me+firmware+resides&cd=17&hl=en&ct=clnk&client=firefox-a&source=www.google.com#88
Page 11/26:
Quote
The management engine’s (ME) persistent code resides in firmware within the same flash memory device as the BIOS, in computer systems [...].
The P67 chipset diagram also points into that direction:

Similar Messages

  • Should I update Intel MEI Firmware or not?

    You know, there is this little chip on every last-gen laptop's motherboard (apple macbooks either) called Intel Management Engine Interface (MEI), and it has its own firmware that is upgradable. I'm currently running Windows 8.1 via Bootcamp on my MacBook Pro 13 (Late 2013 Retina, Haswell based), and it has the Intel MEI Firmware verion 9.5.3.1526, you can check it yourself using Intel MEInfo Tool (detailed info here):
    The question is, can I update this firmware with the newer one that is available (version 9.5.41.1904) here? Is it safe or not? Anyone tried?

    Zhyrnov wrote:
    The benefits are the same as with BIOS\EFI update like bugfixes, improvements, etc. Probably, this new firmware resolves the known 30% CPU Idle issue, I don't know, but I want to try.
    You may want to create a system restore point before you update, so you can roll back easily.
    Zhyrnov wrote:
    Apple boards are nothing but the same Intel boards with Intel chips and logics using some kind of custom design, so I think it is not so much Apple-related thing.
    Apple has written a lot of their own firmware, the latest example is the iMac 5K with ATI cards, which have issues with WHQL drivers. GPU drivers are also similar. Another example is the absence of WiDi on Intel hardware, since Apple has their own AirPlay. It is worth a test, if you keep careful backups of Windows and the OSX to be prepared for disaster.

  • Blank Screen and flashing cursor on new build-P67A GD65 (B3). Help needed.

    As per the title, a computer was built for me with the following specs:
    CPU: Intel Core i5 2500k
    Cpu Cooler: Arctic Freezer xtreme Rev 2.0,
    Motherboard: MSI P67A – GD65 (B3)
    PSU: Super-Flower Amazon 550W
    RAM: 4GB G.Skill RipJaws-X, DDR3, 1600
    HDD: 1TB Samsung Spinpoint F3 7200rpm
    Graphics Card: Sapphire Radeon HD 5850 Xtreme - 1 GB GDDR5
    Disc Drive: Samsung SH-223C DVD+RW
    Case: Cooler Master 690 II LITE Midi-Tower
    OS: Windows 7 Ultimate
    Everything went ok with the build and installation of the OS. Computer was booting ok. When I took the computer home that evening, powered it on and a blank screen with a flashing cursor on top left hand corner appeared. Tried several times but failed to boot up properly. Just to note that I can enter into the BIOS and it recognizes HDD, processor, Disk Drive and RAM. What I have done so far (of course with advice from computer experts as compared to me) are the following:
    1. I removed all the parts except cpu and cooler then put them back. When I restarted a message appeared that win7 need to do a repair. It went thro the process and then it stated it can’t do repair. Did this twice. When I restarted the third time, a blank screen with the blinking cursor appeared again.
    2. Cleared the BIOS using the button on the outside of the motherboard and also once using the jumpers inside the motherboard. After doing this, I pressed on the “”ON” button several times (with no power on to the computer) to dissipate any current that was left there.
    3. Interchanged the RAM on different slots. Also tried using only 1 stick of Ram at a time.
    4. Checked the HDD on another machine and it was ok. Formatted the HDD on the other machine, plugged onto new machine and tried to install OS again but no joy.
    At this point, I’m now stuck after almost a month when the machine was built. Would it be the motherboard? RAM? etc. Just wondering if I should RMA the motherboard since it is just over a month when it was delivered.
    A point to note, there is a message that comes up when it is booting stating no HDD is detected. I googled this but found out it was to do with a marvel adapter that needs to be disabled or something like that. However, it was mentioned that this wasn’t going to affect the performance of the pc as the BIOS can detect all the components.
    I also noticed that when I switch on the pc, there is a small pause before it kicks on then there is a long beep followed by 2 small beeps. I presume this is normal.
    Any help on this will be highly appreciated?

    Quote
    I also noticed that when I switch on the pc, there is a small pause before it kicks on then there is a long beep followed by 2 small beeps. I presume this is normal.
    Disable EuP 2013 & that should take care of the pause. The beeps are normal at startup. Only time I have observed a blank screen & blinking cursor is if the system wasn't getting enough juice to initialize, or their was insufficient power in an OC attempt. What kind of +12V amps does that PSU you have provide?

  • RAID & AHCI devices on the intel sATA's? P67A-GD65 (B3)

    Since i stuffed a 6TB WD Green in my system to use for the bulk stuff i just have to keep, i decided i would go ahead and get the most out of the drives i already had in my system as well, and screw the tiny chance of a data loss, i can just regularly backup the raid to the big old slow drive, and live with it.
    Anyway, so i have a Samsung 830 SSD (120gB) as boot / system drive, and 2x Seagate 500GB sATA drives i wanted to raid up to a stripe RAID.
    The Samsung 830, and the 6TB WD Green hangs of the Intel 6gbit sATA's, and the Seagates hang of the Intel 3gbit sATA. Simply since thats the fastest combination available. However, since the system is up and running, i ran head on in to an issue. You can only switch the Intel channels to RAID as a group. You don't have to include all the drives in the RAID, which of course means drives not included will show up as what they are, single drives available to the OS. However, the AHCI bit's apparently aren't enabled then, and the system fails to boot of the current install on the SSD.
    Back in 2011 Intel stated that RAID on their sATA chip's would enable AHCI, but the only reason for BSOD's on boot that i can come up with, is the lack of AHCI, while the OS expect AHCI.
    Is there a workaround / fix for this? At this point i wont pull the rack out just to move the 2 drives to the Marvell chip, and live with the lower speed. Mainly since it's quite the elaborate procedure to pull the darn case out of the rack cabinet...
    Edit
    In the interest of being thurogh. I got a i5 2500K on the motherboard, and i think i'm running 1.9 BIOS or something. I'm not quite able to reboot right now, but it was the "last one" before they started making magic stuff which made the motherboard twitchy if you updated to a Ivy Bridge BIOS, and ran a Sandy, and vice versa.
    If it makes any damn difference, i'll check the BIOS once my current batch of file transfers are done... Which is in something like 20 hours.
    /Edit

    Quote from: JLio01 on 29-April-15, 08:56:45
    When you installed OS on Samsung, what SATA mode did you set?
    Actually already answered. The OS install expects AHCI, since thats what i've been running for a couple of years.Quote from: Mr_B on 29-April-15, 02:18:52
    Back in 2011 Intel stated that RAID on their sATA chip's would enable AHCI, but the only reason for BSOD's on boot that i can come up with, is the lack of AHCI, while the OS expect AHCI.
    Quote from: JLio01 on 29-April-15, 08:56:45
    default settings is IDE, did you change it to RAID mode?
    When i built the system i switched it to AHCI since Windows 7 knows what that is, and how to use it. When i stuffed the 6tB drive in there, and decided to stripe the 2 500gB drives, i went and switched it to RAID mode.
    On the consecutive boot i went "CTRL-I" and added the two 500 gB drives to a striped volume, leaving the Samsung SSD, and the WD 6tB drives alone. After telling the system i'm done, it reboots again, and the system behaves like expected, and starts to boot windows of the SSD, but reboots or BSOD's after a couple of seconds on the animated loading screen. Fairly typical behavior if your running a mismatched AHCI setup. Meaning, if the OS expects it, but doesn't get it, or vice versa.
    I have no doubt that this would work if i reinstall, but i don't want to, for a couple of reasons. Mainly the simple fact that reinstalling means it wont use AHCI anymore. Perhaps a tiny performance loss, but it's still there. At that rate i'd rather go through the hour long process of pulling the case, and switching over the "to be RAIDED" drives to the marvell chip, and take the performance hit from the slower performance it has.
    If there is anything else i can add to make it clear, feel free to ask again. Thank you for your time and effort.
    I should be able to reboot and check the BIOS version in an hour or so, the transfer is starting to look almost finished.
    B!
    Edit
    Turn out i don't need to reboot to check the BIOS. I still have the forum flasher thingy installed, and it reports the stats when launching. 1.j, or, 1.19. BIOS date, 2012-03-07. I was right as far as it's the latest right up to when they started adding Ivy Bridge support, and things went weird. Not sure if any of the later BIOS alternatives would be helpful in this situation.
    /Edit

  • P67A-GD65 Overclocking Help!

    Hey everyone - I'm new to the forums and fairly new to overclocking in general, although I understand the basics of it... I've run into a snag, though.
    Recently I was redoing my desktop (Intel i5 2500k, MSI P67A-GD65, 16GB DDR3 1600 RAM, yada yada) and decided to update the BIOs, something I hadn't thought of doing since I built the PC over a year and a half ago... So, I updated from 1.9 (I think... it was 1.something) to the latest 4.3, and did a reformat on the HDDs and installed a fresh copy of Windows 7 Ultimate 64 bit... So I'm from scratch. I go into the BIOs to tweak the CPU and all, but I can't adjust anything at all. It's all stuck on "AUTO". I can't make the adjustments I need to make to overclock the CPU... I've read through several tutorials and threads on more forums than I care to admit, and my head is starting to hurt from (1) reading so much and (2) banging my head into the desk over this... Am I missing something? I've read that 4.3 has had some issues when it comes to OC'ing... What should I do? I can grab screenshots or more specs if needed. Thanks for the help in advance - I definitely appreciate it!
    -Ben

    Quote from: Froggy Gremlin on 30-July-13, 04:49:30
    Have you tried a full CMOS clear? PSU power cord removed, battery removed, and then a settings reset? My favorite UEFI/BIOS was the v1.C and the v1.H (2700k support). If you want, it is possible to revert back to a Sandy UEFI/BIOS on the primary BIOS chip. An admin or mod can give you the necessary files and information on how to do it.
    After the Ivy flash, did you also load the new Management Engine driver required? Also with a fresh OS, newest chipset driver installed, etc.? Here's the link to the MSI Website for your board and all the drivers;
    http://msi.com/product/mb/P67A-GD65--B3-.html
    I did a CMOS reset with the "Reset CMOS" button on the motherboard... After I did that and restarted the PC, a message came up informing me that the CMOS had been restored to default settings and asked if I wanted to go into setup or boot as normal... I can pop the battery and PSU cable out if needed... At this point, I'd be perfectly happy reverting back to a Sandy Bridge friendly BIOS, lol...
    I did install the new drivers after flashing the new BIOS, by the way. Followed all the instructions in the link you posted.

  • RADEON 7950 WONT BOOT WITH P67A-GD65

    Just got a new ATI Radeon HD7950 graphics card a couple of days ago and it refuses to even boot in my main PC (Intel i7-2700K, MSI P67A-GD65).
    Won't even get into BIOS. Just black screen.
    Updated to latest BIOS. Still nothing.
    Today I have tried the card in an older PC (Intel Q6600, ASUS Maximus Formula) and it works just fine.
    So I thought it might have been a power supply issue so I swapped the power supply from old PC into my new PC, but it still didn't work.
    So now I think its an incompatibility with the MSI P67A-GD65 motherboard.
    Note: Previous graphics card was ATI Radeon 6870 which is still working fine with P67A-GD65.
    Can anyone suggest why this graphics card won't boot with the P67A-GD65?

    Quote from: Froggy Gremlin on 02-March-13, 06:16:55
    What OS are you running? UEFI/BIOS version? CPU? Is this an MSI graphics card? If not, have you visited with the card manufacturer for any available information they may have?
    Too much time passed for me to edit and delete this question of CPU, as you did list it.

  • High voltage on Low Vdroop Setting P67A-GD65 + 2600k

    Dear members of the MSI-HQ user forum,
    My attempts on overclocking my 2600k processor has been stalled for quite some time now.
    I've been at 4.3GHz for a very long time because I wish to keep my Vcore set on Auto (I don't want my voltage set manually because it will remain at that voltage all the time).
    I've been playing around with a lot of settings and none of them have worked.
    The main problem is I want to be stable at 4.3GHz but with Vdroop set to Auto, it will only deliver 1.288V during a Prime95 torture test. 1.288V is not enough because after 10 min. I will get the 0x124 Bluescreen, which is too little Vcore. I have manually found out that 1.296V will do the trick! But again this is set manual... After switching to Vdroop set to Low Vdroop the Vcore voltage JUMPS to 1.42V during stress test (Prime95 & IBT)!! Waaaay too high. This will only get worse if I set my processor speed to 4.4GHz, Vcore will then be 1.44/1.45V and so on..
    Bios is updated to version 1.H. I updated from 1.8 to 1.C to 1.H, didn't make any difference. I've also played around with bios settings but nothing solves my problem. Eup 2013, spread spectrum, C1E, Overspeed protection all disabled. Tried all C1 states. PLL overvoltage disabled & enabled. Memory both tested @ 1333MHz & 1600MHz auto&linked settings (according to spec). And so on.
    I really want to overclock further then 4.3GHz (at least that one stable) using Auto Vcore. Or my voltage is too low (Vdroop set to auto) or too high (Vdroop set to Low). Please help :(
    My system specs are:
    Windows 7 64Bit
    Intel i7 2600k
    MSI P67A-GD65 (B3)
    Corsair XMS3 8GB 1600MHz dual channel memory kit

    To quote from a recent Ivye Bridge article:
    Quote
    Today Intel defines three different voltages for every Sandy Bridge CPU: LFM, nominal and turbo. LFM is the lowest frequency the CPU can run at (e.g. completely idle), nominal is the frequency it is specified to run at (e.g. 3.3GHz for a 2500K) and turbo is the highest available turbo frequency (e.g. 3.7GHz for a 2500K). Intel determines the lowest voltage possible for each one of those frequencies. Sandy Bridge obviously runs at more than just three frequencies, there are many more intermediate frequencies that it may run at depending on the current workload. The voltages at those intermediate frequencies are interpolated from the three points that I mentioned above.
    There is no definition above that, and it becomes an extrapolation of a voltage above 3,7GHz. Considering that each CPU has slightly different characteristics, even within the defined frequency range, there is no knowing what each one will do and require outside that range. So the required voltage at those overclocked frequencies can vary quite a bit, and the extrapolated voltage range in auto voltage mode at a given frequency may not be enough for the individual sample, furthermore, it is limited in terms of the maximum it will consider and apply in auto mode. Once that critical point is reached, one has to be satisfied or resort to manual intervention.

  • P67A-GD65 (b2) stuck in boot loop after bad flash

    Hello,
    My mainboard is stuck, I can't open bios setup, (even tho it appears in f11 menu), and it won't boot on any device.
    I removed every hard drive and DVD, and tried to boot on DOS with a usb, but it won't even boot DOS, and no usb device appears in f11 menu (I tried every usb ports)
    And I can't enter bios setup (it just reboots)
    Initially I was trying to update my bios because some features I wanted were not in my old version. But I think Avast blocked the update program (E7681v43.exe opened in an usb) and when I restarted the bios flash failed, and my PC entered a boot loop. When I press f11, it's a new interface so some things in the bios updated.
    The only message I get when I put the E7681v43.exe and E7681IMS.430, or the files for v1j (oldest version before ivy bridge support) on a fat32 usb stick (tried formatted, and formated with Rufus), a red message appears saying "bios me updated ... file not found."
    Same thing if I try the MSIHQ flash utility, it doesn't work as my PC won't boot on the usb.
    I think my motherboard is bricked and the only solution is to send it to msi to get a working bios.
    My motherboard p67a gd65 (b2) (the one with bad sata 2 ports) and it doesn't appear in the product name list anymore to register it on msi...
    It was bought the on the 19th of January 2011, I hope I can still ask for msi for help!
    I'm looking forward to your opinions on my issue, and sorry for the long text.

    Quote from: Svet on 24-September-13, 17:50:38
    older b2 cannot be updated to the .4xx
    you have to send the mobo to be replaced with newer revision
    Thanks! do you know where can I ask for a replacement?
    I can't register it on msi, and when I ask a question and I give the serial number it just abords...
    I already send an email to msi France (I live in Belgium). But email are too slow usually.
    and what about the secondary bios, no way to repair primary bios with it?

  • BIOS 4.3 half flashed on MSI P67A-GD65 reboot loop ME not installed

    Hi, yesterday I tried to flash my bios from 1.19 (1.jo) to 4.3 and I followed the SOP guidelines. Made a flash fat32 got bios on it, started it, stopped all my applications under windows and it went with no error. PC Restarted and now it's in infinite reboot loop. The moment the MSI BIOS logo appears, the PC auto reboots.
    If I remove the usb drive or replace the bios file with another version it tells me it's not the file it needs. When I insert the one with the .43 file it goes back to reboot cycle. I tried resetting the CMOS with the button on the mainboard and I have this screen telling me BIOS is 4.3 and it has recognized all my 12gb ram, 2 hard drives and processor. Then it has press F1 to enter setup and press F2 to continue, both options result in reboot.
    I tried the 1.JO on flash, but it tells me again that it's the wrong file. Tried renaming it to amiboot as I found somewhere, but to no avail. Tried renaming the .43 to EIVB.bin as it was suggested in one forum, again no luck.
    System specs:
    OS: Windows 7 64bit
    Mainboard: MSI P67A-GD65 (not B3)
    CPU: Intel Sandy bridge i5-2500k @3.3ghz
    RAM: 2x2gb Kinston 2x4gb Gskill DDR3@1333hz 10600 CL7
    GPU: Nvidia Gigabyte G1 Gaming GTX 970 (reason I wanted to flash bios)
    PSU: Seasonic 80+ platinum 650W
    HDD: WD Caviar Green 2GB
    SSD: Corsair 60gb
    DVD: Liteon burner

    Quote from: Svet on 22-February-15, 19:25:45
    older non B3 versions ME can't be flashed,
    therefor you will brick it if you attempt to do it via MSI's all in one updater..
    you can try anyway to try with barabone setup with 1 memory stick only and disconnect everything that's not required to boot
    and to try the USB key in any of the other USB ports
    and/or with different USB key too
    to see if ME update will able to continue
    I wasn't sure about the ME update, read that someone managed. The Live Update 6 did my 1.19 (1.JO) update. I tried all usb slots and 3 different sticks, formated them and so on. Nothing worked. I tried disconnecting all hard drives and DVD drive too.
    Is there a way to stop this cycle or to restore to the 1.19 version?

  • P67A-GD65 (B3) Cannot Downgrade from 4.3 to 1.19

    Hi MSI Forum!,
    I recently updated to 4.3 to use my new GTX770 because of compatibility issues. Now there is a fix for this, by flashing the bios in the GPU with the C3 Bios. Now I would like to revert back to 1.19 on my Motherboard but it keeps giving me an error. I read on a few threads that I need a "Custom Bios" File. Where can I get one of these?
    My Specs:
    P67A-GD65 B3
    Intel 2600k
    GTX770
    Corsair 650HX
    Patriot Gamer 2 Series 4GBx2 1600 DDR3
    Windows 8.1 64Bit
    Thanks in Advance!!
    Edit: Forgot to put my OS

    Quote
    Now there is a fix for this, by flashing the bios in the GPU with the C3 Bios.
    How do you know that this is really fix?
    Have you tested this combo into another PC to know it for sure?
    IE: Same board, with same bios, with same video card
    I think you probably will end to flash back, and then to find-out the the video card doesn't works there.
    Quote
    Now I would like to revert back to 1.19 on my Motherboard
    Flash back its not possible by regular ways. It's one way direction update to .4xx with no flash back option
    If you still want to return, use this archive with valcheck.com:
    https://forum-en.msi.com/index.php?action=dlattach;topic=161166.0;attach=9985
    Use it with >>Use the MSI HQ Forum USB flasher<< Mode1 Point to bios archive file

  • BIOS 4.2 P67A-GD65 flash failed and motherboard HS ?

    Hi,
    I just ruined my motherboard MSI thanks, I possesses a P67A-GD65 and I wanted to put the last bios 4.2, the pc is stable at 100%, not overclocked etc .... I run the flash freeze win7 64 and freeze .... Now this does not boot anymore when I turn on the pc it'm black screen, it goes off, it turns on black screen in a loop ....
    is there a method to reflash the bios or is what it is .....
    Service thank you in advance

    Try what froggy said but frorm the sound of it, you bricked the board.
    If after clearing the cmos et al, you cannot post you will need to either take it to a computer shop or return it to msi for a bios flashing. I think shipping costs a little more than the computer shop but it only takes a few minutes.

  • Flash on P67A-GD65 went wrong?

    Hi, i bought a R9 290 to put in my P67A-GD65 with a 2500k and didn t boot.
    like this problem https://forum-en.msi.com/index.php?topic=180379.0
    exactly the same, i did the flash using the usb program and bios from the foruns, just like that user, did everything like the guide, but after i flash it and cleared cmos, when i turn up, wont boot, and apears a 9C on botton right of the screen.
    anyway to solve this? did I ruined the motherboard?
    hope you can help me.
    thanks

    Quote from: Mr_Padre on 08-October-14, 21:50:54
    im gonna check my work pc RAM, i think its hyperX from kingstom.. i dont have any friends in the area.
    if diferent ram doesn t work, do i need to start thinking in buy new board?
    if with different RAM make no difference, you can try to swap other components until boot up without error.
    looks like the new bios doesn't play well with some of your components used.
    other option is to to reprogram the BIOS chip with SPI Flash programmer with BIOS version which worked fine for you

  • [P67a-GD65] [Ivy] Infinite reboot loop after flash

    MSIHQ: Information detected by MSIHQ Tool ver: 1.25g
    MSIHQ: Report generated in Tue 01/01/2013 at 13:31:41.33
    Mainboard:  P67A-GD65 (MS-7681) - CPU i5-3570K
    PCB Version:  2.0
    BIOS Version: V4.2
    BIOS Date:  7/16/2012
    Attempted to upgrade to https://forum-en.msi.com/index.php?topic=164135.0
    Due to the inability to hold any overclocks with any voltage besides auto, and because the Windows MSI control center wouldn't keep settings on startup.
    Installed the forum flash tool on a USB drive and it wasn't bootable.
    Tried with another flash drive and it wasn't bootable.
    Used the on-BIOS tool to flash the BIOS
    Flashed, rebooted, and began reboot looping.
    Cleared CMOS - nope
    Removed battery and cleared CMOS - nope
    Removed all but one stick of RAM - nope
    Is it bricked? If so, how do I get a replacement/repair?
    Edit, was perusing the forums and found this:
    Forum flasher defaults to looking for zip files, if you pick rar from the drop down it should accept the file just fine, if you don't use method 1 you won't get the ME flashed.
    It's lovely that that's documented and pointed out in the flashing tool's post, and it's rather odd that all of the BIOSes are saved in .rar archives if the flasher looks for .zip. I used method 2.

    Quote from: Svet on 02-January-13, 04:35:53
    You should use "Fix My USB key" Tool's option 1st before prepare the stick if you having troubles booting from the USB key.
    I realized that after the fact.
    have you done >>Clear CMOS Guide<< with power cord removed and leave 1 memory stick only in 1st DIMM close to CPU socket?
    I just did that, and it unfortunately continues to loop.
    I guess I'll get it packaged up and into the mail. Thanks for the help guys.
    When I do get it fixed, what BIOS will it come with?

  • P67A-GD65 (B3 ) & Windows 7 64Bit Boot Issue

    Hi,
    I feel the need to revisit this old forum post as I do not believe it has been fully resolved:
    https://forum-en.msi.com/index.php?topic=156082.0
    In summary the issue is "Most times the machine boots and performs flawlessly for hours, but often it boots with the Windows-7 “need to repair” screen and after running repair for a while Windows says: “Windows cannot repair the problem”…….but when I press the Reset button, the PC boots and runs just fine".
    I only had the problem since updating from 1F beta 2 to the latest BIOS version. On the original forum thread there are some that had the view that the issue was introduced around BIOS version 1.F (full release, non-beta) and 1.G. Just to confirm this issue NEVER happened for me on 1F beta 2 or earlier BIOS releases. The original forum also has some people saying the issue did not exist on earlier BIOS versions as well.
    Most people seem to have solved the issue by either resetting the CMOS or loading default BIOS settings. I tried this and it did initially solve the problem for me.
    BUT when I installed new drivers (such as nvidia v301.24) or added new hardware (e.g. Bigfoot PCIe network gaming card) the problem came back.
    This implies to me that there is an issue with the BIOS and that resetting the CMOS is a workaround rather than a true fix.
    This leaves me with two choices:
    - use an older BIOS, which is ok but limits me from the new functionality in the BIOS (including not being able to use certain hardware that the BIOS updates support)
    - resetting the CMOS after loading new drivers or installing new hardware and then configure my settings (which is very tedious)
    Neither option is ideal to me.
    The main purpose of raising this issue is to ask whether MSI Support know of this issue and have it on their bug list to fix?
    I am concerned it is not being addressed as other forum entries talk about BIOS version 1.K3 being the last version.
    My system details are P67-GD65(B3), Windows 7 64bit, 16GB Gskill 2133Mhz memory, 2 SSD, 2HDD, Nvidia 570 GTX, Bigfoot network gaming card.

    Quote from: momosala on 25-September-12, 22:19:54
    Thank you _MELK_ for bringing us your experience.
     It was already reported that this bug did not appear with older firmware versions.
     It is interesting to know that version 1.14 does not have this bug.
     This information should help the MSI support team to create a 1.K reliable firmware.
    In my opinion, I do not think that Intel RST is the cause of this bug.
    Sure thing momosala..
    An update to this issue is as follow...
    BIOS 1.14 fixed this issue completely. NO errors since I flashed back to it.   I also reinstalled Intel RST without any issue either.
    Note that I wanted 1.19 for another reason as well (fix for USB 3.0 port issues).  I wound up flashing the chipset for the USB ports themselves instead  .    Now the MB works as intended!  :D
    WARNING: use the info below with CAUTION (not simple to do, and not provided/supported by MSI afaik)
    INFO on USB 3.0 firmware/drivers -- again, use CAUTION and do your research before proceeding!
    Note that it took me a few hours to complete the flash since I had to research which version of the chipset I had (hardware ID helped, LOTS of reading on the subject as well to find out HOW to flash my board properly).
    You can find the drivers/firmware for the "Renesa USB 3.0 Host controller" by searching google for
    Driver: Renesas/Nec Usb 3.0 Version 3.0.23.0/2.1.39.0 WHQL.   
    I used the 2.1.39.0 drivers -- you'll find the firmware at the same place and an explanation on how to flash the chipset we have on the P67A-GD65 (which has TWO identical chips to flash).  The new firmware updater doesn't work on those, so you need to download an older firmware to use the older DOS program to flash with the newer .MEM files.

  • Help Configuring Raid 1 & Raid 5 on the P67A-GD65 (B3) motherboard

    I just purchased the P67A-GD65 (B3) motherboard for a custom system and have a few questions in regards to setting up RAID.
    I have the following HDs
    2x 1TB
    3x 3TB
    I would like to setup RAID 1 with the two 1TB drivers and RADI 5 with the three 3TB drivers.  I connected the two 1TB drives to ports 7&8 so it would be using the Marvell SE9128 and the three 3TB drives to ports 1, 2,3 to use the Intel P67 (B3) PCH.  The documentation says that SATA ports 1-6 support RAID 0/1/5/10 and SATA port 7-8 support RAID 0/1.
    The two 1TB in RAID 1 would be my boot drives (going to run VMWARE ESXi with multiple VMs) and the three 3TB RAID 5 drives are going to be my storage.
    I was under the understanding that you could use both the Intel P67 (B3) PCH and the Marvell SE9128 at the same time but it looks like I can only configure one or the other.  If I have neither of the two setup I can hit CTRL + I and get to Intel or CTRL + M to get to Marvell but when I set one of them up I can’t boot into the other to setup my second RAID. 
    At the end of the day I bought this system to run ESXi 5.0 with multiple VMs with a shared storage area.  If I can’t utilize both controllers then what’s the point of having two on the motherboard?  I made sure in the BIOS settings I enabled RAID for the HDs. 
    If anyone has configured their systems like this please let me know how. 
    NOTE: As others have mentioned if you put in all your memory at one time then the system will go into a continuous reboot state.  You should only put in one and then the others.  Right now I have two 4GB sticks in and will add the others once I figure out is going on with the RAID.

    Quote from: Jack on 29-September-11, 16:56:49
    Please stop flashing the same version all over again, before something goes wrong.  
    It's great to have that info now... is it posted anywhere on the website?
    Quote from: Jack on 29-September-11, 16:56:49
    Please make sure that the memory frequency is manually set to DDR3-1333, the Command Rate to 2T and the memory voltage to 1.575V.  Then retest with all modules.
    I changed the frequency to DDR-1333 and Voltage but I don't know how to change the Command Rate or where it is located?  Any help?
    Also,
    I'm still having problems getting the system to recognize the Marvell RAID config when I boot with the VMWare ESXi 5.0 CD and try to select where I want to install... When I go into the Marvell settings the system it shows that  I have two dirves in RAID 1 Config:
    PD 0: ST31000528AS -> PORT ID = 0; PD ID = 0; Type = SATA PD; Status = Configured; Size 953869MD; Feature Support = NCQ 3G 48Bits; Current Speed = 3G
    PD 8: ST31000528AS -> PORT ID = 1; PD ID = 8; Type = SATA PD; Status = Configured; Size 953869MD; Feature Support = NCQ 3G 48Bits; Current Speed = 3G
    under the HBA 0: Marvell 0 settings it says the following:
    VENDOR ID: 1B4B
    DEVICE ID: 91A3
    REVISION ID: B1
    BIOS VERSION: 1.0.0.1027
    FIRMWARE VERSION: 2.1.2.1505
    PCIe Speed Rate: 5.0Gbps
    Configure SATA as: IDE Mode -> In the BIOS I have the settings to RAID
    Not sure if it matters but here's how I have the Intel Raid setup...
    RAID Volumes
    ID = 0; NAME = Storage; LEVEL = RAID5(Parity); STRIP = 64KB; SIZE = 5.4TB; STATUS = Normal (it's in green); BOOTABLE = Yes
    Physical Devices:
    Port Device Mod Ser  Size  Type/Status(Vol ID)
    0 Hitachi blah blah 2.7TB Member Disk (0)
    1 Hitachi blah blah 2.7TB Member Disk (0)
    2 Hitachi blah blah 2.7TB Member Disk (0)
    Any Thoughts?  I'm trying to boot from the two 1TB drivers setup in the Marvell Raid 1 Config and the Raid5 through the Intel for all my storage needs.  
    Thanks again for helping out.

Maybe you are looking for