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.

Similar Messages

  • 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.

  • 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 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 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(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 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

  • Boot Cooling Issue on MSI P67A-GD65

    I luv my MSI P67A-GD65 with the 1.8b10 bios but this one has me baffled - first of all my system is controlled by a wall switch so at night I hit the switch and all power is off the system.  When I turn it on after work I hit the power button and when I go into bios the temps read 97c!.  After a restart the same thing and then on the third try temps are normal.
    I have the CPU temp setting at 50c and am suspecting that the Corsair H50 pump does not have enough volts to turn over especially when it is cold.   I've been dealing with it but those high temps are kind of scary.
    My Green Power CPU Power setting is APS.  Any Ideas??
    jja
    MSI P67A-GD65 @5.0ghz 1.375vcc | 4g G-Skill RipJaws 1600 7-7-7-24 1.6v : Corsair 1K PS : Corsair H50 Cooler | GIGABYTE 580GTX
    ENABLED settings: SpeedStep, TurboBoost, Internal PLL Overclock, C1E, C-State, HPET, Enable CPU Ratio In OS, Ram XMP Profile.
    DISABLED settings: HyperThreading, OverSpeed Protection, Spread Spectrum
    Also POWER MODE = APS,  VDroop Contol = AUTO and all cores Limited to 50 Mult

    Quote from: Henry on 01-February-11, 11:23:45
    Maybe the fact that by shutting off the power like like that you lose the standby power to the MB creating your problem. Do you have the same problem if you don't shut the wall switch off and just shut the PC down the normal way in Windows?
    I always shut down windows first then hit the wall switch.  Tonight I'll leave the power on to the computer and will check it tomorrow after work.
    thanks
    jja

  • P67a-gd65 (b3) - DDR3 2133 double restart issue

    I have had my p67a-gd65 (b3) for just over a year. Mostly been ok.
    Today I received my Mushkin Enhanced Blackline 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 2133 (PC3 17000) Desktop Memory Model 997015.
    I went in set the bios to 2133, checked voltage (was reporting like 1.488v so I upped the voltage from auto to ~1515 or whatever 2 up from 1.5 is) turned on XMP and rebooted. I immediately found that my overclock was no longer stable. So I reset to 34 multi and auto core voltage.
    Every time I turn on my computer/reboot now it starts to power up, shuts off, then powers back up again (like its booting twice). It is very annoying.
    If I turn the ram down to 1866 it acts normal (1 power on). Set it to 2133 and back to the double power on.
    I was on the latest beta bios, so I tried going back to 1e same thing.
    2600k
    p67a-gd65 B3
    Mushkin Enhanced Blackline 8GB (2 x 4GB) DDR3 2133
    Crucial M4 256gb ssd
    Asus GTX 680
    Enermax maxrevo 1350w psu
    Noctua Nh-D14
    Cooler Master Storm Trooper case

    Excerpts from another earlier thread;
    Quote
    I 'never' have a double boot behavior unless I use a certain configuration of RAM, speed and/or timing settings. Intel systems have had double boot behavior for years. Most of the time, with recent platforms, disable of EuP 2013 fixes it. IMO, I think it's frequency or frequency noise related to some degree.
    Quote
    Like I mentioned, with a certain RAM kit set to 1333, 1600, or 1866 speed = no double boot. With another different kit, 2133 speed = double boot.
    If your multi drops, that usually is an indicator the power duration limits are set too low, or the UEFI/BIOS version is an early release. Make sure EuP 2013 and Spread Spectrum are 'disabled'.
    Added: If you are setting X.M.P. to 'enabled', there should be no reason to set anything manually concerning RAM.

  • Random lock ups with MSI P67A-GD65 (B3). Please help!

    Hello all,
    I just built a new system with the following components:
    MSI P67A-GD65 (B3)
    Intel Core i7-2600K Sandy Bridge 3.4GHz
    EVGA 012-P3-1570-AR GeForce GTX 570
    G.SKILL Ripjaws X Series 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
    Thermaltake Black Widow W0319RU 850W ATX 12V  PSU
    Antec Lanboy air case
    2X Western Digital VelociRaptor WD1500HLFS 150GB in RAID0 running Windows 7 Pro 64 bit
    This was supposed to be my dream computer, but it has turned into a nightmare! It locks up constantly.  Usually the mouse pointer will disappear and the computer will just freeze up.  This normally seems to occur after the computer has been idle for a while.  I have read that there might be compatibility issues with the MSI P67A-GD65 and the GTX 570 video cards.  Can anyone confirm this?  Any suggestions on how to troubleshoot this?  The only thing event viewer is showing is the unexpected shutdown when I have to power cycle it.  Thanks in advance!

    Quote from: HU16E on 12-April-11, 11:26:00
    That can happen, & it can really mess things up if two kits are attempted to be run together. The platform is DDR3 1333 as to native support by the CPU IMC. If the system can't run on 1333 RAM speed at CR 1, 9 9 9 24 @ 1.50v's, then something is wrong. No system should ever have to use an OC (or X.M.P.) as a workaround to make it work. That's why I recommended the Crucial 1333. Plug one stick in the blue primary dimm slot to get everything loaded & checked out, & go from there.
    Exactly which SATA ports are you using for the HDD's & RAID? White Marvell or Intel SATA III, or the black SATA II? 
    Unfortunately, my local shop didn't have the Crucial, so I grabbed the Corsair instead.  The Velociraptors are running from SATA 1 and 2 (the top white connectors).  I also have 2X HITACHI Deskstar 2TB 7200 RPM 64MB Cache SATA 6.0Gb/s running in RAID0 from SATA 3 and 4 for storage (this computer is intended for HD video editing, compositing in After Effects, etc.).  Sorry I forgot to mention that in the original post!

  • P67a-GD65 System Freezes and Recovers During 3D gaming and Online Video

    The Problem:
    Temporary system freeze with audio stutter. The system recovers 30sec - 2min later.
    Key presses made during freeze will execute after system recovers (ctrl+alt+delete for example)
    Usually, but not always, I see an error message in the system tray and I do NOT experience bsod.
    This happens seemingly at random from 3D accelerated applications, and web browsing. Games such as BF3 (moderate), WoW (seldom), Planetside 2 (frequently), Minecraft (seldom), Hawken (seldom), etc.
    Also happens frequently in both Internet Explorer 9/10, Firefox, Chrome, and Steam store browser. Typically when watching steaming video (youtube, HULU, flow player, etc)
    but Pandora audio streaming also seems to create the conditions where this happens.
    Error Message:
    "Display driver stopped responding and has recovered
    Display driver NVIDIA Windows Kernal Mode Driver 314.07 stopped
    responding and has successfully recovered"
    The problem also shows up in the Windows reliability history with the following data:
    Source
    Windows
    Summary
    Video hardware error
    Date
    ‎3/‎6/‎2013 9:11 PM
    Status
    Not reported
    Description
    A problem with your video hardware caused Windows to stop working correctly.
    Problem signature
    Problem Event Name:   LiveKernelEvent
    OS Version:   6.1.7601.2.1.0.768.3
    Locale ID:   1033
    Files that help describe the problem
    WD-20130306-2010.dmp
    sysdata.xml
    WERInternalMetadata.xml
    Extra information about the problem
    BCCode:   117
    BCP1:   FFFFFA8011E0C4E0
    BCP2:   FFFFF8800654A198
    BCP3:   0000000000000000
    BCP4:   0000000000000000
    OS Version:   6_1_7601
    Service Pack:   1_0
    Product:   768_1
    My System Hardware:
    CPU: Intel i7 2600k @ 4.5ghz
    Motherboard: MSI p67a-gd65 (B3 stepping)
    Memory: G.SKILL Sniper 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600
    GPU: Originally MSI 6950 2GB. Replaced with EVGA 670 FTW 2GB.
    PSU: CORSAIR HX Series HX850 850W
    HDD: 3x Western Digital WD RE4 WD5003ABYX 500GB in Raid 0
    OS: Windows 7 Home Premium SP1 with all updates
    Case/Cooling: Silverstone Raven 2E with Thermalright silver arrow cpu heatsink
    What I've tried:
    Updated all motherboard drivers and bios (4.3) to current versions (no improvement)
    Updated display drivers (in safe mode with driver sweeper. No improvement)
    Updated Realtek Audio drivers for onboard sound (no improvement)
    Updated Intel Rapid Storage drivers (no improvment)
    Cleared CMOS and tested system at default settings with no overlock (no improvement)
    Flashed 6950 back to 6950 stock bios and removed overclock (no improvement)
    Replaced old 6950 with new GTX 670 (problem still occurs in the same exact way)
    Tried GPU in 2nd PCIe slot. No improvement.
    Checked GPU Temps. GTX 670 fan profile in EVGA Precision X set to keep temp below 70 degrees Celcius. Card maxes at 60 degrees under heavy gaming load.
    Complete reformat of raid array with fresh install of Windows (4 different times) Seemed to help for a few days, then freezes came back
    Ran OCCT and Prime 95 Torture tests separately for a few hours at stock and OC settings. System stable with core temps of high 50's overclocked, and low 40's stock.
    Ran Memtest86 for 10 hours with zero errors.
    Used digital multimeter to test 12v rail on PSU. Noted solid 12v reported. Didn't test other rails.
    Unplugged PSU cables from motherboard and reattached firmly
    Ran HD Tune and Data Life Guard Tools for error checking on hard disks. Zero errors found.
    Disabled Windows Aero (no improvement)
    Updated Adobe Flash Player to latest setting (no improvement)
    Removed Adobe Flash Player (no improvement)
    Turned off Adobe Flash hardware acceleration (no improvement)
    *EDIT: Forgot that I also adjusted Nvidia driver profiles for apps that have frozen to include power preference to max performance
    All of my hardware with the exception of the new 670 was purchased and configured back in February of 2011. This problem first occured in BF3 multiplayer sometime in early 2012,
    and has gradually been happening more frequently. Web searches found many individuals with this error, but the solutions are all over the map, and I've tried just about everything that I've found.
    I think I've narrowed the problem down to the motherboard, but I just can't find a clear answer or solution. Maybe it's the raid array? I really thought replacing the GPU would solve my trouble here
    and I was...NOT happy when it happened again with the new 670 that I scored for $250 after amazon gift cards. I typically get kicked/disconnected during online game play when this happens and I'm ready to be done with it. I was hoping to fix the issue without needing to buy new hardware, but I don't see any other way at this point.
    My patience runs thin. Please help!

    Quote from: Froggy Gremlin on 11-March-13, 15:28:36
    Might want to ask for the special archive to return the mainboard to pre-Ivy support UEFI/BIOS and then test again with everything set to auto/stock/default.
    Already tested that before updating to 4.3.  I started having the problem on 1.8, then 1.J0, then 4.3.
    Quote from: Bernhard on 11-March-13, 15:30:29
    Just a shot in the dark.
    The length of time that your CPU has been running at the OC could have accelerated the eventual degradation.
    Have you tested your CPU in another board or do you have access to a "known good" CPU to test in your system ?
    I do not have another 1155 lga board to test the cpu in unfortunately, hence the CPU stress testing.  Based upon previous experiences with multiple overclocked systems that I've run at much more aggressive overclocks, I don't believe I'm seeing a processor failure, though I can't rule out the possibility.
    Quote from: xmad on 11-March-13, 23:26:01
    Quite a few components can cause this.
    Do you have a friend that could lend you a psu to test? A weak of failing PSU can often be the cause of something like this?
    No I don't have another PSU to test. I did use a digital multimeter to test the 12v rail, as well as the motherboard contacts for testing voltage to the cpu and system  They were all right in line with what I'm seeing reported in the bios.  I did not test these contacts while the system was under load however, so I may need to do it again.

  • P67A-GD65 BIOS Recovery/Reflash...is it even possible?

    Had a weird issue take out my P67A-GD65 last week so I replaced it with a Z77A-GD65. However, I'd like to see if it's possible to recover/reflash the corrupted BIOS on the dead board before I break the board up and make keychain fobs from the shiny bits.
    Background:
    BIOS flash process went fine. Seemingly so, anyway. After rebooting, however, it's stuck in a loop and never makes it to the POST/BIOS screen. It powers on for about 4-5 seconds, then off, then back on, then off again, repeat Ad nauseam

    Quote from: Froggy Gremlin on 03-April-13, 13:03:09
    If and when a UEFI/BIOS flash is required, use the forum's USB method;
    https://forum-en.msi.com/index.php?topic=108079.0
    In the BIOS Section of the forum, you will find Beta's along with some full releases for some mainboards in the Beta threads.
    If you do not intend to install an Ivy CPU, it is strongly recommended to only install Sandy UEFI/BIOS's.
    If lucky, remove the PSU power cord, remove all but one RAM stick that is placed in the primary DIMM slot, remove the battery for awhile, clear CMOS, hope it will POST and/or boot. If it won't, a pc shop with an SPI flash programming device can restore it for you. Otherwise, an MSI Service Center can do it.
    Thanks for the information. I'm betting it's likely bricked permanently, so I'll probably just toss it.

Maybe you are looking for

  • Can a BIG form be served up one page at a time to avoid long load time?

    Tricks I have read for optimizing the load time of large forms are not helping. Linearization causes the first page to render quickly, but you can't interact with the fields until the whole form finishes loading -- no help there. Is there a way to br

  • Printing multiple sets of Portfolio documents collated

    I use Adobe Acrobat 9 Pro's pdf Portfolio to print multiple documents with similar printing properties (two-sided, stapled, hole-punched) but they are separately two-sided and separately stapled. I try doing multiple copies but the print job comes ou

  • Creating environment in solution manager 4.0

    I have been assigned to create a an environment within Solution Manager under Business Process however I do not know how to do this, can somebody please advice me on how to do this or refer me to the correct guide or CBT. Any help would be much appri

  • Responsive projects autosizing for multiple devices -- best practices?

    While it's a nice idea to have the three different breakpoints on width that allow you to make some major layout changes, I'm having trouble making this work well across multiple devices.  With the high resolutions of current mobile devices, this mod

  • Internal Service Requests (ISRs) for Financial Data management

    Has anyone implemented ISRs for creating workflow approvals for creating GL accounts or Cost Centers ? I am on a project where this is being looked at as an interim solution until the Master Data Governance for Financials tool becomes available. I am