I posted the stuff below to the ocz support site, as I think my hard drive is causing the bsod's. I thought it would probably be better to resolve the bsod's here. "I've been getting bsod's since saturday and have been trying to pinpoint the problem. Sooo the details.. The bsod stop code is: STOP Error 0x000000F4: CRITICAL_OBJECT_TERMINATION STOP error 0xF4 means that a process or thread crucial to system operation has unexpectedly exited or been terminated. STOP code 0x000000F4 may also display "CRITICAL_OBJECT_TERMINATION" on the same STOP message. When the system reboots after the bsod, the bios cannot detect the vertex (boot drive). But when I then restart my comp again its detected and everything boots up fine. This is the first thing which lead me to believe that the vertex was at fault. I got the bsod twice, both 9 hours apart, on saturday and then the next day when i did a full system scan with my anti-virus (KIS 2011), the bsod occurred again when the scan was around 1%. The bsod occurs every time i do a full scan, about 2-3 minutes after i initialize it, always on 1%. Note that when I only do a critical areas scan, that gets completed. This makes me think that certain parts of the ssd are corrupt and when they get accessed by kaspersky, bsod entails. I switched the sata cables between my vertex and my other wd hdd to make sure that it wasn't a sata cable issue, same thing happened. I did a system restore to last friday to rule out any software issues/viruses. I ran a memtest just before and went afk when they were around the 75% mark and no errors were detected yet. When I came back, the comp was showing the bios screen which says it can't find the boot drive which occurs after a bsod. I think I got a STOP Error 0x00000070: SESSION4_INITIALIZATION_FAILED STOP error 0x70 means that the initialization of the Microsoft Windows operating system failed. STOP code 0x00000070 may also display "SESSION4_INITIALIZATION_FAILED" on the same STOP message. once as well but I'm not 100% sure on the code as I didn't have time to take a picture. I did a chkdsk (no parameters) in cmd prompt on my boot drive and no errors were found, when i tried to do chkdsk /f, upon reboot (had to reboot for it to do it) it said it was cancelled for some odd reason. Tried doing this in safe mode with same result. I've also done the kaspersky full scan in safe mode and I still get the blue screen or sometimes the computer just restarts. Kaspersky has also been recently reporting that my databases are corrupted, could this be something to do with not being able to access/read the database files on my boot drive correctly because of a corrupted boot drive? I got a different error today which also supported the ssd being corrupt theory. I got a windows 7 explorer crash "Explorer has stopped working" with problem event name: InPageError and error status code: c000009c. This thread with the same issue as mine seems to think that this error is caused by a damaged HDD and recommends running a diagnostic tool from the hdd manufacturer. Does ocz have a diagnostic tool for its ssd's? I've already done a destructive flash to my ssd when it died around december last year (http://www.ocztechnologyforum.com/fo...ht=#post581102). So what does everyone think the best course of action is? Do you think the SSD is at fault or do you think kaspersky might have something to do with it? What tests can I do to make sure it isn't kaspersky at fault, maybe a reinstall or is there another program that can scan or access all parts of the ssd to show that it would be corrupted. If its the ssd at fault should I format the ssd, reinstall windows on it (is this the same as formatting it?), do a destructive flash or is it time to get a new boot drive? Thanks in advance, if anyone could help it would be awesome." Additional info to that: No .dmp files were produced on my boot drive when the bsod's occurred. Under startup and recovery settings I had automatically restart checked and kernel memory dump with the dump file being %SystemRoot%\MEMORY.DMP. I also had the paging file size automatically managed by windows and it was set to 6142 MB (I think), and I have 6 gb ram. I've now unchecked automatically restart and changed it to small memory dump (256 KB). I've also now manually changed the paging file size to 6300 MB (initial size) and 9213 MB (Maximum size) upon reading info about this in the stickies. I managed to record the specific hex numbers of some of the stop codes, note these occurred before I changed my startup and recovery settings which i mentioned above. STOP: 0xF4 (0x03, 0xFFFFFA8008D8FB30, 0xFFFFFA8008D8FE10, 0xFFFFF800031D6DB0) Another one, STOP: 0xF4 (0x03, 0xFFFFFA8008E36B30, 0xFFFFFA8008E36E10, 0xFFFFF80003183DB0) [may not be 100% correct, couldnt make out some of the numbers from my recorded vid off phone] Collecting data for crash dump ... Initializing disk for crash dump ... Physical memory dump FAILED with status 0xC000009C. Another one which I didn't manage to get a pic of, this is just what I remember, STOP: 0x7A Something to do with dfsc.sys. My computer also starts to hang/freeze after 10-15 mins of use. Just now when I was taking the necessary cpu-z and rammon screenshots, computer freezes and i eventually get a error message saying, Then after 30-60 seconds computer restarted automatically and didn't recognise my boot drive, so I had to manually turn the computer off and on again to boot up. edit1: I posted this below in a reply, View attachment 12890View attachment 12896View attachment 12893View attachment 12894View attachment 12895View attachment 12892View attachment 12889View attachment 12891 The bluescreen i got just before, Kaspersky was closed when it happened and I got some error about windows media player database being corrupted or something just before i bluescreened. Also the bluescreen just waited at Initializing disk for crash dump, I'll post the details of that one as well later since I recorded the info. I've tried sfc /scannow and it stops at verification 54% complete, again I'll edit in the exact message, I just want to get the main details posted before i potentially bsod again. I'm gonna post a little bit of this post at a time because i could get a bsod at any moment.