C1E,C3,C6/7 BSODs with new 4770k

I would suggest you to disable RAID. How to Disable RAID: 5 Steps - wikiHow

Now boot the computer back. Is it booting OK with all the HDDs detected, including the 300 GB one? If not, enable RAID again and wait for next instruction.

If yes, uninstall Marvell 91xx SATA 6G RAID Controller in Control Panel > Programs and features. Then follow Drivers - Clean Left over Files after Uninstall to get rid of any leftovers of the driver.

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Make it sure that your SSDs are running with up-to-date firmware.

• Crucial C300-CTFDDAC128M
• Samsung 840 SSD.

Let us know how the computer is running now.

____________________________________________________________________________________
BSOD ANALYSIS

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff800038ccb05, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800038ccb05, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003b0c100
GetUlongFromAddress: unable to read from fffff80003b0c1c0
 0000000000000000 Nonpaged pool

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`038ccb05 498b08          mov     rcx,qword ptr [r8]

BUGCHECK_STR:  0x1E_c0000005_R

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  wmpnetwk.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000391f728 to fffff800038d4c00

STACK_TEXT:  
fffff880`0ebeee68 fffff800`0391f728 : 00000000`0000001e ffffffff`c0000005 fffff800`038ccb05 00000000`00000000 : nt!KeBugCheckEx
fffff880`0ebeee70 fffff800`038d4282 : fffff880`0ebef648 00000000`00000002 fffff880`0ebef6f0 fffffa80`151be3f8 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`0ebef510 fffff800`038d2b8a : fffffa80`09cef730 fffff800`038fa210 00000000`00000000 fffffa80`1577e010 : nt!KiExceptionDispatch+0xc2
fffff880`0ebef6f0 fffff800`038ccb05 : 00000000`00000002 fffff800`038e46dd 80000003`46965867 fffff880`0ebef900 : nt!KiGeneralProtectionFault+0x10a
fffff880`0ebef880 fffff800`038e46dd : 80000003`46965867 fffff880`0ebef900 fffff700`01080000 fffffa80`151be3f8 : nt!ExpInterlockedPopEntrySListFault16
fffff880`0ebef890 fffff800`038e13fe : 00000000`00000001 00000000`0462d000 fffff880`0ebefae0 fffff680`00023168 : nt!MiResolveDemandZeroFault+0x14d
fffff880`0ebef980 fffff800`038d2d2e : 00000000`00000001 00000000`0462d000 00000000`00000001 00000000`0462d000 : nt!MmAccessFault+0x5de
fffff880`0ebefae0 000007fe`eb251274 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0244f3b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`eb251274


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`038ccb05 498b08          mov     rcx,qword ptr [r8]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!ExpInterlockedPopEntrySListFault16+0

BUCKET_ID:  X64_0x1E_c0000005_R_nt!ExpInterlockedPopEntrySListFault16+0

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