Windows 10: unexpected_kernel_mode_trap

Okay
so this is the third BSOD in a year
But now the BSOD message was unexpected_kernel_mode_trap
What could it be?
Hope the symbol files are already available

:)

 

Phantom USB causing kernel mode bsod

That error was an 0x7f (UNEXPECTED_KERNEL_MODE_TRAP).

Can you provide the memory.dmp file from that crash?

 

Windows 10

Why do I get the message unexpected_kernel_mode_trap and how can I fix it?

 

Latest dump (12/8) shows this:
Code: 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: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: ffffc500474d7b30 Arg3: ffffc500489a2ee0 Arg4: fffff8026bbdf9d0[/quote] May or may or may not be a memory problem but let's start by testing your ram. You have 16GB so it's going to take 12 hours or so for a full 8 passes which is the minimum needed for a good test.

===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

 

Alright
I was unable to complete the 8 passes since the power went down
Last time I saw it, it was on the 4 pass with no errors
But I also updated the bios before you answered the thread
When checking the list of compatible memory module I just saw that my ram was added recently(and it said it was compatible with the xmp profile), so it could have just been unstable at 2400mhz on the old bios
I will update when I have the time to run the 8 passes of memtest
Thank you for your help.
By the way, I noticed that memtest86+ didnt recognize the frequency of the ram module, It said DDR3-0
So I assume it doesnt recognizes DDR4, I dont think it would affect the test but you may know better

 

I finally was able to run 8 passes and no errors whatsoever

 

How is it running as far as BSODs now?

 

So far no BSOD's, It might have been the overclocked ram all this time since the last time I updated the bios was like in march
Well thanks for your help
I'm gonna mark this as solved

 

Might want to give it a week or so then of okay mark as solved.