Recurring BSODs at specific time, then SSD no more detected

Hello and welcome to SF assssn .

The single dump file included in the file uploaded is 0xF4, which is more often than not attributed
to storage related issues. I would like more information if I may.

Please manually check the minidump folder for more dump file:

Code:

C:\Windows\minidump

If dump files are present in that folder copy them to the Desktop, zip and upload in your next post.

Please upload a new MSINFO32 file:

Start → Run → type MSINFO32 then hit Enter.
In MSINFO32 go to, File → Save → name it your user-name.
Once the file is saved right click it and choose Send to → Compressed (zipped) folder.

Attach the file in your next post.


Please export and upload your system event log:

1. Start → type eventvwr → hit Enter.
2. Toggle open the triangle to the left of Windows Logs, right-click on System and choose Save All Events As...
3. 
4. A dialogue box will pop up asking you to name the file and select the save directory, name the file the same as your Seven Forums user-name and save it to the desktop.
5. A second dialogue box will appear asking you to select the Display Information, select Display information for these languages and check the box next to English (if you don't have English automatically offered check the box at the bottom to display additional languages - Show all available languages and check English).
6. 
7. Wait a few moments until the cursor returns to normal. The file will now be on your desktop (given it's the directory it was saved to) UserName.evtx, next to it there will be a folder called LocaleMetaData select both the .evtx file as well as the folder and compress them using Winrar / 7zip and attach it in your next post.

How old is the SSD?
Did you try a different set of SATA / Data & Power?
Did you try a different SATA port on the motherboard?

What is the make, model and age of your PSU?
Fill out this form and post back the result:

• Power Supply Calculator

Hello :) .

The new dumps are all about failing hardware either the SATA port on the motherboard
/ the cables being used / the SSD itself.

Code:

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffffa80064cdb30, Terminating object
Arg3: fffffa80064cde10, Process image file name
Arg4: fffff800033da260, Explanatory message (ascii)

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

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

PROCESS_OBJECT: fffffa80064cdb30

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_RECORD:  fffff88007adeb38 -- (.exr 0xfffff88007adeb38)
ExceptionAddress: 00000000775358e5
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000ff0e3900
   Parameter[2]: 00000000c000000e
Inpage operation failed at 00000000ff0e3900, due to I/O error 00000000c000000e

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.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ERROR_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.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000ff0e3900

EXCEPTION_PARAMETER3:  00000000c000000e

IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

EXCEPTION_STR:  0xc0000006_c000000e

FAULTING_IP: 
+31bbf50
00000000`775358e5 ??              ???

BUGCHECK_STR:  0xF4_IOERR_c000000e

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

FOLLOWUP_IP: 
+31bbf50
00000000`ff0e3900 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

IMAGE_VERSION:  

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_c000000e_IMAGE_hardware_disk

BUCKET_ID:  X64_0xF4_IOERR_c000000e_IMAGE_hardware_disk

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xf4_ioerr_c000000e_image_hardware_disk

FAILURE_ID_HASH:  {f1c8fdae-e969-c285-1e8a-44441903b0fe}

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

0: kd> !dpx
Start memory scan  : 0xfffff88007ade0b8 ($csp)
End memory scan    : 0xfffff88007adf000 (Stack Base)

               rax : 0xfffff88007ade148 : 0xfffff8000338c1ac : nt!NtTerminateProcess+0x20c
               rsp : 0xfffff88007ade0b8 : 0xfffff8000345e392 : nt!PspCatchCriticalBreak+0x92
               rbp : 0xfffff800033da260 :  !da ""Terminating critical process 0x%p (%s).""
               rsi : 0xfffffa80064cde10 :  !da "wininit.exe"
                r9 : 0xfffffa80064cde10 :  !da "wininit.exe"
               r11 : 0xfffff88007ade1c8 : 0xfffff800030d2ad3 : nt!KiSystemServiceCopyEnd+0x13
0xfffff88007ade0b8 : 0xfffff8000345e392 : nt!PspCatchCriticalBreak+0x92
0xfffff88007ade0d8 : 0xfffffa80064cde10 :  !da "wininit.exe"
0xfffff88007ade0e0 : 0xfffff800033da260 :  !da ""Terminating critical process 0x%p (%s).""
0xfffff88007ade148 : 0xfffff8000338c1ac : nt!NtTerminateProcess+0x20c
0xfffff88007ade1c8 : 0xfffff800030d2ad3 : nt!KiSystemServiceCopyEnd+0x13
0xfffff88007ade338 : 0xfffff800030cf070 : nt!KiServiceLinkage
0xfffff88007ade350 : 0xfffff88007ade368 : 0xfffff8000310da9c : nt!KiDispatchException+0x53b
0xfffff88007ade368 : 0xfffff8000310da9c : nt!KiDispatchException+0x53b
0xfffff88007ade6b8 : 0xfffff800030b9cc5 : nt!EtwpReserveTraceBuffer+0xe1
0xfffff88007ade728 : 0xfffff80003064000 : "nt!MmIsSessionAddress <PERF> (nt+0x0)"
0xfffff88007ade758 : 0xfffff800030ebfef : nt!MiInsertPageInFreeOrZeroedList+0x15f
0xfffff88007ade7c8 : 0xfffff8000330d880 : nt!MmFreePageListHead
0xfffff88007ade7f8 : 0xfffff8000316a0b9 : nt!EtwTraceTimedEvent+0xd9
0xfffff88007ade838 : 0xfffff8000310c29c : nt!RtlGetExtendedContextLength+0x14
0xfffff88007ade898 : 0xfffff800030c599c : nt!MiFreeInPageSupportBlock+0x6c
0xfffff88007ade918 : 0xfffff800030c5352 : nt!IoPageRead+0x252
0xfffff88007ade930 : 0xfffff8000310d940 : nt!KiDispatchException+0x3df
0xfffff88007ade9f8 : 0xfffff800030d2ec2 : nt!KiExceptionDispatch+0xc2
0xfffff88007adebd8 : 0xfffff800030d1a3a : nt!KiPageFault+0x23a
0xfffff88007adebe0 : 0x0000000000000000 :  Trap @ fffff88007adebe0

I also see a variety of Disk / Registry errors were logged in the event log, unfortunately the MSINFO32
file is corrupt once more, please try again.

Please look for the latest firmware for the SSD and for a new configuration of the SATA.
Did you try a different set of SATA / Data & Power?
Did you try a different SATA port on the motherboard?