A09 Diag and Crucial C300 SSD Drive

Hi All

I installed a new (sealed) Crucial C300 256GB SSD drive in HD0

when I do the diagnostic test it is failing when trying the DST Hard Disk short test as in picture below

Any Idea why please ?

 

You've installed Windows on it and it works other than this? Or it won't boot at all?

 

i have a M17X and the C300 and when i first install it don't show on the bios but after i install windows it shows on the bios and everything is perfect now

 

It boot perfectly in windows but it fails in diag. as said above

below it the C300 compared to stock seagate 500Gb 7200Rpm

 

Does your Diag Test software reconize the SSD by model and part number ?

 

The diag i am (included in BIOS A09) using does not detect any HD by name at this stage (not even stock HD)

 

why you want to run the diagnosis ? do you see any problems in windows

 

well IMO your Diag sw is not up to date, and thats why your getting the errors.

If you can boot into windows, and it runs fine, your OK

 

Agree with Dave. If it ain't broke, don't fix it. SSDs are still somewhat new technology. There will be some growing pains.

 

Spider, if you really want to retest the drive using Dell's 32-bit Diag, download this and install to a USB flash drive. Boot from the USB flash and retest your system.

Drivers and Downloads

This version is the last updated version - although it states it is for the AW desktops, it will work fine with the AW Notebooks.

As others have mentioned, if it boots into windows and doesn't present any issues, do not worry about it.

 

Hope you fix the problem spider.. Me to was thinking of buying this ssd. If you fix it please write what you did and hopefully its just something simple..

Chears mate

 

Thanks BatBoy

I tested the diag software you linked,

Personally I think that BIOS A09 is far from ready when it comes to SSD Drives.

it still hangs with errors even when doing the short tests. (I tried 2 new SSD's and both failed the short test)

 

It may just be the Diag - it hasn't been updated recently... Could be the BIOS - but if the only error/hang you see is with the Diag and no issues within windows, the Diag app is the most likely cause.

Anyone else seeing this with the diag partition with SSDs (Dell or other brands)? If another SSD owner can confirm then its safe to say its the Diag app and NOT your drive. Only takes a moment folks - anyone with an SSD and 17xR2, boot up with F12 and select the diagnostics option.

Were both the SSDs you tested the Crucial C300 model?

 

Thanks for your reply

yes, windows and benchmarking are working fine . . I did the diag just for info. (hopefully SSD issues will be polished further)

will test again on new BIOS

Edit:

one thing that worries me is that if I set the SATA Operation to ATA instead of AHCI (in BIOS)

the laptop hangs on POST

setting it to ATA is required if there is a drive firmware upgrade

 

Spider, might be an issue with your Crucial drive(s) -

 

yes it could be,(but I doubt it) what I find strange is that it happens on both my c300 256GB SSD, purchased from 2 different places one of them is a month older then the other (was with firmware V0001 which I updated on my Main PC)

both drives pass diag test if tested on my main pc with ASUS Striker II Extreme mainboard

 

Could just be the Crucial F/W... perhaps there is an incompatibility with Crucial C300 drives and the AW/Dell Diag app. Oh well, as long as its working. Sorry can't be definite for you. Good that you are up and running though... Have fun!

 

Thanks for your help in these forums

Yes, in real life I have no problems at all with C300 when using the M17xR2

 

Q:

Is there any windows tool that can test an SSD please ?

 

See this app:
Crystal Dew World

 

Thanks

I have used that tool in post #4 of this thread

what I need is a tool to check drive integrity (but my english is crap lol !!)

 

It doesn't hang, it's slow as hell.

I know it, because I had the same feeling when I updated my C300 firmware to 002.

By the way, I used the USB method, my DVD drive was not recognize while in ATA/IDE mode.