Stop Error 0xF4 - CRITICAL_OBJECT_TERMINATION

Page 1 of 4 123 ... LastLast

  1. Posts : 110
    Windows 10 Home x64
       #1

    Stop Error 0xF4 - CRITICAL_OBJECT_TERMINATION


    First time I've ever got this BSOD. It happened while I was exporting something out of Adobe After Effects and watching an episode of Star Trek in VLC player.

    My system isn't overclocked in any regard. As far as I know I have the latest drivers for everything in my computer.

    Attached all the necessary information.
      My Computer


  2. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #2

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck F4, {3, fffffa80075df040, fffffa80075df320, fffff80003b97130}
    
    ----- ETW minidump data unavailable-----
    Probably caused by : smss.exe
    
    Followup: MachineOwner
    ---------
    0XF4's are often associated with disk errors. There are indications of IO errors in the .dmp file, so lets start by checking your Samsung 1TB using the DOS version of SeaTools (run the SHORT test only):
    SeaTools for DOS and Windows - How to Use

    Now check that you have the latest firmware for the OCZ and INTEL SSD's.
      My Computer


  3. Posts : 110
    Windows 10 Home x64
    Thread Starter
       #3

    HDD came back with no errors.

    Updated OCZ firmware, Intel SSD already has latest firmware.
      My Computer


  4. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #4

    OK. Please do this:

    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
      My Computer


  5. Posts : 110
    Windows 10 Home x64
    Thread Starter
       #5

    Will do.
      My Computer


  6. Posts : 110
    Windows 10 Home x64
    Thread Starter
       #6

    So far, no problems.
      My Computer


  7. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #7

    Interesting...that means the likelihood of a driver causing the BSOD is low. Monitor for further BSOD'S.
      My Computer


  8. Posts : 110
    Windows 10 Home x64
    Thread Starter
       #8

    Shall I disable DV or leave it going?
      My Computer


  9. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #9

    If it has been running > 24hrs without a BSOD, disable it.
      My Computer


  10. Posts : 110
    Windows 10 Home x64
    Thread Starter
       #10

    Alright. I mean, I even played a video game and no problems. :/
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:27.
Find Us