BSOD every ~30 min (Win 7 64b)

...trying to write this info quick before the next BSOD comes. This is my second attempt as the first BSOD got me in the middle of writing the post which has you questioning why I'm wasting time writing th....

Every 30 min or so the computer will stop responding correctly (examples: applications stop responding, my DU Meter application will say data stale, music currently playing starts continuous loop of last 5 seconds or so it played) which is followed by a BSOD a minute or so later.

-Hp elite desktop w Intel i7
Windows 7 premium 64 bit w OS preinstalled (never reinstalled)
owned system about 2 years
-upgraded psu to Corsair HX650W about 6 months ago to allow use of high power video card (video card has been removed in an attempt to problem solve this issue, but problem remains with card removed)
-did individually remove each stick of ram to see if one stick could have been the culprit...system still BSOD'd in all cases.

RAM tested with Memtest86+ with no errors found

Malware bytes is clean with no errors...

Ran current Kaspersky virus scan with nothing found (with boot cd)

Enabled Driver Verifier (created restore point etc first) and the computer would BSOD while booting up. Had to use the restore point to get back up and running...

What do you suggest now? Is there a log file of some sort from the Driver Verifier that I ran to track down which driver caused the BSOD? The BSOD error was very generic and not driver specific.

I'm quite confident that my problem is hardware specific but if there was something I could disable...even with a slow down in computer performance to avoid the restarts, I'm ok with that rather than purchasing new hardware at the moment. Let me know where to go from here...thanks!

I am an interim helper for JaidynM while she is out of town. Did the blue screens with Verifier running result in any new .dmp files being generated? Upload your latest crash logs and we can see if the Verifier crashes gave any new, useful information.

For my first post I followed the instructions on what to post for the BSOD and followed this sequence to create a zip file with the files requested (this is the sequence I followed). Would you like me to do that same sequence again or find individual .dmp files for you? I have no problem doing either, just let me know and I'll do it immediately. Thanks!

Follow the sequence. It will provide better information, especially since I am trying to catch up in this thread. :)

After running the sequence again as requested here are the files in a zip: attached...Thank you for the help.

Security Software: ??? I would recommend Good and Free system security combination. since you already have two of those programs installed. You just need to install Microsoft Security Essentials - Free Antivirus for Windows now.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\winryan\Windows_NT6_BSOD_jcgriff2\040412-15475-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`04605000 PsLoadedModuleList = 0xfffff800`04849650
Debug session time: Wed Apr  4 01:08:05.646 2012 (UTC - 6:00)
System Uptime: 0 days 1:03:01.583
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8009dc0060, fffffa8009dc0340, fffff800049845f0}

Probably caused by : csrss.exe

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

0: 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: fffffa8009dc0060, Terminating object
Arg3: fffffa8009dc0340, Process image file name
Arg4: fffff800049845f0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8009dc0060

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`0699f0e8 fffff800`04a0b7b2 : 00000000`000000f4 00000000`00000003 fffffa80`09dc0060 fffffa80`09dc0340 : nt!KeBugCheckEx
fffff880`0699f0f0 fffff800`049b8c9b : ffffffff`ffffffff fffffa80`0b530b60 fffffa80`09dc0060 fffffa80`09dc0060 : nt!PspCatchCriticalBreak+0x92
fffff880`0699f130 fffff800`04938094 : ffffffff`ffffffff 00000000`00000001 fffffa80`09dc0060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`0699f180 fffff800`04680fd3 : fffffa80`09dc0060 fffff800`c0000005 fffffa80`0b530b60 00000000`028d06f0 : nt!NtTerminateProcess+0xf4
fffff880`0699f200 fffff800`0467d570 : fffff800`046ccaff fffff880`0699fb78 fffff880`0699f8d0 fffff880`0699fc20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0699f398 fffff800`046ccaff : fffff880`0699fb78 fffff880`0699f8d0 fffff880`0699fc20 00000000`028d1f30 : nt!KiServiceLinkage
fffff880`0699f3a0 fffff800`046813c2 : fffff880`0699fb78 00000000`0000d828 fffff880`0699fc20 00000000`028d1a08 : nt! ?? ::FNODOBFM::`string'+0x48e24
fffff880`0699fa40 fffff800`0467ff3a : 00000000`00000001 00000000`028d0ca8 00000000`00000001 00000000`0000d828 : nt!KiExceptionDispatch+0xc2
fffff880`0699fc20 00000000`77ca8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`028d0cb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ca8e3d


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

The crash did not indicate Verifier enabled. Please ensure verifier is enabled by running an Elevated Command Prompt and typing

verifier /query

and making sure there are drivers listed.


Also, for the crash reported, this usually means data corruption has taken place on the system.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

WSE installed. Ran a scan which did not find any problems.

About the verifier...I noticed that with the BSOD scan I ran to collect the info for you, it collected 19 mini dmp files. There is no doubt that I experienced 19 crashes between the time of running verifier having my system be unable to boot, having windows restore the system to a previous state that it could run from, and then send this info to you, so I believe the info sent to you was too long a time after I ran verifier for that info to be included in the report At least that's my guess on why no information was present about the info that could have been obtained in the .dmp files while I did have the verifier enabled (which made my system unbootable)

I am doing no type of overclocking etc at all.

Now after paying close attention to the time at which my BSOD crashes are occuring, they are actually happening at a constant amount of time after bootup! It's almost exactly an hour from the time I log in to windows. I'm assuming that's pretty important in diagnosing this and that having a trace or log of some sort looking at what's going on right before the crash would be useful?

In any case, I am proceeding to do the disk checks and system file checks you have requested now.

As always, thanks for the help!