The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    XPS 1640 Wake From Sleep Freeze/Crash

    Discussion in 'Dell XPS and Studio XPS' started by SovereignGFC, Nov 12, 2011.

  1. SovereignGFC

    SovereignGFC Notebook Guru

    Reputations:
    0
    Messages:
    50
    Likes Received:
    0
    Trophy Points:
    15
    So I thought I solved my computer problem, which was/is: Waking my XPS 1640 (Win7Pro x64) from sleep results in a frozen screen and an eventual hard reset.

    I uninstalled the ATI GPU driver (Radeon HD 3670) using DriverCleaner.NET (the whole Safemode shebang). Then I installed the latest available at the time (11.9). Until yesterday it was fine, but now every use of sleep causes the hard reset.

    The System event log reveals nothing other than the usual "Unexpected shutdown." No driver is faulted, no Blue Screen is found. It's as if the actual cause of the crash somehow eludes the Event Log...

    Possible correlation: Last night I was watching a movie with my girlfriend and the computer really heated up since it was sitting on the bed (I know this is bad--no lecture required :p). It got so hot the decoding began to stutter. I elevated the back to vent heat better and finished the movie. Then the next morning the problems started.

    Could I have killed the GPU?
     
  2. SovereignGFC

    SovereignGFC Notebook Guru

    Reputations:
    0
    Messages:
    50
    Likes Received:
    0
    Trophy Points:
    15
    It appears I answered my own question.

    If you, like me, are using ThrottleStop to manage your CPU's power states rather than letting Windows/Dell cripple your machine, it is necessary to disable Windows CPU management in the Power Options->Advanced settings control panel. Failure to do so seems to cause this issue--setting "Maximum Processor State" and "Minimum Processor State" to 100% appears to have solved the problem.
     
  3. chewyeong90

    chewyeong90 Notebook Evangelist

    Reputations:
    77
    Messages:
    528
    Likes Received:
    0
    Trophy Points:
    30
    I don't think it is ThrottleStop's problem. I used it and also have minimum processor state at default 5% and max 100%.

    If you could post your minidump here in Windows\Minidump I could help you take a look.