Crashes Entering Sleep

[jdoctoroff]

I have been having this problem for a while -- before I got the SSD (had a WD Velociraptor before) -- essentially, the system goes into sleep, whether I tell it to, or it does automatically, and never turns off. The screen goes black, and there is no HD activity, but the fans/lights/etc stay on.

Sometimes, however, the computer does go into sleep (and recover from it) successfully, but I haven't been able to figure out why it works when it does. It always seems to work after a clean install, but again, there's no reason I can discern for why it starts to malfunction.

Any ideas what might be causing this?


In the event there's a BSOD I can't see because the screen turns off, I attached the dump/perfmon files.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? it's a home-built PC, so no
- an OEM or full retail version? from MSDN-AA

- What is the age of system (hardware)? a bit over two years
- What is the age of OS installation (have you re-installed the OS?) less than a month

 

[zigzag3143]

I have been having this problem for a while -- before I got the SSD (had a WD Velociraptor before) -- essentially, the system goes into sleep, whether I tell it to, or it does automatically, and never turns off. The screen goes black, and there is no HD activity, but the fans/lights/etc stay on.

Sometimes, however, the computer does go into sleep (and recover from it) successfully, but I haven't been able to figure out why it works when it does. It always seems to work after a clean install, but again, there's no reason I can discern for why it starts to malfunction.

Any ideas what might be causing this?


In the event there's a BSOD I can't see because the screen turns off, I attached the dump/perfmon files.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? it's a home-built PC, so no
- an OEM or full retail version? from MSDN-AA

- What is the age of system (hardware)? a bit over two years
- What is the age of OS installation (have you re-installed the OS?) less than a month

Single uploaded minidump caused by hardware read here what it means and what to try. Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Thanks


Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\020411-17175-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02867000 PsLoadedModuleList = 0xfffff800`02aa4e50
Debug session time: Fri Feb  4 12:10:38.608 2011 (GMT-5)
System Uptime: 0 days 0:11:52.497
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007896028, fe000000, 300136}

Probably caused by : hardware

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007896028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000300136, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  prime95.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`02830903 : 00000000`00000124 00000000`00000000 fffffa80`07896028 00000000`fe000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`029ed593 : 00000000`00000001 fffffa80`07899a60 00000000`00000000 fffffa80`07899ab0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`028305c8 : 00000000`00000728 fffffa80`07899a60 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`0282ff1a : fffffa80`07899a60 fffff800`00ba8e70 fffffa80`07899a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`0282fdd5 : 00000000`00000008 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`02823e88 : 00000000`5c9ec380 00000000`5c9eadc0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`028d5fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`028d5e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000001`402540f9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`03ecf0e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`402540f9


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner
---------

0: kd> lmvm hardware
start             end                 module name

 

[jdoctoroff]

Hi Ken,

Unfortunately, the dump file you looked at is from much earlier -- that was caused by overclocking too much for the hardware, if I remember correctly. Any idea what could be causing the sleep problems?

Thanks again--