BSOD - 0x000000f4 - CRITICAL_OBJECT_TERMINATION Daily ntoskrnl.exe

Hi cnfdnc.

Make it sure that your Corsair Force GT SSD is running with the latest firmware. Corsair does it via their forum: SSD Firmware Update - The Corsair Support Forums

If it is up-to-date; or if the situation is the same even after the update, do two more things.

First, sometimes the file system monitoring mechanism of an antivirus can cause this Stop 0xF4. And here we are seeing that the ESet NOD32 antivirus system monitor driver is failing.

Code:

fffff880`02ea7148  fffff880`02c30126Unable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
 eamonm+0x20126

Description here: Driver Reference Table - eamon.sys

Uninstall ESET. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Second, sometimes the backup/restore programs also affect the disk behavior adversely. And you have MyPC BackUp. Remove it from startup, and dont let it run in the background unnecessarily. Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

______________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8007501960, fffffa8007501c40, fffff800039867b0}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

Followup: MachineOwner
---------