P67A-GD65 SATA Issues

Just the parts for my build today and unfortunately I've run into a snag. I first plugged in my 2 SATA hard drives from my previous PC in the white (SATA3) plugins. It booted up and recognized only one of the drives. Then, after getting just past the screen with the MSI logo, it got stock with a flashing underscore. So I assumed it was a boot issue and tried a SATA DVD drive and attempted to boot off a windows CD. Same thing happened again. Now, in order to get into the BIOS to select a boot order I had to disconnected all SATA devices. This brought me to a command line EFI shell (the last boot device in the list) whereupon typing exit brings the user to the BIOS. So I set the DVD drive as first boot device, but same issue occured - MSI logo then blinking underscore.
I then tried combinations of HDD/DVD drives connected to the SATA2 black connections and none of the devices were recognized as far as I can tell - there is only a screen for the Marvel controller that comes up before the logo and this deals with the SATA 3 ports. So I was unable to get into the BIOS to see if devices were recognized, because I had to disconnect all devices to get into it. RAM and CPU were correctly recognized in the BIOS, memory passed MSI memory test.
So I'm at a loss at this point - is there anything I might have forgotten or missed? I've disconnected all USB and audio front panel connectors as well, no difference. I fear the SATA controller is bad but I'd like to make sure before an RMA.

Tried with a single stick of RAM in the first slot, same issue occured. RAM was correctly recognized in BIOS. The only other thing I can thing of is a compatibility issue with my old keyboard, it has the old 5-pin DIN connector and I'm using a PS/2 adapter. However, it works fine in the BIOS and I haven't got a keyboard error like I would expect with such a problem. I just wish I could see where it was getting stuck - has the POST phase been completed by the time it gets past the logo to the blinking underscore?
Also I've noticed a blinkin led near the bottom of the board. Is this normal?
Edit: It appears as if this occurs when the primary BIOS fails, however I was able to get into the BIOS so the secondary must be ok. Could I still have boot issues even if a working secondary BIOS was loaded?

Similar Messages

P67A-GD65 major issues

I'm having some major problems with my P67A-GD65. I received this board from an RMA about 2 weeks ago (previous board had the no and/or corrupt ME issue), installed it and have had zero issues until two days ago. I was playing a game when the game crashed. I didn't think anything of it and started up again but the crashes continued from that point on (game has been installed and played without issue for 2 weeks, since new RMA). I did a restart and upon reboot several windows services and other apps all crashed. I checked event viewer and noticed all the crashes are listed under the same event ID (event ID 1000, Exception code: 0xc0000005). At this point I scheduled at disk check (using windows 7, enabled both fix file system errors and scan for bad clusters), I let the scan run it's full course (took several hours) and there were zero errors. I decided to reintall my OS and see if I had any better luck, thinking perhaps the game crash caused some freak, one of kind, system error.
As soon as the OS was running again, I was immediately greeted with more of the same errors. This time searchindexer.exe crashed over 100 times, until I got a BSOD (bad_pool_caller stop 0x000000C2). I rebooted and there were no errors, again checking the event viewer, I saw the same event ID 1000 with same exception code (also, this The Windows Search service terminated unexpectedly. It has done this 138 times, bear in mind this occurred in a 10 minute time period). I tried to install some of my drivers, only to have my sound drivers refuse to install with a CRC error and my video drivers install, then immediately had the catalyst service crash upon reboot. I was afraid perhaps it was my SATA port going bad so I moved my HDD from SATA 8 to SATA 1 (avoiding all the Intel ports) but this didn't help the issue at all. Is it possible I got a bad RMA board from MSI? Any ideas on things I can check out? It's odd it was working fine for the first two weeks.
I mention the problems beginning with the game crash because something odd happened after the crash. I was playing a game within Steam. Right after the crash, steam no longer worked. As soon as I tried to start steam again, it would crash and quit immediately. I had to do a complete reinstall of Steam to get it working again. I do have UAC disabled so is it possible by some freak occurrence the game crash could have damaged my OS install? Again, I did a complete reinstall since then though and had no improvements.

I just wanted to add a few of the errors from event viewer:
Session "Circular Kernel Context Logger" stopped due to the following error: 0xC0000188 (event id 3)
{Registry Hive Recovered} Registry hive (file): '\??\C:\Windows\System32\config\COMPONENTS' was corrupted and it has been recovered. Some data might have been lost. (event id 5)
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2. (event id 55)
Windows (3204) Windows: Database recovery/restore failed with unexpected error -501. (event id 454)
Windows (3204) Windows: Corruption was detected during soft recovery in logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 1417 (0x00000589). This logfile has been damaged and is unusable. (event id 465)
Faulting application name: iexplore.exe, version: 8.0.7600.16385, time stamp: 0x4a5bc69e
Faulting module name: mshtml.dll, version: 8.0.7600.16385, time stamp: 0x4a5bda8a
Exception code: 0xc0000005
Fault offset: 0x0019ed82
Faulting process id: 0xdb0 (event id 1000)

P67A GD65 B3 - issues

Hi everyone
I have some isses with my new p67a-gd65:
Q1. When booting before showing the intel raid utility I hear 1long and 3or4 short beeps. Accorind to google those 3 short beeps should mean that there's a problem with the upper memory. I have F3-12800CL9D-8GBSR2 (2x4GB) and the memory is supported by this mobo according to the gskills website. Furthermore I ran the memtest86+ (v4.20) a week ago and this morning (for about 90mins) and no errors turned out. The system/memory hasn't been overclocked and I'm using the 1f8 bios.
If the beeps are 4short this should mean that the system timer is dead. I cannot see any issues when running win7 or fedora linux. Everything looks ok. Should I be concerned???
I noticed the beeps this morning because it turned out I've used the wrong pins for the beeper (JFP2) for the mobo. That's why I haven't heard them before (if there were any).
Should I be concered for those beeps?
Q2. In the "green" section there are 2 options to choose from: APS and Intel SVID XXXX. When I choose APS all 6 phase leds are on all the time. As I said before the system hasn't been overclocked (i5-2500k). Even in idle (after 15 min) I still have a solid light from all 6 leds.
If I choose Intel SVID instead of APS after the system fully boots it shows 1 led with steady light, the following 4 are lit but not as intensive as the first one, and the last led is blinking. So I still have all of them on. I have enabled the c1e state and the other c states and chosen "no limit" for the c-states.
once again: Should I be concerned about this? Why don't those led turn off et least in idle???
Q3: I'm using an raid0 for my data and therefore have enabled the intel-raid. As a result when booting I have to wait about 7 sec starring in front of the "intel raid-rom bla-a-a-a". Do you know how I can hide the this intel-blaaaaa and speed up the boot process?
otherwise the system looks rock solid but those isses drive me crazy!
--peter

Please post the full system specs.
>>Posting Guide<<

P67A-GD65 Standby issue

Hi,
I've noticed that when I go to the menu to shut down on Windows, there's not an option for Standby, and if I hit the Standby button on my keyboard, it just turns off power completely. Is there no standby option for this motherboard? It's quite possible that I overlooked the setting in the configuration menu for the motherboard, but I'm not sure.
It's a P67A-GD65 (B3), and I've got a Corsair 650W PSU, and an Intel i5-2500k CPU. If you need additional info, let me know.
Thanks,
Nolan

Quote from: Bernhard on 14-March-11, 12:58:12
>>Posting Guide<<
What exact version of Windows are you using ?
Win7 has a "Sleep" option in the shutdown menu drop down. This will put it into the S1 or S3 sleep state depending what you have configured in your BIOS, that is of course if you have not configured something else in the Power Options of the Control Panel.
In the Power Options facility in Windows, you are able to determine what should go to sleep when, and once you have set that up, then there is no real need to use the manual sleep option.
The "Change advanced power settings" allows you to set the minutes for every conceivable piece of hardware to go to sleep.
Sorry, Windows 7 Ultimate (64-bit)

P67A-GD65 boot issue

P67A-GD65
Bios version 1.7
I have this board now a few weeks and can't solve a little problem.
When i boot most of the time the board boots fine but sometimes i get in the right corner the 'B4' post code.
At that time nothing happens. After a short while windows start loading.
From what i know is the 'B4' code usb hot plug.
So i plugged my mouse and keybaord into different usb 2.0 ports..same problem.
No other usb devices are attached at that time.
So..why most of the time a perfect boot and sometimes a code i don't understand ?
Thanks in advance.

Quote from: Bobbika on 23-February-11, 07:15:20
Did you try booting with a different keyboard or mouse or none of them at all? I have a Steelseries Xai mouse that makes the boot hang on code B4. It takes about a minute longer than usual. With a simple Logitech mouse it boots like it should.
I haven't tried another keyboard or mouse.
There is no pattern in the B4 code. Totally random.
It could happen twice or after 10 succesfull reboots

P67A-GD65 USB Issues

Okay folks, I have had much of a system change since lightning took out my AMD box.
My new system is in my sig and I have had it for about 4 months now
I have 3 USB Enclosures. A Hornettek JAWS and a Hornettek Viper, USB 3.0 Editions. I also have a Kingwin USB 3.0 edition.
When using the drives with this particular motherboard, I get some weird behavior from the Hornetteks. Randomly when the system is operating, the drives will disconnect from the system and shutdown power to themselves. To get the drives back, I have to disconnect power..... wait 10 secs.... plug them back in. I have ensured all power management is disabled. It does not matter if the drives are idle or being used. I have updated my BIOS and drivers to the latest versions. I am not overclocking anything.
I contacted Hornettek and RMA'd both boxes. They sent me two new ones and the issue still occurs. The Kingwin box is fine. Does not matter if I am using USB 3.0 or 2.0 ports. Keyboard and mouse, along with all other USB devices is fine.
Contacting MSI resulted in my sending my motherboard in for RMA. I really really REALLY do not want to tear out this watercooling. Any thoughts??? Suggestions??

Quote from: KidDaGoat on 08-September-11, 01:32:54
Since I can't edit my post.... where are you going with the PSU??
I have seen Corsair AX1200 and Antec Quattro 1200W with similar specs to mine. I have had more USB devices plugged into a 700W Tagan ABS PSU without issue.
If mine isn't putting out the juice how would the similarly spec'd items be able to do so??
MSI believes it is the motherboard. Hornettek confirmed the enclosures are fine. I have used them on another computer.
This is the first time I have ever encountered anything like this.
As I have found out and already make the clear statement with my doubts on your PSU's claim of 1250watts by just looking at the combined power of +12v rail. How can the maximum total output of the PSU's +12v combined rail alone take up the whole 1250watts? If that is the case, being a max output of 1250watts for +3.3v, +5v & +12v will leave 0 watts for +3.3v & +5v rails already.
I hope you see the picture here and like I said, I did not want to put the PSU as the main culprit but the specs give doubts. It is always good to test out with another PSU.
If you are wondering if I'm harping on wattages or branding of PSU, I can easily prove you wrong as my old system as listed in my siggy is currently running strong for 7 years and powering 5 USB external drives every now and then. Look at the PSU I'm using and it is no big name, except it is a mid-entry level PSU from AcBel. Before this AcBel, it was powered by an Enermax 475watts which died after 4 years.

Freezing/Hanging - Mobo Issue (P67A-GD65)?

Quote
========
Chassis - COOLER MASTER Elite 430 RC-430-KWN1 Black Steel / Plastic Computer Case
Hard Drive - Western Digital Caviar Blue WD10EALX 1TB 7200 RPM SATA 6.0Gb/s 3.5" Internal Hard Drive
CPU - Intel Core i5-2400 Sandy Bridge 3.1GHz (3.4GHz Turbo Boost) LGA 1155 95W Quad-Core Desktop Processor BX80623I52400
Mobo - MSI P67A-GD65 (B3) LGA 1155 Intel P67 SATA 6Gb/s USB 3.0 ATX Intel Motherboard
PSU - RAIDMAX HYBRID 2 RX-630SS 630W ATX12V V2.2/ EPS12V SLI Ready CrossFire Ready Modular Modular LED Power Supply
RAM - Patriot Gamer 2 Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Desktop Memory Model PGD38G1333ELK
GPU - EVGA 02G-P3-1386-KR GeForce GTX 460 (Fermi) 2GB 256-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card
CD Drive - Asus DRW-24B1ST/BLK/B/AS Black SATA 24X DVD Burner - Bulk - OEM
---------------After reading CPU temps--------------
Upgraded CPU Fan - XIGMATEK LOKI SD963 92mm HYPRO Bearing CPU Cooler bracket included I7 i5 775 1155 AMD and dual fan push pull compatible
=======
Alrighty everyone, so this might end up being a fairly lengthy article, but I want to make sure I give you all of the information so you can correctly assess.
Earlier in the year, I decided that I needed a desktop for college. I had seen people do it before and I was fairly adept at computers, so I put the computer together with the above components from newegg.
Originally, I put the desktop together in about five hours and hooked it up. Worked great, except on startup it gave (and still gives) me an error of saying "No Hard Disk Detected", however the opposite could not be truer as it found my hard drive when I loaded the OS; Windows 7. I then tested it that night with Starcraft II and it worked great; no minor bugs, nothing. The following day, I pull all of my games/programs on it including skype. Here is where things started to get weird. On Borderlands, everything went great and without a hitch, however when I started Civilization V, after playing for about an hour, it froze. And this freeze froze everything; the keyboard, the monitor, the mouse, etc. A buzzing sound came from the speakers and a hard restart was necessary. This freeze also happened again during the Multiplayer for Call of Duty Modern Warfare 2, Starcraft II (after about an hour), League of Legends and even Skype, while using my webcam. Also, in the Windows reliability program and windows events, no freeze is registered.
So I thought "oh, this is obviously overheating or a voltage problem" (the cpu temps were getting between 85-90 C's). So I fixed the RAM's voltage so it fit exactly what it needed (it required 1.65 volts, but the auto detect only gave it 1.5, so it was around .15 off). While waiting for the fan and thermal paste to come, I reinstalled Windows 7, reinstalled the drivers for all of my components and checked event viewer (which I ended up needlessly fixing an event 3011 and 3012 for corrupt performance readers).
My fan and paste came in yesterday and applied both, making my cpu super-cooled leveling off at a max of 50 C's at full load and 25-30 C's idling. The hottest component is now the GPU which usually hits 65-70 C's under full load.
At this point, I figured "great, I have been freeze-free for 2 days, let's retest", so I played two games of league of legends last night (around 1.5 hours) on skype and it froze. Again. Once I restarted my desktop to let everyone know what happened (and loaded skype and rejoined the conversation) I only got in two words before it froze again.
In summary, basically under stress, especially under games/programs requiring the internet, the computer has a full freeze, requiring a hard reset. I tried to fix the voltages (RAM) as well as cool the computer, which seemed to work only for a short while. Further once the computer freezes, whenever I turn it back on, it is more prone to freezing unless I leave it off overnight.
I'm not even necessarily looking for an answer, just an idea of where to start. Thanks again, I would really appreciate some help on this one.
=========
Update: I used Prime95 to test it as well as Intel Burn Test. No freeze during IBT, and for Prime95 it usually gets hit on the In-Place Large FFT or Blend Test. Hasn't frozen on Small FFT. I also just updated the the mobo's BIOS again to the latest one. Also, with the update, if I put the RAM's voltage at 1.65 (or anything above Auto), it won't boot the OS.
Any ideas welcome.

Quote from: bspeir on 08-August-11, 04:15:04
Right, saw this in my email inbox and thought I would respond, being the OP and all. I asked MSI what the problem was (giving all issues I had) - the response I received was
"We have to suggest you contact your reseller (The place you bought this MB from) and have them test the MB completely for you to check if this MB is faulty or not, then ask for some help.
If the reseller for some reason cannot help, we have to ask you to contact MSI distributor or MSI office near your place to seek further help" about 2-3 weeks ago (took them a month to get back).
The only problem with this, is I am a college student and half about five days left to get back to school and I NEED this desktop for school. So giving back the computer, allowing them to run tests, then waiting to return it seems like an entirely long and not necessary considering the desktop WORKS, but only on 4GB of RAM as opposed to 8GB.
However, I AM willing to check the c-state, but I will need some information first to make sure my desktop won't explode if I do this wrong.
1) What does the C-State do?
2) How do I disable it?
3) Is this really an option I should check into?
Thanks again, this community has honestly been more helpful than MSI's actual customer support.
It won't help you with your problem but I've tested C-state for a while and you can read what it will do in the link HU16E provided. I've noticed that in Idle state the usage of power drops a couple of watts, so when you have your PC in idle a lot of time and you care about power saving it's worth trying. When overclocking it can be unstable however. I have a CPU that handles all cores set to 46 with all energy settings on and auto Vcore completely stable, when going to 47 I have to compensate. The first thing I have to do is disable C-State because it will BSOD when in idle for a while. So I will suggest that if you use stock settings and care about power saving you try it and otherwise disable it.

[BUG] Marvell SATA drivers v1051 on P67A-GD65 (B3)

Hi folks,
NOTE: After further testing, drivers 1.0.0.1047 (the ones found on the MSI website) do NOT have this issue, only the driver version 1.0.0.1051 (See post #4).
Discovered a bug on the Marvell controller drivers version 1.0.0.1051 (the ones found on the DVD that comes with the MB). MB is the P67A-GD65(B3) with BIOS 1.9
When I wake up from suspend, 4 times out of 5, my cpu will show 10%-13% of usage caused by Interrupts (shown in Process Explorer). When I open the SysInfo window of PE, I see that ~80% of the core0 is being used just for said interrupts.
This only happens when you resume from suspend (haven't tried hibernation since I won't use that). It never happens if you just boot normally.
After debugging this for a few hours (xperf traces, performance analyses, latencymon.exe), I finally figured out which driver was causing this and it turns out it's the Marvell Controller one.
1) When I disable this controller (only this one), this issue *never* happens.
2) if I uninstall this driver *while* the interrupts are going bonzo, the interrupts go back to normal.
3) when Using the default Microsoft Drivers for this controller, the issue never happens.
- To recreate, just install the drivers (and perhaps do *not* connect any drives to connectors 6-7 (or 7-8) on the mb).
- Go to sleep mode (I suspend to memory here.. not sure what happens on hibernation), then resume a few times, and you'll have the interrupts start going crazy.
Hope this is the right forum for this.. if not, I apologize in advance...
Regards,
M
P.S. This happens whether I overclock or not (currently not OCing and it happens just as frequently)

Bah! I couldn't let it go when I saw that the drivers on the MSI site were version 1.0.0.1047 instead of 1051 ( hate leaving a job unfinished).
So I decided to install the ones on the website, and they work perfectly (in regards to the interrupt after resume issue).
So, thanks for the pointer Jack . I now know that I'll be able to use the 6GB sata ports if I ever need them with the proper drivers (Microsoft's only support 3GB I believe).
/cheers
Regards,
M
P.S. Makes you wonder what they changed in 1051 though.

P67A-GD65(B3) and drive upgrade (3TB, GPT) issues

Hi,
I was happy P67A-GD65 owner.. until now. I've bought 3TB single drive to replace old 2x1TB drives working as RAID-0.
PC had no problems at all with detection new drive, I've connected it with SATA2 port&cable due to such case construction. I've partitioned it with GPT style = all fine.
Troubles started once I wanted to clone RAID-0 partitions to new drive. MBR->GPT partitions are not an issue, but I've got 8 operating systems there (3xWindowses, 5xLinuxes), so I had to use two-stage bootmenu: first stage MBR-based (GRUB) with direct Linux starters + entrance to Windows menu, and second stage EBR-based (Win Vista/7-style) with Windowses only. Strictly I have no idea which program is able (if any, as I doubt) to make simply copy of all structure to new drive, because of MBR... I decided new drive will be GPT-like, so no more WIndows XP and MBR -> if so, so MBR-based boot-menu goes to h*ll -> if so, so first stage menu is gone, half of my operating systems is unstartable.
So I decided to go with "manual way" and install all OSes by hand. Yes, it's a pain. One week probably out of my life calendar.
So I disabled SSD and RAID, sticking with new drive only. Windows 7 has been installed. OK then - I think - time to enable RAID-0 and copy data. ZONK... I simply can't boot "new" drive (UEFI-based) with RAID enabled.
You must know I've done Win7 install with no RAID enabled, as well as BIOS option regarding to SATA mode was set to AHCI (whether my previous setup required setting this to RAID).
SO my question: is it possible to boot PC from UEFI-based drive (GPT-style partitions) and have RAID-0 (MBR-style) attached somehow ? Drive requires AHCI mode and hangs up with RAID mode (bluescreen). I underline - it works the opposite way: I can boot from MBR-ed RAID and attach GPT single drive (BIOS SATA settings: RAID). Have I to reinstall Win7 with RAID turned on ??
Cheers,
Martin

No, it's not GPT partitioning. I've done this properly now, Windows didn't shout during install...
So - summing up:
All connected (SSD & 2xHDDs in RAID-0 & new 3TB HDD) - to Intel SATA ports:
port 0: 3TB Toshiba
port 1: SSD
port 4: RAID-0 vol1
port 5: RAID-0 vol2
.. in BIOS there's SATA mode set to: RAID mode. Clicking F11 - bootmenu - during startup:
* Windows boot manager (UEFI) boot - shows screen with corrupted uefi/someething file, repair or reboot
* Intel RAID-0 boot - loads Win7 from SSD, new drive is shown with no problem
Single drive boot (SSD & RAID-0 unplugged):
* Windows boot manager (UEFI) boot - loads Win7 from new 3TB drive
So I can't work with newly instaled WIndows (and copy a whole content of "old" HDDs having booted from new drive), I have to boot "old" MBR-based RAID-0 system and copy files instead. It's a bit odd as if I wanted to connect RAID-0 (or another bootable drive) in the future = boot might be impossible ?
I'm just afraid how Linuxes will go... brrr.

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.

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.

P67A-GD65 (B2) - Asus R9290 DirectCU II Post Issue

Hi All,
Having an issue with the above card posting which I understand is an issue with the below BIOS version.
BIOS v1.19 / 1.J0
Intel ME 7.1.52.1176
I have tried to flash the BIOS with the forum tool and custom BIOS E7681IMS to allow the ME8 update which I have read on the forum will allow compatibilty with the card. However I am seeing the following message when the tool runs ''The Host CPU does not have write access to the target flash area you must modify the descriptor setting to give host access to this region''
Is there an option I need to check in the BIOS before updating - not seeing anything relating to this in the options.
Appreciate any assistance here.
Thanks
Izzzit

If your P67A-GD65 is really a (B2) you can't flash it with an ME8 bios required to run latest AMD R9 or GeForce GTX7xx and above. Only (B3) can be updated to ME8. The B2 should have been returned long ago when there was an issue with that revision of the Intel chipset that has been cured with the B3 revision.

P67a-gd65 b3 sleep issue

Hi guys,
Just did a new build using p67a-gd65 board with core i7-2600K, evga gtx580, 4GB ripjaw gskill memory, crucial c300 128gb SSD.
The problem I am having is that when the computer goes to sleep (S3 set in bios) it turns completely off, I cant wake it from the mouse or keyboard. Have to hit the power button to get it to start and at that point it's basically rebooting rather than resuming from sleep and Windows complains it wasnt shut down properly.
I have all the right drivers installed from MSI, using their live update utility and all the windows 7 64bit patches etc.
Anyone else facing this issue?

Please post back following the guidelines in this link. This will help users better troubleshoot your issue.
https://forum-en.msi.com/index.php?topic=38822.0
Without knowing details I would say to check 1) OCing, 2) Power supply capabilities and 3) Different RAM, GSkill Ripjaws can be problematic
Quote from: ymee on 13-March-11, 03:38:12
Hi guys,
Just did a new build using p67a-gd65 board with core i7-2600K, evga gtx580, 4GB ripjaw gskill memory, crucial c300 128gb SSD.
The problem I am having is that when the computer goes to sleep (S3 set in bios) it turns completely off, I cant wake it from the mouse or keyboard. Have to hit the power button to get it to start and at that point it's basically rebooting rather than resuming from sleep and Windows complains it wasnt shut down properly.
I have all the right drivers installed from MSI, using their live update utility and all the windows 7 64bit patches etc.
Anyone else facing this issue?

P67A-GD65 new system bios setting recommendations and sata connections

Hey all,
My old dual core HTPC (after many hours of use) finally gave up the ghost and moved on to the great PC grave yard . I have ordered all the new upgrade parts from Newegg and am looking for recommendations on what bios settings and setup procedures I should use on the initial bootup and Windows load. I'm not looking to overclock I just want a fast stable system for video decoding and playback. It's my understanding from the manual that SATA 1-2 are controlled by the Intel P67 chip and 7-8 are controlled by the Marvell chip but I am unsure of SATA 3-6. Can SATA 3-6 do raid 0? I want to use the Crucial SSD as my primary boot drive and the 2 WD drives on raid 0 as my secondary drive. SATA connection advice (which SATA ports) and Raid Bios setting would be helpful. Should I install the raid 0 drives after I have Windows 7 loaded on the SSD? Any other setup advice is appreciated.
Here is my setup.
Windows 7 64bit
Bach HTPC case
Ultra LSP 750Pro PSU
Intel i5-2500 3.3G CPU
MSI P67A-GD65 Motherboard
Sapphire HD5570 1G RT Video Card
Crucial CTFDDAC128MAG-1G1 SSD 6.0Gb/s SATAIII (Primary boot drive)
2 WD3200KS Hard Drives SATA 3.0Gb/s (Raid 0)
Lite-on 12X Blu-Ray Burner SATA
G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600

Two questions answered. SATA 3-6 are controlled by the Intel P67 chip and do support Raid 0 but I still wonder if I should wait to install the drives until Windows has finished it's install.
SATAIII controller integrated in Intel® P67 & Marvell SE9128 chipsets
- Up to 6Gb/s transfer speed.
- Supports two SATAIII ports (SATA1~2) by P67 PCH
- Supports two SATAIII ports (SATA7~8) by Marvell SE9128
- SATA1~6 ports support RAID 0/1/5/10 mode by Intel P67 PCH
- SATA7~8 ports support RAID 0/1 mode by Marvell SE9128

USB3 Issues P67A-GD65 (B3) MB

HI Guys.... little bit of frustration here, recently swapped out my old case to one with a front USB3 port, but when i plugged it into the USB3 header on the motherboard it refuses to read a USB3 hard drive, i've tried my seagate as well as other hard drives but all seem to be suffering the same issue... the best i got was after installing some other drivers not downloaded from the MSI site and it recognised the one hard drive for all of 10secs and then nothing, USB2 devices work perfectly but not USB3, all the USB3 ports in the back panel work perfectly... but i was hoping that i wouldnt have to get down on my hands and knee's under the table to plug them in anymore.... i know this board is quite old but i'm hoping that some one around here has had some luck with solving this issue and can point me in the right direction...
Things i've tried unsuccessfully,
Updating driver
Updating renesas firmware (get a plural device error)
formatting and reinstall win 7 and drivers
*unplug and throw against wall*
System is running:
Win 7 x64 Ultimate SP1
I7 2600
16GB Kingston Ram
MSI 660 TI PE
MSI P67A-GD65 (B3)

First impression is the case connection cable is defective. If you have one or can borrow one, try with a standard accessory USB 3.0 bracket.

P67A-GD65 SATA Issues

Similar Messages

Maybe you are looking for