Windows 10: Unexpected Kernel Mode Trap BSOD

Hello, I've been having an issue where I get a BSOD with Unexpected Kernel Mode Trap while playing the Halo Master Chief Collection for PC. From what I understand this issue is caused by out of date drivers. I have run windows update to make sure I have my most recent drivers and I've updated my graphics card drivers. My specs are AMD FX-8320, 8 gb ddr3 ram, msi 970A-43 PLUS, AMD R9 280. I'll post the dump below, thank you for your help.


MEMORY.DMP says

Microsoft R Windows Debugger Version 10.0.18362.1 AMD64
Copyright c Microsoft Corporation. All rights reserved.



Microsoft R Windows Debugger Version 10.0.18362.1 AMD64
Copyright c Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP 8 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff806`57800000 PsLoadedModuleList = 0xfffff806`57c48150
Debug session time: Wed Apr 8 00:03:22.802 2020 UTC - 4:00
System Uptime: 0 days 22:25:45.956
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
PEB is paged out Peb.Ldr = 00000094`96404018. Type ".hh dbgerr001" for details
Loading unloaded module list
.................................................
For analysis of this file, run !analyze -v
5: 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: ffff8f01bfa840b0
Arg3: ffff8389340a8f50
Arg4: fffff8065790b0eb

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7974

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: V1.1

BIOS_DATE: 07/04/2016

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: 970A-G43 PLUS MS-7974

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: 8

BUGCHECK_P2: ffff8f01bfa840b0

BUGCHECK_P3: ffff8389340a8f50

BUGCHECK_P4: fffff8065790b0eb

BUGCHECK_STR: 0x7f_8

TRAP_FRAME: ffff8f01bfa840b0 -- .trap 0xffff8f01bfa840b0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000200
rdx=0000000000000200 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8065790b0eb rsp=ffff8389340a8f50 rbp=ffff8389340a9050
r8=0000000045504950 r9=0000000000000000 r10=fffff80657b6f030
r11=ffff7efea7400000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!ExAllocateHeapPool+0x2b:
fffff806`5790b0eb 4889742440 mov qword ptr [rsp+40h],rsi ss:0018:ffff8389`340a8f90=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: dac

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

BLACKBOXBSD: 1 !blackboxbsd


BLACKBOXNTFS: 1 !blackboxntfs


BLACKBOXPNP: 1 !blackboxpnp


BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: MCC-Win64-Shipping-WinStore.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-2U1RDLA

ANALYSIS_SESSION_TIME: 04-08-2020 00:25:43.0448

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

STACK_OVERFLOW: Stack Limit: ffff8389340a9000. Use kF and !stackusage to investigate stack usage.

STACKUSAGE_FUNCTION: The function at address 0xfffff8065f602936 was blamed for the stack overflow. It is using 1296 bytes of stack total in 9 instances likely recursion.

FOLLOWUP_IP:
ViGEmBus+2936
fffff806`5f602936 488b0ddb970000 mov rcx,qword ptr [ViGEmBus+0xc118 fffff806`5f60c118]

STACK_COMMAND: .trap 0xffff8f01bfa840b0 ; kb

THREAD_SHA1_HASH_MOD_FUNC: 1f3ef9396dfc0a3334e7153fc81240d91fa9a310

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7f25e228705db64661333148c8575fcb10662c0c

THREAD_SHA1_HASH_MOD: d78f25681fae3324731e386bf6b9753ba844bf25

FAULT_INSTR_CODE: db0d8b48

SYMBOL_STACK_INDEX: f

SYMBOL_NAME: ViGEmBus+2936

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ViGEmBus.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5bc7792b

MODULE_NAME: ViGEmBus

BUCKET_ID_FUNC_OFFSET: 2936

FAILURE_BUCKET_ID: 0x7f_8_STACK_USAGE_RECURSION_ViGEmBus!unknown_function

BUCKET_ID: 0x7f_8_STACK_USAGE_RECURSION_ViGEmBus!unknown_function

PRIMARY_PROBLEM_CLASS: 0x7f_8_STACK_USAGE_RECURSION_ViGEmBus!unknown_function

TARGET_TIME: 2020-04-08T04:03:22.000Z

OSBUILD: 18362

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 6721

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x7f_8_stack_usage_recursion_vigembus!unknown_function

FAILURE_ID_HASH: {73342f3e-7fac-40ea-eac7-3252959239c9}

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

:)

 

[Windows 10 BSOD] Unexpected Kernel Mode Trap

Unexpected kernel mode trap BSOD always appears when I try to update Windows 10 or reset the PC.

I've tried many solutions, such as:

-Disconnecting external devices

-Booting in safe mode

-Memory diagnostic

-chkdsk

none of which worked. Any suggestions to this problem would be greatly appreciated, thanks!

 

Unexpected kernel mode trap bsod

Recently crashed with a unexpected kernel mode trap error. No hardware or software changes have been made recently. Attached is link to memory dump files and my msinfo. Any suggestions on where to start troubleshooting will be welcome.

Troubleshooting files: Public

Thanks

 

unexpected kernel mode trap

I have trouble with the unexpected kernel mode trap for quite a while. It might began with installing Bitdefender. But I removed it and still have trouble. Most of the time it happens when in Firefox but not always.

I reduced the kernel dump to 128 but the BSOD still happened but this time outside of Firefox environment.

What else can I do?

Many thanks!