pc crashed

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 LE R2.0
CPU: AuthenticAMD AMD FX(tm)-8320 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255

On Wed 08/07/2015 06:17:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070815-24086-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x1A (0x403, 0xFFFFF6800011B688, 0x9E300002FCEE7867, 0xFFFFF6800011BE88)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time i need help i did a Memtest and it was good

I would suggest that you run Memtest. Use the free version and follow this link:
MemTest86 - Download now!

https://www.sevenforums.com/bsod-help-support/

Blue Screen of Death (BSOD) Posting Instructions

Right, a bit to go through here. If you have any questions on any of the following please ask.

You have Avast and McAfee installed, this is a big no-no as two AVs can and do conflict with each other. In this case Avast has been blamed in one of your BSODs:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff6800011b688, 9e300002fcee7867, fffff6800011be88}

*** WARNING: Unable to verify timestamp for aswSP.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys
Probably caused by : aswSP.sys ( aswSP+130a8 )

Followup: MachineOwner

You need to uninstall both Avast and McAfee using the uninstallers linked below and install MSE.

Avast Uninstaller

Download



McAfee Uninstaller

Download

Also are you running MalwareBytes in realtime? It's shown up in one of your dumps, and while this could possibly be down to the conflicting AVs it will be best to rule it out. If you're running it realtime please stop and just run it on demand for the time being.

   Note

Please note the text highlighted in green in the code below, we'll address that next.

Code:

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  mbamservice.ex

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

As mitchell65 recommended in post #2 a memory test will be required. There are quite a few pointers towards memory corruption in the dumps, and while this could be down to drivers it's possible there is an issue with your RAM or HDD. Please follow the steps listed underneath the code below which is posted for information purposes.

Code:

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsAcquireFcbWithPaging+12c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52e1be8a

IMAGE_VERSION:  6.1.7601.18378

STACK_COMMAND:  .cxr 0xfffff88009f12120 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsAcquireFcbWithPaging+12c

BUCKET_ID:  X64_0x24_Ntfs!NtfsAcquireFcbWithPaging+12c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x24_ntfs!ntfsacquirefcbwithpaging+12c

FAILURE_ID_HASH:  {d7b71d23-e1d3-bb56-df13-7db73f89bc26}

Followup: MachineOwner

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 5efdf001, 0, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ab3 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 000000005efdf001
Arg3: 0000000000000000
Arg4: fffff70001080000

Download and run MemTest86+ to test your RAM. RAM - Test with Memtest86+

   Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

Run chkdsk. Disk Check

Perform the steps listed above to the letter and report back when you've completed each step successfully. If you have any failures while testing the RAM and HDD/s let us know straight away.

Well there's definitely a problem with the RAM. Now you'll need to test each individual stick in each DIMM slot to prove whether it's the RAM itself or one of the DIMM slots.

If the output is like this then you have bad RAM so the stick(s) need replacing.

No code has to be inserted here.

If the output is like this then you should replace the motherboard, however you can leave that DIMM slot empty although it's not advised to use a system with a faulty motherboard.

No code has to be inserted here.

It's the same test (MemTest86+) but you need to test one stick of RAM at a time in each DIMM slot to see where the failure lies. If one stick fails in both DIMM slots the RAM is bad, if two sticks fail in one slot but pass in the other the DIMM slot is bad.