Continuous BSOD no matter what (Minidumps and other data included)

Noel will be on probably tomorrow morning your time.

The CBSPersist files hold the archived CBS.logs - in compressed format.
The only errors in the SFC scan are the expected ones from KB3068708 - which MS have mis-coded so that variable files are coded as static ones. SFC shouldn't even be checking these.
You can either ignore the results, or uninstall KB3068708 and hide it - MS will eventually get around to re-coding and updating the stuff, and it'll reappear in your updates list then.

Great, glad to see Noel fixed it for you. If you have any further problems, we'll still be here. Please let us know in a few days how it is doing.

here are what your last 2 dumps said

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800030b1a70, fffff8800adfa340, 0}
Probably caused by : memory_corruption ( nt!MiGetPreviousNode+10 )
Followup: MachineOwner

The one other thing they both had in common was

Code:

CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff800030b8e12, 0, 20000000020}
Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+c2 )
Followup: MachineOwner

Memory corruption is where we started. You may try uninstalling Chrome for a while and see if that could be the problem, it has been for a few people. Also you may try the sfc scan again

Open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

If you have a spare hard drive or someone you could borrow one from, do a minimal install on it. Just enough to test how it works. Disconnect 1 wire from every other hard drive you have except the one you are installing on and keep them disconnected until you know you do or do not have the same problem. That is the only way you will know for sure if it is the SSD or if you have another problem.

You could also try a bios update, if a newer one is available, and see if that helps.

Also, try posting a screenshot of disk management Disk Management - Post a Screen Capture Image