I've been trying to search for a solution to this issue without success.
I've had my custom-built desktop set to "sleep" automatically after 25 minutes, and this was working perfectly normally for years. Lately it has not gone to sleep but has instead become completely unresponsive. The screen will turn off first (as it is supposed to) and after some time when it should go to sleep, it instead stays running (i.e. my fans and lights are all still active, power light still on) but it won't respond to input (i.e. moving the mouse or tapping a key). Hitting "caps lock" does not register on the keyboard, and the only way to get it going again is to restart the computer (hard shutdown).
I've never had any issues while actually using the system, and I've been playing some pretty intensive games (albeit for not terribly long duration) with no ill effects.
When the computer is restarted, event viewer shows errors tracing to the time I perform the hard shutdown:
The most recent changes to the computer were the addition of the Radeon 7950 (it was working fine for months after that) and then the addition of a 128 GB Samsung Pro 840 SSD (again, the errors didn't start until months after that).
My specs are as follows:
I reinstalled Windows when I got the SSD in late April and the problems didn't start until a week or so ago. I tried to uninstall Microsoft Security Essentials and run AVG instead; of course MSE keeps re-creating a folder and throwing a new "EppOobe.etl" in there anyway. I'm not sure if it's a hardware or software error?
I tried switching from "hybrid sleep" to "hibernate" and I thought that had worked around the issue, but it did the same thing to me yesterday (became unresponsive instead of hibernating, had to restart to fix). It still seems fine when I'm using it day-to-day. Any suggestions/diagnostics I should run?
I've had my custom-built desktop set to "sleep" automatically after 25 minutes, and this was working perfectly normally for years. Lately it has not gone to sleep but has instead become completely unresponsive. The screen will turn off first (as it is supposed to) and after some time when it should go to sleep, it instead stays running (i.e. my fans and lights are all still active, power light still on) but it won't respond to input (i.e. moving the mouse or tapping a key). Hitting "caps lock" does not register on the keyboard, and the only way to get it going again is to restart the computer (hard shutdown).
I've never had any issues while actually using the system, and I've been playing some pretty intensive games (albeit for not terribly long duration) with no ill effects.
When the computer is restarted, event viewer shows errors tracing to the time I perform the hard shutdown:
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D
The most recent changes to the computer were the addition of the Radeon 7950 (it was working fine for months after that) and then the addition of a 128 GB Samsung Pro 840 SSD (again, the errors didn't start until months after that).
My specs are as follows:
Code:
OS: Windows 7 Pro x64
Processor: Intel Core i5-750 Lynnfield 2.66 GHz
Graphics: Powercolor AMD Radeon HD 7950 3 GB
Motherboard: ASUS P7P55D-E Pro
Memory: G.SKILL Ripjaws 4GB DDR3 1600
Primary (OS) HD: Samsung 840 Pro 128 GB SSD
Secondary (Storage) HD: Hitachi Deskstar 2TB 7200 RPM
Case: Antec Three Hundred Illusion Black
Power Supply: Antec EarthWatts EA750 750W
I reinstalled Windows when I got the SSD in late April and the problems didn't start until a week or so ago. I tried to uninstall Microsoft Security Essentials and run AVG instead; of course MSE keeps re-creating a folder and throwing a new "EppOobe.etl" in there anyway. I'm not sure if it's a hardware or software error?
I tried switching from "hybrid sleep" to "hibernate" and I thought that had worked around the issue, but it did the same thing to me yesterday (became unresponsive instead of hibernating, had to restart to fix). It still seems fine when I'm using it day-to-day. Any suggestions/diagnostics I should run?