Windows 7 Forums Search
Register | Today's Posts | Tutorials | Vista Forum | Windows 8 Forum | Search
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows 7. The Windows 7 forum also covers news and updates and has an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Go Back Windows 7 Forums > Windows 7 help and support > Crashes and Debugging »

Windows 7 - BSOD when system is idle


 
12-15-2009   #1


Windows 7 64bit
2 posts
 
 

BSOD when system is idle
Hello People,

i just built a new system and so far Windows 7 64bit crashed three times with a BSOD. The crashes occured when the system was idle and only a few applications were open. I installed all new drivers from the Asus homepage and flashed the bios. Besides a few regular applications i also installed VMWare Player (seems to come up in one dump) and Avira AntiVir Personal. One full pass of memtest86 resultet in no errors. 3D Mark and BurnInTest also worked without a problem.

So i would be glad if someone can figure out the attached Minidumps and tell me what the problem could be e.g. faulty driver/hardware. The mainboard is rated as Windows 7 ready (-> maybe something with the mainboard is wrong or some power save function?).

Thank You


System:
Mobo: Asus P7P55D
CPU: Intel i5 2,6Ghz
RAM: Corsair XMS3 2x2GB
GPU: Sapphire Radeon HD 4670 (Passiv Cooling)
PSU: Seasonic SS-430 GB Active PFCF3 (About one year old, but should be ok)
ST31500341AS ATA
ST3200822A ATA

Dump 1-3:

41 Kernel-Power

1)
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\jupiter\Downloads\121209-23384-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symcache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0280f000 PsLoadedModuleList = 0xfffff800`02a4ce50
Debug session time: Sat Dec 12 14:38:47.014 2009 (GMT+1)
System Uptime: 0 days 2:58:18.450
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80058513e0, fffffa80058516c0, fffff80002b89240}

Probably caused by : csrss.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80058513e0, Terminating object
Arg3: fffffa80058516c0, Process image file name
Arg4: fffff80002b89240, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa80058513e0

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

BUGCHECK_STR:  0xF4_C0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`05d39b58 fffff800`02c0c142 : 00000000`000000f4 00000000`00000003 fffffa80`058513e0 fffffa80`058516c0 : nt!KeBugCheckEx
fffff880`05d39b60 fffff800`02bb8269 : ffffffff`ffffffff fffffa80`063fe060 fffffa80`058513e0 fffffa80`058513e0 : nt!PspCatchCriticalBreak+0x92
fffff880`05d39ba0 fffff800`02b3cc74 : ffffffff`ffffffff 00000000`00000001 fffffa80`058513e0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17a06
fffff880`05d39bf0 fffff800`02880153 : fffffa80`058513e0 00000000`c0000005 fffffa80`063fe060 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`05d39c70 fffff800`0287c6f0 : fffff800`028c0ada fffff880`05d3aa00 fffff880`05d3a340 fffff880`05d3ac20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`05d39e08 fffff800`028c0ada : fffff880`05d3aa00 fffff880`05d3a340 fffff880`05d3ac20 00000000`00000002 : nt!KiServiceLinkage
fffff880`05d39e10 fffff800`029833d9 : fffff880`05d3aa00 fffff880`05d3aa00 fffff880`05d3ac20 fffff880`05d3a4e0 : nt! ?? ::FNODOBFM::`string'+0x4619d
fffff880`05d3a4b0 fffff800`02882bfb : fffff880`05d3aa00 fffffa80`063fe060 00000000`003473a0 fffff880`05d3abc0 : nt!KiRaiseException+0x1b9
fffff880`05d3aae0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtRaiseException+0x7b


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

Followup: MachineOwner
---------
2)
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\jupiter\Downloads\121209-24242-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symcache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02863000 PsLoadedModuleList = 0xfffff800`02aa0e50
Debug session time: Sat Dec 12 18:56:19.302 2009 (GMT+1)
System Uptime: 0 days 2:56:46.738
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffe18002f64624, 0, fffff8000289423b, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ExQueryPoolUsage+e0 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffe18002f64624, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000289423b, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b0b0e0
 ffffe18002f64624 

FAULTING_IP: 
nt!ExQueryPoolUsage+e0
fffff800`0289423b 8379e400        cmp     dword ptr [rcx-1Ch],0

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  vmware-authd.e

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880061f86a0 -- (.trap 0xfffff880061f86a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe18002f64640
rdx=fffff880061f897c rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000289423b rsp=fffff880061f8830 rbp=fffff880061f8ca0
 r8=fffff880061f8978  r9=fffff80002a78720 r10=0000000000000005
r11=fffff880061f895c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!ExQueryPoolUsage+0xe0:
fffff800`0289423b 8379e400        cmp     dword ptr [rcx-1Ch],0 ds:1a80:ffffe180`02f64624=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002952b19 to fffff800028d4f00

STACK_TEXT:  
fffff880`061f8538 fffff800`02952b19 : 00000000`00000050 ffffe180`02f64624 00000000`00000000 fffff880`061f86a0 : nt!KeBugCheckEx
fffff880`061f8540 fffff800`028d2fee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40edb
fffff880`061f86a0 fffff800`0289423b : 00000000`00c3ef80 fffff800`02bcf09b 00000000`00000000 00000000`000a5cad : nt!KiPageFault+0x16e
fffff880`061f8830 fffff800`02bcf09b : 00000000`00000000 00000000`000a5cad 00000000`000a5cad 00000000`00000004 : nt!ExQueryPoolUsage+0xe0
fffff880`061f8840 fffff800`02bd0e49 : 00000000`00c3ef80 fffff800`02b849c3 00000000`019bf6a4 00000000`00000000 : nt!ExpQuerySystemInformation+0x5a9
fffff880`061f8be0 fffff800`028d4153 : fffffa80`062a6810 00000000`005aa6e0 00000000`0027dc50 fffffa80`06152960 : nt!NtQuerySystemInformation+0x4d
fffff880`061f8c20 00000000`76fe021a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00c3e778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fe021a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExQueryPoolUsage+e0
fffff800`0289423b 8379e400        cmp     dword ptr [rcx-1Ch],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!ExQueryPoolUsage+e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x50_nt!ExQueryPoolUsage+e0

BUCKET_ID:  X64_0x50_nt!ExQueryPoolUsage+e0

Followup: MachineOwner
---------
3)
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\jupiter\Downloads\121409-18267-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symcache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a63000 PsLoadedModuleList = 0xfffff800`02ca0e50
Debug session time: Mon Dec 14 17:36:42.335 2009 (GMT+1)
System Uptime: 0 days 1:57:26.397
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002dd838f, fffff88006e710e0, 0}

Probably caused by : ntkrnlmp.exe ( nt!AlpcpLookupMessage+bf )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002dd838f, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006e710e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP: 
nt!AlpcpLookupMessage+bf
fffff800`02dd838f 4439a7f0000000  cmp     dword ptr [rdi+0F0h],r12d

CONTEXT:  fffff88006e710e0 -- (.cxr 0xfffff88006e710e0)
rax=ffff54a00939f331 rbx=0000000000000000 rcx=ffff54a00939f330
rdx=00000000000002bc rsi=fffff8a00007daf0 rdi=ffff54a00939f330
rip=fffff80002dd838f rsp=fffff88006e71ac0 rbp=0000000000029724
 r8=fffff8a00979b000  r9=0000000000000000 r10=fffffa8003d286f0
r11=fffff88006e71b28 r12=00000000000002bc r13=fffffa8004f88090
r14=fffff8a000088ef0 r15=fffff88006e71b78
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!AlpcpLookupMessage+0xbf:
fffff800`02dd838f 4439a7f0000000  cmp     dword ptr [rdi+0F0h],r12d ds:002b:ffff54a0`0939f420=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  services.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002da74a4 to fffff80002dd838f

STACK_TEXT:  
fffff880`06e71ac0 fffff800`02da74a4 : fffff880`06e71ca0 00000000`00020001 00000000`00029724 fffffa80`04f88090 : nt!AlpcpLookupMessage+0xbf
fffff880`06e71b30 fffff800`02ad4153 : fffffa80`06954060 00000000`0103f548 fffff880`06e71bc8 00000000`0103f608 : nt!NtAlpcQueryInformationMessage+0x1dc
fffff880`06e71bb0 00000000`772806ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0103f528 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772806ea


FOLLOWUP_IP: 
nt!AlpcpLookupMessage+bf
fffff800`02dd838f 4439a7f0000000  cmp     dword ptr [rdi+0F0h],r12d

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!AlpcpLookupMessage+bf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff88006e710e0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!AlpcpLookupMessage+bf

BUCKET_ID:  X64_0x3B_nt!AlpcpLookupMessage+bf

Followup: MachineOwner
---------
My System SpecsSystem Spec
12-15-2009   #2


Windows 7 RTM X64
5,895 posts
 
 

Those mostly look to be system files and they are something different each time which tends to point to an underlying problem. Have you tried using the XMP memory profiles for your memory?

Make sure it's set up like this.
4GB 2 x 2GB PC3-12800 1600MHz 240-pin DDR3 Timing: 9-9-9-24 1.65v
Also try 1333Mhz setting
My System SpecsSystem Spec
12-15-2009   #3


Windows 7 64bit
2 posts
 
 

Ok I activated XMP. The sticker on the RAM says that 1600Mhz 9-9-9-24 1.8V is possible. The bios does not allow 1600Mhz to be selected so it is now running with 1333Mhz 9-9-9-24 1.8V.

Any other ideas to narrow down the problem?
My System SpecsSystem Spec
.


Reply

 BSOD when system is idle problems?



« Windows Error Recovery everytime | Failed to connect to a Windows Service »
Thread Tools



Similar Threads for: BSOD when system is idle
Thread Forum
Random BSOD, cant pin down, happens even while system idle Crashes and Debugging
BSOD when System is idle Crashes and Debugging
BSOD while system is idle after a few hours Crashes and Debugging
BSOD, During all but Idle (Web browsing, File system work) Crashes and Debugging
BSOD when system sitting idle Crashes and Debugging


All times are GMT -5. The time now is 01:30 AM.

Windows 8 Forums - - Contact Us - Windows 7 Forums - Legal - Privacy and cookies - Top


Windows 7 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30