You have stop 0x24 errors.
Please see this for further information that could be helpful to you:
http://msdn.microsoft.com/en-us/library/ms793935.aspx
Run chkdsk /r command for each partition and /or drive on the system.
For example:
chkdsk /r C:
for C: etc...change to D: for another partition until all are finished.
Do this from an elevated command prompt. Copy and paste can be used.
memtest has been running this whole time, and just 2 seconds ago I got errors galore...
not really sure what any of them mean tho, i just see a bunch of red..
i'll try what you are suggesting in a bit..
Multiple errors in Memtest mean you've got memory problems.
Follow Steps 7 to 10 in this link to test the sticks and the slots individually: http://www.carrona.org/memdiag.html
that's what i've been doing today. I brought my pc to work so I can work better on the bench.
I'll post more once I know more..
Both sticks have failed numerous times in multiple slots.
I have requested an RMA from OCZ, so once I get the new RAM, I will update the post.
Thank you guys for your help so far.
do yo need to use memtest on win7 machines??? or the built in memory diagnostics on the boot menu?
Ok well here's an update:
Since my last post I had gotten a hold of another pair of RAM and tested my slots to make sure it wasn't my mobo. It wasn't, they both passed. So then I tried resetting my CMOS. That seemed to fix
the problem. I haven't had a BSOD since that night. Then just a few minutes ago I did.
I want to see if it's still memory related. I have included the dump.
I also ran the Windows Memory Diagnostics Tool and while it was running it said (immediately) that there were hardware problems, but when I logged into windows, after the scan, there was no
logfile. Or I just don't know where to find it.
I guess I still do have to go forth with the RMA to OCZ.
Just want to wait to make sure that the dumpfile says its RAM related again.
Thanks in advance.
That's showing a 0xC2 error with mpfilter.sys, which is a Microsoft Windows Malware protection system driver file.
As a theory, possibly some malware is running on the pc that could be causing this. You could scan with Malwarebytes to see or possibly others too.
But yeah, it is some type of memory error.
"The current thread attempted to free the pool, which was already freed."
Quote