Windows 7 Sleep and/or lockup issue

Jayhawk

New Member
I've got a Windows 7 Pro 64 bit system (6.1.7600.16385) with a bit of an issue. It's a high end, RAID 1 (hardware configured) system. Quad core Xeon and 8GB ram... I need this system to stay running until I tell it otherwise..... but it's not. I always disable Windows updates, just for this purpose.

The first time I had a problem I came in one morning and it APPEARED the system was asleep. The power was on, the monitors were asleep, but the mouse and/or keyboard would not wake the system up. I ended up having to hard boot the system, which is bad. I assumed it could be resolved by telling it not to sleep. So, I used the power settings option and told it to never sleep.

A few weeks later, I came in and found the exact same problem. So, I did some reading and found that, within the power settings, there is an option for USB power save which can be problematic, I ran a power report and confirmed this was likely the culprit, so I disabled that feature.

Now, today, I came in and found my system had restarted on its own. I'm not sure if this is what normally occurs or not, because it hung at the bios (which is "normal" on my system when there is a USB flash drive inserted on startup). I started it up and, like it always does, it indicates it was shut down improperly. The other times it indicates this (by asking if I want to start in safe mode) I assumed it was because I had to hard boot. But this time I didn't hard boot.

I think at this point it's more likely locking up, but I don't know how to tell. Oh, and just to head things off at the pass, this is not an issue on any other computer in my office/home and wasn't a problem on this computer when it's been running Ubuntu or WinXP. Thanks in advance...

Symptoms when system is found "frozen":

  • Computer on, disks running
  • Lights on keyboard and mouse on
  • Monitor asleep
  • USB unresponsive (new device plugged in would not light up)
  • System unable to "wake up" (whatever that means)
When I force it to power off and bring it back up, the event viewer and it shows this:
Code:
Log Name: System
Source: EventLog
Date: 3/3/2010 6:13:51 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: my-PC
Description:
The previous system shutdown at 9:02:31 PM on ‎3/‎2/‎2010 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-03-03T13:13:51.000000000Z" />
<EventRecordID>4087</EventRecordID>
<Channel>System</Channel>
<Computer>my-PC</Computer>
<Security />
</System>
<EventData>
<Data>9:02:31 PM</Data>
<Data>‎3/‎2/‎2010</Data>
<Data>
</Data>
<Data>
</Data>
<Data>136697</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>DA07030002000200150002001F009201DA07030003000300040002001F0092013C0000003C000000000000000000000000000000000000000100000000000000</Binary>
</EventData>
</Event>

Now, despite it saying that the previous system shutdown was at 9:02 PM, I believe that's when I forced it off this morning at 6:13. Why? Because the logs don't show that "unexpected shutdown"... just this one. So, I'm guessing it locked up at 9:02 last night, becoming unresponsive, and was thus unable to log the powerdown this morning at 6:13. Maybe?

Ideas? This is more than an annoyance... it's dangerous for what this computer is used for... I desperately need ideas.
 
Last edited:
Back
Top