Random BSOD, error 0x0000000A

Hello, I've had a BSOD while downloading a game and playing Dwarf Fortress, which are not CPU or GPU intensive activities. This crash happened on the 05th of December 2012 at around 11 o'clock.

Before these BSODs I used to get other crashes of a different more frequent type, but these were because of a faulty video card, which I removed.
Now, after enjoying a BSOD free computer for a few hours I suddently get this one.
Using the program WhoCrashed it says this:

Code:

On Thu 12/6/2012 5:01:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120512-14648-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0xA (0x100000041, 0x2, 0x1, 0xFFFFF80003A9B468)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time. 



On Thu 12/6/2012 5:01:17 AM 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: 0xA (0x100000041, 0x2, 0x1, 0xFFFFF80003A9B468)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.

They are apparently random and don't happen very frequently. (once every three hours or so)

I would really appreciate anyone's help. Thank you for your time.

SPECS: https://www.sevenforums.com/members/toxicfyre.html
Attatched BSOD info.

Welcome to SevenForums :)

AVG can contribute in BSOD-s. Please uninstall it and replace with Microsoft Security Essentials (To test).

• AVG | Download tools and utilities

MSE is recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software:-

1. Microsoft Security Essentials - Free Antivirus for Windows
2. Malwarebytes - Free
3. Good and Free system security combination.

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

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

---

Run the System File Checker. It allows the user to scan for and restore corruptions in Windows system files.

• 
  1. Click on the
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

---

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

• Disk Check

---

Free up the start-up, nothing except the antivirus is usually needed.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

---

Go to this link: Intel® Driver Update Utility and check the system for latest updates. Download and install all the recent driver(s) it finds.

*Post back if this brings stability or you get any BSOD-s after making these changes.

Then test 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+

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.

Errors are sometimes found after 8 passes.
Do this test overnight, before going to bed.

Wheww, that took a long time.
Ok after testing one RAM stick for 8 passes, and the other two for 16 passes, I found two errors on one of them after 15 passes. (I don't know if only two errors is enough O.o)
So I took out that RAM stick with the errors, and am now checking if it will crash. Will post again if it does. :)

Thank you

I just got a crash...

Here is the dump:

Thank's everyone who viewed this thread, and thank you koolkat77 for replying. :)
And for everyone that's gonna reply in the future, thanks in advance. :)

Why'd you enable driver verifier?

Driver Verifier - Enable and Disable

OK.

Post when you have new dumps.

Crash, after a full day of crash free bliss.
Here is the dump:
Thank you so much for helping me. :)
I really appreciate it.

P.S. If it helps, here is my "WhoCrashed" Dump about these recent crashes:

Code:

On Sun 12/23/2012 1:06:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122212-10280-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0x1A (0x41287, 0x77000109A788, 0x0, 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 that cannot be identified at this time. 



On Sun 12/23/2012 12:08:20 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122212-10280-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0x7F (0x8, 0x80050033, 0x6F8, 0xFFFFF80003A8051B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

PP.S Ohh, and both recent crashes happened while I was playing BF3.