Random BSOD Crashing frequently

dalagr · 06 Apr 2012

Hi all,
i have been getting random blue screens happening, its completely random when it happens whether i am playing a game like BF3 or MW3 or just idling on the desktop.

I have tested the RAM with MEMTEST86 for 6 passes on single sticks at a time. The RAM is about 3 weeks old.

All the BSOD's have a different error, and some still show the mouse with the loading symbol.

I have attached my Dumps etc Hope someone can help.

i believe it could be the RAM but Memtest86 come back with no errors at all which is what is confusing me.

Thanks

writhziden · 07 Apr 2012

Security Software (just to check it is installed and working properly; nothing needs to be done with this information at this time):

Code:

avp.exe	c:\program files (x86)\kaspersky lab\kaspersky internet security 2012\avp.exe	2092	8	200	1380	06/04/2012 21:24	12.0.0.374	197.55 KB (202,296 bytes)	24/04/2011 23:15
avp.exe	c:\program files (x86)\kaspersky lab\kaspersky internet security 2012\avp.exe	4212	8	200	1380	06/04/2012 21:24	12.0.0.374	197.55 KB (202,296 bytes)	24/04/2011 23:15
klwtblfs.exe	c:\program files (x86)\kaspersky lab\kaspersky internet security 2012\x64\klwtblfs.exe	4896	8	200	1380	06/04/2012 21:27	12.0.0.374	168.39 KB (172,432 bytes)	24/04/2011 23:14
klwtblfs.exe	c:\program files (x86)\kaspersky lab\kaspersky internet security 2012\x64\klwtblfs.exe	5364	8	200	1380	06/04/2012 21:29	12.0.0.374	168.39 KB (172,432 bytes)	24/04/2011 23:14

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\dalagr\Windows_NT6_BSOD_jcgriff2\040612-10202-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 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`030a6650
Debug session time: Fri Apr  6 14:20:44.169 2012 (UTC - 6:00)
System Uptime: 0 days 0:50:37.371
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8007be9b30, fffffa8007be9e10, fffff800031e15f0}

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: fffffa8007be9b30, Terminating object
Arg3: fffffa8007be9e10, Process image file name
Arg4: fffff800031e15f0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8007be9b30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_C0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`05feeb08 fffff800`032687b2 : 00000000`000000f4 00000000`00000003 fffffa80`07be9b30 fffffa80`07be9e10 : nt!KeBugCheckEx
fffff880`05feeb10 fffff800`03215c9b : ffffffff`ffffffff fffffa80`07fb7b60 fffffa80`07be9b30 fffffa80`07be9b30 : nt!PspCatchCriticalBreak+0x92
fffff880`05feeb50 fffff800`03195094 : ffffffff`ffffffff 00000000`00000001 fffffa80`07be9b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`05feeba0 fffff800`02eddfd3 : fffffa80`07be9b30 fffff880`c0000005 fffffa80`07fb7b60 fffffa80`06e00b60 : nt!NtTerminateProcess+0xf4
fffff880`05feec20 00000000`777215da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01a5d618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777215da


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
---------

Is your SSD firmware up to date?

Is your BIOS up to date? Appears to be...

Are the hard disk controller drivers up to date?

Are the chipset drivers up to date?

Some of your crashes point to memory; they also point to ASUS utility software which is known to cause instability. Remove any ASUS utilities that you are not using. Also, Memtest86+ does not always catch bad RAM, so it may be better to test your RAM by running one module at a time and seeing how the system responds during your normal routine in Windows. Avoid Static Damage to Your PC when swapping memory modules.