A660 still Blue screens, already 'repaired'​, advice?

Question

I got my a660 late September, early October, and I've been having random blue screens since I got it. I love it; it's very fast, works great... other than the blue screens.
I had been getting stop errors around every day (I spend a lot of time on this thing) before I sent it in during January. I got it back with a repair notice saying 'Hard drive failed tests, needed to be replaced and reimaged. New hard drive passed all tests' then checks by some random tests they do (BIOS and things) where it passed. All seemed well; I got most of my programs reinstalled. However about a week later, I got a blue screen again.
Before the replacement, I had been getting two different stop errors:
Kernel_Data_Inpage_Error of 0x0000007A
and something about a crucial thread terminated with 0x000000F4. This one started up a couple months after the first, so I assume it was the bad sectors on the hard drive that did it.
Both errors still appeared even after a fresh back to box reinstall, with absolutely nothing running.
I haven't seen the crucial thread terminated error yet, but the kernel error has reared its ugly head again.
Here's where it gets tricky. 
I've done two different RAM tests, both showed up clean. I ran the normal Windows one for about 40 hours (10 laps, I think) and the memtest86x one for just over 10 hours, which ended up being 9 laps.
I've had this hard drive, which was tested, for 2 weeks now, so it shouldn't be that. I'm running a checkdisc process later this evening just in case.
I updated a ton of drivers (however not the Intel chipset's, since I can't figure out my exact model)
My worst problem is the fact that when it blue screens, it prepares to write the crash dump but fails, then attempts a restart, where it either just sits at a black screen with the white cursor, or after some time just pops up a partially grey screen that claims the HDD/SDD 'is failed'. Though it's fine with an immediate restart on a power down. I can't get a mini-dump to help check what's causing it, but i've photographed (terribly, on my cell phone) a couple of the errors.
My latest one reads
***Stop: 0x0000007A (0x00000000000000020, 0xFFFFFFFFC0000090, 0xFFFFFA-cut off-
x0000000000000000)
Though this is old, the critical errors said:
Stop: 0x000000F4 (0x0000000000000003, 0xFFFFFA800814CB30, 0xFFFFFA80081-cut off-
-cut off-800037C75D0)
Any ideas? I'm running out of them, and I don't want to send it in, having it missing a month, and get it back not actually repaired, or with a temporary fix. (That and the call centers have really hard to understand accents, and I think they think the same of me. It was very hard for either of us to communicate :C )

Answer 1

I have finally managed a successful dump of a Kernel Data failure.
After doing exessive amounts of testing for everything else, I think I have a faulty connection somewhere?
I used bluescreenview and have a second parameter of 
0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.
Which confirms a bad wire? I've added the minidump to this reply, if anyone can weed anymore information out of it.
I got a new 'error' when it was trying to reboot, stating a "Boot failed" and a quick display of "check cables".
Is this something I could take it to get fixed, I wonder, or will I have to send it in? I want this fixed, since the problem's likely been found, and I really love this laptop otherwise.
Also:
"Something weird about the Intel drivers for Toshiba devices, is that Toshiba modifies the drivers for the intel chipsets, so you cannot use the generic drivers off of the intel website"
Which is my other problem. I can't update because I can't figure out my specific model. There's several a660s available and I don't want to grab the wrong one.
Attachments:
030111-23774-01.dm.txt ‏297 KB