BSOD CRITICAL_OBJECT_TERMINATION (f4)


  1. Posts : 9
    Windows 7 Ultimate x64
       #1

    BSOD CRITICAL_OBJECT_TERMINATION (f4)


    Been having infrequent bsod's since start 2014. got really bad now, once/ twice a day.

    Tested Ram with memtest for 14 passes, tested hd with seagate tools, all reported thumbs up.
    Also did a chkdsk c: /r without any errors.
    Installed the latest drivers from the manufacture, didn't solve it,
    installed latest drivers from intel. Didn't solve it.
    Swapped ram to different slot.
    Reinstalled windows with latest drivers from manufacture, problem continued.*
    Swapped out the RAM for new stick**, and here I am asking more learned people then myself for a hand.

    The first minidump happened at * stge of troubleshooting, the last 2 minidump happened at **

    All help apreciated

    PS. didn't have the foresight to conserve old minidumps, they got erased when I reinstalled windows.

    PPS. tried to install Win7 in UEFI mode, but it kept hanging at "starting windows" screen, despite trying several workarounds I found on the net. Just gave up and activated CSM and installed in bios mode. PC originally came with windows 8, and that windows would install in UEFI mode without a hitch, but I think thats a matter for another thread.
      My Computer


  2. Posts : 9
    Windows 7 Ultimate x64
    Thread Starter
       #2

    just realized audio and card reader drivers went installed, just installed them from the manufactures page (lenovo), activated driver verifier as suggested in other posts to make sure its not a driver problem.
      My Computer


  3. Posts : 26,869
    Windows 11 Pro
       #3

    Hello, Ivanissevich. I will try to help you with this. I read your troubleshooting steps you have taken, but from reading the dumps it appears to be a hard drive error.

    Code:
    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: fffff6fc40009c98, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000000e, error status (normally i/o status code)
    Arg3: 0000000121130860, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff880013939a0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    Code:
    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
    DISK_HARDWARE_ERROR: There was error with disk hardware

    The other 2 were this

    Code:
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8005503b30, Terminating object
    Arg3: fffffa8005503e10, Process image file name
    Arg4: fffff80002de3db0, Explanatory message (ascii)
    Stop Code f4 is almost always a hard drive error

    Code:
    !process fffffa8005503b30 3
    GetPointerFromAddress: unable to read from fffff80002d11000
    PROCESS fffffa8005503b30
        SessionId: none  Cid: 0170    Peb: 7fffffd5000  ParentCid: 0168
        DirBase: 18e79000  ObjectTable: fffff8a000a2fd80  HandleCount: <Data Not Accessible>
        Image: csrss.exe
        VadRoot fffffa80055008f0 Vads 87 Clone 0 Private 465. Modified 283. Locked 0.
        DeviceMap fffff8a000008d80
        Token                             fffff8a000a2f060
        ReadMemory error: Cannot get nt!KeMaximumIncrement value.

    If you would, please make sure your machine is set to create Small Memory Dumps Dump Files - Configure Windows to Create on BSOD

    Please fill out your System Specs

       Information
    Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

    If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs

    Also, I know you have already run it, but I would like you to run Seatools for DOS again. Run the long and the short test. SeaTools for DOS and Windows - How to Use

    Also run Check Disk Disk Check
      My Computer


  4. Posts : 9
    Windows 7 Ultimate x64
    Thread Starter
       #4

    Sorry about the sys specs, filled them in with my personal pc, however this BSOD pertains to a friend's pc, his specs are:

    Lenovo C240 10113
    Intel Celeron 847
    Motherboard chipset Intel NM70
    Kingston DDR3 sodimm 2GB 666.7MHZ
    Intel HD Graphics 2000
    Monitor Lenovo LXM-WL20AH
    HDD Seagate ST500DM002-1BD142

    Have had 1 more BSOD, windows was installing updates when I Shut down the pc, this was early this morning, 7am. When I left at 11.30 it was still at it, when I came back had restarted with notice of bad shutdown, new minidump (attached) so I gues it BSODed again. The fact it was taking so long to install updates (in fairness they were like 250 updates, but some updates took for ever to process).

    I have changed windows to create minidumps as per your request (was creating kernel dumps).
    will run seatools for dos and diskcheck now and post back as soon as I have results.

    Thank you very much for your help and time.
      My Computer


  5. Posts : 9
    Windows 7 Ultimate x64
    Thread Starter
       #5

    SeaTools Tests PASSED


    SeaTools for DOS would hang on the Lenovo with that drive, had to remove the drive and test in another PC. The drive passed the test. I also ran chkdsk without issues.

    I installed another drive in the Lenovo, installed windows and have had it running with no issues for 2 days (installing programs, updating windows, etc). Interestingly, SeaTools for DOS worked on the Lenovo with this drive installed. The drive failed the short test, passed the long test.

    The original Lenovo drive is installed in another PC and hasn't presented any issues so far, though its just a data drive with OS on another HDD.
    Last edited by Ivanissevich; 26 Mar 2015 at 16:10. Reason: Spelling mistake
      My Computer


  6. Posts : 26,869
    Windows 11 Pro
       #6

    It looks like it was the Hard Drive.

    Code:
    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000009d, error status (normally i/o status code)
    Arg3: fffffa8005d047c8, current process (virtual address for lock type 3, or PTE)
    Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    Debugging Details:
    ------------------
    
    ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
    DISK_HARDWARE_ERROR: There was error with disk hardware
    BUGCHECK_STR:  0x7a_c000009d
      My Computer


 

  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 02:58.
Find Us