Good advice given so far, very good.
Just read through the entire thread, was thinking hardware problem from the beginning.
Would like to 'agree' with a few things mentioned already;
1. New hardware can fail.
2. Just because hardware passes a test doesn't mean it's good. Just the way electronics are.
3. At some point you need to test hardware by removing/replacing it.
4. Assuming you have two RAM cards, remove one and see if your system is stable, if not stable then change out the RAM card for the other one in a different slot.
5. Remove the OS HDD, install your OS on another HDD.
6. Remove all devices that are not absolutely required to run your system, ie run bare bones.
The two biggest hardware failures are RAM and PSU.
What PSU do you have?
If you haven't already, check your motherboard for a ground fault, this may require removing the motherboard from the case.
What version of EasyUS did you use? Older versions are not compatible with W8. When re-sizing a partition the program will make a copy, re-size the partition, re-store the copy. If it's not compatible it can result in errors.
Another thought, strange issues like this have been solved by changing the mouse and/or keyboard, if either one is faulty they can and will throw a massive amount of errors, seemingly not possible from these devices. It's worth checking if the usual steps aren't working.
The files you uploaded in post#56 are not usable.
If you upload the BSoD crash report files, I'll analyze them and see if anything else is indicated.
Can you upload the entire BSOD Posting Instructions files, these will help us analyze your crash.
If you can't access through the above program, look in 'C: Windows > Minidump' for the dump files. Copy the files, zip all of them and attach them here.
If you have access to the OS make sure the dump settings are set to small memory dump (Minidump).
Dump Files - Configure Windows to Create on BSOD
Follow steps 1-4 then '6. To have Windows Create a small memory dump (Minidump) File on BSOD', then go to 9&10.
From your previous post:
General possible causes, this is a fairly generic stop code.
STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory
0xC0000005: STATUS_ACCESS_VIOLATION indicates that a memory access violation occurred.
csrss.exe is probably the result of the crash and not the cause, when Windows crashes it tries to find the cause, if it can't then it will list the last process that was running in the faulting string. This is very common in hardware faults.
The Microsoft Client Server Runtime Server subsystem utilizes the process csrss.exe for managing the majority of the graphical instruction sets under the Microsoft Windows operating system. As such Csrss.exe provides the critical functions of the operating system, and its termination can result in the Blue Screen of Death being displayed.
Csrss.exe controls threading and Win32 console window features. Threading is where the application splits itself into multiple simultaneous running tasks. Threads supported by csrss.exe are different from processes in that threads are commonly contained within the process, with various threads sharing resources within the same process. The Win32 console is the plain text window in the Windows API system (programs can use the console without the need for image display).
In mobile devices such as notebooks and laptops, the process csrss.exe is closely dependent on power management schemes implemented by the system as defined under the Control Panel option.
The stack trace is showing faults from the beginning, this is usually due to hardware, in this case likely RAM or HDD.
How much free space do you have in your OS partition?