BSOD during general use, downloading, code a

Was downloading some updates, got bsod.

Had previous problems with BSOD'ing but I reformatted due to them, problem still persists. I ran a memtest and no problems. Using a new hard drive I just bought.

I would BSOD at least once per day during general use/bootup. It's been a reoccuring problem.

Welcome.

For how many passes did you run memtest?

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\layolan\SF_18-01-2014\011814-21546-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8281c000 PsLoadedModuleList = 0x82964810
Debug session time: Sun Jan 19 07:24:30.517 2014 (UTC + 6:00)
System Uptime: 0 days 0:04:29.001
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {7c9fffec, 2, 1, 828a81d8}

Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+138 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 7c9fffec, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 828a81d8, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82984718
Unable to read MiSystemVaType memory at 82964160
 7c9fffec 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiRemoveAnyPage+138
828a81d8 f00fba2800      lock bts dword ptr [eax],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  332.21-desktop

TRAP_FRAME:  8ee6179c -- (.trap 0xffffffff8ee6179c)
ErrCode = 00000002
eax=7c9fffec ebx=7c9fffec ecx=00000002 edx=00000001 esi=7c9fffe4 edi=84fdf808
eip=828a81d8 esp=8ee61810 ebp=8ee61868 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MiRemoveAnyPage+0x138:
828a81d8 f00fba2800      lock bts dword ptr [eax],0   ds:0023:7c9fffec=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828a81d8 to 828627eb

STACK_TEXT:  
8ee6179c 828a81d8 badb0d00 00000001 85208ea8 nt!KiTrap0E+0x2cf
8ee61868 828b0273 00000002 00000000 a5773540 nt!MiRemoveAnyPage+0x138
8ee61890 8287e878 00000005 00000000 a0d61000 nt!MiGetPage+0x28a
8ee6194c 828aec17 a60e7000 02a5fb40 00000000 nt!MmCopyToCachedPage+0x56a
8ee619e0 828b1bfc 85208ea8 02a5fb40 8ee61a30 nt!CcMapAndCopyInToCache+0x1f0
8ee61a38 8b2364d2 85221418 8ee61b1c 001082a5 nt!CcCopyWrite+0x1d9
8ee61b48 8b23785f 8518b9b0 8518b008 05c050ae Ntfs!NtfsCommonWrite+0x22e9
8ee61bc0 828584bc 85f5b020 8518b008 8518b008 Ntfs!NtfsFsdWrite+0x2e1
8ee61bd8 8b11520c 85f63c20 8518b008 00000000 nt!IofCallDriver+0x63
8ee61bfc 8b1153cb 8ee61c1c 85f63c20 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
8ee61c34 828584bc 85f63c20 8518b008 8518b008 fltmgr!FltpDispatch+0xc5
8ee61c4c 82a59eee 85221418 8518b008 8518b1e0 nt!IofCallDriver+0x63
8ee61c6c 82a5a7a2 85f63c20 85221418 00000001 nt!IopSynchronousServiceTail+0x1f8
8ee61d08 8285f42a 85f63c20 00000000 00000000 nt!NtWriteFile+0x6e8
8ee61d08 77a064f4 85f63c20 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
029ffb48 00000000 00000000 00000000 00000000 0x77a064f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRemoveAnyPage+138
828a81d8 f00fba2800      lock bts dword ptr [eax],0

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRemoveAnyPage+138

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiRemoveAnyPage+138

BUCKET_ID:  0xA_nt!MiRemoveAnyPage+138

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

Please run it again.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Upload new SF log.

Stop editing the original post. How one will determine which one is the latest files in that crowd??

Upload the zip and attach it with your subsequent post only.