BSOD Doing everyday actions on my computer

Hello Samweeze.

Apparently I am finding it is your antivirus that is causing the crash. Trend Micro Internet Security

Code:

fffff880`073a3f58  fffff880`02ded5d8Unable to load image \SystemRoot\system32\DRIVERS\tmevtmgr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tmevtmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for tmevtmgr.sys
 tmevtmgr+0xa5d8

Description here.

Uninstall Trend Micro. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

You dont have Service pack 1 installed. So it vulnerable to any threats.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17118.amd64fre.win7_gdr.120830-0334

Install Service pack 1.
Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Let us know the results. And, if there is a further problem, provide us with some more useful information. Upload your SystemInfo.txt file, alongwith the further crash dumps.

• Click this button of SF Diag Tool.
  
• Zip the output on desktop
• Upload it here following Screenshots and Files - Upload and Post in Seven Forums

Most probably it is a hardware error.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800030827dd, fffff88003193a78, fffff880031932e0}

Probably caused by : hardware ( nt!KiStartSystemThread+16 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800030827dd, The address that the exception occurred at
Arg3: fffff88003193a78, Exception Record Address
Arg4: fffff880031932e0, Context Record Address

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!ExpWorkerThread+ed
fffff800`030827dd 3002            xor     byte ptr [rdx],al

EXCEPTION_RECORD:  fffff88003193a78 -- (.exr 0xfffff88003193a78)
ExceptionAddress: fffff800030827dd (nt!ExpWorkerThread+0x00000000000000ed)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000059200000000
Attempt to write to address 0000059200000000

CONTEXT:  fffff880031932e0 -- (.cxr 0xfffff880031932e0)
rax=0000000000000001 rbx=fffff80003069220 rcx=0000000000000000
rdx=0000059200000000 rsi=fffffa8006a1d040 rdi=fffffa8006a21ee0
rip=fffff800030827dd rsp=fffff88003193cb0 rbp=fffff800032195a0
 r8=fffff88002f68750  r9=0000000000000000 r10=0000000000000002
r11=fffffa8006a21550 r12=fffffa8006a21ee0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ExpWorkerThread+0xed:
fffff800`030827dd 3002            xor     byte ptr [rdx],al ds:002b:00000592`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000059200000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ac0e0
GetUlongFromAddress: unable to read from fffff800032ac198
 0000059200000000 Nonpaged pool

FOLLOWUP_IP: 
nt!KiStartSystemThread+16
fffff800`03053ac6 48c7c10e000000  mov     rcx,0Eh

BUGCHECK_STR:  0x7E

MISALIGNED_IP: 
nt!ExpWorkerThread+ed
fffff800`030827dd 3002            xor     byte ptr [rdx],al

LAST_CONTROL_TRANSFER:  from fffff8000331496a to fffff800030827dd

STACK_TEXT:  
fffff880`03193cb0 fffff800`0331496a : 00000000`00000000 fffffa80`06a1d040 00000000`00000080 fffffa80`06a05b30 : nt!ExpWorkerThread+0xed
fffff880`03193d40 fffff800`03053ac6 : fffff880`02f64180 fffffa80`06a1d040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03193d80 00000000`00000000 : fffff880`03194000 fffff880`0318e000 fffff880`031939f0 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiStartSystemThread+16

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff880031932e0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.


Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

It seems that some of latest crashes were failed to be recorded. Amd, there are some other issues, too.

Uninstall Trend Micro. ** Do you use Norton too? Two AV programs installed at the same time is very harmful. Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one. Scan the system for possible virus infection with these programs, too.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Uninstall Registry Kit. It is not only unnecessary, but also harmful. It may cause damages to the file system beyond repair. After uninstalling it, run SFC /SCANNOW Command - System File Checker

Let us know the results.