Z68A-GD65 (G3) not always finding ocz vertex 3

Me and a friend just bought identical setups, among them was the Z68A-GD65 (G3) motherboard and OCZ Vertex 3 120GB SSD. Both of us get some random crashes and sometimes when trying to boot the computer the SSD does not show up in BIOS (therefore can't boot from SSD). This also happens after a random crash. This usually gets temporarily fixed if you do a hard reboot. However it is very annoying when the computer freezes randomly (can be days between freezes). When BIOS cant' find the SSD it takes a longer time to show the mobo splash screen thingy.
It is noteworthy that when doing a "hard reboot" it sometimes takes the computer about 5 seconds to startup after pressing the power button.
Anyone got an idea how to fix this?
I don't really know how i would go about solving this as it works most of the time so i don't want to fiddle with things i don't completely understand.
System spec:
CPU: i7 2600K, 3.4GHz
Motherboard: MSI Z68A-GD65 (G3), v 23.1
RAM: 4xCorsair Vengeance Low Profile 4GB DDR3 PC-12800 1600MHz (16GB total)
GPU: Sapphire HD6950 1GB
SSD: OCZ Vertex 3 120GB
OS: Windows 7 Ultimate
PSU: 650W Corsair

Quote from: Henry on 17-October-11, 06:59:47
Check with OCZ for the latest firmware update and see it that fixes your problem.
Had to install Linux for that and had alot of trouble, but after some hours i finally updated the firmware.
We will see if it ever happens again.

Similar Messages

  • Z68A-GD65 (G3) not detecting discrete video

    Yesterday I picked up the following:
    mobo: msi Z68A-GD65(G3)
    cpu: i7 2600k
    ram: gskill ripjaws x 2133 mhz
    I put my video card that was working just fine in my old system (ati hd 6870) and I cannot get a picture out of it on this new setup. I tried out of the box to just hook up the dvi to the card and didn't get a signal, I went into the bios and tried disabled virtu with the initiate video on peg and that failed, I've tried virtu -d mode as well. The fan is spinning on my gpu. I installed windows on integrated, windows doesn't recognize the card. I tried to install virtu software, which says I don't have a discrete video card. It's essentially viewed as just not there.
    Any help would be very appreciated.

    Quote from: SonDa5 on 07-November-11, 23:28:23
    Does the BIOS have any options for Discrete video out vs. CPU video out?  Try the DVI/VGA outputs from the MB?
    I just got this MB and haven't had time to set it up.  I hope I don't have this problem.
    It has the option to, but its not detecting that it's in the slot at all. The onboard/onprocessor video works fine.
    Quote
    This is not just an MSI problem; if you do a search on the web for Z68 and no video out; you will find other motherboards from other companies are having the same issue.  For some people they work just fine and for others they don't.  From what I've read; some have fixed this problem by pulling the battery and doing a bios reset and others this has not worked.  There is some speculation by some; that for some reason the bios is not seeing that there is a graphics card installed in the PCI-e slots and because of this is not turning off the onboard video.  While other people think that it is a problem with the PCI-e slots themselves. 
    The general idea is that the board gives you an option for which video output to 'primary' - it uses the primary if it's found, and falls back to secondary if not. Everything powers up and fans spin, etc. It's quite annoying. -_-' lol. I'll need to try pulling the mobo battery. Still looking for a fix. Planning to call MSI tomorrow.

  • Mac Mini (Late 2014) not recognizing SSD OCZ Vertex 2

    Hello community,
    After days of tests and readings, I turn to you to seek for advice.
    Here is my problem:
    I am trying to upgrade a new Mac Mini (Late 2014 model) from it's original mechanical HDD to a Vertex 2 SSD I have been using for a few years with no problems to report, great product.
    First 1 cloned my HDD onto the Vertex 2 SSD using SuperDuper, all went well.
    I then switched disks and set the SSD in the SATA III slot inside the Mac Mini and reboot... the disk would boot, the recovery system and the disk utility would not see the disk (or it would see it just long enough to try to make a disk verification and then would disappear).
    Here is what I have already tried:
    - Boot from Linux LiveCD, I can see the Vertex SSD, I can see all it's file and browse them
    - Reformat the disk, in HFS+ with GUID partition table
    - Clean PRAM
    - Perform a Hardware Check - all good
    - Boot from the original HDD connected through a SATA-to-USB adapter - all good, i can boot the system, but i don't see the SSD drive (or only for a moment then as soon as i try some action on it (like a disk verification) it stalls and then disappears)
    - Try to OCZ toolbox to make a security erase and start fresh. I had here a major issue, the OCZ toolbox would not start, it froze after a lot of complaints a "Scanning for hard disk partitions and creating /etc/fstab" and wouldn't move.
    - Dissassembled the Mac Mini, removed the SSD, put it in a Macbook Pro, use OCZ Toolbox on it, this time, it loaded perfectly, identified the disk, i did a firmware update to the latest (1.37) and performed a security erase. All went perfectly. For verificiation I rebooted in recovery mode from the Macbook with the SSD and formatted properly the disk using the Apple Disk Utility (GUIP partition table+ HFS+ partition) and the system neatly identified it as a good host for system install. Then i removed the Vertex 2 SSD from the Macbook pro, put it back in the Mac Mini (reassembled it - god, that's a big pain !) and boot it again in recovery, only to see... nothing, the disk is still not recognized by the system.
    Voilà... now I'm out of idea, It could be some low level hardware incompatibility, or anything else, i read about TRIM and Yosemite sometime not behaving well, about SATA II and SATA III compatibility problems, but so far, nothing clear.
    I therefore welcome in anticipation your knowledge and hope we can figure this out. For the sake of extending the reach, I will also post this on Anandtech and Apple support forums.

    Well, thank you tbirdvet, but the problem was actually an incompatibility at the controller level.
    To quote the OCZ support :
    The issue is incompatibility between the older SandForce 1222 controller used in the Vertex 2 and the newer Intel Haswell platform used in the Late 2014 Mac Mini.  The incompatibility started with the Intel 8 and now 9 series chipsets and spans across all products that used the controller regardless of manufacturer.  It is expected behavior to be able to connect the Vertex 2 then clone to it, but if you try and cold boot to it the detection will fail.  Unfortunately, the Vertex 2 and the controller it utilized are long EOL and never received a firmware update (if that was even possible) to adjust for the release of these new chipsets.
    So I can stop looking around it simply wont boot, ever. Product being End Of Support, no new firmware will ever fix this.
    So I guess, i'll have to look another SSD.

  • Z68a-gd65 (g3) Not Gen3 pci? (with Radeon R9 280x)

    Hi all.
    Just got my AMD Radeon R9 280x installed. I have MSI Z68A GS65 (G3) motherboard with the latest BIOS ver.
    Doing a check in Catalyst Control Center -> Information -> Hardware the Grapics Bus Capability report PCI Express 2.0 x16
    In bios the PCI 3.0 setting is set to auto.
    Is this a AMD CCC info bug, I am realy running PCI 3.0? Is there another way I can check if the Grapich card is running on PCI 3.0 or PCI 2.0?
    Regards

    Quote from: Metamsi on 01-November-13, 17:06:01
    Intel® Core i7-2600K Processor
    I am starting to suspect that I need a Ivy Bridge Processor to be able to run PCI 3.0, like the i7-3770K.
    That's right.
    i7-2600K
    http://ark.intel.com/products/52214
    PCI Express Revision : 2.0
    i7-3770K
    http://ark.intel.com/products/65523
    PCI Express Revision : 3.0

  • Z68A-GD65 (B3) & Vertex 3 MI Edition: random crashes (no minidump)

    I'm kinda pulling my hair out here, so i hope someone can shine some light on my issues.
    I've been trying to update the BIOS for the Z68A-GD65 (B3) board, but i can't seem to get it to work because of an error. I've used the HQ USB Flashing Tool to update it, but every time i boot from the USB stick and try to flash, it results in an error message saying that BIOS corruption has been detected  
    I wanna update the BIOS because i'm having lockup/freeze issues, which i thought were related to my SSD drive (OZC Vertex 3 MI Edition). But since RMA sent me a new SSD 3 days ago, and this 1 is giving me the same error/BSOD (without Minidump creation, so no idea what error that is) i'm starting to think something else is wrong. RAM is tested with memtest and passes fine.
    Any thoughts on how to update my BIOS? FIXED!
    System Specs
    MSI Z68A-GD65 (B3) with BIOS v22.4, i7-2600k, Windows 7 Enterprise x64
    OZC Vertex 3 MI Edition 120GB (VTX3MI-25SAT3-120G)
    Kingston ValueRAM 2x4GB (KVR1333D3N9K2/8G) + Kingston ValueRAM 2x2GB (KVR1333D3N9K2/4G)
    LG BH10LS30 BD-writer
    BeQuiet DarkPower 450W powersupply
    no overclocks.
    The crashes happen randomly, but not very often. For example the system has been running for 2 days now, before i JUST noticed the first BSOD. For some strange reason there isn't a Minidump created, so i can't check what's going on (minidump (Kernel size) & pagefile both enabled). In the last week the system has 'crashed' for about 4 times and since every time that happened (mostly during nights) i was seeing a black screen with the message: No boot device detected. Insert boot device and restart system (or something like that).
    When i checked my SSD, i was showing a green & red light on the back. Hard reboot seems to fix everything, red light goes away and the system runs normally again. Since i thought the BSODs were related to my SSD, it's been sent for RMA, and i received a new one 3 days ago, only today.... i had another crash :(
    What did i do/try/test?
    - Ran memtest for a night -> no errors
    - Updated FW of Vertex 3 to latest
    - Did a clean windows install
    - Updated motherboard BIOS (just did that today)
    - RAM settings (fixed): 1066MHz, 7-7-7-20, 1.55V, spread spectrum disabled (i know these settings fixed problems with my P55-GD65 board)
    I hope someone recognizes this issue, or has any thoughts on how to figure out what's going on. Off course it's possible that i've got another faulty SSD, but i think the changes on that (after RMA the first 1) have been dramatically reduced...

    Quote from: Bernhard on 11-September-11, 22:19:23
    The first thing I would suggest is to test your system with only one of those Kingston RAM kits installed. i.e. only use the 2 X 2 kit and test or only the 2 X 4 kit.
    Mixing of mem sticks on the Sandy Bridge platform is not a good idea and can lead to unexplained and inconsistent errors, even if its just the RAM amount that differs on the modules.
    If you haven't tested the RAM in isolation, then do that. You may even want to test with only one single stick installed first.
    After only installing the targeted kit/module do a CMOS clear and start testing again. >>Clear CMOS Guide<<
    I've test a single bank of RAM, a dual-kit of RAM and all 4 banks filles. It has been running at least 20 passes of test 5 & 7 of Memtest, without any errors. I think i can assume my RAM is a OK after this testrun.
    Quote from: louisville slugger on 11-September-11, 23:17:04
    When you flashed the SSD to the latest firmware was hotplugging disabled or enabled in the BIOS? The staff over on the OCZ forums thinks the drive will act like an external drive if it was flashed to the latest firmware while hotplugging was enabled. Does your machine freeze, BSOD, reboot and then say "insert boot device"? (Bugcheck 0x000000F4) OCZ has mentioned a new firmware might be in the works and could be available for download in the next few weeks. One of the staff members mentioned a potential fix (for members using Intel chipsets) in the meantime which may or may not work.
    http://www.ocztechnologyforum.com/forum/showthread.php?93919-All-you-guys-with-Intel-chipsets-and-BSOD-here-is-something-you-can-try...it-may-or-may-not-work-it-will-do-no-harm-though
    I am testing it out right now. Originally I had reset CMOS, re-flashed the drive with hotplugging disabled and AHCI set in the BIOS, secure erased the drive using the Linux bootable .iso, re-installed windows, installed all the drivers, but my machine would still experience occasional BSODs. A few days ago tried the steps in that thread up to the  "If you want to go a step further than this you can try the following...ONLY do this after you have done the steps above” line.
    I haven't had a BSOD since **knocks on wood**.
    When i upgraded this desktop, i was running an Vertex 2 (BIOS set to hot swap & AHCI enabled), and since the Vertex 3 can't update FW when it's being used for OS driver, hot swap was enabled while i flashed it. What you're talking about REALLY sounds like my problem. Since the freezes/crashes mostly occured during nights i wasn't able to see what the source of the issue was. Today was the first time i noticed a BSOD (for a second...) before it rebooted, and then (indeed!) it showed me the screen telling me there wasn't a bootdevice availabe. I'll go check out that thread you refered to and read up on that. BIG TNX for the link

  • Z68A-GD65 (B3) Intel SRT will not work.

    I have been trying to get Intel SRT to operate for a few days now and have run out of ideas.
    I have read through Intel's instructions and instructions on any number of hardware websites (such as Anandtech, HardOCP, etc) and have followed these instruction to the letter with no luck.
    I have the Z68A-GD65 (B3) with EFI/BIOS # 22.4 (latest official), a OCZ Agility3 60 GB SSD I am trying to use as a cache for My OS drive; a 500GB Seagate 7200.12 drive.
    The process I went through (a few times now) is as follows:
    -I have SATA set to RAID in the BIOS
    -Leave SSD unplugged
    -Installed Win7 on the Seagate
    -Installed all drivers for the MB and other hardware
    -Installed Intel RST application (various versions, but currently have 10.5.0.1027 installed as it appeared to be the one that others online had the most luck with)
    -shut computer down, plug in the OCZ SSD
    -boot to windows and open Intel RST app
    What invariably happens is that there is no "Accelerate" button in the app (this is RST's way of activating SRT [ugh- acronym overload]).
    If I install an additional HDD the "Create" button shows up to set up a new RAID volume, but even this won't show up with just the OCZ SSD and OS HDD installed. The SSD is always recognized by RST, but it won't give me the option to "Accelerate".
    This is one of the features that made me buy a Z68 based board and not being able to get it working is driving me nuts (and wasting a lot of time as well).

    Yup! You are 100% correct. I had it wrong. That's what I get for speed reading the articles about it. Here are some thoughts, possible the SSD is faulty or a firmware update needed? Any compatibility issues noted at the OCZ Website or forums? Any insight as to initialization or compatibility problems at the Intel Website or forum? It might also not be a bad idea to get MSI Tech Support involved in this as well. They will want to be aware of any hardware incompatibilities so it can be looked at & a resolution reached quickly at their end. http://support.msi.com/   

  • OCZ Vertex 3 not showing up on Disk Utility (2011 17" Macbook Pro)

    I have a problem with my 120GB Vertex 3 installed on my 2011 Macbook Pro. It wouldn't boot after the apple logo after using it for a while...I tried starting up my mac with safe mode, commad+c,command+v,and command+option+p+r but it didn't help.
    So I took out the vertex form my mac and then replaced it with the original toshiba hard drive, opened disk utility but the vertex didn't even show up.
    before that, I also tried booting with the mac os x disk (vertex inside the mbp) and opened disk utility from it but I had the same result.

    Chris,
    I had a similar problem. This was with a brand new Vertex 3 that I tried to install into the system. It would not be recognized by Disk Utility or Time Machine Restore from the OSX 10.6 boot CD.
    Here is my solution to the problem:
    1) I put the original 250GB HDD back into the system. I used Disk Utility to format it to only use the first 120GB of the disk, leaving the rest blank (OSX reserves a 200MB partition, so the exact size of the system partition is 119.69 GB (119,690,170,368 bytes)). You can always make it 1-2 GB smaller, to be safe.
    2) I used Time Machine to restore the system onto the original HDD.
    3) I placed the OCZ Vertex 3 into an external USB enclosure. I then re-booted the system into Gparted using a Linux live CD (http://gparted.sourceforge.net/)
    4) I used the Linux command dd (http://enwikipedia.org/wiki/Dd_(Unix)) to make a byte-for-byte copy of the two disks. dd will stop when the Vertex 3 becomes full, so you need be absolutely sure that your partition is small enough.
    Here is the dd syntax: if stands for input file (source disk), of stands for output file (target disk). It takes a really long time, and has no indication of its progress. You can tell it is working by seeing the external enclosure LED blink.
    >dd if=/dev/sda of=/dev/sdb
    dd is a standard UNIX command and comes with OSX too. You could always try this from the Terminal application from the OSX boot CD. I did it using Linux, because I am slightly more famailiar with Linux over Unix command line.
    The internal (standard HDD) hard drive should be mounted on sda. The Vertex 3 (inside the USB enclosure) might be sdb, but if there are other disks present it might not be. Use dd with extreme caution! I highly suggest that you detach all other disks (such as the Time Machine disk) before attempting this. If you set of= to the wrong disk, it will completely wipe it out.
    5) Swap drives. Computer boots, everything works!
    6) (Optional)... if you made the partition smaller than the Vertex 3, you can try to resize it to use the full capacity of the disk with Disk Utility from within OSX.
    Let me know if this was helpful. Send me a reply or PM if you need any more detailed instructions. I would be glad to help.
    -Sam

  • USB Drives not always showing Finder

    I currently have two USB Drives connected through a powered hub and they do not always show in the Finder window. Also when I pug in a USB memory stick it does the same thing.
    I am new to Mac, I love it but this really bugs me. is there a setting somewhere, what is happening? If I disconnect then re-plug in the memory stick it shows up. What is really funny, that doing this also causes the missing USB drives to show up......

    I tried that, but still no go with a thumbdrive. I can go to "Computer", and the USB drive shows up under that. All my other USB external HDs, my iDisk, and even FireWire drives show up on the left pane of the finder, just not the USB stick.
    Any ideas?

  • Files do not always show in finder when accessing server

    When I access our server(PC) files do not always show up in the finder. Sometimes it shows and sometimes it does not. I have to go back and start over. I recently updated to Snow when this problem started happening. Example. If i'm in illustrator and want to open a file on the server I will go to server than to the folder on the server. once the folder is open there is not any files showing. If I go back and start over they will be there. Sometimes I have to do this several time to show files. There are multiple type of files in the folders and none of them show. Any suggestions would be greatly appreciated.

    When you are viewing the tracks on the hard disc, did you then click on "Import CD"?  This is needed to initiate the importing process that will add the tracks to your library.

  • Always finding problem "server not find in safari"

    Always finding problem "server not find in safari" for any redirection or even opening some sites through google.. Hv to delete cookies an still some times work some times no..pls do not give me ******** answer like apple for restarting wifi..its a serious issue and i think millions of users are finding this problem.. Apple should be forced to fix this issue through an update..or should come out with a  or react solution..

    It is not a broad issue, I have absolutely no problems using Safari and ios7.1 on many ipads.
    Verify that you have good DNS entries, that can be a major cause of this type of message.

  • Networked Macs Not Always Showing Up In Network In Finder - On One Mac

    The problem is that awake and running networked macs do not always show up in Network on the Finder. Sometimes they do and sometimes they do not. The problem happens fequently on one machine. Very similar questions have been posted on this. I suspect many are dancing around the same issue. I am hoping to get to the bottom of this.
    All the OS X machines are running 10.4.9. Two are networked by Airport. The Airport and the problem iMac, an older G3, are wired to a LAN. On the LAN sits a PPC 7200 running OS9 IpNetRouter serving up IP addresses for all the connected devices, including printers. IpNetRouter also provides an internet connection out through a second ethernet card. The PPC 7200 drive is always reliably available for connecting to in the Finder.
    Each of the OS X machines are set for Personal File Sharing only, with Firewall running, and without Stealth Mode enabled.
    The problem is noticed on the wired Mac. Perhaps that is the key to this. The problem is not two way. The Finder on the wireless Macs shows the wired Mac in Network when the wired Mac is not showing the wireless Mac. Sometimes only one of the wireless Macs shows on the wired Mac. When that happens it is always the wireless eMac instead of the wireless Intel Mac.
    When this problem occurs, it is always possible to connect to the "missing" wireless Macs by using their local IP address reported by IpNetRouter. It is not possible to do the same using the computer name of the Mac that should be visible in Network or by using its DHCP client ID.

    No Macs are sleeping, but they might have been in the past. They don't show up when they are sleeping. These machines are often on for days. All are updated on a regular basis, including in the past two days.

  • Z68A-GD65 (G3) - Motherboard's not booting with a PCI Soundblaster Audigy 2.

    Hi everybody, as thread title says I've got some trouble with my motherboard, Z68A-GD65 (G3) and a Soundblaster Audigy 2 ZS that a friend of mine gave to me. I gave a try in both PCI slots avaiable on the motherboard but as i place the SB in PCI slot 1 or PCI slot 2 the system do not boot up. As soon as i take it off, the system works great as usual.
    Of course i disabled the onboard audio to avoid resource sharing between the two. This is the only hint i had reading around on MSI trobleshootin.
    The only other parameter i can change regarding PCI is latency in the BIOS. I found to be 32 cycle by default and i did not modified it.
    The Audigy works flawlessly on another Intel P45 Board from a different brand and with the same video card in the PCI-E Slot. Of course Cpu end Ram ar different. When i did the try i disconnected everything unnecessary for the boot process.
    Any hint would be very appreciated.
    Thanks, Daniele.

    As i read on manual, the PCI setting into the bios is not something can cause instability:
    PCI Subsystem Settings
    Press <Enter> to enter the sub-menu.
    PCI Latency Timer
    This item controls how long each PCI device can hold the bus before another
    takes over. When set to higher values, every PCI device can conduct transactions
    for a longer time and thus improve the effective PCI bandwidth. For better PCI
    performance, you should set the item to higher values.

  • OCZ Vertex 2 in Mac Pro 2009

    Although this has already been discussed a few times I'd like to add my experience with the OCZ Vertex SSD over 8 months. Since I got mostly shoulder shrugs everywhere else, I hope a competent tech head will stumble upon this and point me in the right direction.
    The initial install was a doddle and this drive is insanely fast as a main system drive. I heard about the issues with SSDs wearing out over time without TRIM etc but never fully understood it. I'm not a tech head. A couple of days ago my Mac started to behave strangely with complete freezes to the point that I had to do hard reboots (power button). One out of two times OSX would boot back normally but then freeze completely after about 10-15 min. of use. The other times it wouldn't even find the startup drive (blank screen and folder with ?). So logically the SSD must be the culprit. I was lucky to have made a time machine backup and restore OSX to a HD. The backup runs fine, so there is no issue with OSX itself.
    The OCZ is on firmware 1.2. There are other users having the same problem and apparently it has something to do with the fact that OCZ drives don't handle power functions too well on a Mac, like sleep, hibernation etc. For most of those users, a firmware upgrade did not solve the problem. I followed all the other hints, disable sleep, downloaded TRIM for non-Apple SSDs etc but to no avail.
    Before I start the RMA process (which OCZ might refuse?), does it make sense to upgrade the firmware on a device that was running fine for several months? I mean, it can't be the firmware if it was always working before, can it? I actually suspect the SSD to have become bad over time. However I think I'm still far off having had enough read/write cycles to wear out the drive according to the specs floating about.
    I'm inclined to demand a replacement drive, a brand new one, but on the other hand I've lost all confidence in SSDs. Especially as the main system drive. It's very irritating when the whole system freezes in the middle of a project. How long are those drives supposed to last, REALLY honestly?? I simply can't believe the "up to" 20 years myth.
    Cheers for any hint.

    TRIM Enabler support thread:
    http://forums.macrumors.com/showthread.php&t=1125400
    http://www.groths.org/?p=308
    I don't know that model but I would update the firmware.
    I'd also let the SF controller do its think and not use TE unless you feel it is safe and the current version. That may not have always been true. SF Background GC should be enough. And wipe/reinstall if not.
    As for sleep etc, hibernation is a laptop feature. And even PC BIOS have had to be updated (two PCs, Intel and Gigabyte) and until then it was an issue at times.
    OWC uses SF and does not recommend TRIM for OS X.
    So, what I would say is this:
    When your computer has a hard freeze, it needs you to act/react accordingly:
    Safe Boot at minimum to clean up and attempt to repair its directory.
    Not sure why or what but that can happen to anyone almost and may not even be SSD related.
    I'd keep the drive, check back OCZ and firmware, talk to others on the MacRumors and Groths.
    note: I reformat drives regularly, couple times a year, replace system drive also, and it is the amount of writes and I/O your SSD has to handle, not years. Even DVDs don't last two decades.

  • Z68A-GD65 G3 Reboot Loop

    I'm putting together a new build and I've run into a reboot loop.  When I attempt to start it up, it runs for about 5 seconds, then turns off.  This goes on in an endless loop.  It never gets to POST.  The 6 LEDs light up and the BIOS ones don't (so this appear normal).  I have never gotten a successful bootup.
    My setup:
    Motherboard: Z68A-GD65 G3
    CPU: Intel Core i5, i5-2500K
    Memory: Kingston HyperX (4x4GB DDR3 - 1600 CL9 240)
    Power Supply: OCZ ZX Series 850W
    CPU Cooling: Xigmatek Gaia SD1283
    I am not listing anything else, because I am not getting far enough for it to matter.
    I am running with only the above pieces connected to rule out all but the essentials.
    I've inspected the CPU and slot.  Both appear fine.
    I've cleared the CMOS using the button on the I/O panel and removing the battery.
    I've subbed out the Power Supply.
    Only the 8 pin CPU and 24 pin motherboard connections are made.
    I've tried various things with the RAM.  All 4, just 2, and just 1 (in the DIMM1 slot).  Most testing was done with just 1.  I have tried all 4 in the DIMM1 slot.
    I've removed it from the case and booted it up in the cardboard box (nonconducting) it came in, to rule out a short.
    I've inspected the motherboard carefully, no obvious issues.
    I've checked that the CPU cooler is making good contact with the CPU.
    I've verified that the OC button is not active, although I've tried that too.
    I've read through the forums, but have not been able to find a solution that works.
    Please help.  Thanks.

    I had this very same problem with a Biostar T-POWER I55 2 years ago, to cut a story short the retailer and the distributor who handled Biostar RMA's rejected the RMA.
    I spoke to Trading Standards/Consumer Direct as I read in the Sales Act that in the first 6 months of a purchase if the damage cannot be proven to be done by the end user then a warranty claim still exists.
    Finally after stating this & quoting the Trading Standards Reference number to the retailer, I got a call from them saying they would offer a refurbished motherboard worth £113, my original motherboard cost £138 so I refused this & asked if they would agree if I could purchase a brand new alternative for (£75ish) around 50% of its purchase value to which after another day they rang back & agreed.
    You are not the first and won't be the last this has happend too, One manufacturer will cover for warranty in these circumstances because I asked them.
    I suppose you could get a 2 year warranty via Amazon, small expense for peace of mind which covers you for Accidental damage as well as mechanical failure, quite good if the  motherboard pins snap off the motherboard.
    Click >> SquareTrade 2-Year Warranty Plus Accident Protection (£150-175 Items) £29.99
    The above only complys to people in the UK, other countrys have different sales of goods act laws.

  • Z68A-GD65 Hangs in UEFI *Help wanted*

    Hi there! im new to this forum.
    I just bought myself an Z68A-GD65, and first thing i noticed was the bios revision was really old, so i updated to the latest version.
    Now i wanted to try some overclocking, i went into bios and upped the multiplier and the voltage, pressed save and exit and UEFI froze, however, the temperatures were still monitoring and updating on the side?? but i couldnt do anything. Had to shut down PC on the button.
    I went into UEFI again after reset and i see the changes did not apply, so i load defaults, press save and exit, and UEFI froze again, now i cannot save and exit at all.
    What should i do? reflash ? something is obviously wrong....
    Help plz
    EDIT: It seems the problem was the new N7 bios, i flashed to the older N4 and now it works just fine.
    The motheboard came with N2.

    Quote from: HU16E on 01-May-12, 19:16:09
    What does the DRAM V. 'Read Only' voltage read? Might try to set it manually to 1.521v and see if that helps. To really be of help, a full listing of all your systems components will be helpful in troubleshooting. It would also make it a bit easier if the settings you have are listed too. The sub section 'CPU Features' has some settings that can cause problems if not set right as well as in the Eco Section. EuP 2013 should be disabled for example.
    I always changed the DRAM Voltage to 1.652 volts, and set the speed with XMP (1600mhz).
    My system specs:
    Intel i5 2500k
    8gb Kingston HyperX 1600mhz CL9 1.65v
    MSI Z68A-GD65 (now flashed to the latest bios again)
    Nvidia Geforce GTX 470
    Corsair VX550W powersupply.
    Creative X-FI xtreme gamer soundcard.
    D-link DWA-556 xtreme wireless network card.
    Razer Naga molten edition mouse.
    Logitech Ultra X flat keyboard.
    I am trying to troubleshoot this problem now, step by step, im changing 1 thing in UEFI, save and exit, booting into windows, rebooting and changing 1 thing again.
    Its gonna take some time, but hopefully i can find whats causing the UEFI freeze.
    Here is the steps i took immidietly before:
    1. Changed the boot order to SSD first, enabled hot swap on sata port1(recommended by MSI according to the site), rest disabled.
    2. Changed to AHCI
    3. Disabled onboard LAN and External SATA 6gb/s
    4. Changed to XMP and manually set DRAM voltage to 1.652v.
    5. Saved and exited.
    6. Went into windows, rebooted, changed 1 random setting (didnt matter what) and UEFI freeze upon pressing "Save and Exit"
    Clear CMOS > Solved problem, i now can change the settings again, until i find whatever is it from that list that is causing the UEFI to freeze.
    Question: what is Eco mode and standard mode? im always changing the settings in Standard mode.
    EDIT:  The problem seems to be related to the "Advanced Settings" section in the UEFI, which includes the settings : to disabling the onboard LAN + external sata 6gb/s and changing the boot order and enabling hot swap.
    The problem is in other words related to the onboard lan disable, external sata 6gb/s, changing boot order or enabling hot swap on sata port1. So i left those 4 things at default and it appears its working now since i have now rebooted and saved & exited bios many times since i decided to narrow this problem down.
    I have now successfully done the following to help out with the OC:
    Disabled:  EIST, Speedstep, Turbo boost, EuP2013, C-state, Overspeed protection, C1E Support, Power technology, Spread Sectrum.
    Enabled: Internal PLL Overvolt and XMP profile.
    Manually: Set memory voltage to 1.652v, CPU voltage to 1.325v (doin OCCT linpack right now, seems stable so far)
    Using BCLK: 100.2 (10010 in bios) to compensate up from 99.8mhz.
    Will get back soon.
    EDIT2: BSOD after 50mins OCCT at 4.5ghz 1.325v, backed off the BCLK increase from 100.2 to default 99.8, and upped volts to 1.330v, if its stable, im backing off volts to 1.325 again and running again.
    Also tried to disable onboard LAN, disable serial port, UEFI still functions properly. It seems the problem is caused by enabling Hot Swap.
    Question: what should i put PLL volt on?

Maybe you are looking for