BSOD, possibly memory?

[visibleman]

Long story short, i've been getting BSOD's for a while and originally thought it was down to a dodgy stick of ram (Ballistix PC2-5300 BL2KIT12864AA663.8FE4) which didn't like running at the correct timings (3-3-3-12 @ 2.1/2.2v). Pulled this and the system seemed to be ok.
But recently i've been getting BSOD's again except this time with irql_not_less_or_equal and memory_management errors. I've done the usually MemTest86 and Memtest for Windows and more, info Ballistix DDR2 Possible Woes - Overclockers UK Forums on this charade, and all remaining sticks seemed to check out. System appeared to be stable on Prime for 6hrs and didn't BSOD. Yet i've just put it back together and then Firefox kept crashing before it BSOD with a memory_management error. Then the system kept rebooting just before the windows loading screen and i had to pull a stick to get to boot.

I'm well and trurly stumped by all of this, so it'd be much appreciated if someone could look at my reports/mem dumps and see if any more light could be shed on the situation.

Cheers!

p.s - i've heard that Daemon Tools can cause BSOD's, is it worth removing then?

Edit - System Spec:

CPU - Q6600
Motherboard - Abit IP35 Pro XE (running latest 11 bios)
Ram - 2x Crucial Ballistix PC2-5300 BL2KIT12864AA663.8FE4 2x1GB (so 4GB total)
GPU - BFG 8800GT
PSU - Corsair TX650
OS - Originally XP64, now Win7 x64

Edit 2 - Have uninstall Daemon Tools and uninstalled SPTD driver, will see how that goes. But if someone could look at the memory dumps and see if they spot something that would be brilliant

Edit 3 - Whilst reading the forums, a few of you have said to update network drivers, so i've just update my Realtek Nics to the latest drivers.

 

[Lemur]

Welcome to SF.

This seems to point to memory:

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000031, The subtype of the bugcheck.
Arg2: fffffa8002d19c00
Arg3: fffff88008f31000
Arg4: fffff8a00b0fd9aa

Update your Realtec network driver:

Driver c:\windows\system32\drivers\rt64win7.sys (7.9.1105.2009, 284.50 KB (291,328 bytes), 05/11/2009 13:15)

sptd.sys

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: http://www.duplexsecure.com/en/downloads

 

[visibleman]

Thanks Lemur, much appreciated.
I've removed Daemon Tools, the SPTD driver and have upgraded the network driver to the recent version.
But are you saying that it's still most likely memory that is at fault? I'll leave Memtest86+ running tonight and see what happens, but previously (the link posted highlights the whole checking memory fiasco) the current sticks seemed to check out with the exception that i did get Memtest86 to throws errors once or twice (in different configurations) but could never replicate them.

Cheers again though

 

[Lemur]

Ok. Let's see how it does with the two changes you have made.