• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Yay. Had my first BSOD with Vertex 3 MI

Axonn

Axonn

Senior member
Have a Vertex 3 MAX IOPS. 4 days ago I had my first BSOD, (error 1e), after 8 days of successful use. While 1 BSOD in almost 2 weeks is not scaring me, I am worried nevertheless.

I got firmware 2.08 but on OCZ site they got 2.15. However, that 2.15 is published BEFORE SandForce announced fixing their controller BSOD bug, so I'm not going to get it. I'm waiting for 2.16.

Has anybody fixed BSODs with 2.15?
 
Last edited:
Hi Axonn,

I recommend you do upgrade to 2.15. It includes a lot of significant changes and as I understand it, this also includes input from Intel.

You should also install the latest BIOS for your mobo.

As a matter of interest what mobo do you have and do you know what level of Option Rom the BIOS supports?

2.15 has solved many peoples problems; this is apparent on the OCZ forum.

Regds, JR
 
Thanks for answering again man ::- ).

I got a P8Z68 V-Pro Gen 3 from ASUS.

I haven't made myself a user on OCZ but will probably do so soon, just so I ask when they think they'll release 2.16.
 
Axonn,

The first and latest BIOS for the P8Z68 V-Pro Rev 3 has the 10.6 Orom. So, if you are not already, you should be using the 10.6 Intel RST AHCI driver as listed for your mobo by Asus (this may sort things out for you without having to upgarde the fw; though I feel you should do so anyway).

I imagine this will also improve your AS SSD score 🙂

Regds, JR
 
It was my understanding that 2.15 is the firmware update which incorporates the fix by Sandforce for the BSOD problems.

You should deffinately update to this. As the process is non-destructive you should have nothing to lose.

Another update may be months away.
 
"Yay I'm running an old firmware with known bugs that are fixed in newer versions and finally got one of those known bugs!"

Umn yes congratulations - why exactly is this thread worthy?
 
Voo: I made a mistake when I wrote the first post. I said that the firmware was published AFTER SandForce announced the fix. What I meant was BEFORE. The 2.15 firmware date is 16 October if my memory serves. I am, however, sure that SandForce announced the fix later. So, at least theoretically, OCZ would not have known about the fix at the time of publishing 2.15.

reynoldsjrmy: I'm not very fond of upgrading firmware/BIOS, especially not very new ones (as they may have bugs). But the releases are sufficiently old by now so I will do it.

Coup27: Theoretically it's non-destructive. Practically, anything can happen ::- D. As I told Voo, it seems strange that 2.15 fixed the bug, as SandForce announced the fix a bit later.
 
Last edited:
Axonn said:
As I told Voo, it seems strange that 2.15 fixed the bug, as SandForce announced the fix a bit later.
Click to expand...
I do think you have this wrong somehow. The AT article which announced that SF had developed a fix and it would be out today is dated 17 Oct. Anand also says that OCZ firmware 2.15 references this firmware. OCZ made the firmware available on their forums on 17 Oct.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top