Force GT Raid0: Sleep problems

[Cooper]

Hello, I have setup a 2x480Gb Force GT Raid0 a few days ago, most recent firmware, and everything seemed to work fine, sleep too. Now in the last 24 hours the pc didn't recover from sleep a couple of times, and I had to reset. There was no blue screen, the monitor just wouldn't turn on.

 

The last time this happened, the system drive (which is on the raid0 setup obviously) got corrupted and had to be fixed with chkdsk. Wrong file records and the like. Actually all the corrupted files were inside an antivirus related folder (GData).

 

So I was wondering, are there still sleep related issues for the Force GT series or should I look into other hardware?

[driverswanted]

It seems like some are still having issues even after firmware update 1.3.3. I have had similar problems (2xForce GT120Raid0) with my setup, I decided to secure erase both SSD and start fresh with new install (total pain). I can report I have not had an issue so far.

 

Have you tried windows "event viewer"? may indicate if you have a hanging driver issue.

[Cooper]

Yes I looked into it but there's nothing. Installing fresh would be the last option, I need to try everything else first.

[Toasted]

-Try updating your chipset drivers.

-We need your system specs.

[Cooper]

Chipset drivers are up to date, downloaded and installed on friday.

[madnisman]

Since you are using 2 SSDs in RAID0, I guess you have Intel RST installed. Have you applied the LPM reg fix?

 

Btw: you can post your system specs in "User CP" -> "Edit System Specs"

[Cooper]

Since you are using 2 SSDs in RAID0, I guess you have Intel RST installed. Have you applied the LPM reg fix?

 

Btw: you can post your system specs in "User CP" -> "Edit System Specs"

 

Thanks, I've added the specs, hadn't noticed the feature.

 

I don't know anything about this fix, I'll search on the forum.

 

EDIT: Ok, I've found out about the fix, but actually I am on a new LGA2011 chipset with Intel C600 raid controller which seems to be quite a departure from older Intel controllers. The configuration software is new and is called RST enterprise (RSTe). So, do I need the fix anyway? This is what I'm seeing in the registry on port0 (they're all the same):

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port0]

"AN"=dword:00000000

"LPM"=dword:00000000

"LPMSTATE"=dword:00000000

"LPMDSTATE"=dword:00000001

"GTF"=dword:00000000

"DIPM"=dword:00000000

[madnisman]

I'm not sure if you need this fix for RSTe driver. The parameters "LPM", "LPMSTATE", "LPMDSTATE" and "DIPM" should be set either to "0" (LPM disabled) or "1" (LPM enabled). "AN" and "GTF" are not existing in my registry. Maybe it's worth to try different setting and see if the freezing issue still occurs.

[Cooperdale]

I'll manually change lpmdstate to 0 on the ssds only and see what happens.

[Cooper]

I just noticed I posted with two different accounts... I'm Cooperdale too. Anyway I haven't gotten another crash post sleep since saturday.

[Jamestee]

I have the same problem with my SSd 120G force 3, when the machine falls to sleep and i try wake it up it all boots ups as normal with exception of my monitor and as of yet cant understand why and how to resolve it.

 

I only installed windows bout a week ago and dnt fancy Reinstalling it

[Toasted]

If you are going to reinstall Windows, I recommend you secure erase your SSD.

[Cooper]

I have re-installed windows, didn't have any sleep problems since Saturday anyway but there were other glitches. This is the first clean windows install I do with the Force GTs as system drive, and there's a strange thing:

 

There is no

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor

 

It looks like Intel latest IRSe drivers don't create this key. I didn't found any port0 and such keys anywhere else in the registry.

 

There are iaStorA, iaStorF and iaStorV keys though, which you can find below in case anyone is interested:

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorA]
"Start"=dword:00000000
"Type"=dword:00000001
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\
 72,00,69,00,76,00,65,00,72,00,73,00,5c,00,69,00,61,00,53,00,74,00,6f,00,72,\
 00,41,00,2e,00,73,00,79,00,73,00,00,00
"Group"="SCSI miniport"
"DriverPackageId"="iastora.inf_amd64_neutral_fa4bad793f7bca10"
"Tag"=dword:00000040

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorA\Parameters]
"BusType"=dword:00000008

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorA\Parameters\Device]
"EnableQueryAccessAlignment"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorA\Parameters\PnpInterface]
"5"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorA\Enum]
"0"="PCI\\VEN_8086&DEV_2826&SUBSYS_84EF1043&REV_05\\3&11583659&0&FA"
"Count"=dword:00000001
"NextInstance"=dword:00000001

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorF]
"Start"=dword:00000000
"Type"=dword:00000001
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\
 72,00,69,00,76,00,65,00,72,00,73,00,5c,00,69,00,61,00,53,00,74,00,6f,00,72,\
 00,46,00,2e,00,73,00,79,00,73,00,00,00
"DriverPackageId"="iastora.inf_amd64_neutral_fa4bad793f7bca10"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorF\Enum]
"0"="SCSI\\Disk&Ven_ATA&Prod_ST33000651AS\\4&15fa6d97&0&020000"
"Count"=dword:00000005
"NextInstance"=dword:00000005
"1"="SCSI\\Disk&Ven_ATA&Prod_WDC_WD30EZRX-00M\\4&15fa6d97&0&040000"
"2"="SCSI\\Disk&Ven_Intel&Prod_Raid_0_Volume\\4&15fa6d97&0&060100"
"3"="USBSTOR\\Disk&Ven_SanDisk&Prod_Cruzer&Rev_7.01\\1101900C6141FD7E&0"
"4"="USBSTOR\\Disk&Ven_WDC_WD30&Prod_EZRX-00MMMB0&Rev_80.0\\0123456789ABCDEF020F&0"

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorV]
"Start"=dword:00000003
"Type"=dword:00000001
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
 74,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,72,\
 00,69,00,76,00,65,00,72,00,73,00,5c,00,69,00,61,00,53,00,74,00,6f,00,72,00,\
 56,00,2e,00,73,00,79,00,73,00,00,00
"Group"="SCSI Miniport"
"DriverPackageId"="iastorv.inf_amd64_neutral_18cccb83b34e1453"
"Tag"=dword:00000019
"DisplayName"="Controller RAID Intel - Windows 7"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorV\Parameters]
"queuePriorityEnable"=dword:00000000
"BusType"=dword:00000008

[madnisman]

I have re-installed windows, didn't have any sleep problems since Saturday anyway but there were other glitches.

 

What are the other glitches?

 

There is no

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor

 

It looks like Intel latest IRSe drivers don't create this key. I didn't found any port0 and such keys anywhere else in the registry.

 

There are iaStorA, iaStorF and iaStorV keys though, which you can find below in case anyone is interested:

 

Right, when installing normal RST driver, the LPM reg key isn't created as well. I needed to add the lines manually. Since I have no experience with Intel RSTe, I cannot tell you if you need the LPM reg fix. But there could be an issue with TRIM command:

 

http://communities.intel.com/thread/26700

 

"Owners of an X79 chipset mainboard need to use the new Intel® RSTe drivers (actual version: 3.0.0.2003 WHQL) instead of the RST ones. Since the Intel® RSTe drivers of the v3.0 series do handle the SSD's as "SCSI Disk Devices" I am wondering, if these drivers really pass through the Trim command to the SSD. This question is only valid for Win7 systems running in AHCI mode."

[Cooper]

What are the other glitches?

 

 

 

Right, when installing normal RST driver, the LPM reg key isn't created as well. I needed to add the lines manually. Since I have no experience with Intel RSTe, I cannot tell you if you need the LPM reg fix. But there could be an issue with TRIM command:

 

Sorry I didn't explain myself better, I meant I didn't reinstall for the standby problem, but other small glitches unrelated to the SSD drives.

 

Anyway there was no standby problem at all since last Saturday. I think my pc woke up at least 30 times this week with no problem.

 

Trim doesn't work with raid so I think any trim problem will not affect my system.

[madnisman]

Trim doesn't work with raid so I think any trim problem will not affect my system.

 

Right, I forgot you are using RAID0.

 

Just to clarify: since the new installation seems to solve your issue, was your first, faulty installation a fresh installation or a cloned one? Have you SecureErased the drive before re-installing Windows?

[Cooper]

Sorry, I had lost track of this thread. The first installation was actually cloned. I have never SecureErased the drive but I'm using DiskKeeper and benchmarks are better now than when the drive was fresh.