[SOLVED] BSOD unexpected kernel mode trap

Solution
The UNEXPECTED_KERNEL_MODE_TRAP stop code has a reason code in argument 1 (0x8) indicating an EXCEPTION_DOUBLE_FAULT. This means that whilst the kernel was handling an exception (an unexpected event), a second exception occurred. This type of error generally only occurs in third-party drivers, so we're looking for a suspect third-party driver.

The stack text in the dump, which is a record of all modules that have been called, shows that the Easy Ant-Cheat module eaanticheat.sys was called several times immediately prior to the bugcheck...
Rich (BB code):
STACK_TEXT:
ffffd180`e3a59d28 fffff800`36e0af69     : 00000000`0000007f 00000000`00000008 ffffd180`e3a59e70 fffff002`40278fb0 : nt!KeBugCheckEx
ffffd180`e3a59d30 fffff800`36e05d83     ...
Hi,
I'm getting this bsod error frequently, please can someone tell me what the memory dump says and how I could fix it.
If you need anymore info, just ask.
Thank you

Motherboard: MSI MAG Z690 TOMAHAWK WIFI DDR4
CPU: i7-12700K
RAM: Corsair Vengeance LPX 32GB (4 x 8GB) DDR4-3600MHz Memory

Memory.dmp:
https://drive.google.com/file/d/1yQPUt4BclGpNk5WF5yaQSJS0KkU85o2s/view?usp=sharing
There are a couple of reasons this error could occur. The most common reason you will see this error is if you have a faulty RAM module that randomly gives read/write errors. If you find this is your problem, you will need to scan your system and replace the faulty RAM module.

Or bios needs a update

Or ram is unsupported by this mobo

Also improper or no chipset drivers will cause the issue due to failed readings from the complete system basically
 
  • Like
Reactions: andrew051098

Colif

Win 11 Master
Moderator
Conversion of dumps

report - Click run as fiddle to see report

File: MEMORY.DMP (Sep 28 2022 - 07:03:05)
BugCheck: [UNEXPECTED_KERNEL_MODE_TRAP (7F)]
Probably caused by: memory_corruption (Process: lsass.exe)
Uptime: 0 Day(s), 0 Hour(s), 10 Min(s), and 41 Sec(s)

how long you been using 2 sets of ram?
8192MB3600MHzCorsairCMK16GX4M2D3600C18
8192MB3600MHzCorsairCMK16GX4M2D3600C18
8192MB3600MHzCorsairCMK16GX4M2D3600C18
8192MB3600MHzCorsairCMK16GX4M2D3600C18
https://www.corsair.com/us/en/Categories/Products/Memory/VENGEANCE-LPX/p/CMK16GX4M2D3600C18
just cause they both same sticks doesn't mean they work together. Sticks in sets tested to ONLY work with other sticks in that set. More you try to mix, more chance of errors
Intel better at it than AMD are but it still could be cause.
try taking 1 set out and see if you still BSOD

how many Anti cheat apps do you have?
I see Vanguard but the stack text seems to refer to Easy Anti cheat as well or maybe EA Anti cheat.
 

ubuysa

Distinguished
The UNEXPECTED_KERNEL_MODE_TRAP stop code has a reason code in argument 1 (0x8) indicating an EXCEPTION_DOUBLE_FAULT. This means that whilst the kernel was handling an exception (an unexpected event), a second exception occurred. This type of error generally only occurs in third-party drivers, so we're looking for a suspect third-party driver.

The stack text in the dump, which is a record of all modules that have been called, shows that the Easy Ant-Cheat module eaanticheat.sys was called several times immediately prior to the bugcheck...
Rich (BB code):
STACK_TEXT:
ffffd180`e3a59d28 fffff800`36e0af69     : 00000000`0000007f 00000000`00000008 ffffd180`e3a59e70 fffff002`40278fb0 : nt!KeBugCheckEx
ffffd180`e3a59d30 fffff800`36e05d83     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd180`e3a59e70 fffff800`370290c5     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c3
fffff002`40278fb0 fffff800`370289f7     : ffffa10b`19190010 ffffa10a`f16ce4e0 00000000`00000000 00000000`00000000 : nt!ObpCaptureObjectCreateInformation+0x25
fffff002`40279050 fffff800`37072d5f     : ffffa10a`00000000 fffff002`40279618 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0xc7
fffff002`40279180 fffff800`3707281d     : fffff002`40279750 00000000`00000000 fffff002`40279618 fffff002`402794b0 : nt!IopCreateFile+0x40f
fffff002`40279220 fffff800`34beb7d3     : fffff800`34c04701 fffff002`40279379 ffffa10b`195b8128 00000000`00000000 : nt!IoCreateFileEx+0x11d
fffff002`402792c0 fffff800`34c047ad     : fffff800`34c04720 fffff804`13e180f0 00000000`8791206e fffff804`00000000 : FLTMGR!FltpCreateFile+0x16f
fffff002`402793b0 fffff804`13e16c75     : ffffa10b`18153258 00000001`00000000 fffff002`402794b0 00000001`00000000 : FLTMGR!FltCreateFile+0x8d
fffff002`40279440 fffff804`13e1ad31     : 00000000`00000200 00000000`00000000 00000000`000000a0 fffff800`373b2094 : eaanticheat+0x236c75
fffff002`402796c0 fffff804`13ee4399     : fffff804`13f0c04d fffff804`13ee342d 5bd623f9`1a332a56 fffff804`13ee335c : eaanticheat+0x23ad31
fffff002`402797c0 fffff804`13ef0b3b     : cb0f8f59`00000082 00000000`00000000 00000000`00000000 00000000`00000000 : eaanticheat+0x304399
fffff002`40279c80 fffff804`13f00ac7     : fffff804`13f0c040 fffff002`40279e20 01000000`aea378fd 00000000`1abda346 : eaanticheat+0x310b3b
fffff002`40279dd0 fffff800`3700a96c     : ffffb105`75eb4780 ffffa10a`f16c8598 fffff002`4027a548 00000000`00000000 : eaanticheat+0x320ac7
fffff002`4027a490 fffff800`3700aada     : 00000000`00000001 00000000`00000000 00000000`00000000 ffffb8bb`dd64df5a : nt!ObpCallPreOperationCallbacks+0x10c
fffff002`4027a510 fffff800`37003f23     : ffffa10a`f16c84e0 fffff002`4027a6a0 fffff002`4027ab20 fffff002`4027ab20 : nt!ObpPreInterceptHandleCreate+0xaa
fffff002`4027a580 fffff800`37082c29     : fffff002`4027ab20 ffffa10b`198a2080 ffffd180`e3a00180 00000000`00000000 : nt!ObpCreateHandle+0xce3
fffff002`4027a790 fffff800`37019a2f     : 00000000`00000001 fffff002`4027ae60 00000000`00000000 fffff802`00000001 : nt!ObOpenObjectByPointer+0x1b9
<snip>

The failure bucket in the dump also clearly points at eaanticheat.sys...
Rich (BB code):
FAILURE_BUCKET_ID:  0x7f_8_eaanticheat!unknown_function

The version of the eaanticheat.sys driver that you have installed is very new...
Rich (BB code):
8: kd> lmDvm eaanticheat
Browse full module list
start             end                 module name
fffff804`13be0000 fffff804`15128000   eaanticheat   (no symbols)        
    Loaded symbol image file: eaanticheat.sys
    Image path: \SystemRoot\system32\drivers\eaanticheat.sys
    Image name: eaanticheat.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Sep  9 23:39:02 2022 (631BA466)
    CheckSum:         0157A4E1
    ImageSize:        01548000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

You might want to contact the Easy Anti-Cheat technical support and see whether problems have been reported with this version of eaanticheat.sys.

Unless they can help you quickly I would suggest that you manually uninstall East Anti-Cheat using the instructions here and see whether the BSODs stop.
 
Solution