BSOD random occurrence , error 0xF4 (0x3, 0xFFFFFA800AAE1B30) Randomly

Welcome to SF :) .

Both bugchecks are 0xF4, which is usually related to storage.
Considering how young the system is at this point I believe it's a software issue,
I would like to have a look at the virtual memory usage but I am unable to using a minidump.

Please upload the Kernel dump located at the Windows directory.
The Kernel dump file is large (a few hundred Megabytes in size) so you will not be able to attach
it to your next post, please use dropbox / skydrive to link to the file.

Code:

C:\Windows\MEMORY.dmp

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: fffffa800aae1b30, Terminating object
Arg3: fffffa800aae1e10, Process image file name
Arg4: fffff800037dcdb0, Explanatory message (ascii)

Debugging Details:
------------------

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa800aae1b30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xF4

CURRENT_IRQL:  0

STACK_TEXT:  
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IMAGE_csrss.exe

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

Thanks for the link :).
Hmm, there is a chance of it not being the same bug check code..
The link is still uploading so I can't download it at this time.

In the mean time please post a new instance of the SFDT.

I think your drive is a defect...

Hi unfortunately what I was looking for in the kernel dump wasn't present .

Code:

fffffa8006f4a000: Unable to get pool descriptor, paged pool usage may be wrong
    PagedPool Usage:           0 (         0 Kb)

Given that you are having continuous issues with the same bug check, including the latest
batch of dump files, I think it's time to test the the HDD just to get a feeling of it's health before
we go any further.

   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.

Y not seatools for Windows ?!?!