SSD upgrade to LE1700?

[John Hill]

At Allegiance, we have been getting a lot of requests from our customers to upgrade their LE1700s with an SSD. Researching on the web provides a lot of conflicting information so I just bought 2 of them to test out. I expect them to arrive in a couple days and will post about our success or failure. We have put the PhotoFast in an LS800 and I expect it to work fine in the LE1700.

[Bartman]

Okay, I have disabled TRIM now. With this command:

fsutil behavior set DisableDeleteNotify 1

The Runcore 64 GB is still installed. I wonder if disabling TRIM has an effect on the infrequent BSOD crashes. If not I am convinced that Runcore is overpriced crap.

Disabling TRIM seems to work for others, though. Please read this:

http://forums.tweaktown.com/f78/blue...f-1-8-a-37568/

l am not alone with a Runcore that has BSOD issues. It's my 2nd one with this problem. The first had the old 1819 and the new one has the 1916 Firmware.

[Maiklas3000]

Are you able to run wipe? And are you using 32- or 64-bit Window7?

[Bartman]

32 bit Windows 7 and what is it and where do I find this wipe command?

[Maiklas3000]

Get wiper from OCZ:
http://www.ocztechnologyforum.com/fo...ith-Wiper-0525

Or from Gskill:
http://www.xtremesystems.org/forums/....php?p=3784347
(see http://forum.eeeuser.com/viewtopic.php?pid=653852)

The Runcore IV has the same Indilinx controller as the OCZ and Gskill versions, which is why wiper still works.

Do crystaldiskmark before and after wiper to see if it improves performance.

Or wait for me to receive my Runcore and I can test wiper on it.

[Bartman]

I got more BSOD crashes with the Runcore, even after disabling TRIM:



On Mon 29.03.2010 06:46:25 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0x87F45538, 0x82D5BAE0, 0x87E14508)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\Windows\Minidump\032910-10857-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 28.03.2010 20:11:12 your computer crashed
This was likely caused by the following module: nwusbser.sys
Bugcheck code: 0x44 (0x852C7BC8, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
Dump file: C:\Windows\Minidump\032810-14508-01.dmp
file path: C:\Windows\system32\drivers\nwusbser.sys
product: Novatel Wireless USB Modem/Serial Device Driver
company: Novatel Wireless Inc.
description: Novatel Wireless USB Modem/Serial Device Driver

I did install the Sprint software for the Novatel! Wireless after the first crash.

[Maiklas3000]

Sorry to hear your troubles, especially because they could soon be my troubles. (My Runcore is on order.)

This is interesting:
http://www.sevenforums.com/drivers/2...e-failure.html

One guy with a very different system except with a twin of the Runcore (Super Talent, also Indilinx-based) had the same problem.

The obvious thing to try is to disable the WWAN card in Bios or by removing it. I don't have an SSD yet, but my (European) WWAN card causes me some boot failures.

The other thing that sticks out in that discussion is that hibernate seems to be required to trigger the problem. So, try sleep instead of hibernate, or vice versa.

This is also interesting:

http://www.sevenforums.com/crashes-d...-shutdown.html

The freefall protection on his laptop seemed to be the source of his problems. I seem to recall Motion strongly advising against using Motion DataGuard with an SSD, I think going so far as to say it would cause crashes. Do you have DataGuard?

If those ideas don't help, head over to sevenforums.com and post your info.

[Bartman]

Hmm, I had a Toshiba 60 GB PATA drive in my LE1700 for months while I was waiting for the replacement Runcore. No crash, no freeze with the normal hard drive.

Since I am using those two Runcore drives I had nothing but trouble. Well not always, boot time was great and everything is very snappy. The speed is excellent but the BSOD errors are not tolerable. I tried putting the LE1700 to sleep and yes the crashes occur usually during daytime when I am at work. When I get home there is either a BSOD or the system froze while been in standby. Somehow the system managed to get a BSOD in Sleep mode.

Dataguard does not seem to be active, at least I can't do anything with the button in the Motion Dashboard.

:-) Weird. I had WWAN disabled and it did not help either.

This is the crash message from today (found the LE1700 frozen and I had to hold the power switch for more than 5 seconds to resume):

On Wed 31.03.2010 22:20:34 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0x869B9908, 0x82D3BAE0, 0x85D2FCC0)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\Windows\Minidump\033110-13182-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

[Maiklas3000]

I don't have DataGuard installed, and I don't see any sort of mention of it in Dashboard. Check in add/remove programs and in services.

Check all your drivers. Nothing in device manager with an exclamation point? No optional updates for drivers in Windows Update?

In a few days, I'll be able to try it out on mine, which might help diagnose yours. Not much difference, but mine is 64-bit and never had DataGuard.

[Bartman]

Wow I do have Dataguard installed, removing it now. I hope this helps.

All drivers, except for the fingerprint reader, are the latest. I have checked this with DriverMax. In addition to this, everything is recognized in the Device Manager.

No, it was not the Dataguard feature.

I got another crash this morning:

On Fri 02.04.2010 07:31:21 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0x87F43768, 0x82D39AE0, 0x85DE6AB8)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\Windows\Minidump\040210-10264-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

And my next crash, I think it is time to pull the plug.

On Sun 04.04.2010 07:26:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0x87B19030, 0x80D8ADB0, 0x85A178C8)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\Windows\Minidump\040410-11200-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.