M225 warranty advice.

jakspyder

jakspyder

jakspyder

Soldato
Joined
12 Aug 2008
Posts
3,043
Location
London
Hey guys, recently iv been getting a lot of BSODs totally out of the blue. No pun intended, im currently incapable of humour! :mad:

Initial thought was probably an unstable overclock. So i spent hours tinkering in the bios. refining settings lowering clocks stress testing. No BSODs! Excellent. So on i go and a few hours in BSOD again. Here rage starts setting in. Eventually i drop all overclocks and continue to get them! :mad:

Using a tool i forget the name of, I managed to find that the BSOD was due to "CRITICAL_OBJECT_TERMINATION" And according to the internet this is a problem with my OS being unable to read files. Ok perhaps windows screwed up so im on a fresh install, problem still there. fresh install on my mechanical drive. Problem solved!

So this leads me to believe my 128gig crucial M225 is kaput!

SSD life shows it as in excellent health. But the bar that the bottom says 24% (low in my opinion for something in excellent health!)

With only 10k hours of use it would appear as though the drive has degraded a lot. It is an old drive and would I be able to return it under warranty?


Sorry for the long story.

TL:DR SSD seems to be degraded, causing BSODs. Do I have enough grounds to return under warranty or will i be charged shipping back and be stuck with it? Do they still make the M225 and if not would I get a sneeky upgrade? Afterall it costs me £280 back then Inc VAT :/
 
The M225's, crucials first SSD's came with 5 years warranty.
from reading around the drive you get back may be an M4 :)

But ideally you need to do some more testing to support your theory of it being the drive at fault.
Try new sata cable, plugged into a different port, HDTune error check etc etc. After that email them and explain your problem and let them decide.
 
Ok I'v tried different cables and different sata ports. Issue is still there. Downloaded and ran HDTune. The "(C7) Ultra DMA CRC Error Count" is showing status Warning.

When doing an error scan, I blue screen every time.

Anything else I can do before I contact Crucial and see what they say?
 
CRC error's are usually cased buy a bad controller either board or drive or the cable in between. Also as above bad memory may impact on this too.

First thing to do would be to grab yourself memtestpro or memtest86+ and leave your memoory testing for several hours, just to rule it out
 
You must log in or register to reply here.
Back
Top Bottom