On 12/04/2012 2:14 AM, Paul wrote:
> That reminds me of "LPM", which was an issue at one time.
>
> http://www.ocztechnologyforum.com/fo...pset-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

On Apr 12, 2:14*am, Paul <nos...@needed.com> wrote:
> 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

On 14/04/2012 10:57 AM, Rick wrote:
> 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

On Thu, 12 Apr 2012 01:49:29 -0400, Yousuf Khan
<(E-Mail Removed)> wrote:

>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...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.

On 03/05/2012 11:07 PM, Loren Pechtel wrote:
> On Thu, 12 Apr 2012 01:49:29 -0400, Yousuf Khan
> <(E-Mail Removed)> wrote:
>
>> 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...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.

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

On 04/05/2012 4:10 AM, Yousuf Khan wrote:
>> 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

Yousuf Khan wrote:
> On 04/05/2012 4:10 AM, Yousuf Khan wrote:
>>> 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.

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

On Fri, 04 May 2012 04:10:33 -0400, Yousuf Khan
<(E-Mail Removed)> wrote:

>On 03/05/2012 11:07 PM, Loren Pechtel wrote:
>> On Thu, 12 Apr 2012 01:49:29 -0400, Yousuf Khan
>> <(E-Mail Removed)> wrote:
>>
>>> 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...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.
>
>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.

On Fri, 04 May 2012 10:30:50 -0400, Paul <(E-Mail Removed)> wrote:

>Yousuf Khan wrote:
>> On 04/05/2012 4:10 AM, Yousuf Khan wrote:
>>>> 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.

Loren Pechtel wrote:
> On Fri, 04 May 2012 04:10:33 -0400, Yousuf Khan
> <(E-Mail Removed)> wrote:
>
>> On 03/05/2012 11:07 PM, Loren Pechtel wrote:
>>> On Thu, 12 Apr 2012 01:49:29 -0400, Yousuf Khan
>>> <(E-Mail Removed)> wrote:
>>>
>>>> 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...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.
>> 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.

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