system BSOD, ssd to blame?

[SeanFL]

Built a machine for a client that uses an OCZ Vertex 2 (60gb). Worked fine for weeks, then started locking up and bsod from time to time. Now it happens quite a bit. He swapped out memory twice, and while it seemed to help for a while, the problems are back. Bummer that he's not nearby for me to help swap things out.

One key piece of info he shared: when it reboots, it sometimes says it can't find a bootable drive. So my thoughts turned to the SSD. Have read about the issues surrounding some ssd's and have updated to the latest firmware but still seems to be happening.

Would you try anything else before trying to wipe the ssd and give another try? I have four other OCZ's in use in a studio and all have worked without issue.

The system build:
ASRock H67M
core i3-2100
OCZ Vertex 2
G.Skill memory (4 gig)
Samsung F4 2tb for data

Thanks for any guidance.

Sean
voice over talent
http://www.seancaldwell.com

 

[God Mode]

I would also suspect the motherboard. I've had issues with motherboards where having a hd (usually port 0 out of 0,1,2,3) would crash or refuse to find boot device.

 

[bryanW1995]

That doesn't explain the lock ups and bsod's, however. I'd try another ssd and report back with results.

 

[Coup27]

Either you didn't do your research or took a punt to keep the costs down, but it was a real risk to use a Vertex 2 in a box for a "client", especially one you cannot provide on-site support for.

 

[taltamir]

That doesn't explain the lock ups and bsod's, however. I'd try another ssd and report back with results.

If the OS drive somehow fails/disconnects windows will lockup or BSOD.
And actually it can happen when a SECONDARY storage drive does that as well. I had it happen with a spindle HDD before.

Repairing a machine is simple, you replace parts until the problem is gone. Replace that SSD and see if the problem is gone now. It does not mean that SSDs are inherently faulty btw even if it was the cause, vast majority of people don't have such issues with SSDs.

 

[Obsoleet]

Built a machine for a client that uses an OCZ Vertex 2 (60gb).

That's your problem. Been there with that same drive.

Only put Intel or Samsung in your client machines.

 

[groberts101]

I have 7 Sandforce controlled drives on this one machine alone(6 in R0 for nearly 2 years straight now) and have tested many others as well. In my experience, first gen SF controllers have flaws and limitations that need to be taken into consideration.

Given that experience.. it's probably related to power mgmt in some way shape or form. I always advise anyone running these older gen SF based drives to bypass typical sleep/hibernate functionality to reduce varibles being introduced into the mix.

as to the problem at hand here. When these issues do crop up?.. the best(and often fastest in the long run) avenue to pursue is to properly secure erase(SE) the drive(use toolbox with the SSD as spare or Linux tool without change).. force flash the firmware once more(this assures fresh code after the SE).. and start fresh once more.

Other than that?.. and as others have already noted.. it may be best to move to another controller on a problematic machine(which may or may not be the case here).. or RMA the drive in hopes that it was somehow faulty beyond the typical firmware limitations which may have been antagonized by typically used power transitions.

 

[Obsoleet]

So in summary OP, buy yourself an Intel or Samsung drive.

 

[groberts101]

LOL.. or whatever has been working for you in the past might still be a good bet as well.