SSD and Hibernation File Location

[Ken429]

I have a Quad system running W7 Home Premium that is OverClocked and will not work with the Sleep function but works just fine with Hibernation. Now that SSD drives are becoming more affordable has anyone come up with a way to move the Hibernation file to a different physical drive. Based on the number of Googles I've seen this appears to be a common issue.

 

[Jonathan_King]

Unfortunately, there does not appear to be a way to do this.

 

[Mexman]

Hiber is usually disabled with an ssd (conserve ssd space and write activity), should boot almost as fast as waking from hiber.

 

[Ken429]

Good point - problem solved! Thanks for getting back - it is kind of strange that with all the people Googling the issue that I did not see one other response with the all to obvious solution. Hibernation will be grayed out going forward.

 

[Mexman]

Greyed out? you need specific steps to delete it.
http://www.sevenforums.com/tutorials/819-hibernate-enable-disable.html

 

[Ken429]

I understand, I have that thread in my OC bible since I've been in and out of Sleep and Hibernation several times along the way to 4 GHz trying to make the Sleep function work on the Quad system.

 

[Lestrad]

Hibernate and SSD

I installed Windows 7 on an SSD and have had the installation become unbootable four separate times. Now it's unrecoverable. Someone told me that this is because I use Hibernate a lot (I do - every day) and that the writes involved in Hibernating will ruin an SSD. Do you think this is the case, and if so, what can I do to be able to use Hibernate AND have my OS on an SSD? If there's nothing (I know it's impossible to move hiberfile.sys to an HDD where it logically belongs), then what's my alternative other than never using Hibernate?

TIA

 

[Corazon]

Hi Lestrad,

just for future reference, if you could post your issue in a new thread rather than reviving a year-old one (even if it's related), that would be appreciated. It also gives you more visibility and a better chance of getting responses.

As for your SSD, it sounds like you haven't had it for very long. While hibernating would stress the SSD with large blocks of writes - shortening its lifetime, although you'll still get a long time out of it - it shouldn't cause the system to become unbootable.

If you experience various errors in Windows and applications and things just generally seem to go bad before the system stops booting, then there's a good possibility your SSD needs a firmware update to fix bugs leading to data corruption. This seems to apply specificially to some OCZ models.

You might also try using backup software such as Macrium Reflect to image your system to another drive, perform a sanitary erase on the SSD, and then restore the image you made.

 

[Lestrad]

Thanks for you advice and your reply. The drive was purchased in July 2011 and the W7 install dates from July 14. In other words, three months of use - admittedly with almost daily hibernations. The drive is a Kingston SSDNow V100, 128 Gb. DO you think your advice re firmware might apply here? Or is the drive itself defective? SInce it's under warranty I'm going to try to get it replaced.

I did make a drive image with DriveImageXML, but it's of the drive in an unbootable state, so I doubt it'll be of any help.

Thanks again for you willingness to help!
Les

 

[Hopalong X]

Hibernate is one thing almost all if not all SSD manufacturers state to turn off in Windows.

Sleep is okay.

This may not be your porblem though with 128GB of space.

 

[Lestrad]

Hibernate is one thing almost all if not all SSD manufacturers state to turn off in Windows.

Sleep is okay.

This may not be your porblem though with 128GB of space.

But do they say to turn it off to save space on the SSD - knowing that it seems the hiberfile.sys file can't be moved to another disk - or because they know it'll fry the SSD? Because mine is sure acting as if it's fried.

 

[Hopalong X]

To save space mostly. Early SSD's were only 40-60GB so space was at a premium on them.

It won't damage the SSD.

 

[Corazon]

The drive is a Kingston SSDNow V100, 128 Gb. DO you think your advice re firmware might apply here?

I can't really answer that question, having no experience with or knowledge about Kingston SSDs. See what you can find on Kingston's website under support/downloads for your specific model.

If there is a firmware update available, you might be able to read which issues are fixed with it and whether you recognize any as applying to your specific situation.

That will help you decide whether to try the firmware upgrade, although it's usually always a good idea.

 

[Lestrad]

The drive is a Kingston SSDNow V100, 128 Gb. DO you think your advice re firmware might apply here?

I can't really answer that question, having no experience with or knowledge about Kingston SSDs. See what you can find on Kingston's website under support/downloads for your specific model.

I just looked and saw that Kingston has a firmware update for my specifc model that's supposed to clear up malfunctions, and I got all excited... but on looking closer I saw that the label on my drive indicates that it's already been updated at the factory.

So now, going on what you said about how it's not normal to have boot problems after 3 months (by the way, every time I do a full reboot I also get reports of file errors and Diskchk kicks in - I didn't mention that), I'm assuming the disk is defective and sending it back while I still can. I'll post further developments here.

Thanks again for your excellent help
Les

 

[Corazon]

Glad to hear you can get it replaced under warranty - do let us know how the new drive works out. Good luck