Stop Error 0xF4 - CRITICAL_OBJECT_TERMINATION

Still haven't had another occurrence of that BSOD... could it possibly have been a one time bug/fluke?

No, I think the firmware updated fixed it.

Golden said:

No, I think the firmware updated fixed it.

Alrighty. Then I'll mark this as solved. :)

Well, my computer just had the same BSOD...

I also get a 0xc000000F on boot, going into my BIOS, my OCZ ARC-100 isn't listed at all... I turn my computer off and then back on and it's fine again... I hope I don't have to RMA this SSD.

I also had a dump for BugCheck 3B...

Just for the sake of I installed the latest chipset drivers, etc. from my motherboard manufacturers website just on the off chance they weren't up-to-date, now I haven't got USB 3.0 support because the VIA USB 3.0 drivers won't install and it's clearly enabled in my BIOS.

The setup says it can't find any valid hardware. It was listed under my devices prior to the chipset drivers being installed... now it's not. :/

Well, I ran sfc /scannow, no problems found.

I checked all the cables, unplugged them, plugged them back in, etc.

I'm not sure what else to do, short of re-installing Windows in the hopes that fixes the problem... I got this drive on February 27th.

And my USB 3.0 entries are back under Device Manager... O.o

I replaced all the SATA cables today, unplugged and plugged back in, so let's hope it was a cable issue... I hope.

Didn't have this issue until the new SSD, which I got on the 24th of last month, first BSOD was on the 11th of this month, then again the 18th, same program was suspect, smss.exe.

Chris2005 said:

I also get a 0xc000000F on boot, going into my BIOS, my OCZ ARC-100 isn't listed at all... I turn my computer off and then back on and it's fine again... I hope I don't have to RMA this SSD.

Those symptoms suggest something disk-related. lets see what the new cables do.

Golden said:

Those symptoms suggest something disk-related. lets see what the new cables do.

Alright. I mean it was odd that the same BSOD happened almost exactly 7-days apart... plus/minus a few hours/minutes... BSOD on the 11th, then again on the 18th...

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode