new 2.5 SSD on thinkpad, windows 7 x64; need a complete burn test solution

[fire400]

thinkpad t420s
lite-on mSATA (LMH-256V2M-11)
how reliable is this WD software? my windows 7 x64 pro OS keeps telling me there are drive errors on an mSATA. i've wiped the drive clean with 1's and 0's and did a short and long test on the drive. all passed clean. put a vanilla win7 on the drive. still, win7 is saying it detects drive errors in win7. using webroot as internet security. i let someone borrow the laptop and a couple days later this was happening. they claimed they just checked their e-mail and did taxes. not sure what to do?

product key is activated. drivers are directly from Lenovo.
tested the mSATA on a DOS based SSD tool, and all tests passed.
this is the 3rd t420s laptop in less than a year, and so far this 3rd unit, the system does not like win7, for some odd reason. set it up the same way as the 1st and 2nd one.

thinking maybe the motherboard might be bad or some really bad malware?
ran intel-burn-test on win8.1 with all drivers installed on a 2.5" AHCI SSD in the hard drive slot, 8+ hours on 16gb DDR3 RAM (NEW), everything was stable and ran fine.

i've already setup CMD to skip scanning, but the maintenance tab in win7 keeps telling me the drive has errors on it.
and i run SC: Broodwar on the laptop for several hours at a time without the system freezing or shutting down.

any ideas?

 

[VirtualLarry]

Checked with CrystalDiskInfo yet?

 

[fire400]

i have a PNY CS1311, and the health status is GOOD.

the liteon for health status is UNKNOWN.
power on count: 478 count
power on hours: 39 hours
features: smart, AAM, NCQ, TRIM, DEVSLP

under atr names: currents are all maxed at 100 and the worsts are maxed at 100, thresholds are all 0.

i'm guessing the drive is or might be a 3rd party buy out for NOT PASSING QA and just sold to the open market because I got it on eBay.

oh well, not like SSD's are invulnerable, I'm probably going to return it or toss it. but I don't know I want to risk running a potential soon-to-be-ghost drive and lose data or work on a hardware-misfire OS blackout?

 

[VirtualLarry]

Hmm. Has Win7 64-bit always given the warning, since you installed the lite-on mSATA?

I'm just wondering, you've done read and write tests on it, and it passed.

If CDI says "Health: Unknown", then maybe it's an OEM drive, and doesn't support a full complement of SMART data readings, and maybe Windows is trying to read SMART to calculate health, and can't, so it's puking, even if there's nothing really wrong with the drive?

Has anything actually crashed, or reported a disk or paging error on that drive?

What does the Windows System Event Log report?

 

[VirtualLarry]

how reliable is this WD software?

By "WD" do you mean Western Digital, or Windows Diagnostic? I wouldn't trust Western Digital software to diagnose anything but their own-branded drives.

 

[fire400]

western digital tools.

event log:
The driver detected a controller error on \Device\Harddisk2\DR2.

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Disk" />
<EventID Qualifiers="49156">11</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-21T23:34:43.461470600Z" />

I went to look at the storage controller, it's from the Lenovo website, "2015" IRST, updated it, and the driver dates back to 2012.

this was the install history of the laptop software stacking:
win x64 pro SP0, upgraded to SP1 offline, security software, drivers installed, minimal lenovo apps, windows updates.

haven't had issues with m3 or m6, but this LMH - V2M is being a pain in the face. i'm going to have to pull it and try it on another laptop if it keeps doing this. i think so far it's doing okay, but the error log was from earlier today. i will run a long max-burn-test to see if the t420s can handle it.

link:
http://www.liteonssd.com/CONSUMER-SATA-SSD/item/CONSUMER-MSATA/zeta-msata.html

 

[XavierMace]

It's more than likely a Dell pull and Dell's know for putting firmware on a variety of things that cause problems when running in a non-Dell system.

 

[fire400]

"It's more than likely a Dell pull and Dell's know for putting firmware on a variety of things that cause problems when running in a non-Dell system."
I contemplated something similar, probably why it's next to impossible to find firmware updates for this mSATA chip.

Ran Intel burntest on stress level of maximum for several-plus hours, system ran fine.
Could be a motherboard glitch on the controller interconnect?

eBay seller is willing to ship me another unit, or offer a refund. i'll just return it and get something else.