SSD freezes from time to time

[Yousuf Khan]

That reminds me of "LPM", which was an issue at one time.

http://www.ocztechnologyforum.com/f...AHCI-mode-on-Intel-6-series-Chipset-platforms

I suppose the thinking goes, "where would the fun be if
you didn't have to tweak something". :-(

You'd think the SSD manufacturers, could come up with an "SSD ready"
software, to pre-check these things for you. Instead of this week long
"search the web for hints" thing the customers have to do now. That
way, they could encapsulate all they've learned about their product
versus Windows or Linux.

This does sound like a very similar issue. I noticed in the LPM issue
one of the registry entries was for DIPM.

I suppose I could test to see which setting in particular caused the
issue, the HIPM or the DIPM, but having them both disabled fixed it, and
I don't think I'm that concerned about energy savings on a desktop, like
I would be on a laptop.

Yousuf Khan

 

[YKhan]

You'd think the SSD manufacturers, could come up with an "SSD ready"
software, to pre-check these things for you. Instead of this week long
"search the web for hints" thing the customers have to do now. That
way, they could encapsulate all they've learned about their product
versus Windows or Linux.

Also, I don't think the power issue is necessarily a problem with the
SSD, it could be an issue with the motherboard chipset, or even
cabling between drive and motherboard for all we know. So it's not an
issue that affects all installations, just a large number of them.

Yousuf Khan

 

[Yousuf Khan]

Intel just released an update for their 320 SSD if that is the one you have you might check it out

Nope, that's not my drive, but the problem has been solved. It turns out
that it was an obscure power management setting in the AHCI drivers
called HIPM-DIPM. Once those settings were turned off, the freeze-ups
went away.

Yousuf Khan

 

[Loren Pechtel]

You need to set a key in the Registry to allow this feature to be
accessed by the Power Management advanced options. You need to go to the
following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\0b2d69d7-a2a1-449c-9680-f91c70521c60

And set the "Attributes" field to a DWORD of 0x2.

You can then follow this article on what to do to disable it:

http://www.sevenforums.com/tutorials/177819-ahci-link-power-management-enable-hipm-dipm.html

I followed the article, and switched back to the AHCI drivers, and no
longer had any freeze-up problems.

Yousuf Khan

I wish that was the answer for me.

The 0b2d... section of the key doesn't exist on my box.

The link shows an option that's not on my system, either.

 

[Yousuf Khan]

I wish that was the answer for me.

The 0b2d... section of the key doesn't exist on my box.

The link shows an option that's not on my system, either.

If it doesn't exist, then create it. In my case, though that
"0b2d...1c60" key did exist, the "Attributes" field underneath it didn't
exist. So I created that one. Now, everything is fine. You'll simply
have to create the key and then the field too.

It seems that not all registry entries are created by default on all
machines, and are only created on an as needed basis, otherwise default
values are taken.

Yousuf Khan

 

[Yousuf Khan]

If it doesn't exist, then create it. In my case, though that
"0b2d...1c60" key did exist, the "Attributes" field underneath it didn't
exist. So I created that one. Now, everything is fine. You'll simply
have to create the key and then the field too.

It seems that not all registry entries are created by default on all
machines, and are only created on an as needed basis, otherwise default
values are taken.

Yousuf Khan

BTW, this is what my registry looks like in that section (you can copy
and paste):

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\0b2d69d7-a2a1-449c-9680-f91c70521c60]
"FriendlyName"=hex(2):41,00,48,00,43,00,49,00,20,00,4c,00,69,00,6e,00,6b,00,20,\

00,50,00,6f,00,77,00,65,00,72,00,20,00,4d,00,61,00,6e,00,61,00,67,00,65,00,\

6d,00,65,00,6e,00,74,00,20,00,2d,00,20,00,48,00,49,00,50,00,4d,00,2f,00,44,\
00,49,00,50,00,4d,00,00,00
"Description"=hex(2):43,00,6f,00,6e,00,66,00,69,00,67,00,75,00,72,00,65,00,73,\

00,20,00,74,00,68,00,65,00,20,00,4c,00,50,00,4d,00,20,00,73,00,74,00,61,00,\
74,00,65,00,2e,00,00,00
"IconResource"=hex(2):00,00
"Attributes"=dword:00000000

 

[Paul]

If it doesn't exist, then create it. In my case, though that
"0b2d...1c60" key did exist, the "Attributes" field underneath it didn't
exist. So I created that one. Now, everything is fine. You'll simply
have to create the key and then the field too.

It seems that not all registry entries are created by default on all
machines, and are only created on an as needed basis, otherwise default
values are taken.

Yousuf Khan

BTW, this is what my registry looks like in that section (you can copy
and paste):

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\0b2d69d7-a2a1-449c-9680-f91c70521c60]

"FriendlyName"=hex(2):41,00,48,00,43,00,49,00,20,00,4c,00,69,00,6e,00,6b,00,20,\


00,50,00,6f,00,77,00,65,00,72,00,20,00,4d,00,61,00,6e,00,61,00,67,00,65,00,\


6d,00,65,00,6e,00,74,00,20,00,2d,00,20,00,48,00,49,00,50,00,4d,00,2f,00,44,\

00,49,00,50,00,4d,00,00,00
"Description"=hex(2):43,00,6f,00,6e,00,66,00,69,00,67,00,75,00,72,00,65,00,73,\


00,20,00,74,00,68,00,65,00,20,00,4c,00,50,00,4d,00,20,00,73,00,74,00,61,00,\

74,00,65,00,2e,00,00,00
"IconResource"=hex(2):00,00
"Attributes"=dword:00000000

An alternating sequence of 00 and non 00 hex value, is a Unicode text string.
A person seeing the above, might conclude it was "complicated and scary", when
in fact that could be a device name, a file path name, and so on.

For fun, let's translate this much. There are ten non-zero items, and
those correspond to ten ASCII letters/numbers.

41,00,48,00,43,00,49,00,20,00,4c,00,69,00,6e,00,6b,00,20 = "AHCI Link "

You can get an ASCII table from a UNIX man page, to finish the translation
process, and understand what is stored there. Unicode encoding is a nuisance,
but it's here to stay. The 41 is 0x41 hex, so you use the hex column when
translating to ASCII.

http://unixhelp.ed.ac.uk/CGI/man-cgi?ascii+7

Paul

 

[Loren Pechtel]

If it doesn't exist, then create it. In my case, though that
"0b2d...1c60" key did exist, the "Attributes" field underneath it didn't
exist. So I created that one. Now, everything is fine. You'll simply
have to create the key and then the field too.

Created, I'll see what happens. I *HATE* these blue-screens!

It seems that not all registry entries are created by default on all
machines, and are only created on an as needed basis, otherwise default
values are taken.

The thing is the AHCI settings in the URL don't show up on my machine
either.

 

[Loren Pechtel]

I wish that was the answer for me.

The 0b2d... section of the key doesn't exist on my box.

The link shows an option that's not on my system, either.

If it doesn't exist, then create it. In my case, though that
"0b2d...1c60" key did exist, the "Attributes" field underneath it didn't
exist. So I created that one. Now, everything is fine. You'll simply
have to create the key and then the field too.

It seems that not all registry entries are created by default on all
machines, and are only created on an as needed basis, otherwise default
values are taken.

Yousuf Khan

BTW, this is what my registry looks like in that section (you can copy
and paste):

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\0b2d69d7-a2a1-449c-9680-f91c70521c60]

"FriendlyName"=hex(2):41,00,48,00,43,00,49,00,20,00,4c,00,69,00,6e,00,6b,00,20,\


00,50,00,6f,00,77,00,65,00,72,00,20,00,4d,00,61,00,6e,00,61,00,67,00,65,00,\


6d,00,65,00,6e,00,74,00,20,00,2d,00,20,00,48,00,49,00,50,00,4d,00,2f,00,44,\

00,49,00,50,00,4d,00,00,00
"Description"=hex(2):43,00,6f,00,6e,00,66,00,69,00,67,00,75,00,72,00,65,00,73,\


00,20,00,74,00,68,00,65,00,20,00,4c,00,50,00,4d,00,20,00,73,00,74,00,61,00,\

74,00,65,00,2e,00,00,00
"IconResource"=hex(2):00,00
"Attributes"=dword:00000000

An alternating sequence of 00 and non 00 hex value, is a Unicode text string.
A person seeing the above, might conclude it was "complicated and scary", when
in fact that could be a device name, a file path name, and so on.

Remember, though, the people in here have mostly built their own
rigs--such stuff won't be so scary.

Not to mention that I have written code professionally for more than
20 years. It's not one bit scary.

 

[Paul]

Created, I'll see what happens. I *HATE* these blue-screens!


The thing is the AHCI settings in the URL don't show up on my machine
either.

Any chance the GUIDs are specific to brands of chipsets ?
Are you and Yousef using the same chipset ?

Can you search in Regedit, for a Unicode string, like "ACPI Link" etc ?
That's what I don't like about Unicode, is there aren't necessarily good ways
of doing searches. In one case, I had to write my own program, to do
such a search, when debugging a problem.

Paul

 

[Yousuf Khan]

BTW, this is what my registry looks like in that section (you can copy
and paste):

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\0b2d69d7-a2a1-449c-9680-f91c70521c60]

"FriendlyName"=hex(2):41,00,48,00,43,00,49,00,20,00,4c,00,69,00,6e,00,6b,00,20,\


00,50,00,6f,00,77,00,65,00,72,00,20,00,4d,00,61,00,6e,00,61,00,67,00,65,00,\


6d,00,65,00,6e,00,74,00,20,00,2d,00,20,00,48,00,49,00,50,00,4d,00,2f,00,44,\

00,49,00,50,00,4d,00,00,00
"Description"=hex(2):43,00,6f,00,6e,00,66,00,69,00,67,00,75,00,72,00,65,00,73,\


00,20,00,74,00,68,00,65,00,20,00,4c,00,50,00,4d,00,20,00,73,00,74,00,61,00,\

74,00,65,00,2e,00,00,00
"IconResource"=hex(2):00,00
"Attributes"=dword:00000000

An alternating sequence of 00 and non 00 hex value, is a Unicode text string.
A person seeing the above, might conclude it was "complicated and scary", when
in fact that could be a device name, a file path name, and so on.

For fun, let's translate this much. There are ten non-zero items, and
those correspond to ten ASCII letters/numbers.

41,00,48,00,43,00,49,00,20,00,4c,00,69,00,6e,00,6b,00,20 = "AHCI Link "

Yeah, I know I noticed that too, but that's how it got saved when I
exported it from the regedit as a *.reg file. But when I was viewing it
in the regedit itself it was simply text.

Yousuf Khan

 

[Yousuf Khan]

Any chance the GUIDs are specific to brands of chipsets ?
Are you and Yousef using the same chipset ?

Can you search in Regedit, for a Unicode string, like "ACPI Link" etc ?
That's what I don't like about Unicode, is there aren't necessarily good ways
of doing searches. In one case, I had to write my own program, to do
such a search, when debugging a problem.

Paul

I'm simply using the standard Microsoft AHCI and/or IDE drivers. When
using the IDE drivers, these power management fields don't show up,
because that sort of power management didn't exist in that generation of
the ATA specifications, i.e. version 7, so the registry entries for
power management are simply ignored. But when you go upto the newer
Microsoft AHCI drivers, which is ATA version 8, these specs include this
power management, so if the registry entries exist, and there is a value
set for them, then it'll take effect.

On the other hand, if he's using something other than the standard
Microsoft drivers, such as the Intel drivers, then these entries may or
may not have any effect. The original webpage I linked to mentioned that
these settings don't have any effect except with Intel ICH9M drivers and
later.

Yousuf Khan

 

[Yousuf Khan]

The thing is the AHCI settings in the URL don't show up on my machine
either.

If you've taken my registry settings, then chances are that you won't
see the link power management options show up, because I've set the
"Attributes" field to a value of zero. This setting should disable the
link power management feature for all power schemes, by default. So you
*won't* see those settings in the power management settings.

However, if you do want to see those settings, then you'll have to set
the Attributes field to a value of 2, and then all of those settings
will show up, provided you're using the Microsoft AHCI drivers for your
disks. But then you'll have to edit and disable the power management in
each of your power schemes individually. That's because after you set
the Attributes field to 2, the link power management then becomes a
local setting for each power scheme, rather than a global setting for
all of them.

Yousuf Khan

 

[Loren Pechtel]

Any chance the GUIDs are specific to brands of chipsets ?
Are you and Yousef using the same chipset ?

Note that I said the settings in the *URL*--a link to an article with
some screenshots. Those settings don't show up here.

While I do agree it's likely chipset related I don't think it's just a
matter of different keys.

 

[Loren Pechtel]

If you've taken my registry settings, then chances are that you won't
see the link power management options show up, because I've set the
"Attributes" field to a value of zero. This setting should disable the
link power management feature for all power schemes, by default. So you
*won't* see those settings in the power management settings.

However, if you do want to see those settings, then you'll have to set
the Attributes field to a value of 2, and then all of those settings
will show up, provided you're using the Microsoft AHCI drivers for your
disks. But then you'll have to edit and disable the power management in
each of your power schemes individually. That's because after you set
the Attributes field to 2, the link power management then becomes a
local setting for each power scheme, rather than a global setting for
all of them.

They were missing before I made the registry changes.

 

[Loren Pechtel]

On the other hand, if he's using something other than the standard
Microsoft drivers, such as the Intel drivers, then these entries may or
may not have any effect. The original webpage I linked to mentioned that
these settings don't have any effect except with Intel ICH9M drivers and
later.

I'm using the Intel driver--it's what came with the motherboard, I
didn't even know there was a useable Microsoft option.

 

[Yousuf Khan]

I'm using the Intel driver--it's what came with the motherboard, I
didn't even know there was a useable Microsoft option.

Try switching over to the Microsoft drivers, if you're not using Intel
RAID or anything like that.

Yousuf Khan

 

[Yousuf Khan]

They were missing before I made the registry changes.

That doesn't matter.

Yousuf Khan

 

[Loren Pechtel]

Try switching over to the Microsoft drivers, if you're not using Intel
RAID or anything like that.

I am using the RAID. Sys is a SSD, data is RAID 1.

 

[Yousuf Khan]

I am using the RAID. Sys is a SSD, data is RAID 1.

Then you have no choice, but to keep using it. You could of course,
break the mirror and mirror it instead through the Microsoft dynamic
disk system.

Yousuf Khan