Intel Communities: Message List

Re: SSD not working

webadmin@intel.com — Wed, 02 May 2012 00:20:21 GMT

Roger on the drives.

Maybe I'd have an idea if you can reproduce the exact error.

Re: SSD not working

webadmin@intel.com — Tue, 01 May 2012 23:57:36 GMT

Did you install the drivers for the vt6421 pci controller?

Casalini wrote:

But i cannot partition or format it because the system
launch the message formatting not possible or somehing like that.

The exact error message could be helpful.

Re: Why doesn't my BIOS detect my SSD?

webadmin@intel.com — Sun, 29 Apr 2012 20:56:52 GMT

Some notebooks/laptops may have weird BIOS settings/limitations. You'd have to check with the manufacturer.

Re: Why doesn't my BIOS detect my SSD?

webadmin@intel.com — Sun, 29 Apr 2012 19:04:12 GMT

If the drive is not detected in the BIOS it's most likely DOA (Dead On Arrival). Time for an RMA.

Re: Another failing 520 (SSDSC2CW120A310)

webadmin@intel.com — Sun, 29 Apr 2012 18:59:55 GMT

OK, got my replacement drive.

First thing I tried was to fit it in my D820, and this time it fitted (the original drive wouldn't slide all the way in, it seemed the SATA connector was mis-aligned).

Then I cloned my X25-M, and I've been running the drive 4 days without problems, so I suggest anyone with similar problems to just RMA the drive & get a working one!

Re: Another failing 520 (SSDSC2CW120A310)

webadmin@intel.com — Wed, 18 Apr 2012 11:19:56 GMT

OK, I've RMA'd the drive, waiting for the replacement drive (I got it through a friend in the UK, so I have to wait till he post it). lets hope I get a working drive

Re: Superfetch/Prefetch in a system with SSD and HDD

webadmin@intel.com — Wed, 18 Apr 2012 11:17:23 GMT

Have a read here: http://blogs.msdn.com/b/e7/archive/2009/05/05/support-and-q-a-for-solid-state-drives-and.aspx

Be default, Windows 7 will disable Superfetch, ReadyBoost, as well as boot and application launch prefetching on SSDs with good random read, random write and flush performance. These technologies were all designed to improve performance on traditional HDDs, where random read performance could easily be a major bottleneck. See the FAQ section for more details.

Since SSDs tend to perform at their best when the operating system’s partitions are created with the SSD’s alignment needs in mind, all of the partition-creating tools in Windows 7 place newly created partitions with the appropriate alignment.

Re: Question on my SSD usage - I've defragged manually!!!

webadmin@intel.com — Fri, 06 Apr 2012 16:13:31 GMT

Have a look at these two articles:

http://www.helpwithwindows.com/techfiles/Cleaning-Up-After-Windows.html

http://www.helpwithwindows.com/Windows7/Optimize-Windows-7-for-use-with-Solid-State-Drive.html

Windows XP is not the best option for running on an SSD drive.

Another failing 520 (SSDSC2CW120A310)

webadmin@intel.com — Fri, 06 Apr 2012 15:57:41 GMT

I have enjoyed my X25-M drive for nearly a year without any problem, so this month I got myself a 120GB 520 drive... that has turned out to be a disaster so far.

I had installed it as my boot drive, and used Acronis to get an image of my system on the drive. No problem, except I started getting the dreaded BugCheck F4 errors.

My system:

Asus P6T WS Pro (x58)
Sata: Intel ICH10R (rev 12)
Driver: iaStor 10.8.0.1003

1st April: CRITICAL_OBJECT_TERMINATION BugCheck F4, {3, fffffa801174ab30, fffffa801174ae10, fffff800039965f0}

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

2nd April: CRITICAL_OBJECT_TERMINATION BugCheck F4, {3, fffffa8010888b30, fffffa8010888e10, fffff800029db5f0}

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

4rd April: CRITICAL_OBJECT_TERMINATION BugCheck F4, {3, fffffa801183b060, fffffa801183b340, fffff800029d45f0}

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

6th April (#1): CRITICAL_OBJECT_TERMINATION BugCheck F4, {3, fffffa8010844630, fffffa8010844910, fffff800029d15f0}

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

6th April (#2): CRITICAL_OBJECT_TERMINATION BugCheck F4, {3, fffffa80108a8b30, fffffa80108a8e10, fffff8000299c5f0}

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

At that point I had more then enough, and put my trusty X25-M back in my system, re-imaged it and back in (stable) business.

The 'broken' 520 is attached, so I started with a secure erase. After rebooting my system I wanted to check the drive, but again, it was partially missing at show from Disk Manager: and SSD Toolbox:

I had spend the extra $$ to buy Intel in the hope of a quality product, but I'm now quite disappointed.

I'll try to get this drive replaced and see how that goes.

Also noted the crazy SMART details claiming the drive had been on for 102+ years and a gazillion errors (I know, seems an error in interpreting the raw SMART data by the toolbox software, but that is something that should have been fixed by now).

Arie