Hi
I've been having this problem for a few weeks. When my computer goes in to sleep mode and stays that way for more than 30min or so, when i wake it the thing crashes and has to reboot.
It is a new computer I built myself, running Win7 64bit. Only about 6weeks old.
I have been through and removed some programs that were causing problems and also updated my BIOS as per suggestions in my last post.
I have included powercfg.txt as requested as well.
Thanks in advance
Ok this is a fairly unusual one. Only seen this once before. A driver (KS.sys) basically returned without releasing its parent. Not to worry.
Things you can do
1-run a system file check to verify and repair KS.sys and all your system files.
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
read here for more information SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
2-update all the old drivers
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
3- If you are overclocking STOP, update your raid driver even though it is current.
Let us know if you need any further assistance
Ken J
Code:
Bug Check 0x39: SYSTEM_EXIT_OWNED_MUTEX
The SYSTEM_EXIT_OWNED_MUTEX bug check has a value of 0x00000039. This indicates that the worker routine returned without releasing the mutex object that it owned.
Important Information If You Have Received a STOP Code
If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or your computer manufacturer, Contact Support.
If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.
The following actions might prevent an error like this from happening again:
- Download and install updates and device drivers for your computer from Windows Update.
- Scan your computer for computer viruses.
- Check your hard disk for errors.
SYSTEM_EXIT_OWNED_MUTEX Parameters
The following parameters are displayed on the blue screen.
Analysis
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\081610-22978-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03017000 PsLoadedModuleList = 0xfffff800`03254e50
Debug session time: Mon Aug 16 05:52:23.624 2010 (GMT-4)
System Uptime: 0 days 21:42:15.606
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 39, {fffff88004be8e80, fffffa8006b498a0, fffffa80056dc3a0, 0}
Probably caused by : ks.sys ( ks!CKsDevice::PassiveWakeDevice+0 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_EXIT_OWNED_MUTEX (39)
Arguments:
Arg1: fffff88004be8e80
Arg2: fffffa8006b498a0
Arg3: fffffa80056dc3a0
Arg4: 0000000000000000
Debugging Details:
------------------
FAULTING_IP:
ks!CKsDevice::PassiveWakeDevice+0
fffff880`04be8e80 48895c2410 mov qword ptr [rsp+10h],rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x39
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000303252b to fffff80003087740
STACK_TEXT:
fffff880`03966ca8 fffff800`0303252b : 00000000`00000039 fffff880`04be8e80 fffffa80`06b498a0 fffffa80`056dc3a0 : nt!KeBugCheckEx
fffff880`03966cb0 fffff800`0332bc06 : 00000000`00000000 fffffa80`039ed680 00000000`00000080 fffffa80`039d4b30 : nt! ?? ::FNODOBFM::`string'+0x54420
fffff880`03966d40 fffff800`03065c26 : fffff880`03887180 fffffa80`039ed680 fffff880`03892040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03966d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
ks!CKsDevice::PassiveWakeDevice+0
fffff880`04be8e80 48895c2410 mov qword ptr [rsp+10h],rbx
SYMBOL_NAME: ks!CKsDevice::PassiveWakeDevice+0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ks
IMAGE_NAME: ks.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bca9f
FAILURE_BUCKET_ID: X64_0x39_ks!CKsDevice::PassiveWakeDevice+0
BUCKET_ID: X64_0x39_ks!CKsDevice::PassiveWakeDevice+0
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_EXIT_OWNED_MUTEX (39)
Arguments:
Arg1: fffff88004be8e80
Arg2: fffffa8006b498a0
Arg3: fffffa80056dc3a0
Arg4: 0000000000000000
Debugging Details:
------------------
FAULTING_IP:
ks!CKsDevice::PassiveWakeDevice+0
fffff880`04be8e80 48895c2410 mov qword ptr [rsp+10h],rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x39
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000303252b to fffff80003087740
STACK_TEXT:
fffff880`03966ca8 fffff800`0303252b : 00000000`00000039 fffff880`04be8e80 fffffa80`06b498a0 fffffa80`056dc3a0 : nt!KeBugCheckEx
fffff880`03966cb0 fffff800`0332bc06 : 00000000`00000000 fffffa80`039ed680 00000000`00000080 fffffa80`039d4b30 : nt! ?? ::FNODOBFM::`string'+0x54420
fffff880`03966d40 fffff800`03065c26 : fffff880`03887180 fffffa80`039ed680 fffff880`03892040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03966d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
ks!CKsDevice::PassiveWakeDevice+0
fffff880`04be8e80 48895c2410 mov qword ptr [rsp+10h],rbx
SYMBOL_NAME: ks!CKsDevice::PassiveWakeDevice+0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ks
IMAGE_NAME: ks.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bca9f
FAILURE_BUCKET_ID: X64_0x39_ks!CKsDevice::PassiveWakeDevice+0
BUCKET_ID: X64_0x39_ks!CKsDevice::PassiveWakeDevice+0
Followup: MachineOwner
---------
Old drivers needing update
Code:
gdrv.sys gdrv.sys+17e9 fffff880`07f60000 fffff880`07f69000 0x00009000 0x489c9066 8/8/2008 14:28:54
spldr.sys fffff880`017d9000 fffff880`017e1000 0x00008000 0x4a0858bb 5/11/2009 12:56:27
GEARAspiWDM.sys fffff880`044e8000 fffff880`044f5000 0x0000d000 0x4a1151c0 5/18/2009 08:17:04
amdxata.sys fffff880`00fe5000 fffff880`00ff0000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59
Quote