Help! Computer randomly restarts and/or powers off UNEXPECTED_KERNEL_MODE_TRAP_M

[skilletrx]

HELP with BSOD UNEXPECTED_KERNEL_MODE_TRAP_M

Hey guys, I need help w/ my BSOD, I never get the blue screen, my computer just randomly reboots/andor/ powers off when it wants to... so I had to run the debugger to get the BSOD information. I have pasted the debug info below. This is on a new fresh xp install, no drivers are updated. Used several RAM modules, and the funny thing is, no matter what I DDR module I test... the computer will always just power off in the middle of the RAM test (I used MS, not memtest86's prog). I've thought about updating the BIOS but on my motherboards site, the version that is posted is lower than the current one I have. My mobo is the MSI 661FM2-V. I have all the windows updates, thanks in advance for your help this has baffled me for a few weeks now, thought I'd get the world on this matter

--------

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


Loading Dump File [C:\windows\minidump\mini032506-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: c:\windows\i386
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Mar 25 06:14:05.133 2006 (GMT-5)
System Uptime: 0 days 11:07:46.247
Loading Kernel Symbols
.................................................. .................................................. ...................
Loading User Symbols
Loading unloaded module list
.........................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 80042000, 0, 0}

Probably caused by : hardware ( nt!KiTrap0D+16a )

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

0: kd> !analyze -show
Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
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: 80042000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

MISALIGNED_IP:
nt!KiTrap0D+16a
804e02c0 308ed88ec08b xor [esi+0x8bc08ed8],cl

LAST_CONTROL_TRANSFER: from 00000000 to 804e02c0

STACK_TEXT:
f698003c 00000000 f93818d8 ff9f0023 00210893 nt!KiTrap0D+0x16a
WARNING: Frame IP not in any known module. Following frames may be wrong.
ffb55668 00000000 00000000 00000000 00000000 0x0


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0D+16a
804e02c0 308ed88ec08b xor [esi+0x8bc08ed8],cl

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTrap0D+16a

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

 

[altheman]

and the funny thing is, no matter what I DDR module I test... the computer will always just power off in the middle of the RAM test .

try testing one ram module first, with the other one removed, and then test the other one in the same way. try also using memtest, it runs in dos mode it should work better. that way you can find out which of the ram is faulty, or eliminate the ram modules as the problem.