BSOD 0x000000f4 (Dump file)

This crashdump shows that during a disk-to-RAM I/O operation an error occurred that the associated object was not found. What that is exactly, I'm not sure, but I know it involves the drive.

I see that you are using an OCZ drive. Just as a forewarning, OCZ drives are very unstable and often cause a lot of problems, notably being one of the least reliable SSD brands in the industry. There is a very good possibility your drive may be bad. You should first find and download and install any new drivers and firmware for it (firmware is very important!), then run CrystalDiskInfo, take a snapshot of the results and send it to us.

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: fffffa800fd6d060, Terminating object
Arg3: fffffa800fd6d340, Process image file name
Arg4: fffff80002f98460, Explanatory message (ascii)

Code:

0: kd> !process fffffa800fd6d060 3
PROCESS fffffa800fd6d060
    SessionId: 1  Cid: 0260    Peb: 7fffffd8000  ParentCid: 0250
    DirBase: 3c38f3000  ObjectTable: fffff8a00416c930  HandleCount: 403.

The text in green highlights the address in which the process has failed and been terminated. This can be seen within the Stack Text.

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.

Code:

STACK_TEXT:  
fffff880`0c5440e8 fffff800`03020822 : 00000000`000000f4 00000000`00000003 fffffa80`0fd6d060 fffffa80`0fd6d340 : nt!KeBugCheckEx
fffff880`0c5440f0 fffff800`02fcce0b : ffffffff`ffffffff fffffa80`104dcb50 fffffa80`0fd6d060 fffffa80`0fd6d060 : nt!PspCatchCriticalBreak+0x92
fffff880`0c544130 fffff800`02f4bf04 : ffffffff`ffffffff 00000000`00000001 fffffa80`0fd6d060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`0c544180 fffff800`02c98253 : fffffa80`0fd6d060 fffff800`c0000006 fffffa80`104dcb50 00000000`040d0c60 : nt!NtTerminateProcess+0xf4
fffff880`0c544200 fffff800`02c94810 : fffff800`02ce3b7f fffff880`0c544b78 fffff880`0c5448d0 fffff880`0c544c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0c544398 fffff800`02ce3b7f : fffff880`0c544b78 fffff880`0c5448d0 fffff880`0c544c20 00000000`040d1800 : nt!KiServiceLinkage
fffff880`0c5443a0 fffff800`02c98642 : fffff880`0c544b78 00000000`000713b8 fffff880`0c544c20 00000000`040d12d8 : nt! ?? ::FNODOBFM::`string'+0x488a4
fffff880`0c544a40 fffff800`02c971ba : 00000000`00000000 00000000`76d08af4 00000000`040d1201 00000000`000713b8 : nt!KiExceptionDispatch+0xc2
fffff880`0c544c20 00000000`77219c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`040d1220 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77219c12

I found it interesting, that a page fault occurred, which from what I understand (if I'm correct), is when a driver or process references a address which doesn't exist or is available within virtual memory.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• Screenshots and Files - Upload and Post in Seven Forums

Make sure you have the latest firmware for SSD, and ensure all the SATA and Power cables are connected to the drive.

Check for any file system errors and bad sectors using Option #2 of:

• Disk Check

Use this command with Disk Check:

Code:

chkdsk C: /f /r

EDIT: Vir has posted :)

Page faults are commonplace and normal operation, and yes, they occur when the requested virtual memory does not have its true counterpart present in RAM. However, it's during the pagefault in this case that an I/O error occurred when attempting to retrieve the data to put into RAM. Dumping the raw thread stack will show that it's littered with 3 NTSTATUS error codes:

Code:

6: kd> !error c000000e
Error code: (NTSTATUS) 0xc000000e (3221225486) - A device which does not exist was specified.
6: kd> !error c0000005
Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
6: kd> !error c0000006
Error code: (NTSTATUS) 0xc0000006 (3221225478) - 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.

The item of special attention is the first error code, which triggered the rest, in that a specified device (most likely the storage device) does not exist, due to it being inaccessible at the time and was probably offloaded by the system. A common occurrence during hardware failure involving bad drives or bad storage controllers.

Thanks for information Vir :)

Thx alot :)

I will check if new firware is awaible for the SSD and also update driver.

Hope that it will help.

:)