• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Computer doesn't sleep correctly

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
LoneWolf121188

LoneWolf121188

Member
​
Joined
Dec 31, 2004
Location
Osan AB, South Korea
I've been dealing with this for a while now, but this happened to me again last night and I lost a few hours of work in Premiere and I'm pissed about it, so I'm finally getting around to trying to fix this. :bang head

Occasionally, my computer appears to freeze up right before it goes to sleep. I don't know any other way to describe it. I click Sleep, and it goes through the normal process for about a second: the GPU turns off (as evidenced by the fact that my monitor thinks it's not connected to anything), the USB ports turn off (as evidenced by my keyboard not lighting up), everything appears normal...but the fans just keep running, and the power LED stays on. It then doesn't respond to any input from the keyboard/mouse, doesn't do anything if I plug in a USB hard drive, etc. The only thing I can do is hold down the power button until it turns off, then reboot.

Any ideas where I can start troubleshooting this?

Looking in the Event Viewer, there's nothing significant from last night when I got this freeze. There are 3 simultaneous "Information" entries, which I copied below.


Log Name: Microsoft-Windows-Diagnosis-DPS/Operational
Source: Microsoft-Windows-Diagnosis-DPS
Date: 3/30/2014 11:17:28 PM
Event ID: 110
Task Category: Scenario Lifecycle
Level: Information
Keywords: Scenario lifecycle events
User: LOCAL SERVICE
Computer: [NAME]-Desktop
Description:
Diagnostic module {282396B2-6C46-4D66-B413-70B0445DF33C} (%SystemRoot%\system32\diagperf.dll) finished troubleshooting scenario {186F47EF-626C-4670-800A-4A30756BABAD}, instance {4F485030-9002-4810-8E39-96783C357B61}, original activity ID {00000000-0000-0000-0000-000000000000}. No resolution was set by the diagnostic module.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnosis-DPS" Guid="{6BBA3851-2C7E-4DEA-8F54-31E5AFD029E3}" />
<EventID>110</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>1</Task>
<Opcode>14</Opcode>
<Keywords>0x4000000800000000</Keywords>
<TimeCreated SystemTime="2014-03-31T04:17:28.189596000Z" />
<EventRecordID>13335</EventRecordID>
<Correlation ActivityID="{4F485030-9002-4810-8E39-96783C357B61}" />
<Execution ProcessID="1860" ThreadID="8760" />
<Channel>Microsoft-Windows-Diagnosis-DPS/Operational</Channel>
<Computer>[NAME]-Desktop</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ScenarioId">{186F47EF-626C-4670-800A-4A30756BABAD}</Data>
<Data Name="InstanceId">{4F485030-9002-4810-8E39-96783C357B61}</Data>
<Data Name="OriginalActivityId">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="DiagnosticModuleImageName">%SystemRoot%\system32\diagperf.dll</Data>
<Data Name="DiagnosticModuleId">{282396B2-6C46-4D66-B413-70B0445DF33C}</Data>
</EventData>
</Event>

Log Name: Microsoft-Windows-Diagnosis-DPS/Operational
Source: Microsoft-Windows-Diagnosis-DPS
Date: 3/30/2014 11:17:28 PM
Event ID: 105
Task Category: Scenario Lifecycle
Level: Information
Keywords: Scenario lifecycle events
User: LOCAL SERVICE
Computer: [NAME]-Desktop
Description:
Diagnostic module {282396B2-6C46-4D66-B413-70B0445DF33C} (%SystemRoot%\system32\diagperf.dll) started troubleshooting scenario {186F47EF-626C-4670-800A-4A30756BABAD}, instance {4F485030-9002-4810-8E39-96783C357B61}, original activity ID {00000000-0000-0000-0000-000000000000}.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnosis-DPS" Guid="{6BBA3851-2C7E-4DEA-8F54-31E5AFD029E3}" />
<EventID>105</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>1</Task>
<Opcode>13</Opcode>
<Keywords>0x4000000800000000</Keywords>
<TimeCreated SystemTime="2014-03-31T04:17:28.188596000Z" />
<EventRecordID>13334</EventRecordID>
<Correlation ActivityID="{4F485030-9002-4810-8E39-96783C357B61}" />
<Execution ProcessID="1860" ThreadID="8760" />
<Channel>Microsoft-Windows-Diagnosis-DPS/Operational</Channel>
<Computer>[NAME]-Desktop</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ScenarioId">{186F47EF-626C-4670-800A-4A30756BABAD}</Data>
<Data Name="InstanceId">{4F485030-9002-4810-8E39-96783C357B61}</Data>
<Data Name="OriginalActivityId">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="DiagnosticModuleImageName">%SystemRoot%\system32\diagperf.dll</Data>
<Data Name="DiagnosticModuleId">{282396B2-6C46-4D66-B413-70B0445DF33C}</Data>
</EventData>
</Event>

Log Name: Microsoft-Windows-Diagnosis-DPS/Operational
Source: Microsoft-Windows-Diagnosis-DPS
Date: 3/30/2014 11:17:28 PM
Event ID: 100
Task Category: Scenario Lifecycle
Level: Information
Keywords: Scenario lifecycle events
User: LOCAL SERVICE
Computer: [NAME]-Desktop
Description:
Diagnostic module {282396B2-6C46-4D66-B413-70B0445DF33C} (%SystemRoot%\system32\diagperf.dll) detected a problem for scenario {186F47EF-626C-4670-800A-4A30756BABAD}, instance {4F485030-9002-4810-8E39-96783C357B61}, original activity ID {00000000-0000-0000-0000-000000000000}.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnosis-DPS" Guid="{6BBA3851-2C7E-4DEA-8F54-31E5AFD029E3}" />
<EventID>100</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>1</Task>
<Opcode>12</Opcode>
<Keywords>0x4000000800000000</Keywords>
<TimeCreated SystemTime="2014-03-31T04:17:28.188596000Z" />
<EventRecordID>13333</EventRecordID>
<Correlation ActivityID="{4F485030-9002-4810-8E39-96783C357B61}" />
<Execution ProcessID="1860" ThreadID="8760" />
<Channel>Microsoft-Windows-Diagnosis-DPS/Operational</Channel>
<Computer>[NAME]-Desktop</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ScenarioId">{186F47EF-626C-4670-800A-4A30756BABAD}</Data>
<Data Name="InstanceId">{4F485030-9002-4810-8E39-96783C357B61}</Data>
<Data Name="OriginalActivityId">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="DiagnosticModuleImageName">%SystemRoot%\system32\diagperf.dll</Data>
<Data Name="DiagnosticModuleId">{282396B2-6C46-4D66-B413-70B0445DF33C}</Data>
</EventData>
</Event>
 
Last edited:
Lonewolf do you have AI Suite installed? I had the same exact problem with my CHV when I had it installed and the problem went away after I un-installed it.
 
LoneWolf121188 said:
I can't seem to find a spot in the BIOS to enable/disable specific sleep states...
Click to expand...

The only thing I could find in the manual is PCH configuration.

Are you using Hybrid sleep? some times that can cause trouble, so if you are turn that off and see if that will help.
 

Attachments

  • attachment.jpg
    attachment.jpg
    41.5 KB · Views: 348
Last edited:
The c-state are accessable in BIOS under the advanced tab. Navigate to the CPU power management section and look for CPU C states. Default is set to auto, change it to enabled and you'll then see all the c-state options.
 
Well, somehow between updating my BIOS and uninstalling and reinstalling AI Suite, the problem appears to have magically fixed itself. I'm not sure if it was AI Suite causing the problem, but thanks for the tip, Mandrake.
 
You must log in or register to reply here.

Similar threads

S
PSU Related BSOD?
Replies
12
Views
1K
Suppressor1137
S
S
CPU, Ram or Motherboard Going Bad?
Replies
8
Views
2K
Stoneysilence
S
Zakarro
Random CTDs in games, same exception code c0000005
Replies
4
Views
952
Zakarro
Zakarro
K
Computer keeps restarting randomly without warning.
Replies
4
Views
521
Conumdrum
Conumdrum
N
Random Freezes Kernel-power 41
Replies
3
Views
1K
RJARRRPCGP
R
Back