New SSD, New OS = 0xF4 BSOD

[zYx]

Hi There,

As you can see, I have upgraded my PC recently to a SSD drive. Installed new Win 7 x64 and if I leave my PC on overnight, I often find it crashed with 0xF4 BSOD error.

I've never seen the 0xF4 error before, only now with SSD and new OS.

Windows 7 x64 retail, hardware pretty much new, so is OS, installed a week ago.

According to M$, they say it's a CRITICAL_OBJECT_TERMINATION detailed here: Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION

Please take a look at my crash details (attachment).

I will be grateful for any help.

Thanks!

 

[Seven Eleven]

Since i got Vertex 3 my PC BSODs regularly
Intervals are like from 1 day to 2.5 weeks.
It BSODed on my old motherboard 785G/SB710 and on my fresh and new 990X/SB950, both with different CPUs.

I'm tired of doing all the voodoo magic that are posted on OCZ forums (flashing BIOS, reseting CMOS, secure erasing drive, unlugging cables, changing BIOS settings, changing OS settings etc).

It BSODed on 2.11 firmware and after latest F4 BSOD yesterday i reflashed to latest 2.13.

After searching some clues i found out that there are two schools of thought:

1) BSOD have something to do with power management/sleep states so drive disconnects when it wants

2) SF firmware can't correctly handle CRC errors so drive crawls to snail speed and becomes unavailable and OS BSODs.

I got BSODs while playing games, browsing web and idling with empty desktop etc, so i think number 2 is more likely. Looks like Sandfrorce is fail because drives from different brands with same controller have same problems.
And both Intel and AMD chipsets are affected.

Now i'm going to try and mirror drive and secure erase it and mirror back.

I'm getting closer and closer to moment when i will go back to HDD. For this much money i could have bought 12 500GB Barracudas ffs

 

[zYx]

I have updated my Agility 3 from 2.11 to 2.13.
All I can do is to wait for another BSOD...

 

[Seven Eleven]

After updating, but before getting to secure erase, i got another BSOD. This time it wasn't F4. It was about ntfs.sys or something. Yay

Now it's secure erased and mirrored back. No BSOD so far, but that's much too early to be getting optimistic. If it runs for a month then and maybe then there is hope that it's fixed.

Btw someone on OCZ forums mentioned that switching from AHCI to IDE in bios fixed BSODs for him. Drive was ~20% slower, though. Others were not so lucky.


Have AnandTech wrote this a month earlier, maybe i would have gone for HDD for one more year or so... Roundup begins on veeery optimistic note.

 

[zYx]

I don't think my situation is as bad.

I think that when I do get BSOD, I get a series of them within a period of time. THis period of time can be few hours but no more than 24 hours-ish..

I haven't had any BSODs since yesterday, but it's too early to say...

Here's just three screenshots I've managed to do.




I think I saw 0x111 error once as well.

Here's the discussion http://j.mp/BSOD_0xF4_OCZ

 

[Seven Eleven]

Here's just three screenshots I've managed to do.

Left one is soooo familiar to me... :|
Haven't seen middle one ever.
Right one looks like ATI video driver :/