ntkrnlmp.exe causing blue screen...can't figure out

[Malitah]

Been having some BSOD issues lately. Before I did any trouble shooting, I ran memtest, which resulted in several errors. So I dug some old RAM I knew was working, out of storage, and swapped out. It ran fine for about a day, and BSOD'ed again. It's done it 3-4 times in 2 days now. Which is actually less often than before. I haven't tested the "new" RAM, but like I said, I know it was good when I stored it.
I set out on a google quest. I found windbg, and did all that fun stuff, which is how I found out that the culprit is ntkrnlmp.exe....however, I have absolutely no clue what that means, and for the life of me can find anything about it anywhere. I found one thread on here where a guy had a similar problem, with the same file, but his debug info was different.
At any rate, here's my debug info, I hope somebody here can make sense of this, cause I sure cant, lol.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Phoenix\Desktop\073011-22916-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02c9fe50
Debug session time: Sat Jul 30 00:04:13.367 2011 (UTC - 4:00)
System Uptime: 0 days 6:56:46.943
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 406f8, fffff80002adccff}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff80002adccff

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: avp.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002ad1c69 to fffff80002ad2700

STACK_TEXT:
fffff880`035d9ce8 fffff800`02ad1c69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff880`035d9cf0 fffff800`02ad0132 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`035d9e30 fffff800`02adccff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`08c795c4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepMandatoryIntegrityCheck+0x20f


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02ad0132 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

Any input is appreciated, thank you.

Also, I'm aware of forum etiquette, and after my family goes home this weekend, I will look around and see if there is something I can assist someone with. I just thought while I'm busy with family, it would be a good time to wait for a response

[CMB]

Buried in there is
PROCESS_NAME: avp.exe
which I believe is kaspersky antivirus.
Have you tried disabling that ?

[Malitah]

Well, no I haven't. Considering it's my only antivirus. The only thing I could do would be to disable it and let my computer set idle. However, while my computer is idle, it will sit there for days without a BSOD.
I've never heard of an antivirus causing blue screens though. Update problems, and firewall problems, sure, but not blue screens...however, I'm no expert. If you think it's worth a shot, I'll try it.

[no2guncntrl]

I found this over at the KAS forum which explains about
the avp.exe. Can you go into msconfig, click startup and
uncheck the box for Kaspersky at startup and see what
happens ?

http://support.kaspersky.com/kav6mp2/all?qid=208259934

[CMB]

You could disable kaspersky and run microsoft freebie av just to see if the bsod disappears.

[Malitah]

Ok, I'm in the middle of running memtest on all my RAM. I ran it for about 5 hours on all 4 (1gb) sticks at once, and got like 880 errors. So I am currently going through and testing each stick separately. Which brings me to another question. Can a RAM slot go bad?
The first stick i tested was good in slots 1, and 2. I checked it in 3, and got errors. I let it run through 3 full passes each time.
Also, given the fact that windbg listed ntkrnlmp.exe as my problem, could it be RAM?
For the record, I am still going to try disabling Kaspersky once I'm done Mem testing.
I'm just so confused right now.

[SkaarjMaster]

Yes, it's possible for a slot to go bad on the MB. If you have sticks that you know are good and they keep getting memtest errors in slot 3, then slot 3 is bad.

[Malitah]

Just got done running memtest.

Using a stick I knew was good, I tested each slot. Found out Slots 3 and 4 are bad. Then using Slot 1 (which was good...along with slot 2) I tested all my RAM, one at a time. Only 1 stick was bad. I am currently running 2 of the good sticks in slots 1 and 2. So far so good, but it's only been an hour or so, and I haven't really done anything other than web surfing. I'm gonna try to do some gaming here in a bit and see if it holds up.

For the record, while testing RAM/ RAM slots, I let memtest make 2 full passes each time, just to be sure.
I'll keep this thread updated as I find stuff out.