0xF4 - Applications crashing sporadically

Hello and welcome to SF WhitePhoenix :).

BugCheck Code 0xF4 are more often than not storage issues, being the disk itself or the storage subsystem
(i.e. SATA ports / SATA cables (Data & Power) / the Chipset).

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: fffffa800df01560, Terminating object
Arg3: fffffa800df01840, Process image file name
Arg4: fffff80002fd37b0, Explanatory message (ascii)

Code:

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

Are all of the parts used to build the system new?
Please test the HDD.

   Warning

The Following Method Should NOT Be Performed On An SSD!

Testing the HDD:

1. Perform a Disk Check | Disk Check- Scroll down to OPTION TWO of the tutorial and use the /R switch in the CHKDSK command | chkdsk C: /R.
2. Then Post the Disk Check results following | This Tutorial.
3. Once back in Windows, download Crystal Disk Info and post a screenshot (multiple shots if you have more than one drive).
4. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
5. If SeaTools for DOS is unable to recognize your HDD:
6. Visit HDDdiag and follow the instructions | Or follow the instructions below.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fx key.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

• *Popular BIOS access keys.

Arc said:

Re-seat the sata and power.

Let us know the results.

Hi again :).

No new dumps are present in the file uploaded but good job on catching the BugCheck Code at least.

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes:
Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection,
Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack.

Do you by any chance remember the value of the 2nd parameter?

The system event log is filled with these errors:

Code:

Event[28177]:
  Log Name: System
  Source: atapi
  Date: 2014-01-31T10:12:19.093
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: WhitePhoenix
  Description: 
The driver detected a controller error on \Device\Ide\IdePort1.

Code:

Event[28178]:
  Log Name: System
  Source: Disk
  Date: 2014-01-31T10:12:19.093
  Event ID: 15
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: WhitePhoenix
  Description: 
The device, \Device\Harddisk1\DR1, is not ready for access yet.

Code:

Event[28179]:
  Log Name: System
  Source: Disk
  Date: 2014-01-31T10:12:19.093
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: WhitePhoenix
  Description: 
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Harddisk1 is your HDD;

Code:

Model    WDC WD2002FAEX-007BA0 ATA Device
Partition    Disk #1, Partition #0

Reset your Page File:

1. Start Menu> Run >type control.exe system
and press the Enter key.
A windows will open and on the Left hand side you will see Advanced system settings, click it.



2. Next click on the Advanced tab and Settings which correspond to the Performance section;



3. Then the Advanced tab once more and click on the Change button;



4. Untick the checkbox next to Automatically manage paging file size for all drives;

Select No paging file and Click on the Set button;


5. Confirm all the windows.

6. Restart the PC.

7. Reverse the procedure, by following steps 1-3, only this time select System managed size
and click the Set button;



8. Recheck the box next to Automatically manage paging file size for all drives
and exit the windows by clicking the OK button;



9. Confirm all of the remaining windows by click the OK button
and restart the PC once again to take affect.


Please scan for possible infection and file corruption:

• Download TDSS-Killer and scan for rootkits.
• Download Kaspersky Rescue CD and scan for other types of infections. (a how-to tutorial)
• Download Malwarebytes and DON'T activate the trail (uncheck the box at the end of the installation)
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

(*Kaspersky Rescue CD from a USB thumbdrive)


Also try to completely replace the SATA Data & Power on both drives.

Let us know how it handles :) .

Darn, well sometimes it fails to create a minidump but manages to dump the Kernel dump.
You can look for them (Well it as it overwrites the older one) in C:\Windows\
there should be a file named MEMORY.DMP .

You won't be able to upload it here due to the size restriction.

Please upload the Kernel dump file using Dropbox or Skydrive, the file is located in the Windows directory
and is usually a few hundred Megabytes in size.

Code:

C:\Windows\MEMORY.dmp