BSOD while doing various tasks, error 0x1A

Hi! My computer's been randomly bluescreening for a long time now and it's exhausting, i'm almost to the point of getting a new computer. It happens out of the blue, sometimes while playing world of warcraft, sometimes while cruising the internet, it doesnt necessarily happen while running any one program.

On Mon 10/29/2012 3:35:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-33852-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x50 (0xFFFFFA8056D900C8, 0x0, 0xFFFFF80002D9ADEC, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 10/29/2012 3:35:56 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFFA8056D900C8, 0x0, 0xFFFFF80002D9ADEC, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 10/26/2012 4:55:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102612-37580-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800572B3B0, 0xFFFF, 0x0)
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 which cannot be identified at this time.

https://www.sevenforums.com/crashes-d...tructions.html

Hmm, consider switching your antivirus, on permanent basis. AVG is contributing in BSODs as I see in your dumps. Use the removal tool for AVG, make sure nothing related to AVG is left on your computer.

• AVG | Download tools and utilities

Recommended antivirus program for Windows 7 based on stability compared to others:-

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes - The Free version
• Good and Free system security combination.

Run a full scan with both (separately) once downloaded, installed and updated.

Code:

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA 
Usual causes:  Defective hardware (particularly memory - but not just RAM), 
Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
BugCheck 50, {fffffa8056d900c8, 0, fffff80002d9adec, 5}
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc )
===========================================================================
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA 
Usual causes:  Defective hardware (particularly memory - but not just RAM), 
Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
BugCheck 50, {fffff8a05532f870, 1, fffff880012e0ad5, 5}
Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+31 )
===========================================================================
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes:  Device driver, memory, kernel
BugCheck 1A, {41790, fffffa800572b3e0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
===========================================================================
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c0000005, fffff88004322e29, fffff8800a548510, 0}
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
Probably caused by : avgldx64.sys ( avgldx64+12e29 )

Code:

Start Menu\Programs\Alcohol 120%    Public:Start Menu\Programs\Alcohol 120%    Public

Remove Daemon Tools/Alchohol%, sptd.sys is known to cause BSODs!

• How to remove sptd.sys from system

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• SFC /SCANNOW Command - System File Checker

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• Disk Check

For the 1A BugCheck BSODs, proceed with testing your ram.

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

• RAM - Test with Memtest86+
• Guide to using Memtest86+ - Geeks to Go Forums

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.

Let us know the results and further BSODs

Were the blue screen issues resolved?