XPS 17 L702X with Win7 SP1 (and vertex 3) resume always crashes with BSOD (BugCheck)

Discussion in 'Dell XPS and Studio XPS' started by joco, Apr 10, 2011.

Thread Status:
Not open for further replies.
  1. joco

    joco Notebook Consultant

    Reputations:
    2
    Messages:
    176
    Likes Received:
    2
    Trophy Points:
    31
    Currently i always have a problem when i resume from suspend.
    Then a few seconds later it crashes with a BSOD, most of the time with a BugCheck error code 0xf4

    i think it is related to this:

    BSoD 0x000000f4 Windows 7 SP1 installed on an SSD on Dell Studio 1555 waking from sleep or hibernation

    there they are talking about changing stuff like:

    Boot into BIOS Setup
    Go to Power options
    Change the "ACPI S3 Hard Disk Reset" option to "Enable"

    and that is a problem because we don't have any power options in the bios.. At least i can't find them

    What does seem to work for me is going to hibernate and resuming from that. (but i do need to test that a bit more)

    It looks like something doesn't want to wake up from sleep or something like that. I also installed the hotfix they are mentioning here:

    http://forums.techguy.org/windows-7/975882-windows-7-hibernate-resume-problem.html

    But that doesn't seem to affect me.
    Anybody else have some idea? Or something similar?

    EDIT: and i don't really want to use hibernate to disk all the time because that would mean that i write twice a day 12GB so thats 24GB per day only suspending.. Thats quite a lot of data for an SSD
     
  2. DakkonA

    DakkonA Notebook Evangelist

    Reputations:
    30
    Messages:
    448
    Likes Received:
    0
    Trophy Points:
    30
    <strike>The hibernation file is never deleted and only grows in size if it has to, so it should always be writing to the same block of sectors.</strike>
     
  3. joco

    joco Notebook Consultant

    Reputations:
    2
    Messages:
    176
    Likes Received:
    2
    Trophy Points:
    31
    and and SSD will make sure that it will not write the the same block of sectors (== flash pages) because a flash cell can only be written around 3000 times

    So if hibernate will write out 12GB of my memory (the file is a little bit smaller its around 9.5GB) then the SSD will constantly write that to different pages of flash else if it would write the the same cells over and over again, those cells will be worn out way quicker then the rest
    Ofcourse 3000 times is a lot, even if it would just be suspend/resume on the same cells then i could do that 3000/twice a day/365 = 4 years.
     
  4. NoSlow5oh

    NoSlow5oh Notebook Evangelist

    Reputations:
    27
    Messages:
    451
    Likes Received:
    0
    Trophy Points:
    30
    Remember, even my C400 which is rated at only 72TB of total data written before it dies, would take 40GB worth of writing every day for 5 years to meet that quota. By then, any enthusiast (I'm assuming you are because of your vertex purchase) will have a newer drive by then.

    On a side note: OCZ has been having these problems resuming from hibernate/suspend since the launch of the Vertex 2's, and have yet to fix the issue. This is one reason I chose the slightly slower C400. I wish I had any valuable info for you, but it's seems only OCZ can fix this issue with a firmware update. This is of course, if I'm understanding the problem your having.
     
  5. DakkonA

    DakkonA Notebook Evangelist

    Reputations:
    30
    Messages:
    448
    Likes Received:
    0
    Trophy Points:
    30
    Of course, duh. That makes total sense. The SSD info I saw always talked about new files, not changing a single file. Thanks.
     
  6. joco

    joco Notebook Consultant

    Reputations:
    2
    Messages:
    176
    Likes Received:
    2
    Trophy Points:
    31
    But how do we know it is the Vertex?
    That's the biggest problem i currently have it is a very generic error that other people also do encounter with Win7 SP1 ..
    So i don't know what is really the cause..

    The vertex does come up just fine, at least it can write the memory dump to disk.. But it could be that it is not fast enough?
     
  7. joco

    joco Notebook Consultant

    Reputations:
    2
    Messages:
    176
    Likes Received:
    2
    Trophy Points:
    31
    ok i seem to have fixed this issue, maybe this will help others:

    What i had installed where the latest chipset drivers from the Dell site:

    Intel(R) 6 Series/C200 Series Chipset Family 6 Port SATA AHCI Controller - 1C03

    the inf file has this info:

    CatalogFile=cougahci.cat
    DriverVer=09/10/2010, 9.2.0.1011

    Then i downloaded the latest Intel Rapid Storage Technology drivers:

    http://downloadcenter.intel.com/Deta...=3321&lang=eng

    and installed those

    Then the device manager reported "Intel(R) Mobile Express Chipdset SATA AHCI Controller" (iaStore driver) with as version: 10.1.0.1008 my guess is that this one is a bit newer then the , 9.2.0.1011 reported above (if you can compare those)

    But now my suspend problem seems to be gone, at least i have tried it now about 5 times and every time it wakes up quickly and i can login

    The problem i am now getting is the "The device, \Device\Ide\iaStor0, did not respond within the timeout period."

    But i think i have seen a solution for that somewhere , that was related to LPM (Link Power Management)

    I have added these registry settings to see if that will fix that problem:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port0]
    "LPM"=dword:00000000
    "LPMDSTATE"=dword:00000000
    "DIPM"=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port1]
    "LPM"=dword:00000000
    "LPMDSTATE"=dword:00000000
    "DIPM"=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port2]
    "LPM"=dword:00000000
    "LPMDSTATE"=dword:00000000
    "DIPM"=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port3]
    "LPM"=dword:00000000
    "LPMDSTATE"=dword:00000000
    "DIPM"=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port4]
    "LPM"=dword:00000000
    "LPMDSTATE"=dword:00000000
    "DIPM"=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port5]
    "LPM"=dword:00000000
    "LPMDSTATE"=dword:00000000
    "DIPM"=dword:00000000
     
  8. NoSlow5oh

    NoSlow5oh Notebook Evangelist

    Reputations:
    27
    Messages:
    451
    Likes Received:
    0
    Trophy Points:
    30
    I did the same thing to my L502x yesterday, and it seems to fix the random stutering it was having. It is due to the Link Power Management and Intel Rapid Storage Technology, and is affecting all new SATA III drives (at least the vertex 3, C400/M4, and even affected the older C300). I, however, did not have any bsod's or any other hibernate/suspend problems. Only a random 15 sec. stutter out of the blue every now and then. I'll report back on whether or not this fixed my issue once I get a few hours of run time on my laptop.
     
  9. joco

    joco Notebook Consultant

    Reputations:
    2
    Messages:
    176
    Likes Received:
    2
    Trophy Points:
    31
    you didn't have the BSOD because you are already using the "real" intel drivers and because of that you had the stuttering.
    I didn't have the stutter but the BSOD because i used the Dell intel drivers.
    But now i also have the stuttering now and then, but i have now added those registry settings and will see if that also killed that problem,
     
  10. DakkonA

    DakkonA Notebook Evangelist

    Reputations:
    30
    Messages:
    448
    Likes Received:
    0
    Trophy Points:
    30
    The default Dell-provided driver should be 10.1.2.1004 with a date of 1/12/2011... At least that's the version I have in my C:\Drivers\Chipset_IRST\f6flpy-x64 folder, and the version in the latest Dell-provided package. It should be called "Intel(R) Mobile Express Chipset SATA AHCI Controller".

    Of course I don't have an SSD to test this, but I don't know why both drivers you're using, joco, are older.
     
Loading...
Thread Status:
Not open for further replies.

Share This Page