BSOD several times a day different stop errors

I have been getting several blue screens a day with different stop errors.

i have attached the dmp files, please help.

i am using 64 bit windows 7.

There were not many dump files included in your crash report. If you are using any disk cleaning software (CCleaner, Windows Disk Cleanup, etc.), they can delete dump files after crashes occur, so please do not run them after your crashes. Also, make sure your dump files are configured correctly by following the steps in Dump Files - Configure Windows to Create on BSOD OPTION ONE part 6.

Code:

Loading Dump File [F:\BSODDmpFiles\Mbox\Windows_NT6_BSOD_jcgriff2\020112-16910-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a49000 PsLoadedModuleList = 0xfffff800`03c8e670
Debug session time: Wed Feb  1 12:32:01.511 2012 (GMT-7)
System Uptime: 0 days 2:50:32.667
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003ad1a9b, fffff8800872a0b0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )

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

2: 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: fffff80003ad1a9b, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800872a0b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!KiInsertTimerTable+13b
fffff800`03ad1a9b 488b42f8        mov     rax,qword ptr [rdx-8]

CONTEXT:  fffff8800872a0b0 -- (.cxr 0xfffff8800872a0b0)
rax=0000000000000002 rbx=fffffa800732cc20 rcx=0000000000000002
rdx=00fffa800800a940 rsi=0000000000000a00 rdi=fffff88002f64180
rip=fffff80003ad1a9b rsp=fffff8800872aa90 rbp=fffff88002f66d88
 r8=ffffffffffffffff  r9=0000000000000040 r10=fffff88002f64180
r11=00000000002f5b00 r12=fffff88002f66d88 r13=0000000000000001
r14=0000000000000000 r15=00000017d325412c
iopl=0         nv up ei pl nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010217
nt!KiInsertTimerTable+0x13b:
fffff800`03ad1a9b 488b42f8        mov     rax,qword ptr [rdx-8] ds:002b:00fffa80`0800a938=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003acb092 to fffff80003ad1a9b

STACK_TEXT:  
fffff880`0872aa90 fffff800`03acb092 : fffffa80`0732cb60 fffffa80`0732cb60 00000000`00000000 00000000`00000002 : nt!KiInsertTimerTable+0x13b
fffff880`0872aaf0 fffff800`03acc742 : 00000000`00000000 00000000`00000000 00000000`00000040 00000000`00000000 : nt!KiCommitThreadWait+0x332
fffff880`0872ab80 fffff800`03dbc4de : fffffa80`0732cb60 fffff800`03ac4f11 00000000`0fc4f100 00000000`00000040 : nt!KeDelayExecutionThread+0x186
fffff880`0872abf0 fffff800`03ac4ed3 : 00000000`12b2d450 fffff880`0872aca0 ffffffff`ffffd8f0 00000000`7eef1000 : nt!NtDelayExecution+0x59
fffff880`0872ac20 00000000`74c42e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0fc4f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74c42e09


FOLLOWUP_IP: 
nt!KiInsertTimerTable+13b
fffff800`03ad1a9b 488b42f8        mov     rax,qword ptr [rdx-8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiInsertTimerTable+13b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff8800872a0b0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiInsertTimerTable+13b

BUCKET_ID:  X64_0x3B_nt!KiInsertTimerTable+13b

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

This crash report was fairly inconclusive. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver...


Thanks to Dave76 for help understanding possible causes.



Proceed with the following steps. Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• 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
  
  
  
• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
  
  
  
• Update your display card drivers.
  
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
     
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  8. Restart your computer after uninstalling drivers for all display cards
  9. Install the latest driver for the display cards once Windows starts
  
  
  Alternatively:
  
  1. Login as an adminstrative user
  2. Download the latest drivers for your display card(s)
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Expand Display adapters
  8. Do the following for each adapter (in case you have multiple display cards)
     
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  9. Restart your computer after uninstalling drivers for all display cards
  10. Install the latest driver for the display cards once Windows starts
  
  
  
  
• Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode.
  
  
  
• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
  
  
  
• Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.