SSD Setup Tips

[usasma]

Start with:
- Disable automatic defrag (this means you'll have to manually defrag any connected platter-based hard drives - use Task Scheduler)
- Disable Superfetch service
- Disable Prefetch (through the registry)

Details here: http://support.microsoft.com/kb/2727880/en-us?sd=rss&spid=14019
Article is for Win7, but I'd expect it to apply to the other Windows client OS's

Original post in Windows Tips and Tricks forum: https://www.sysnative.com/forums/showthread.php/4276-SSD-Setup-Tips?p=31321#post31321
Please post any additions/comments/etc there.
This copy is closed.

 

[usasma]

Troubleshooting tips from writhziden: https://www.sysnative.com/forums/sh...A-errors-(0x124)?p=23397&viewfull=1#post23397

stucko, have you tried a power cycle with the SSD? I have seen OCZ SSD firmware updates and the like cause problems between the BIOS/SSD interface that can result in 0x124 and 0x7A crashes. Resetting the BIOS/SSD connection can resolve the problem and the steps to do so involve power cycling the SSD. I just gave these steps to another SSD OCZ user, and I gave them to an OCZ user a couple months back getting a 0x124 crash that was resolved with the power cycle.

SSD Troubleshooting:

Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.

1. Power off the system.
2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
6. Let the computer remain in the BIOS for 20 minutes.
7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
8. Leave the drive disconnected for 30 seconds to let all power drain from it.
9. Replace the drive connection(s) and then do steps 4-8 again.
10. Repeat steps 1-4.
11. Start your computer normally and run Windows.

The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community


While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.
​

 

[Fred Garvin]

Just to add a little clarification: The OCZ SSD drive issue below, where the drive disappears, is related to the firmware on M4 SSD drives. The resolution is to update the firmware on the drive. IIRC, the problem has to do with TRIM data not being able to write back to the drive, or find designated free space to write the data.

Troubleshooting tips from writhziden: PCI-E WHEA errors (0x124) - Page 2

stucko, have you tried a power cycle with the SSD? I have seen OCZ SSD firmware updates and the like cause problems between the BIOS/SSD interface that can result in 0x124 and 0x7A crashes. Resetting the BIOS/SSD connection can resolve the problem and the steps to do so involve power cycling the SSD. I just gave these steps to another SSD OCZ user, and I gave them to an OCZ user a couple months back getting a 0x124 crash that was resolved with the power cycle.

SSD Troubleshooting:

Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.

1. Power off the system.
2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
6. Let the computer remain in the BIOS for 20 minutes.
7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
8. Leave the drive disconnected for 30 seconds to let all power drain from it.
9. Replace the drive connection(s) and then do steps 4-8 again.
10. Repeat steps 1-4.
11. Start your computer normally and run Windows.

The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community


While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.
​

 

[writhziden]

True, but sometimes a firmware update will cause those problems to occur until the power cycle is performed after the firmware update.

The 0x124 blue screen crash can happen with any SSD drive, not just the Crucial M4 or OCZ drive, after a firmware update is performed. Sometimes a firmware update will cause the drive detection to become intermittent, and the power cycle will fix that problem and reset the SSD so it works with the new firmware.

 

[writhziden]

Recently found something out that may be useful to hardware and blue screen analysts. We can check a user's SSD firmware version through the perfmon /report output asked for in the blue screen posting instructions. Might make it easier for us to advise whether a firmware update is available.

 

[Corrine]

There has been a lot of controversy about defrag and SSD. Even if you don't want to take the time to read the complete article, note the conclusion from The real and complete story - Does Windows defragment your SSD?, prepared by Scott Hanselman and including information provided through consultation with developers on the Windows storage team:

No, Windows is not foolishly or blindly running a defrag on your SSD every night, and no, Windows defrag isn't shortening the life of your SSD unnecessarily. Modern SSDs don't work the same way that we are used to with traditional hard drives.

Yes, your SSD's file system sometimes needs a kind of defragmentation and that's handled by Windows, monthly by default, when appropriate. The intent is to maximize performance and a long life. If you disable defragmentation completely, you are taking a risk that your filesystem metadata could reach maximum fragmentation and get you potentially in trouble.