Okay so I just built my new computer 2 days ago and I've gotten a BSOD everyday. It only comes when I leave my computer on idle and when I come back there's the BSOD, I can play games, download, and install fine it's just when I leave it idle sometimes there's a BSOD. I have tested the ram with window 7 memtest twice and no errors.
Here is my specs
Intel 2500k 3.3ghz
gigabyte z68A-D3-B3
GTX 560 TI
g.skill ripjaw 2 x 4gb ddr3 1600 9-9-9-28
750gb WD HDD
Corsair TX650 V2
Windows 7 Ultimate
Here is my minidump
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\092211-18860-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`0444b3c0?
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03067000 PsLoadedModuleList = 0xfffff800`032ac670
Debug session time: Thu Sep 22 00:25:14.162 2011 (GMT-7)
System Uptime: 0 days 8:52:39.005
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80070ed060, fffff8000444b3d8, fffffa80068bd4a0}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80070ed060, Physical Device Object of the stack
Arg3: fffff8000444b3d8, Functional Device Object of the stack
Arg4: fffffa80068bd4a0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa80068bd4a0
DEVICE_OBJECT: fffffa8008073050
DRIVER_OBJECT: fffffa800807de70
IMAGE_NAME: Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2ee89f
MODULE_NAME: Rt64win7
FAULTING_MODULE: fffff88004285000 Rt64win7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80003151cd2 to fffff800030e3c40
STACK_TEXT:
fffff800`0444b388 fffff800`03151cd2 : 00000000`0000009f 00000000`00000003 fffffa80`070ed060 fffff800`0444b3d8 : nt!KeBugCheckEx
fffff800`0444b390 fffff800`030ef5fc : fffff800`0444b550 fffff800`0444b550 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`0444b430 fffff800`030ef496 : fffff800`0328ef00 00000000`001f4281 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`0444b4a0 fffff800`030ef37e : 0000004a`690d4eaa fffff800`0444bb18 00000000`001f4281 fffff800`0325d2a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`0444baf0 fffff800`030ef167 : 00000018`0cffa4c7 00000018`001f4281 00000018`0cffa4fb 00000000`00000081 : nt!KiTimerExpiration+0x1be
fffff800`0444bb90 fffff800`030db96a : fffff800`03259e80 fffff800`03267cc0 00000000`00000000 fffff880`01620a00 : nt!KiRetireDpcList+0x277
fffff800`0444bc40 00000000`00000000 : fffff800`0444c000 fffff800`04446000 fffff800`0444bc00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_Rt64win7.sys
BUCKET_ID: X64_0x9F_IMAGE_Rt64win7.sys
Followup: MachineOwner
---------
Here is my specs
Intel 2500k 3.3ghz
gigabyte z68A-D3-B3
GTX 560 TI
g.skill ripjaw 2 x 4gb ddr3 1600 9-9-9-28
750gb WD HDD
Corsair TX650 V2
Windows 7 Ultimate
Here is my minidump
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\092211-18860-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`0444b3c0?
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03067000 PsLoadedModuleList = 0xfffff800`032ac670
Debug session time: Thu Sep 22 00:25:14.162 2011 (GMT-7)
System Uptime: 0 days 8:52:39.005
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80070ed060, fffff8000444b3d8, fffffa80068bd4a0}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80070ed060, Physical Device Object of the stack
Arg3: fffff8000444b3d8, Functional Device Object of the stack
Arg4: fffffa80068bd4a0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa80068bd4a0
DEVICE_OBJECT: fffffa8008073050
DRIVER_OBJECT: fffffa800807de70
IMAGE_NAME: Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2ee89f
MODULE_NAME: Rt64win7
FAULTING_MODULE: fffff88004285000 Rt64win7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80003151cd2 to fffff800030e3c40
STACK_TEXT:
fffff800`0444b388 fffff800`03151cd2 : 00000000`0000009f 00000000`00000003 fffffa80`070ed060 fffff800`0444b3d8 : nt!KeBugCheckEx
fffff800`0444b390 fffff800`030ef5fc : fffff800`0444b550 fffff800`0444b550 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`0444b430 fffff800`030ef496 : fffff800`0328ef00 00000000`001f4281 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`0444b4a0 fffff800`030ef37e : 0000004a`690d4eaa fffff800`0444bb18 00000000`001f4281 fffff800`0325d2a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`0444baf0 fffff800`030ef167 : 00000018`0cffa4c7 00000018`001f4281 00000018`0cffa4fb 00000000`00000081 : nt!KiTimerExpiration+0x1be
fffff800`0444bb90 fffff800`030db96a : fffff800`03259e80 fffff800`03267cc0 00000000`00000000 fffff880`01620a00 : nt!KiRetireDpcList+0x277
fffff800`0444bc40 00000000`00000000 : fffff800`0444c000 fffff800`04446000 fffff800`0444bc00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_Rt64win7.sys
BUCKET_ID: X64_0x9F_IMAGE_Rt64win7.sys
Followup: MachineOwner
---------