P67A-GD65 B3 - Permanent loop - anyone else?

Just received my brand new B3 motherboard today and it won't boot, my machine is in a permanent loop trying to reboot. The power switch that is on the MB is illuminated, the CPU fan comes on for a second (as well as the CPU phase 1 blue led) then turns off for about 5 seconds then tries again.
I've reset the CMOS several times with no success, even with removing the battery.
Removed all the other cards, and peripherals, just leaving the memory and CPU in the board but no difference. I tried swapping the memory sticks, running with just one and then the other, no difference.
Did anyone receive the new B3 MB and can confirm that it works fine? Does anyone have any idea on how to fix this issue?
FYI the rest of my config:
- CPU: i7 2600K
- RAM: G.SKILL Ripjaws X + Turbulence II Series 2 x 2GB DDR3 2133 (PC3 17000)
I bough the CPU and the RAM with the board so unfortunately I cannot confirm that they work on another rig.
Help! I've been waiting for this MB for 2 months now!

You wern't the only one with that problem. I had the same problem (mine turned on for about 7 secs before shutting down). It worked perfectly before I took the motherboard out to get the serial number (as shown thats supposedly the only place to find it). I put it back in, turned it on, then noticed a serial number on the box.  . And when i booted it, it shut down again. I took everything out, made sure ALL the connections were not loose, turned it on again. I smelled something funny this time.. I turned it on once more, lo and behold there was a little bit of smoke. 
If this helps, I used a magnetic screwdriver when screwing the screws in, and I think i might have touched the gold part on the screw holes    and im not sure if that has something to do with it or not, but i think it does. I had to RMA it to newegg, still have yet to pack it up.. also about 4-5 other people giving reviews to that same motherboard on newegg showed the same problem (minus the smoke). 

Similar Messages

  • MSI P67A-GD65 infinite boot/loop problem

    installed everything into my case and go to boot into the UEFI and nothing !
    i press the power switch, everything starts fine and the fans spin up and the LED's on the board are fine, waits 5 secs then it shuts itself off and tries the exact same process again. it keeps doing this until i cut the power !
    i've checked the 24pin etc, KB & mouse r fine, 2 different sets off RAM in every slot, cleared CMOS (i think).
    seems like a very common problem with this board after a bit of googling !!
    also tried
    Quote
    this is the 1st time ive used it !
    tried the OC genie button on and off.
    been sitting in the box unused for about 1.5 months. doubt that means anything tho.
    put the stock cooler on securely, and still the same problem !
    now tho, it wont start for about 3 secs after i press the power button
    and
    Quote
    disconnected all the SATA's bar 1, and still the problem :/!
    all the standoffs etc r fitted correctly and iv re-connected the 8 pin cpu and 24 pin. 1 stick off RAM in the 1st slot also :/!
    checked no molex connectors r touching the case metal either
    any suggestions?

    motherboard: MSI P67A-GD65 (B3) bought on march 31st and used today for 1st time
    CPU: intel core i7 2600K
    CPU Cooler: tried an alpenfohn matterhorn with Scythe 1850RPM gentle typhoon Push/pull also tried the stock cooler
    RAM Corsair CMD4GX3M2A1600C9 (2X2GB kit of 1600Mhz CL9 corsair dominator DDR3) and tried Patriot PSD34G1600KH (2X2GB kit of Patriot signature DDR3)
    PSU Corsair TX650 650w psu
    GPU XFX radeon 4870 1GB
    Case NZXT M59 + mainly scythe fans and a noctua and coolermaster
    DVDRW liteon DVDRW
    Storage 128GB kinsgton SSDnow V100, 1TB Samsung F3 7200RPM, 1TB Hitachi 7K100 7200RPM all sata 3gb/s
    Generic 5.25" fan controller
    2 x 12" blue CCFL's
    OS windows 7 x64 professional (installed on the SSD, but havent booted it yet as the board doesnt even get to BIOS :()
    peripherals Microsoft reclusa keyboard and gigabyte GM-6990 (i think) mouse
    monitor Benq g2222hdl connected via DVI
    the only things i have changed today are, put the new notcua fan in my case, changed the Motherboard and CPU from and Asus M4A78LT-M & Athlon II X4 640 to MSI P67A-GD65 (b3) & intel core i7 2600k. Also, put the alpenfohn matterhorn on today.
    everything is confirmed working apart from the CPU & Motherboard. everything worked yesterday, but i didnt have the necessary equipment to test the motherboard or cpu before using them together (today)
    hope this will help

  • Aperture and DNG.  Anyone else seeing this?

    I shoot a lot of RAW images and some of them on a camera that is not currently supported by Aperture (Panasonic DMC FZ8). When I convert those RAW images to DNG, Aperture displays them perfectly in the import preview. When I import them to a project, Aperture displays them for a few seconds. Then they disappear only to be replaced by the usual blank red image placeholder and the message "Unsupported Image Format". If the program can display these images for 5 or 10 seconds why not permanently?
    Anyone else seeing this? If so is there a way to manage these images in Aperture? I like the program, but it's difficult using one app for RAW images and another for the rest. Any news (rumors) as to when Apple may be updating the supported camera list?
    Thanks
    Joe

    Aperture only supports DNG from cameras that it supports the RAW file from, so your Panasonic DNGs are not supported. What you are seeing is simply the embedded JPEG that flicks on until Aperture realizes it is not a supported file.

  • When I export a AAF file from Protools 9 and Import the file into Logic ProX the drum track is out of sync.  I created the drum loop using NI Maschine.  Has anyone else seem this??

    When I export an AAF file/project from Protools 9 using an external drive and import the AAF into Logice Pro X the drum track does not play correctly.  It is out of sync with the rest of the track.  I created the drum loop as a plugin using Native Instruments Maschine. Has anyone else had this problem??  Also how would I go about exporting the midi tracks from the Protools session.  The midi track does not show when the file is imported to Logic Pro X.  The midi data should export with the AAF file correct??

    Are you using any plugins in Logic?
    In Preferences/Audio  under the General tab, how do you have the plug-in-latency compensation set?

  • For Those Experiencing the Infinite Boot Loop on P67A-GD65

    My story in a nutshell - bought the original (non B3) P67A-GD65 from Newegg on the first day it was available along with 8 GB (2X4 GB) Corsair Vengeance DDR3-1600 ram and Intel i5 2500k processor.  Received the items, hooked them up on a test bench (rubber mb supports so no grounding issues) along with a Corsair VX-550 P/S (both 24 pin and 8 pin leads plugged in), GTX-460 video card (2 PCI-E 6 pin connectors plugged in), the default Intel i5 heatsink and a known good USB KB and mouse.  Promptly experienced the infinite loop boot issue others have described - fans on h/s and video card spin up, 1st APS LED lights for a fraction of a second then all 6 light up for 3 to 4 seconds then APS LEDs go out and fans on h/s and video card spin down.  No beeps from speaker and no video signal to monitor.  After everything has stopped spinning (about 3 to 4 seconds), the power comes back on and the cycle repeats exactly the same way every time until I turn off the power supply.  Here is what I tried:
    1.  Used only 1 stick of ram (tried in all 4 slots)
    2.  Pulled 1 stick of DDR3-1600 ram from my working X58 system (again tried in all 4 slots)
    3.  Different power supply (OCZ 520-ADJ)
    4.  Known good PCI video card instead of GTX-460 (in case there was some problem with power draw)
    Under each of these changes, the same infinite boot loop occurred.  Called tech support, they walked me through each step I had already tried and finally suggested I RMA both the MB and the CPU to Newegg.  Did so and the replacements worked fine from the start.
    Then came the B2 stepping issue.  Notified both Newegg and MSI that I had one of the B2 boards.  Newegg notified me they had the new B3 boards in stock.  Arranged for cross shipment where they would ship me the new board and then I would return the old one.  Received the new one last Friday.  Put it on the same test bench as above and the same infinite boot loop is now happening on the new B3 stepping board.  Just to test, put the cpu, ram and GTX-460 video card back into the B2 stepping board and everything works perfectly.
    Another test, since some people reported the infinite loop problem when they had failed to plug in the 8 Pin power lead to the mb, I unplugged the 8 pin connector on the working B2 stepping board.  The infinite loop problem is entirely different in this case.  When you press the power switch, the fans start to spin and the first LED lights for less than a second.  Then the LED goes off and the fans start to spin down.  After everything has stopped, it repeats until the power supply is turned off.
    This is my first MSI motherboard after 15 years of Abit and Asus with the occasional Gigabyte or EVGA thrown in and I am not happy with the QC I have experienced with this board!
    So to summarize, 2 of the 3 P67A-GD65 boards I received from Newegg have had this infinite boot loop problem.  Apparently, I have to RMA again.  Am I lucky or what???!!!
    Monte

    Quote from: BMSliger on 16-March-11, 00:05:11
    If it was the chipset causing this problem, it seems it would be a widespread complaint among all vendors.  I have looked at the Asus and Gigabyte boards and do not see this particular problem described and certainly not multiple users reporting the same problem.  I am giving up on this and will arrange an RMA and will see if I can talk Newegg into an Asus board for only the price difference.  MSI has a very good reputation in the industry, but it has been a disaster for me!!!
    Thanks for your replies,
    Monte
    Frankly, I can understand your frustrations on the problem but it is not fair to judge a brand by looking at the number of complains in a forum. I can guarantee you, there are more RMAs out there from all other manufacturers even before an user even knows that a Forum ever exist for them to post for enquiry and most of them aren't an IT engineer or hardware engineer by self.
    If you want to compare, I have also been in this industry for more than 15 years and I have many DOA boards from other manufacturers as well and DOAs after RMAs are common to me. When you handle thousands of PCs, laptops and mainframes, such things are really common.
    Back to your problem. Maybe I didn't make it clear on how I want to describe on my previous post for your issue in words. I am referring to having a chance to let the system boot into BIOS or past BIOS after multiple times of rebooting, then you can try to flash the BIOS. This is also not uncommon as I have encountered systems which are problematic but are able to boot into Windows after 15 to 20 times of infinite reboots by itself.
    How about processor? Tested it in another system yet? Or is this another unless suggestion to you?

  • Has anyone else got permanent Hilton Hotel pins on their ios 7 maps?

    I was excited to see how Maps have updated on ios 7, however, I've noticed that there are pins for local Hilton Hotels. I tried to remove them but there is no option to. Does anyone else have this problem or any other 'permanent' pins. I hope this isn't some sort of advertising scheme!!

    Ok, turns out I just had to search for something first, then they disappear. Now I feel like an idiot...

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

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

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

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

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

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

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

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

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

  • P67A GD65 System build First startup goes into restart loop

    I just build a p67a GD65 System i am an experienced system builder testing out on a cardboard surface after the system would not boot.
    Using corsair Vengence ddr 3 ram
    Coolmaster silent pro 800 W power supply
    Hyper 212 plus cooler
    2600k processor
    After the continuous loop i tested power supplies swapped them and got the same problem
    Then i got a clean cardboard box and started troubleshooting now the system, even barebone with the essential hardware only won't boot at all I do however see the green power light go on and OC genie light, light up when i press the power button but the system won't budge, I'm wondering if this is a bad processor or motherboard? I am leaning towards a bad mobo as these problems with this particular MSI board have been rampant.
    Just to add none of the bios LED's light up.

    Quote from: crxer on 16-September-11, 04:44:54
    I just build a p67a GD65 System i am an experienced system builder testing out on a cardboard surface after the system would not boot.
    After the continuous loop i tested power supplies swapped them and got the same problem
    Then i got a clean cardboard box and started troubleshooting now the system, even barebone with the essential hardware only won't boot at all I do however see the green power light go on and OC genie light, light up when i press the power button but the system won't budge, I'm wondering if this is a bad processor or motherboard? I am leaning towards a bad mobo as these problems with this particular MSI board have been rampant.
    Just to add none of the bios LED's light up.
    I have a question crxer, does the OC Genie Light come on and stay on, or does it turn off? If it stays on then you have the OC Genie Button pushed in and you're trying to overclock the system right off the bat which you don't want to do, and that could be why the constant power cycling because of an OC failure.
    Not that this is similar to your problem, but I had a Z68A-GD65(B3) which gave me nothing but problems with overclocking and the the dual bios feature. I would get the power on recycling a few times every time I tried any OC and reboot whether by using the OC Genie button or manual OC, but it would then eventually boot. Mine would also give me the Bios LED coming on in all the different configurations telling me the primary bios failed or secondary or both but I was always able to re-flash the primary bios and the board was never bricked. You're not having that problem thank goodness.
    I am a very experienced builder and troubleshooter and tried everything to isolate the problem and make that Z68A board work, but to no avail, which is why I returned it to Newegg and replaced it with a MSI P67A-GD55(B3) shown in my signature, which is similar to your GD65 and it works perfectly with all the same components as I used on the Z68A-GD65(B3), and I have it manually OC'd it to 4.3 Ghz which is good enough for now. Good luck crxer. 

  • P67A-GD65 rebooting loop

    I have the constant rebooting problem, its the same problem (mine turned on for about 7 secs before shutting down) as many others. It worked perfectly before I took the motherboard out to get the serial number (as shown thats supposedly the only place to find it). I put it back in, turned it on, then noticed a serial number on the box. And when i booted it, it shut down again. I took everything out, made sure ALL the connections were not loose, turned it on again. I smelled something funny this time.. I turned it on once more, lo and behold there was a little bit of smoke.        
    If this helps, I used a magnetic screwdriver when screwing the screws in, and I think i might have touched the gold part on the screw holes and im not sure if that has something to do with it or not, but i think it might. I had to RMA it to newegg, still have yet to pack it up.. also about 4-5 other people giving reviews to that same motherboard on newegg showed the same problem (minus the smoke). Also the smoke I saw was around the south bridge area if this helps, which was ironically right at the end or near the end of my graphics card.    
    My specs:
    Case: HAF 932 blue
    PSU: TX650
    mobo: P67A-GD65
    Ram: G.Skill RipJaws X 4 GB (2 +2)
    graphics: GTX 460 hawk

    Quote from: Snake_X on 13-March-11, 21:27:29
    Also the smoke I saw was around the south bridge area if this helps, which was ironically right at the end or near the end of my graphics card.
    Smoke... Never a good sign!
    Is there any visible damage to the component that you might have spotted during the time it smoked?
    How many times did you attempt to restart the PC after the reboot?
    Did you have any BIOS details that appeared on the screen during the 7 sec?
    Try to remove the MB carefully and check to see if you haven't maybe lost a screw underneath the MB whilst putting it back!
    Quote from: Snake_X
    no trust me, I had this thing working up until i did this, and then I didn't even take any of the cables out of their m-connectors and I even took a some pics of how it was arranged before i did it and referenced them when I re-did it.
    Quote from: Snake_X
    That's what someone told me what might have happened during the time when my 8 pin was unplugged, it might have overloaded a component?
    This is contradictory!
    Did you or did you not remove any wires?

  • Anyone else getting a loop between setup and "connect to iTunes"?

    My iPad Air syncs with iTunes just fine, or so it seems, but the iPad doesn't know it and keeps trying to have me start the setup again. Anyone else?

    Silly me. But, on some level, what were the human interface designers thinking?
    After synching the new iPad, I was delivered to the same screen that greeted me when I first turned it on, leaving me to believe that nothing had happened. When presented with the possibility of setting up the iPad as a new device, I passed on that one, expecting that everything I'd added would be erased, so I never chose that option. Would it trouble the HID folks to deliver you to a screen that tells you where you've been and what you've done so far and gives you options of where to go? Where's Tog when we need him?
    But it's just as much my fault for thinking that because I synched my iPad that I wasn't setting up a new iPad. I think.
    Two calls to Apple Care resolved the issue. Over an hour on the phone.

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

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

  • 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

  • How to connect macbook to smart tv

    I have a 2008 macbook and want to connect iT to my Samsung smart tv. I have bought a minidisplayport to HDMI adapter and get a gold video signal in my tv, bit no. sound. Does anyone know how to get. this right?

  • NOTES SYNCING NO LONGER AN OPTION??

    I am really baffled guys - pleasssse help... I use notes regularly on iPhone 3G (iOS4.1) and on my Mac Mail and sync via MobileMe... The option for syncing Notes on the iPhone has now disappeared - ie, when you go into Mail, Calendar and Contacts Set

  • Can't add attachments in new messages in Mail 2.1.3

    I am trying to help someone with a problem they are having with Mail. No matter what method they use it will not allow attachments to be added to new messages. This is on an Aluminium Intel iMac running OS 10.4.11 and Mail 2.1.3 We have tried the fol

  • How to Update&Delete a field in a record of tablecontrol in screens

    Hi,       I have one requirement in table control of Modulepool Programming. I want 2 put 2 pushbuttons as "Delete","Update" in Tablecontrol Screen.when ever i select a record that time i want 2 delete that and i have 2 update particular value on tab

  • Duplicate IN parameters for PreparedStatement

    I have a prepared statement like "SELECT a FROM b WHERE c =? UNION SELECT d FROM e WHERE f =?" In this case I will always want to both parameters to be the same. My code currently has two lines:- preparedStatement.setString(1, value); preparedStateme