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

This topic has been moved to Intel Core-iX boards.
https://forum-en.msi.com/index.php?topic=152612.0

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.

Similar Messages

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.

Can the P67A-GD65 boot without a graphic card?

Hi,
I just bought a P67A-GD65 with a Core i7 2600k and I want to operate the board without a
graphic card (as a server running Linux). To my surprise, the machine does not boot
with I remove the graphic card. I know it does not boot because I do not hear any
noise coming from the hard drive, nor do I see any SATA LED blinking. When I plug
in my ATI card, all is well.
I looked around in the UEFI BIOS and could not find any option to turn on/off.
The board is running FW 1.40.
Is this a known limitation?

Quote
No ? There is absolutly no way to get the card to boot and without a grafic card ? That is pretty bad isnt it ? :(
The mainboard was never intended to be used as a server as the OP had inquired about. With newer chipsets that have on-board graphics in the CPU, then it might be easy to configure. Not sure about this, but it may be possible to put a fake card or device in to trick it thinking it has a graphics card, but I have no information about it.
As per the forum rules;
Don’t…
- Hijack other peoples’ topics or resurrect old topics. A topic is considered old when its last update is 14 days old.

Need help configuring VPN - problems accessing the networks

Hi everyone, hope someone can help me out here.
I'm administering the network for our small company. We basically have two sets of machines - public ones with fixed net addresses (mail, web, dns servers, etc), and private ones behind a wireless router/nat.
Our main need here is to be able to VPN in to the public side, in particular, the mailserver, so that we can get around all the stupid things that get done to SMTP when we connect at the BedBug Inn ("Free wifi, administered by gibbons").
Secondarily, it would be nice to be able to connect to and browse some of the internal machines.
So here is what I did:
* Installed 10.4.10 Server on a machine with two ethernet interfaces, one that has a public IP address, the other connects into the private network. When I'm actually at that machine, things work fine - I can browse the private network shares, connect to the net, etc.
* Configured VPN. I have no problems getting a VPN connection, both sides are happy. The VPN assigns incoming clients IP addresses in the private network IP range, but outside those assigned by the wireless router's NAT.
* Added 192.168.2.1/255 (the private network) and 12.17.29.193/224 (the public network) to the Network Routing Definition box under VPN/Settings/Client Information.
However, here's where it all falls down. Once the VPN is established, I can't connect to any of the public machines, and the only private-side device that seems to respond is the Wireless/NAT box (A Belkin N1). So the only thing I can do is administer the Belkin remotely, which, while nice, is not exactly what I had in mind.
Doing a traceroute while VPN is active to my mailserver shows the first hop direct to the VPN machine, then off into * * * heaven (though I have no idea if traceroute works over VPN!).
One curious note: when I change the order of the Network Routing Definitions so that the public network comes first, and the private one second, I can't contact the Belkin box.
Any advice, oh wise and powerful masters of technology?
Various, but the server is running on a G4 Mac OS X (10.4.10)

I said:
"let's assume I VPN to the wireless box"
You replied:
"That's not correct as it is not the device running the VPN endpoint - in this case. "
But wouldn't I have to (on the VPN client) specify the public IP of the wireless box in order connect (because the packets are forwarded) to the actual OS X box running the VPN? Otherwise, it can't see it.
Part of the problem I have is that I can't dedicate a whole machine to VPN. The OS X machine running VPN is also running DNS, and will eventually run our mailserver and perhaps FTP, web, etc, as I slowly migrate stuff to it.
So this machine has to have a public IP address. It cannot be hidden behind the wireless NAT. And it seems to me that this is the crux of the problem. What I think you are telling me is that if the VPN machine was entirely hidden behind the wireless NAT, and had no direct public (WAN) interface, then since all the packets destined for the outside world (including my public servers)would have to go through the NAT, and all would be OK.
If so, then it seems to me that the best solution is to use something like OpenVPN on another OS X (not OS X Server, since I only have one of those) machine in the private network. Since the incoming VPN traffic will be Mac only, it shouldn't be an issue, L2TP-only is fine.
"Otherwise you have to run NAT and the firewall in the VPN server too and use private IPs for VPN clients - or use "only" it (remove the other NAT box and put it on the LAN only). Using only one device for NAT/gw means less configuration."
It is entirely unclear to me, in my setup, what effect turning on NAT on the VPN box (or perhaps, just IP forwarding) would have -- and if I do turn on NAT, would I still have the VPN assign IP's to clients in the internal private network's range, or would I use a different range (ie: private is 192.168.237.xxx, VPN assigns 192.168.239.xxx) and expect the NAT to handle the conversion?
I'm a bit leery of just trying it and seeing what happens because it if mucks things up so badly that the server becomes unreachable (via server admin), I'll have to schlep down to the office to fix it.
"Other things to consider is "bottlenecks" between your LAN and WAN."
Not a real issue. We have a small office, and a relatively small pipe to the internet. Most of the traffic from that pipe is from the public machines anyway. The traffic that goes through the wireless router is basically websurfing and hitting the mailserver.
I could, of course, use the VPN OS X machine as the NAT/DHCP server, and hang the wireless router off the internal network as a simple access point. But would that resolve all the VPN issues?
Once again, thanks for your helpful and prompt replies.

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

This topic has been moved to Overclockers & Undervolting & Modding Corner.
https://forum-en.msi.com/index.php?topic=155777.0

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 (B3) Marvel 6gb/s sATA performance?

I was talking "elsewhere" on a forum, and the topic of the marvel chip came up. It was argued that the design / implementation of the Marvel controller on these motherboards all were the 91xx series, and they all had a pretty horrifying flaw. They share a 5gb/s bus. For something that is said to support 2 6gb/s devices, that is pretty devastating, so i had to come here, where the knowledge about all things MSI is at its highest density. I mean, if the answer is out there, then it's more likely to be here, then anywhere else.
So.
Is this issue a part of the P67A-GD65 (B3) motherboard design?
Assuming the first answer is yes, is there anything you can do to minimize the impact of it?
Thank you for your time & effort.
B!

It's actually not an issue with the mainboard design, it is a problem with the Marvell controller itself. It is an add-on feature to provide SATA III function, but it is not the best. ASMedia controller isn't really a lot better either. At least the Marvell allows RAID for those that desire it. The answer is in the Intel 'native' SATA III controllers which are quite good. A lot depends on the drives used. With spinner HDD's, SATA II or SATA III doesn't make a lot of difference in their performance anyway.
Quote
Assuming the first answer is yes, is there anything you can do to minimize the impact of it?
Not really, other than maybe a Z87 with all the SATA ports Intel controlled SATA III.
Added: I have no experience with them, but maybe an aftermarket add-in SATA III controller card would work better.

Can I make a hardware raid with the on board Marvell SE9128 chip on p67a-gd65?

Hi,
as you all know the RAID 0/1/10/5/JBOD with the p67 chipset are pure software raids or "fake" raids. I saw some sata-raid pcie 2.0 x1 cards on the sell which have the Marvell SE9128 chip. So my question is: Can I make a hardware raid with the onboard Marvell SE9128 chip on the p67a-gd65?
Thanks
--pepe

Quote from: Stu on 06-November-11, 02:31:26
Hardware RAID explained:
http://www.pcguide.com/ref/hdd/perf/raid/conf/ctrlHardware-c.html
What do you want to say with this? I know what's the difference between a software (fake) and hardware raid? Your post doesn't answer the question. The p67-chipset has integrated software raid. The marvell se9128 is also found on some hardware raid cards. That's why I'm still wondering if it is for a hardware raid on this board or not.

Newb Needs Help Setting Up RAID 0

Hi, I am a newb and this is my first post. I just bought 2 80 gig Maxtor uata/133 drives and plan on putting them in a RAID 0 configuration. I have the K8T-Neo FIS2R motherboard. Would I have to put them in a master and slave configuration on one ide cable connecting to the ide3 slot? Will that work or is the ide3 for a SATA-ide RAID config?

No, u were correct.
Make 1 master, 1 slave
Attach em to IDE3
Activate Promise Raid controller in BIOS
Set up a raid array in the Promise RAID setup that comes by at post
That's it.
Keep the floppy with the promise drivers at hand while installing XP, if u want to set it as ur boot device.
Best is to set it up first get everything working, be4 reinstalling, to rule out possible errors, while still having a working computer

Help with P67A-GD65

Hi everyone, just wanted some advise please, i have ordered the parts for my new gaming pc (This is my first build)
I have ordered the MSI P67A-GD65 motherboard and after doing some research i getting worried that my CPU cooler won't clear my ram.
I have the coolermaster V6GT CPU cooler and the G.Skill RipJawX 4GB DDR3 kit
I just wanted to know if anyone else has this board RAM and cooler ?
If not could i get some advise on wether i should change my CPU cooler to some thing like the Akasa AK-CCX-4002HP Venom CPU Cooler ?
Or could i move my RAM into slots 2 and 4 ? would this work or would the system not boot properly ? (sorry first build )
Thanks to anyone that helps

Quote from: HU16E on 28-January-11, 06:46:30
Well, that's what I get for not doing the testing myself! The P67A-GD65 'does' boot with a stick in the dimm 2 black slot, & then with a second stick placed in the other black slot. However, the manual is specific about initial startup with a RAM stick in dimm 1, which is of course the first blue slot next to the CPU. Without starting from scratch again, I can't verify initial build startup with a stick in the dimm 2 black slot will work or not. I guess if someone tries it, & it fails, obvious move would be to go to the dimm 1 & give it a go. Trouble is, I can't go back & edit my posts now to correct them.
Ha, it's OK, I read the same thing in the manual. The manual certainly doesn't leave any room for assumption, it flat out states you should use 1 & 3.

P67A-GD65 freezing up

I've never seen a "Forum" that wants new topics for the exact same problems (spreading potential fixes for the same issue all over the place instead of in one thread), but apparently if I post to another topic from someone with identical problems (the one right below this one with the same issue) I'm called a thread hijacker.
Seems like a ton of people are having these issues with lockups with the P67A-GD65
My setup - all new components
P67A-GD65
I7 2600k SandyBridge 3.4Ghz
G.SKILL F3-14900CL9D-8GBXL (2 x 4GB sticks in slot 1 and 3)
Nvidia GeForce GTX 460
two WD Black sata III 1TB drives in a RAID0 in sata ports 1 and 2 (SATA 6Gb)
two WD Green sata II 1TB drives in a RAID0 in sata ports 3 and 4 (SATA 3Gb)
one WD Black sata III 1TB drive in sata port 5 (system resides on this non raid drive)
Bluray drives in sata ports 6 and 7
Corsair 750W 80 PLUS Power supply
Then go to another machine and RDP to it, no problems. Wait about an hour, RDP and you get "Welcome" and it just hangs.
So if I go to the console, it tells me someone else is trying to login, but no drive activity at all, and won't let me do anything and I have to hard power off.
If I'm at the machine, just doing different "normal" things, browser windows lockup, applications lockup, all requiring a hard shutdown by the button since I can't select the option to reboot normally. No BSOD's, no OC, the OC Genie is OFF
My memory is even certified for this damn board on bios 1.B which I have updated to. But in "auto" doesn't even get the memory timings correct.
http://www.gskill.com/products.php?index=378
I'm Going nutz trying to figure out what the f--k is going on. I even ran the on board memory test and it passed.
I'm thinking that quality control on this production line is crap. I've seen a ton of complaints of BSOD's, rebot loops, and random lockups which can be reproduced easily.
MSI? Are you going to fix this!!!
How about posting the serial numbers of the bad run from manufacturing so users can see if they have a bad board? I've been building systems for 15 years and I've never had so much trouble with a board.
Has anyone had a success story that wasn't from an RMA? I haven't found a post where a user had these issues and made a few bios changes and they came back with "great, that fixed it".
Thanks
Scott

Quote
I've never seen a "Forum" that wants new topics for the exact same problems (spreading potential fixes for the same issue all over the place instead of in one thread), but apparently if I post to another topic from someone with identical problems (the one right below this one with the same issue) I'm called a thread hijacker.
Now you have seen it. Get over it and also please skip this kind of stuff:
Quote
this damn board
Quote
what the f--k
Quote
this production line is crap
... because if you can't, I will close this thread immediately and delete the entire thing a.s.a.p. This latent aggressive attitude is not going to shed one bit of useful light on the problem. >>Please read and comply with the Forum Rules.<<
Also:
Quote
I've been building systems for 15 years and I've never had so much trouble with a board.
I've heard that kind of thing a million times. Be that as it may, it does not really tell us anything about the actual cause of the problem. Furthermore, if you are so sure it is the board, why didn't you simply send it back/RMA it/have it exchanged after you have ruled all other explanations out systematically?
Quote
Seems like a ton of people are having these issues with lockups with the P67A-GD65
There are thousands of freeze issues on all different hardware configurations. However, more important than the symptoms are the precise hardware configuration the freezes occur in and the actual causes for the common symptom. Once the causes are truly found out it makes sense to compare similar issues. It should not be done, however, because of a common symptom. And that is exactly why your problem (and any other problem that is just a symptom at first) deserves its own, seperate thread.
Quote
P67A-GD65
I7 2600k SandyBridge 3.4Ghz
G.SKILL F3-14900CL9D-8GBXL (2 x 4GB sticks in slot 1 and 3)
Nvidia GeForce GTX 460
two WD Black sata III 1TB drives in a RAID0 in sata ports 1 and 2 (SATA 6Gb)
two WD Green sata II 1TB drives in a RAID0 in sata ports 3 and 4 (SATA 3Gb)
one WD Black sata III 1TB drive in sata port 5 (system resides on this non raid drive)
Bluray drives in sata ports 6 and 7
Corsair 750W 80 PLUS Power supply
Please reduce the complexity of your system to the most basic configuration needed to run your operating system. Use one stick of RAM only, make sure it is set to run at a frequency that does not exceed the specifications of the processor's memory controller (DDR3-1333 max.!). Unplug all the hard drives, optical drives, SSDs, card readers, add-on cards, USB devices etc. that are not needed to work with the operating system (you need just mouse, keyboard, video card, processor, one stick of RAM).
Once you have reduced the system complexity and please unplug your PSU from A/C power, >>Clear CMOS<< and then load "Optimized Defaults" in UEFI Setup. Then apply your custom settings (e.g. RAID Mode settings & Memory Speed = DDR3-1333).
Then retest.
In case the freezes still occur, then please disable all CPU related power saving settings in UEFI Setup (C1E, C-States, EIST) and retest. Also, try if setting the phase control mode from "APS" to "Intel SVID" mode.

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.

Problem with downgrading bios. MSI P67A-GD65 (B3).

Hi!
I'm having problems with downgrading my bios from version 4.3 to 1.19. I want to downgrade, because 4.3 doesn't want to boot when I use xmp settings for my RAM ( that might be related to my CPU since I have i5 2500k which is 32nm and 4.3 version of BIOS is recommended for 22nm processors ). When I try to flash with the MSI Forum HQ USB Flashing Tool I'm getting an error: "Rom file ROMID is not compatible with existing BIOS ROMID". I've ran out of ideas how to downgrade my bios so I'm asking you for help. My specs:
MOBO: MSI P67A-GD65 (B3)
CPU: INTEL CORE i5 2500K
RAM: G.SKILL RIPJAWS X 4GB (2x2GB) DDR3 1600MHZ CL6 (F3-12800CL6D-4GBXH)

Here you go. GD65 and GD55 usde the same BIOS files;
https://forum-en.msi.com/index.php?topic=179837.msg1295420#msg1295420

Msi P67A-GD65 keep restarting after bios update

Hello
I have a Msi P67A-GD65 B2 motherboard, I tried today to upgrade bios to version 4.2,after update pc start up showing marvel controller then MSI logo and then computer restart over and over,if I try to enter BIOS will show 'entering setup', and restart again.Dual BIOS led does not light up and is not blinking.What can I do in this situation? How to switch the motherboard BIOS to boot from the other one?

Quote
Can you verify that, I don't think they make a B2.
Not sure why the hijack in this thread with different hardware involved, but a B2 is a defective mainboard from the beginning, and should have been replaced at the time of the replacement offers over a year or so ago.
Quote
I understood that there was a backup BIOS so I felt confident to be able to fall back in some way. Can you help me using that backup?
The Ivy udpate flashes the secondary chip as well on the GD65, so it would do no good to have access to it unless you could get into the UEFI/BIOS somehow to 'enable' the Dual BIOS Auto Update setting to restore the corrupted primary.

P67A-GD65 Power Cycle (Rebooting)

CPU: i7-2600k
RAM: F3-12800CL6D-4GBXH DDR3-1600 (CL6-8-6-24)
Motherboard: P67A-GD65
Motherboard BIOS: 1.8?
Hello, I have recently purchased a P67A-GD65 from newegg along with a 2600k and G.SKILL DDR3-1600 (F3-12800CL6D-4GBXH)
The problem I am having is that the motherboard will stay on for about 5 seconds then it will reboot, and continue to do so until I turn off the power from the PSU. It will not post so I cannot access the bios or anything.
I have been in contact with msi tech support and they keep telling me to do what I have already done so many times.
I already returned my board for a replacement once but the replacement had the same power cycling issues. I am thinking of buying some cheap 1333 CL9 RAM to see if I can manage to get into the UEFI and see if I can tweak something into making my RAM work
I went on to the G.SKILL forum and found an interesting thread about RAM incompatiblities. Could this be causing the constant reboots?
(Have cleared CMOS many times, tried different PSU, ETC)
tl;dr
Is my RAM causing the P67A-GD65 to continuously reboot without posting?
Bought some Patriot 2GB 240-Pin DDR3 SDRAM DDR3 1333 CL9 RAM from newegg today to see if those will work.
Your help is greatly appreciated, Thanks!

Quote
I am thinking of buying some cheap 1333 CL9 RAM to see if I can manage to get into the UEFI and see if I can tweak something into making my RAM work. I went on to the G.SKILL forum and found an interesting thread about RAM incompatiblities. Could this be causing the constant reboots?
Quote
Alright, the new ram I bought should arrive in a few days (3 or 4).
In the meantime while waiting, try this. With one stick RAM in the primary blue dimm slot, if you get in to the BIOS then, set DRAM Mode to 'Link', timings to 9 9 9 24, tRFC 88, DRAM V. to 1.507 or 1.521. Looking at those timings of the G.Skills in your component list, SPD being set must be rather non standard (just a guess).

XMP feature on P67A-GD65 B3

Hi,
I have recently built a new rig using the P67A-GD65 B3 board and G-Skill Ripjaws memory. I had originally installed 2x2GB DDR3 2133MHz (F3-17000CL7D-4GBXHD), with which I had enabled XMP with success, the memory then running at 2133MHz with 7-10-7-27 as advertised by the vendor without any other tweaking than enabling XMP in the BIOS.
I then decided that it was a shame to only use 2 of these 4 memory slots so I ordered the same memory kit again, and added another 2x2GB of the exact same memory. As for any memory addition event, the BIOS then automatically disabled all memory tweakings, so I re-enabled XMP, rebooted my machine, and then it never came back up, it went into the permanent loop thing, had to clear the CMOS to recover.
Is this something anyone has ever come across, did I get lucky to get XMP to work with two sticks without additionnal tweaking and does it make sense that with 4 sticks it wouldn't work the same way? Furthermore, assuming I need to do some more tweaking than just enabling XMP to get all 4 sticks to run at the expected timings and frequency, what would you recommend I do? change the voltage?
Edit: tried OC Genie and manually putting the RAM settings in the BIOS with the same outcome in both cases, the "permaloop".
Thanks!

Quote from: Mike on 14-March-11, 07:59:23
Also, the memory controller is in the CPU...it is not in the board.
Does anyone know how to configure XMP using Intel i7 2600k then? It's listed in the MOBO user manual but not in the BIOS or settings. Could it be possible that I need to update my bios?

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

Similar Messages

Maybe you are looking for