Help Analyzing Minidump (BSOD CRITICAL PROCESS DIED)

Hi there, im having a long time problem, that started with windows 10. Sometimes i get CRITICAL PROCESS DIED. it can take a day, or a week to happen. I tried to use sfc /scannow, but didnt help. so i tried a fresh install. no help either. the only think im absolutely SURE that cant be, is a fault memory, since i replaced then with new ones, and the problem persists. here is a dump, that says it could be svchost.exe, but no luck either to find the real problem. searching the internet, i found that some people have the same problem with the same ssd (120gb evo 840) but no use to find a solution. i have another ssd, but i really dont want to use it since its a little slower than the evo, and there is no guarantee that the problem will not happen either.
here is the minidump, any help would be great. thanks!

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*

Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\103115-14000-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is: srv*
Windows 8 Kernel Version 10240 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16545.amd64fre.th1.150930-1750
Machine Name:
Kernel base = 0xfffff803`43016000 PsLoadedModuleList = 0xfffff803`4333b070
Debug session time: Sat Oct 31 18:19:11.752 2015 (UTC - 2:00)
System Uptime: 0 days 0:00:37.433
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...............................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EF, {ffffe0006cbd9840, 0, 0, 0}

----- ETW minidump data unavailable-----
Probably caused by : svchost.exe

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

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

CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffe0006cbd9840, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

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

PROCESS_OBJECT: ffffe0006cbd9840

IMAGE_NAME: svchost.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: svchost

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: svchost.exe

EXCEPTION_CODE: (NTSTATUS) 0x755f0000 - <Unable to get error code text>

BUGCHECK_STR: 0xEF_755f0000

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre

STACK_TEXT:
ffffd000`241cd948 fffff803`436d3b5c : 00000000`000000ef ffffe000`6cbd9840 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`241cd950 fffff803`4360a9b1 : 00000000`00000000 ffffe000`6e827400 00000000`00000000 00000000`00000000 : nt!PspCatchCriticalBreak+0xa4
ffffd000`241cd990 fffff803`4349c589 : ffffe000`6cbd9840 ffffd000`00000001 ffffe000`6cbd9840 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x40101
ffffd000`241cd9f0 fffff803`4349c269 : ffffffff`ffffffff ffffd000`241cda99 ffffe000`6e3d9840 ffffe000`6e827080 : nt!PspTerminateProcess+0xfd
ffffd000`241cda30 fffff803`4316e963 : ffffe000`6e827080 00007ffa`755f0000 ffffe000`6e827080 ffffd000`241cdb80 : nt!NtTerminateProcess+0xb9
ffffd000`241cdb00 00007ffa`9b3137ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000052`77afe7f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`9b3137ba


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION:

FAILURE_BUCKET_ID: 0xEF_755f0000_IMAGE_svchost.exe

BUCKET_ID: 0xEF_755f0000_IMAGE_svchost.exe

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xef_755f0000_image_svchost.exe

FAILURE_ID_HASH: {984ed2b6-513e-7fe5-434c-d1c6f4031710}

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