Random BSOD on new computer build ntoskrnl.exe

Run DM Log collector again, as administrator obviously.

Also, run SF Diag tool too. Attach the result of that one too. Either of them will grab all the files.

Asking for those repetitively, because some other files are more important than crash dumps for stop 0xF4 troubleshooting.

Event[10111]:
Log Name: System
Source: atapi
Date: 2015-07-04T00:28:39.958
Event ID: 11
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Checkered-Venom
Description:
The driver detected a controller error on \Device\Ide\IdePort1.

So it is .....

Code:

Model    Samsung SSD 850 EVO 500GB ATA Device
SCSI Port    1

The driver is msahci, the system native storage controller by microsoft, which never fails itself.

Code:

Name    Intel(R) 9 Series Chipset Family SATA AHCI Controller  - 8C82
Driver    c:\windows\system32\drivers\msahci.sys (6.1.7601.17514, 30.38 KB (31,104 bytes), 6/28/2015 7:51 PM)

So that is an issue from the part of the hardware. Either the SSD itself or the SATA port or connectivity.

A crash dump gives the info in details.

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.

Code:

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

DISK_HARDWARE_ERROR: There was error with disk hardware

So we can say that apparently there is no doubt that the disc hardware is causing the issue. Three things are falling within its scope.

1. The SATA port on the motherboard;
2. The SATA cable; and
3. The disc itself.

Troubleshoot those elements.

1. Apply the disc to another unused SATA port on the motherboard.
2. While doing 1 above, use a new SATA cable. Make it sure that the clips are properly locked at both the ends of the SATA cable. Dont do toolless mounting for now. Use screws to hold the discs with the stand, and dont leave a loose screw or an unused screw hole.

See how it goes after doing upto that stage. If things does not change, we have to go for the third possibility there.

3. The firmware is up-to-date, the SMART data is OK, still a SSD can fail. And we cannot test a SSD with the conventional disc check tools like Seatools or WinDFT. So if the issue continues even after doing 1 and 2 above, create a partition on the WD 1 TB (there is huge free space), install windows there and see how it goes. That's how we can isolate the SSD to be failing or not.

Krait killa said:

Are you sure it's the SSD?

I am just another guy trying to help you based on your data and my knowledge, man! I am not the God.

If you need surety from me .... both of us are in the wrong place.

Krait killa said:

Ok, so I can now 100% confirm that the SSD is not the cause of the blue screen. A while after I secure erased it, I got a BSOD. I completely removed it from the PC and decided to see If I would get any more blue screens. Eventually I did.

If you got both the discs corrupt .... that will be extreme. Still, test the HDD with WD Data Lifeguard .... taking the short test and the extended test.

If you get hard disc corruption on two different discs attached to two different ports with two different SATA cables, then I have nothing left to suggest you but replacing the motherboard.