This is what your dump shows:
BSOD Index | STOP 0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M
BSOD Analyze Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 801dd000, 0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 801dd000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: YahooMessenger
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 00000000 to 82cc8652
STACK_TEXT:
8079d6a0 00000000 00000007 00000000 00000000 nt!KiSwapThread+0x25b
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
82cc8d80-82cc8d83 4 bytes - nt!KiServiceTable+24
[ c2 f7 f4 82:08 c7 a4 90 ]
82cc8da8-82cc8dab 4 bytes - nt!KiServiceTable+4c (+0x28)
[ cc 4b e7 82:c8 77 f7 91 ]
82cc8e08-82cc8e0b 4 bytes - nt!KiServiceTable+ac (+0x60)
[ ca 9f e4 82:1c d1 a4 90 ]
82cc8e5c-82cc8e63 8 bytes - nt!KiServiceTable+100 (+0x54)
[ ef b7 e8 82 d0 54 f5 82:28 7f a5 90 74 7f a5 90 ]
82cc8e68-82cc8e6b 4 bytes - nt!KiServiceTable+10c (+0x0c)
[ 75 58 ea 82:f6 80 a5 90 ]
82cc8e84-82cc8e87 4 bytes - nt!KiServiceTable+128 (+0x1c)
[ 8e b2 e5 82:96 7e a5 90 ]
82cc8eac-82cc8eb3 8 bytes - nt!KiServiceTable+150 (+0x28)
[ 4d e0 e6 82 85 0a e5 82:ba 7b f7 91 de 7e a5 90 ]
82cc8eb8-82cc8ec3 12 bytes - nt!KiServiceTable+15c (+0x0c)
[ d6 6e f2 82 4b b3 eb 82:10 d3 a4 90 98 d4 a4 90 ]
82cc8edc-82cc8edf 4 bytes - nt!KiServiceTable+180 (+0x24)
[ b0 8d ef 82:9c da a4 90 ]
82cc8eec-82cc8eef 4 bytes - nt!KiServiceTable+190 (+0x10)
[ f3 f7 f4 82:56 c7 a4 90 ]
82cc8f68-82cc8f6b 4 bytes - nt!KiServiceTable+20c (+0x7c)
[ 7a 44 d0 82:ac 78 f7 91 ]
82cc8fc8-82cc8fcb 4 bytes - nt!KiServiceTable+26c (+0x60)
[ fc 0b e1 82:be c3 a4 90 ]
64 errors : !nt (82cc8d80-82cc8fcb)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
--------- Lets start with testing your memory. Follow the tutorial below and test your ram modules preferably overnight for 8 passes:
RAM - Test with Memtest86+
Take your time and post back results