970a g43 dont recognize ocz vertex 3 90gb ssd

hello everyone, having problems connecting ocz vertex3 90gb ssd on my 970ag43 motherboard, my boar dont recognize it otherwise another motherboard like h61m-p31 does it

Get into your bios it's likely you need to change the HDD from IDE to AHCI. By default the G46 and G43 have IDE enabled not AHCI.

Similar Messages

  • Hello, i just installed a vertex 2e 90gb ssd in my macbook pro 13" (8.1 early 2011). But when i do a disk speed test i only get 125 mb/s write speed and 146 mb/s read speed.

    Hello, i just installed a vertex 2e 90gb ssd in my macbook pro 13" (8.1 early 2011). But when i do a disk speed test i only get 125 mb/s write speed and 146 mb/s read speed. Thats under 50% of what i should get. The disk have firmware 1.35 and 3 gb/s linkspeed when i check in systemreport.
    Anyone know why i get so low speed from my ssd?

    Speak to the manufacturer. They did the bench tests.

  • OCZ Vertex 4 512GB SSD on W520 guaranteed BSOD--BEWARE!

    Just wanted to make a quick post to let prospective W520 upgraders know about Blue Screen of Death (BSOD) problems that occurrs when using a the 512GB Vertex 4.  This is an issue that affects more than just Lenovos (Alienware in particular). When resuming from sleep, the W520 will BSOD 100% of the time.  I have posted on the OCX forums along with others.  I went ahead and returned the Vertex 4 after I bought it from Amazon, since no amount of troubleshooting would fix it.  I am replacing it with the Samsung 512GB since there are many people on the forum who have had success with that. 
    Bottom line: don't buy a Vertex 4 until Lenovo or OCZ come out with a fix, unless you don't mind testing manufacturer's stuff for free!
    W520 CTO BIOS rev 1.37. Core i7-2760QM, 32GB PC3-10600, NVidia Quadro 1000M, Samsung 830 512GB, SanDisk pSSD-S2 32GB, x64 tri-boot: Win2k8R2, Fedora 17, Ubuntu 12.04

    I would go with Intel for reliability:
    http://www.tomshardware.com/reviews/ssd-reliability-failure-rate,2923-9.html
    My next machine, which will be 17" Ivy Bridge/Kepler w/120Hz 3D display, will have dual Intel SSDs in RAID0, with probably an mSATA SSD for backup. And if you keep data/docs on a separate partition from the system partition, then you seldom need to backup the system (I dump my data/docs to a NAS each day, which itself is backed up).
    The problem with less reliable SSDs is that SSDs tend to fail completely and with no warning, unlike hard drives. So, if avoiding downtime is important to you, then you want one of the more reliable SSDs. Overall, the more reliable SSDs (the orange line & dotted line in the chart, which should include the Intel 520-series SSDs) now appear to be more reliable than hard drives, under heavy use, according to that article.
    But, as with any computer-related product nowadays, I would make sure that users say that the current firmware/drivers are stable with your computer, before buying. 

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

  • Results from the OCZ Vertex 2 SSD

    Hey All,
    I just installed an OCZ Vertex 2 120GB SSD. At first I had some lag (about a minute) before the Apple logo would appear at the boot screen. I thought this might be the drive being unresponsive, but as it turns out a quick SMC reset fixed it.
    I now get a full restart in 37.2 seconds. Cold boot in just under 24 seconds. Photoshop is 5 seconds flat, and wake from sleep is instant. I'm pretty pleased with this upgrade. It definitely put some new life into my MacBook without breaking the bank.
    I have also noticed considerable battery life gain over my WD 7200 scorpion HD that I replaced.
    This is a great upgrade for anyone looking.
    Cheers!
    Message was edited by: eightamrock

    not bad!
    That`s true, the MacBook rock`s once again.
    The Vertex 2 is a graet Drive!
    just for info: with AJA System Test i get 255 MB/s Write and 202 MB/s read speeds.
    i recommend too

  • Very slow write speed in SSD OCZ Vertex II (no Mac edition) in "Lion"

    Hi guys
    I have an iMac mid-2010: i7 2,93/8Gb/ATI HD 5700/1Tb HDD + OSX Lion 10.7.2
    The SO seemed very slow, so I decided to add an SSD... In Apple authorized service center recomended OCZ Vertex II 120 SSD (no Mac Edition)...
    Hardware instalation by Apple´s Service It´s OK, SSD show on Mac information (Spanish)
    Before installing "Lion", I did a speed test, with these results
    My surprise is that the SSD is very slow in writing... Read results speed It´s Ok...
    FW up to update v1.35 (factory default)... And the install "Trim Enabler" because the result It´s the same...
    What do you think is the problem?

    I"m having the same (mostly) problem. Any thoughts?

  • OCZ Vertex 2 fails to fully resume from suspend to RAM

    I have installed an OCZ Vertex 2 60GB SSD in my laptop and I cannot resume normally from S3 using pm-suspend or any other method.  It looks like / isn't remounting, however it does seem that home is remounting. 
    I have flashed the firmware to the latest.  I tested suspend after a base install, with only acpi and hal (pm-utils being a dep for hal) and it failed. 
    Here is fstab, mtab, and fdisk -l.  If any other information is needed let me know. 
    Disk /dev/sda: 60.0 GB, 60022480896 bytes
    255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xb8372fcd
    Device Boot Start End Blocks Id System
    /dev/sda1 2048 206847 102400 83 Linux
    /dev/sda2 206848 21178367 10485760 83 Linux
    /dev/sda3 21178368 117231407 48026520 83 Linux
    proc /proc proc rw,relatime
    sys /sys sysfs rw,relatime
    udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=502347,mode=755
    /dev/disk/by-uuid/fd40337d-ed8a-4e76-be3f-aa09f5558998 / ext4 rw,noatime,barrier=1,data=ordered,discard
    devpts /dev/pts devpts rw 0 0
    shm /dev/shm tmpfs rw,nosuid,nodev 0 0
    /dev/sda3 /home ext4 rw,noatime,discard 0 0
    /dev/sda1 /boot ext2 rw 0 0
    none /tmp tmpfs rw,nosuid,nodev,noatime,size=1000M,mode=1777 0 0
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    devpts /dev/pts devpts defaults 0 0
    shm /dev/shm tmpfs nodev,nosuid 0 0
    #/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
    #/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    #/dev/fd0 /media/fl auto user,noauto 0 0
    UUID=8f046367-0eec-410f-b3b5-0e298e065c5e /home ext4 defaults,noatime,discard 0 1
    UUID=a6f6aa9a-e5d8-4763-ad75-0b0b6c549929 /boot ext2 defaults 0 1
    UUID=fd40337d-ed8a-4e76-be3f-aa09f5558998 / ext4 defaults,noatime,discard 0 1
    none /tmp tmpfs nodev,nosuid,noatime,size=1000M,mode=1777 0 0
    Here are some errors after suspend:
    http://img180.imageshack.us/f/fserror.jpg/
    http://yfrog.com/izfserror2j
    I've also been advised to try enter S1, however I'm not sure how to do that since power states don't seem to work like this anymore (since kernel 2.6):
    #echo 1 > sleep
    I'm very frustrated at this point and I will be extremely gracious for any advice on this problem

    I just successfully suspended to RAM.  I was redirecting the log file to text file to make sure it kept it.....here it is.  I'm going to check it out further to see if a package update fixed it, or if it was simply dumb luck.
    /usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
    Kernel modesetting video driver detected, not using quirks.
    /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
    kernel.acpi_video_flags = 0
    /usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
    Mon Nov 1 19:35:30 CDT 2010: performing suspend
    Initial commandline parameters:
    Thu Nov 4 00:54:33 CDT 2010: Running hooks for suspend.
    Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
    Linux l33tpc 2.6.36-ARCH #1 SMP PREEMPT Sun Oct 31 09:29:11 CET 2010 x86_64 Genuine Intel(R) CPU U7300 @ 1.30GHz GenuineIntel GNU/Linux
    Module Size Used by
    cryptd 6262 0
    aes_x86_64 7412 1
    aes_generic 26170 1 aes_x86_64
    ipv6 281961 14
    ext2 63599 1
    usb_storage 42540 0
    uvcvideo 61404 0
    videodev 64318 1 uvcvideo
    v4l1_compat 15578 2 uvcvideo,videodev
    v4l2_compat_ioctl32 10212 1 videodev
    arc4 1378 2
    ecb 2041 2
    snd_hda_codec_intelhdmi 10645 1
    snd_hda_codec_realtek 275631 1
    i915 320893 2
    snd_seq_dummy 1431 0
    ath9k 79976 0
    snd_seq_oss 28760 0
    joydev 10055 0
    snd_seq_midi_event 5436 1 snd_seq_oss
    snd_hda_intel 22253 0
    snd_seq 50082 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
    snd_seq_device 5297 3 snd_seq_dummy,snd_seq_oss,snd_seq
    uhci_hcd 21926 0
    snd_hda_codec 79192 3 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel
    mac80211 195924 1 ath9k
    drm_kms_helper 25963 1 i915
    snd_pcm_oss 39157 0
    snd_mixer_oss 17106 1 snd_pcm_oss
    ath9k_common 3496 1 ath9k
    snd_hwdep 6110 1 snd_hda_codec
    drm 175314 2 i915,drm_kms_helper
    ath9k_hw 289341 2 ath9k,ath9k_common
    snd_pcm 71921 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
    ath 8822 2 ath9k,ath9k_hw
    ehci_hcd 36860 0
    i2c_algo_bit 4911 1 i915
    asus_laptop 14243 0
    i2c_core 18726 5 videodev,i915,drm_kms_helper,drm,i2c_algo_bit
    sparse_keymap 2563 1 asus_laptop
    snd_timer 19265 2 snd_seq,snd_pcm
    ac 3105 0
    vboxdrv 1740411 0
    battery 10039 0
    cfg80211 142886 3 ath9k,mac80211,ath
    snd 57562 11 snd_hda_codec_realtek,snd_seq_oss,snd_seq,snd_hda_intel,snd_seq_device,snd_pcm_oss,snd_hda_codec,snd_hwdep,snd_mixer_oss,snd_pcm,snd_timer
    atl1c 31532 0
    video 19305 1 i915
    iTCO_wdt 10669 0
    sg 25652 0
    processor 25936 2
    rfkill 15882 2 asus_laptop,cfg80211
    soundcore 5969 1 snd
    psmouse 52592 0
    output 1940 1 video
    iTCO_vendor_support 1801 1 iTCO_wdt
    thermal 12242 0
    button 4834 1 i915
    usbcore 137506 5 usb_storage,uvcvideo,uhci_hcd,ehci_hcd
    evdev 8519 7
    serio_raw 4486 0
    intel_agp 29427 2 i915
    led_class 2331 2 ath9k,asus_laptop
    pcspkr 1819 0
    snd_page_alloc 7249 2 snd_hda_intel,snd_pcm
    ext4 313574 2
    mbcache 5722 2 ext2,ext4
    jbd2 69002 1 ext4
    crc16 1297 1 ext4
    sd_mod 25824 4
    ahci 20353 3
    libahci 17886 1 ahci
    libata 156316 2 ahci,libahci
    scsi_mod 124859 4 usb_storage,sg,sd_mod,libata
    total used free shared buffers cached
    Mem: 4020904 219844 3801060 0 22892 53336
    -/+ buffers/cache: 143616 3877288
    Swap: 0 0 0
    /usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
    /usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
    /usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend:
    /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
    /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend:
    Having NetworkManager put all interaces to sleep...Done.
    /usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
    /usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
    /usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/91wicd suspend suspend:
    /usr/lib/pm-utils/sleep.d/91wicd suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
    /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
    /usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
    Kernel modesetting video driver detected, not using quirks.
    /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
    kernel.acpi_video_flags = 0
    /usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
    Thu Nov 4 00:54:34 CDT 2010: performing suspend
    Thu Nov 4 00:57:50 CDT 2010: Awake.
    Thu Nov 4 00:57:50 CDT 2010: Running hooks for resume
    Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:
    /usr/lib/pm-utils/sleep.d/99video resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:
    /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:
    /usr/lib/pm-utils/sleep.d/95led resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
    /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/91wicd resume suspend:
    /usr/lib/pm-utils/sleep.d/91wicd resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:
    /usr/lib/pm-utils/sleep.d/90clock resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/75modules resume suspend:
    Reloaded unloaded modules.
    /usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend:
    Having NetworkManager wake interfaces back up...Done.
    /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/49bluetooth resume suspend:
    /usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/11netcfg resume suspend:
    /usr/lib/pm-utils/sleep.d/11netcfg resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/01grub resume suspend:
    /usr/lib/pm-utils/sleep.d/01grub resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/00powersave resume suspend:
    /usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/00logging resume suspend:
    /usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
    Thu Nov 4 00:57:52 CDT 2010: Finished.
    It failed again.  I have compared the logs and the last entry is :
    /usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
    Thu Nov 4 01:24:45 CDT 2010: performing suspend
    Last edited by DarksideEE7 (2010-11-04 07:29:06)

  • Freezing issues with MSI 970A-G43 and AMD FX 8320

    Hey all,
    I bought my brother a new system a few days ago, but he has had serious issues with the machine crashing ever since.
    The machine has had a fresh installation of Windows 7, it has all the latest drivers for both motherboard, sound, chipset and video card (Latest VGA driver tested as well as the latest Beta version)
    I thought the problem might be with the VGA card, as the computer would just shut off during 3d Gaming, but it also seems to happen when surfing the internet or doing normal "2d" activities
    What happens is the computer will just seemingly shut off, the LED lights on the front of the case, around the dials, start blinking and the only way to get it back up again, is to turn if off at the power supply unit and then turn it back on again.
    I'll paste in what my brother sent me (As I live in the UK and can't see the machine crashing myself), he said:
    I dunno what the issue is but, last night the comp just shut off in middle of game play on 3 different games, and the lights were flashing, I had to turn complete power off to the power box and back on to restart comp, I kept checking all my temps with speccy and speed fan and nothing seemed high at all, also when it shuts off and I re start it, a lot of my desktop icons move around to different spots,
    Update: crashed a few times on me, once playing euro, once just browsing Internet 5 min after the first one, changed out ram just for shots and giggles and ran euro on ultra for about 5 min and crashed. I dl a gpu monitor gadget, was accurate on temp but said the gpu was 0% but with just Internet would randomly jump to 99% or 40% then back to 0 and would stay and eventually crash
    Spec is:
    AMD FX-8320 3.5GHZ EIGHT CORE
    500GB SATA III 6GB/S 7200RPM 16MB
    COOLERMASTER SEIDON 120M WATER COOLER
    4Gb DDR3 / 1600 MHZ MEMORY
    MSI 970A-G43 AMD 970 CROSSFIRE AM3+ DDR3 USB 3.0 SATA
    CORSAIR 500 WATTS CX500 V2 80 PLUS POWER SUPPLY
    ASUS XONAR DG 5.1 CHANNELS PCI XONAR DG SOUND CARD
    AMD RADEON 7750 2GB PCI-E
    There was a concern I did have when I did search earlier, via a thread on Tomshardware in which a similiar board had issues with the FX8350's wattage going above the stated 125 watts and causing the board to freeze.
    It's a different board/chip, but I wonder if the wattage of the CPU goes above 125W and causes problems on the board? Hmm
    I feel really guilty right now, because I bought this for him as a present, it was $700ish plus shipping etc and it's been nothing but problems ever since.
    I'm going to see what version of Bios he's running when he gets out of bed, but the Live Update software said there were no updates, but I'll have him check manually.
    Another issue I noted, was I sent him some ram before the PC arrived, which was:
    XMS3 — 8GB Dual Channel DDR3 Memory Kit (CMX8GX3M2A1333C9)
    He originally put that ram in with the existing 4gb of ram, so I thought it "Might" be a conflict, due to them having a different Mhz value
    So I had him remove the 4gb stick that came with the PC
    As soon as he entered the bios, it froze and did so twice
    So he removed that ram and put back the original 4gb stick and the bios worked
    No idea if the two are related.

    I hope this doesn't count as necro-ing a thread (last post was in October), but it's the one closest to my situation.
    I have the following setup:
    MSI 970a-g43 motherboard
    AMD FX-6300 cpu
    ATI Radeon HD 4550 graphics card
    4x 2GB RAM sticks
    2x 500 GB 3.5" SATA hard drives
    CoolMax 700W psu
    16x r/rw DVD burner
    cheapo SD and others card reader that fits in the floppy drive bay
    Older PC tower that has a temperature sensor built into it
    I built it around November 15th, and it worked until a couple days ago (December 12th I think), when it started doing the sudden shut-off thing. Same as Adresch described: shuts off, tower light blinks, have to flip the i/o switch off and back on to boot again. I consulted a friend for some suggestions, and he said I should put a water cooler in there, because the stock heatsink that comes with most processors are junk. So I went out and bought a Corsair H55 water cooler and installed that.
    The computer seemed to run for a bit longer before shutting off. I loaded up the BIOS software, SpeedFan, and HWMonitor. SF said the CPU was running average of 48*C, and GPU was averaging 51*C. The CPU's highest was at 61*C and its lowest was 36*C. BIOS software said CPU was at 35*C the whole time. HWMonitor listed the GPU at 51*C, and the CPU at 7*C. These are all very inconsistent with each other as far as I can tell, so I don't know what to make of these readings. Didn't seem to much matter as the computer continued shutting off.
    My options then being replacing the PSU or the motherboard, I decided to replace the power supply, since I was just within the 30 days. Switched for a ThermalTake TR2 700W. Before installing it, I pulled the tower's CPU temperature sensor wire from between the water cooler heatsink and the CPU, just in case. Then I installed the PSU, checked and rechecked all of the connections, and turned it on.
    Nothing.
    I then spent the next two hours rechecking everything, even unplugging everything and putting it back together. Still nothing. The best I could get was a flicker of the tower light and the fans doing a quarter turn before ceasing movement. The red LED on the front of the SD card reader stayed on the entire time, though, so I guess it was getting at least a trickle of power. I also removed everything but the PSU, motherboard, CPU, and one stick of RAM. Still no power. I think the new PSU may have been open box, so I'm returning it today for a different one, and even bumping it up to 850W.
    I'm not sure that will solve my original issue though, so I'll be looking for a heatsink to put on the VRMS as mentioned. Just thought I'd get this down in a relevant thread in case anyone had other thoughts on what could be going on.

  • Is OCZ Vertex Turbo 60GB 2.5" SSD compatible with my Mac Pro, or do I need

    Is OCZ Vertex Turbo 60GB 2.5" SSD compatible with my Mac Pro, or do I need the Vertex Mac Edition?
    I have decided to purchase a SSD to use as a boot drive in the spare optical drive bay.
    There are so many brands available, and Intel X25-M 'G2' seems generally to be the most highly rated overall. However, there is virtually no stock of 80GBs in the UK at present, except at extortionate prices, and I don't need 160GB.
    Kingston SSDs are very reasonably priced, but seem to be a bit of an unknown quantity, although I rate their DDR3 memory very highly.
    I have visited the websites of several manufacturers, and read various online reviews, and the recently introduced OCZ Vertex Turbo has had some good reviews, albeit on PC forums.
    At the moment I can buy the 60GB Turbo for £170.66 inc.VAT from ebuyer.com, whereas their price for the standard Vertex 60GB is £193.99 inc. VAT, which seems very strange!
    When I googled "OCZ Solid State Drives +UK", Amazon UK appeared on the listings, but there was a footnote which said " not suitable for use on Mac".
    OCZ list a Vertex Series Mac Edition on their website, and that is why I am asking this question.
    Unfortunately, there are no UK listings when I google the Mac Edition, and I am hoping that somebody of the ilk of "the hatter" or "samsara" will be able to answer my question.
    If anybody else is using the Vertex Turbo in a Mac, I would be very grateful for your input. Likewise if you have had bad experiences with OCZ SSDs.
    If I wait 3-4 weeks I should be able to buy an Intel X25-M G2 80GB for round about the same price as the Vertex Turbo 60GB, i.e. if prices remain the same as currently being quoted by vendors who are out of stock.
    All input will be very gratefully received. If it is positive, I will go ahead and order a Vertex Turbo from ebuyer, in case they run out of stock (which is 16 at present).
    Many thanks in anticipation, guys!

    Hi Samsara,
    Many thanks for your advices once again.
    60GB will be more than adequate as my boot drive. At the moment I am using a VelociRaptor 300GB, and I have used less than 30GB of space. That is after reinstalling all my applications and software, and includes all my files, folders, and printer drivers etc.
    I have utilised under 50GB of the original 640GB hard drive, but that includes a lot of photo images which I imported into both iPhoto and Aperture.
    When I receive my Agility EX SSD I will clone from the VelociRaptor using Super Duper, and I will then set up a 4 drive RAID 0 using 4 VelociRaptor 300GB disks. That set up should suit my needs for many years to come, even when I eventually upgrade from Photoshop Elements 8 to CS5.
    I will back up the Agility EX to the 640GB hard drive using Super Duper Smart Update, and that will be my spare boot drive.
    The 4 drive RAID 0 will be backed up to the My Book Studio Edition II 2TB, using Time Machine.
    In your experienced opinion, do you think that set up will be satisfactory?
    The Agility EX is actually the latest generation of OCZ SSDs, and it is one of only 2 models in their "Maximum Performance" range, whereas the original Agility was only a "Mainstream" model.
    The key factor is that the Agility EX uses single-level cells (SLC), instead of multi-level cells (MLC). It is second only to the Vertex EX Series in terms of performance per GB in the OCZ range of SATA 2.5" Solid State Drives.
    In very recent reviews it has outperformed both the Vertex Turbo and Vertex 120GB models from the OCZ "Performance" range in most of the test benchmarks.
    http://www.hardwarecanucks.com/forum/hardware-canucks-reviews/24507-ocz-agility- ex-60gb-ssd-review.html
    http://www.phoronix.com/scan.php?page=article&item=oczagilityex&num=1
    http://www.guru3d.com/article/ocz-agility-ex-ssd-60gb-review-test/3
    The above are just a few of the very favourable reviews of the Agility EX SSD.
    I preferred to buy a 60GB SLC, rather than a 120GB MLC, because SLCs reputedly have 10 times more life expectancy, and performance wise per GB there is no comparison.
    Only time will tell if I have made the right decision!

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

  • MSI P67A-C43 (B3) & OCZ Vertex 3 VTX3-25SAT3 Issues

    Specifications:
    Quote
    Mobo/Laptop: MSI P67A-C43 (B3)
    BIOS: 1.B (2011-04-14)
    CPU: Intel Core i5-2500K
    RAM: 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 CML8GX3M2A1600C9B
    Vid: ASUS ENGTX560 TI DCII TOP/2DI/1GD5 GeForce GTX 560 Ti
    PSU: HX750 (CMPSU-750HX)
    HDD: OCZ Vertex 3 VTX3-25SAT3-120G v2.11
    Chipset: Intel P67 (B3) RSD v10.6.0.1002
    OS: Windows 7 Ultimate 64 Bit SP1
    Let's start from the beginning: So I built my PC in July and ever since I've been having on and off BSODs with the Vertex 3 drive. Mostly they'll happen once a week. When I first built the machine my drive came with Firmware 2.06. I installed all the drivers from MSI's website as well as the latest Intel Rapid Storage Drivers. Eventually I flashed the SSD to 2.11 when it was released but still had similar issues. Hotplugging was enabled when I installed Windows 7 for the first time AND when I flashed to 2.11 from 2.06. Some members over on the OCZ boards stated this might have been the cause of the BSOD. Basically the PC froze, BSOD'd, restarted, and then the system couldn't detect the drive. I had to power the system down, remove the power cable, wait 10 seconds, re-connect the cable and power on the PC. After I did this Windows booted normally.
    I received some advice on the OCZ forums to reset CMOS and leave hotplugging disabled. Then re-flash the drive to 2.11 with hotplugging disabled. Some members thought this would make the drive act like an internal drive, not an external drive. However, a week after doing this the same BSOD appeared. I've started from scratch last week by secure erasing the drive and re-installing Windows, but same issues. I noticed MSI released a new BIOS for my board in July. I have the one from April currently.
    Is it worth upgrading my BIOS? The listed fixes don't say anything about SSDs.
    I plan on trying this when I get home from work:
    Quote from: Tony;676791
    Going to keep this brief and to the point, this hack will force the 2 primary sata2 or sata3 ports on the motherboards to be designated Internal only...You can do this hack for all Intel chipsets from around ICH8 onwards in win7 and Vista.
    You also need to make sure hotplugging is disabled in uefi/bios if your boards bios has the option(s) do this first before you do any of these regedits etc
    1 Remove all traces of Intel drivers on your system, that means remove the management engine driver, the RST driver and the INF driver, you do this thru the programs and features option in control panel.  I remove them all before I reboot, the system will automagically set you using the MSAHCI driver.
    2 Now reboot, let win7 detect the ssd and reboot again.
    3 now open a elevated command window (CMD with administrator privileges) and copy/paste the following...then hit enter.
    Code: [Select]
    reg.exe add "HKLM\SYSTEM\CurrentControlSet\Services\msahci\Controller0\Channel0" /f /v TreatAsInternalPort /t REG_DWORD /d 0x00000001 
    Once you hit enter you can then add the following again using copy/paste.
    Code: [Select]
    reg.exe add "HKLM\SYSTEM\CurrentControlSet\Services\msahci\Controller0\Channel1" /f /v TreatAsInternalPort /t REG_DWORD /d 0x00000001 
    Hit enter and close CMD.EXE down, reboot
    This will now force the 2 sata 3 ports to Internal only, this means they will apply LPM if you set it and will support Automatic Partial to slumber.
    I now suggest you experiment with power schemes, for some high performance may work better than balanced...try both
    You also need to make sure hotplugging is disabled in uefi do this first before you do any of these regedits etc
    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.
    remove the SSD to start
    1 create a temporary win7 install on a hdd, use the msahci driver and once installed do the hack to force the 2 ports to internal only. Have the hdd connected to port 1 on the motherboard.
    2 once the install is ready and you have installed toolbox to it power down and connect the SSD to port 0
    3 now boot to the HDD, use the manual boot menu option to make sure you are booting to the HDD and make sure hotplugging is OFF in UEFI
    4 once in win7, flash the FW to the drive, when its finished flashing, close toolbox, reboot back to the HDD and back into win7...make sure the SSD is detected in my computer.
    5 now power off, remove the HDD...then boot to UEFI and make sure to set the SSD as first boot device
    6 Power up, boot to the SSD
    Stay using the MSAHCI driver for now, do not install any INF, IME or RST drivers.
    Edit 09/09/11
    Had a few end users quoting disabling TRIM solved BSOD for them...now im not saying it will solve BSOD for all but it may be worth trying. Remember the SandForce controller was originally designed without TRIM in mind, it functions just fine without it so you should see no loss of performance. If you want to help the controller stay fast you could always add some extra over provisioning by reducing the volume on the drive and leaving that space unallocated...totally up to you what you do though....
    I like 25% OP on my drives, this means if I have a 120 with 115GB showing in windows I lose 15GB to OP and use 100GB for the volume....
    A forum member wrote a little script to enable /disable trim...he wrote in support for wiper for Indilinx drives also...just ignore that part and use the TRIM function only...
    http://www.ocztechnologyforum.com/forum/showthread.php?63830-A-small-script-to-enable-disable-Trim
    Here is a link to force TRIM also.. http://www.ocztechnologyforum.com/forum/showthread.php?73888-Here-s-a-tool-to-force-TRIM-your-entire-drive&p=523305&viewfull=1#post523305  you could if you wanted use this once a week to force the drive to TRIM all marked deleted blocks if you turn off native TRIM in win7.
    Again....not saying this cures any BSOD but a few end users have said they disabled TRIM and issues went away...anything I have suggested here is totally reversible and will do no harm to your systems.
    If this doesn't work and I get a BSOD after a week I'll disable TRIM and if that doesn't work I have no idea. OCZ said they're working on a new firmware release so who knows. I just hate feeling like I am a beta tester.
    If anyone has any suggestions let me know.

    OK, had some time to go test your suggestions here
    These are the 1.5V Vengeance RAM Modules.  Tried installing 2 of the RAM on slots 2 and 4 on their own.  System Boots Fine.
    Went into the BIOS and changed the voltage applied to the RAM modules from
    AUTO to 1.575V.   On AUTO it says is applying 1.5V to the 2x 4GB modules.
    Installed the full 4x RAM on all slots... and the system just shuts down.  Power cycling again.
    What do you think here?  Bad Motherboard?  Can't think of anything else to try...  totally stumped! 
    Thanks!

  • How can i get my hp dv-7 to stop blue screening with the new ocz vertex 3 ssd

    installed a new ocz vertex 3 ssd on my pavilion DV-7-6b75nr and it will now not stop blue screening.Even took it to a computer shop and they could solve the issue. is this laptop not meant for sata 3 SSD's or do i need a certain one or does hp have to install it? windows7,computer 3 weeks old,I7 processer...using the SSD for my os and main boot drive..Computer shop said i might need to rewrite HPs bios...??

    Hi,
    You can find the list on the following link:
        http://h10025.www1.hp.com/ewfrf/wc/document?docnam​e=c02763358&tmp_task=prodinfoCategory&cc=us&dlc=en​...
    Please install the following list:
    1. Software multimedia
    2. All components of Software solutions
    3. Utilities
    from the following link:
       http://h10025.www1.hp.com/ewfrf/wc/softwareCategor​y?os=4063&lc=en&cc=us&dlc=en&sw_lang=&product=5064​...
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • MacBook Pro 11/2007 problem with SSD OCZ Vertex Series 250 GB

    Hi,
    you can read my detailed problem in the OCZ board here:
    http://www.ocztechnologyforum.com/forum/showthread.php?t=64941
    The short version:
    - I bought an OCZ Vertex SSD with 250 GB for my 2 years old MacBook Pro
    - System Details: MacBookPro3,1; Boot Rom: MBP31.0070.B07; CPU: Intel Core 2 Duo 2.4GHz; SMC: 1.18f5
    - The first 250 GB OCZ SSD was an firmware 1.3 and I could install it with Snow Leopard very easy. After 2 days the HDD just disappeared and it also didn't work in an other PC with an internal SATA port and also not with an external disk with sata to FireWire / USB
    - I RMA'ed the disk with OCZ and received a new one with firmware 1.4. I tried to install the computer from scratch and it couldn't write the partition when the SSD was connected to the internal SATA port of the MBP. I used the external SATA to USB and formated the disk with another mac. Then I could install SL from scratch but after some hours the computer began to stall and after the reboot it tried to run fschk and I got the error: "kernel[0]: disk0: I/O error."
    (again: Further details please have a look at the link above)
    - When I boot the system through firewire with the SSD connected through SATA to Firewire it works like a charm but that doesn't make sense (Having a MBP with an external boot drive)
    - I RMA'ed the disk again and last week I received the third one but it had the exact same problem.
    So now OCZ told me to ask apple for a possible solution. Does anybody have an idea what to do?
    I've read two posts about OCZ problems and they wrote about efi 1.7 problem and with efi 1.6 it would work. Didn't try it out yet - should I?
    Thanks for you help!
    --Goetz aka Tankmann

    No ideas?

  • HT1551 My apple tv 1st generation dont recognize wi fi. Any ideas?

    evn though I have tried to connect my apple tv 1 st generation dont recognize the wi fi system I'm using.every other system in the house works find (ipad,iphone). Any sugestions?

    try by ethernet to see if that works if it does
    try updating the appletv software
    also try to update the firmware of the wifi router the fact
    that other devices works is of little relevance

  • K9N2 Sli Platinum + SSD OCZ Vertex 3 = Slow Speed Problem [PARTIALLY SOLVED]

    Hey folks,
    I have a problem with my new SSD. I only get sequential reads of 140MB/s and writes of 114MB/s.
    I think it is a driver related issue. I once got faster SATA2-like speeds but cannot reproduce the system settings again... Everything back to SATA1-like speeds after reboot.
    First my pc specs:
    MSI K9N2 Sli Platinum, BIOS v3.9
    - 6 SATAII ports by nForce 750a SLI
    - 2 ESATA (External-SATA) ports (back panel) by JMB363
    - Supports storage and data transfers at up to 3 Gb/s
    AMD Phenom II 965 Black
    Patriot PV224G8500ELKB Viper II Series DDR2 4GB (2 x 2GB, CL5 PC-8500/1066MHz)
    SSD SATAIII OCZ Vertex 3, 120GB, FW v2.11
    LG Internal BlueRay BH10LS30
    Windows 7 Ultimate x64
    I only get very slow speeds with the SSD. I tried so many things that I am getting very frustrated now, I am even thinking about getting a new board and ram just to get the SSD up to speed...  
    1)
    I installed Win7 first with all the default settings in Windows Setup from DVD. Default "IDE ATA/ATAPI controllers" driver was "Standard AHCI1.0 Serial ATA Controller".
    SSD was connected to SATA1-port,  On-Chip Sata Controller AHCI enabled in BIOS,  Extra RAID/IDE Controller disabled.
    All fine, but whichever benchmark I used (AS SSD, HD Tune Pro, Atto Disk Benchmark, CrystalDiskMark; other tools used: DriveControllerInfo, AIDA64/Everest, CrystalDiskInfo ) I got e.g. 140MB/s Read and 114MB/s Write sequentially (CrystalDiskmark, similar with random data AND only zeros ).
    Trim working (it seems) with AHCI driver. I also changed to nvstor64 driver (nforce driver setup 15.56), with is marginally faster but not what you would expect from a SATAIII drive on SATAII controller.
    2)
    I installed Win7 using "diskpart" (Shift-F10) during disk setup, setting a cluster size of 64k instead of default. No real change.
    3)
    After reinstall of Win7 x64 (again...), I changed from SATA1 port to SATA6 port, also enabled Extra Raid/IDE controller set to AHCI as well.
    Nothing changed. With all settings to default in Windows (ahci default driver), I then manually updated the ahci to nvstore64 driver in Device Management, rebooted.
    Then a minute later after reboot I got the following Sequential speeds with CrystalDiskMark:
    273MB/s read and 137MB/s write (random data)  +  274MB/s read and 220MB/s write (with zeros) !!!
    While I ran this benchmark Windows came up with a message: "You must restart your computer to apply these changes - Restart Now/Restart Later".
    After the previos reboot, when I changed manually from AHCI to NVSTORE, I had changed nothing in the current session, apart from running CrystalDiskMark.
    I did reboot and I was back to the slow SSD speeds again = 140/114 MB/s...
    4)
    I have tried every possible combination of mainboard SATA ports, drivers changing with nvidia setup/manually, deleting and disabling controllers (incl BSOD and startup repair :D ), chaning bios settings around, but I just cannot get back the faster speeds  
    There is never any change in speed, whether I use ahci or nvstore64, whichever benchmark I use, whether random or zeros...
    5)
    Could the SSD be broken, something internally preventing it from faster speeds (with this one random exception)?
    Could it be that my K9N2 SataPorts only allows for / reduced to SATA1 speeds?
    Am I missing something with the driver setup?
    Do I need additional drivers for the extra JMicron Controller when using SataPorts 5/6 ?
    I have no other mainboard to test this with...
    Please guys, I am going to jump out of the window if I can't fix it... :(
    Thanks, Mike

    Hey guys - problem 'solved':  
    I tested the OCZ SSD Vertex 3 120GB with following sata3 controller card http://www.lycom.com.tw/PE-115H.htm.
    The card itself works immediately (needs at least PCIe x4 slot, will work slower otherwise but still faster than the OCZ SSD @sata1 with nvidia chipset).
    There is some raid setup, doesn't apply to me, the boot even with the card is really only a few seconds longer and not annoying at all. Windows (7 x64) needed a driver, supplied on CD (which is cheap and making noise like h**l). The card works w/o the driver but doesn't harm to install it...
    Also, just to clarify, this sata controller card did not need any specific setup at all. Just put it in, plug in sata cable (I use akasa sata3-rated), maybe change boot device in BIOS (I didn't even have to), done - booting Windows as usual.
    Benchmark CDM with sata controller card Lycom PE-115H:
    http://img24.imageshack.us/img24/3845/cdmpe115hahci0x00.png
    http://img850.imageshack.us/img850/7549/cdmpe115hahcirand.png
    Speed is much better than before with nvidia chipset 750a SLI controller: sata1 (sata2 whenever it randomly worked):
    http://img839.imageshack.us/img839/505/cdmahci0x0.png
    http://img13.imageshack.us/img13/6258/cdmahci0x0sata6contnv64.png
    Final thoughts:
    Well, I am happy with the SSD speed now (PCIe limited to 5Gbps). However, I had to spent quite some time to get it working on my sata2-cabable mainboard. Finally, I had to buy a extra controller card to get it working reliably at speeds faster than sata1. There is hardly any useful information on why this problem occurs with (older) nvidia chipsets and OCZ (sata3) SSDs. I still think that OCZ must know about this problem, but regards this issue as low priority, while at the same time not planning on giving up on sales to people with nvidia chipsets. Maybe OCZ should just make a big sticker on the box the drives come in with something like "Does/Might not work with nvidia chipsets, please use third-party sata controller card or different SSD manufacturer".   But then none of these potential customers would buy OCZ SSDs...  
    I will keep the sata3 controller, anyway handy to have, but return the OCZ Vertex 3 120GB and replace it with a SSD from a different manufacturer (Corsair Force GT, Patriot and OWC are not that great to get around here). The benchmarks for most people will not achieve the maximum advertised OCZ speeds anyway, so why not go with a brand that allows for some plug'n'play with some customer support.
    Hope this post helps others like me with their nvidia chipset  + sata1 speed problem
    Cheers, Mike

Maybe you are looking for