Vertex 3 BSOD

nanaki333

Diamond Member
Sep 14, 2002
3,772
13
81
Well it's finally happening. I put my Vertex 3 240GB in my wife's computer when I upgraded her to an SB setup.

Now for some background. I originally had the drive in my desktop as a boot drive, but replaced it with 2x intel 320 160GB in raid0 and used the v3 as my steam/games drive. I ended up getting a Crucial M4 for free, so I swapped the v3 for the m4.

Still with me? So, when I got the new SB PC built, I noticed there was an update for the v3. I put it back in my PC, downloaded the vertex toolbox thing, successfully updated it, secure erased it, then put it in my wife's pc.

Now this brings us to the present... The past few days, the pc would get a BSOD at completely random times. Sometimes after 40 minutes, sometimes after a few hours, sometimes it doesn't at all. I noticed a bios update for the motherboard, and took care of that. Reinstalled windows just for shits 'n giggles. Guess what? Still random BSOD.

This drive seemed to run perfectly in my computer, which is a similar SB build. The only major difference, is I had the original firmware on it when it was my boot drive (and steam drive actually). I'm about to go post this on the OCZ forum, but I'm convinced some of their techs are retarded.

The reason I say that about OCZ techs, is I had a Vertex 1 drive that had the original firmware that I found laying around my house. I wanted to update it to the latest and was told I HAVE to send it back in. Period. Later, when I mention it on here, grobster told me that was silly and I could have done it myself if they sent me the destructive flashing tool. So I'm hoping to get little grobby's attention here to help out. He also helped out with the hot swap bios setting thing where the v3 would hiccup and freeze in my desktop the very first time I installed it. :)
 

Claudius-07

Member
Dec 4, 2009
187
0
0
Can you be sure that the random BSOD are as a result of the Vertex 3? What error are code are you getting for the BSOD? Just asking -- could be anything.

Is the system stable enough to boot into Win 7, run a stress testing software, while monitoring the temps and the voltage? i.e., install CPU-Z for checking your voltages and speed of ram etc, install something like RealTemp etc to monitor the temps and then download something like Prime95 64bit to check for stability. All this to rule out say CPU/RAM voltages etc. If you have already done this then please disregard.

Did you install any of the Intel chipset device software drivers like their new 9.2.0.1030 ones or the matrix storage manager? If so does it crash with it and without these drivers?

If all else fails can you restore or move back to the Firware you had before, using the same tool and just finding the older firware on OCZ's site and then testing the Vertex 3 to see if it is indeed the firmware that pooched everything? This would be last ditch effort if indeed it is the SSD drive I mean.

Are you running in AHCI or IDE mode? Reading a lot of issues for some based on what board and chipset they have, having issues with AHCI. Just something to test. I've had success setting the option in the BIOS to RAID instead of AHCI or IDE. You can test that as well.

In your advanced power features, did you disable "power down this drive" after xxx amount? At least for my SSD's I dont have any of them ever power down. When i reach xx amount of time, my system just goes into suspend mode... period.

What SATA port are you running this from on your wife's system? Is it SATA 6? Is the board a new revision with the fix? Can you try plugging the SSD into a different SATA port?
 

nanaki333

Diamond Member
Sep 14, 2002
3,772
13
81
the board is a gigabyte something... i don't remember the model off the top of my head. it's z68 based, so obviously a b3 stepping. raid is set in the bios since there are 2 velociraptors in raid0 on there as well.

cpu is not overclocked. it is a 2500K with an aftermarket cooler idling about 32c. before i put the v3 on her pc, i installed windows on an x25-e 64GB that i had in her original setup before i got the free m4 and replaced my v3 steam drive. so it's definitely the v3 that is at fault here. it's plugged in to one of the sata3 ports. i don't have the code handy, as i'm at work. all signs point to the v3 though.
 

groberts101

Golden Member
Mar 17, 2011
1,390
0
0
unfortunately.. all signs do point to the V3 in that scenario. Whether you need to start throwing blame is really irrelevent at this point since it can't be backflashed and life will have to go on with some extra work on your end at this juncture.

Mobo mfgrs, Intel, Sandforce and even Microsoft are all working on it with a few new OROM's already being introduced already. In a nutshell.. some existing problems were taken care of from 2.02 while newer one's were introduced with 2.06. Welcome to Sandforce, buddy.

There seems to be a very specific order/method of attack that is working for some so far and should be pursued until the permenant fixes are more widespread and have proven to work. A PITA I know, but you seem versed enough with this tech to muddle your way through it once again.

I can't completely share info recieved on the beta testers forum over there but will say that some have replicated and worked around it so far. From now on I would rec going to the mfgrs forum to get some firsthand attention from me&er to possibly help you get past it.
http://www.ocztechnologyforum.com/f...vtx3-agility3-or-solid3-and-bsod-look-in-here
 

curlysir

Member
Feb 21, 2011
43
0
0
And this problem is not just with OCZ, the new Corsair Force 3 with the same Sandforce controller is experiencing the same problem. I have been following it on both forums and the problem is being looked at very hard by all parties. And as groberts101 points out the drive cannot be flashed back at this time.

I had a Vertex 3 Max IOPS that I had to have replaced because it locked up after 2 days. The replacement drive has worked fine for almost a month now. And it is on 2.06. So if you have done some of the things they suggest on the OCZ forum and still have the problem, RMA might be a good option.
 

WaTaGuMp

Lifer
May 10, 2001
21,207
2,506
126
These king of posts really make me stay away from SSD's. Once they get cheaper and more reliable I will be glad I waited.
 

groberts101

Golden Member
Mar 17, 2011
1,390
0
0
These king of posts really make me stay away from SSD's. Once they get cheaper and more reliable I will be glad I waited.

only because you don't realize how much time can be saved overall by owning one. Even if you have many problems?.. the potential gains are hard to miss.

After a year or 2 you could almost say something like.. "OK.. I have the option of buying back 2 weeks of my life for time spent on the PC. Is it worth it to me?" Everyone's time and money is worth something different so YMMV.

@nanaki.. where'd you end up on this? Did you see some of the most recent resolutions for these issues?
 
Last edited:

nanaki333

Diamond Member
Sep 14, 2002
3,772
13
81
to be honest, i did not even see i had replies in this thread until saturday. ended being really busy at work and just got home. i'm going to troll the ocz forums and see what's what. her pc did not do it for a few days so i thought it fixed itself, but it happened again this morning. i'll check things out in the morning or make a post before i get busy though :)

watagump, at least if the drive fails just shy of the end of your warranty, you get a brand new fresh drive. if it wasn't for the bugs in the SF controller, there would be no reason to choose anything over the vertex 3 or equivalent.