Windows 10: Blue Screen Of Death (Probably Caused By: ntkrnlmp.exe)

I keep getting a BSOD and i dont know to fix it and it's by ntkrnlmp.exe



---------------------------------------------------------------------------------------


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


Loading Dump File [C:\Users\Leland Villa\Desktop\minidumps\010219-7203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff801`4000a000 PsLoadedModuleList = 0xfffff801`40424a50
Debug session time: Wed Jan 2 11:27:19.378 2019 (UTC - 8:00)
System Uptime: 0 days 0:45:14.064
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F7, {80fb9e66955346, fb9e66955346, ffff0461996aacb9, 0}

Probably caused by : ntkrnlmp.exe ( nt!_report_gsfailure+25 )

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

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 0080fb9e66955346, Actual security check cookie from the stack
Arg2: 0000fb9e66955346, Expected security check cookie
Arg3: ffff0461996aacb9, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: AX370-Gaming

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F21

BIOS_DATE: 02/08/2018

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: AX370-Gaming-CF

BASEBOARD_VERSION: se1

DUMP_TYPE: 2

BUGCHECK_P1: 80fb9e66955346

BUGCHECK_P2: fb9e66955346

BUGCHECK_P3: ffff0461996aacb9

BUGCHECK_P4: 0

SECURITY_COOKIE: Expected 0000fb9e66955346 found 0080fb9e66955346

BUGCHECK_STR: 0xF7_ONE_BIT

CPU_COUNT: c

CPU_MHZ: c80

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: audiodg.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-F67U2VA

ANALYSIS_SESSION_TIME: 01-02-2019 15:00:39.0272

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

LAST_CONTROL_TRANSFER: from fffff80140270b15 to fffff801401bbb40

STACK_TEXT:
ffff9282`efb802c8 fffff801`40270b15 : 00000000`000000f7 0080fb9e`66955346 0000fb9e`66955346 ffff0461`996aacb9 : nt!KeBugCheckEx
ffff9282`efb802d0 fffff801`405da294 : ffff9282`efb805c0 00000000`00000000 ffff810e`00000ef5 00000000`6d57624f : nt!_report_gsfailure+0x25
ffff9282`efb80310 fffff801`405d9f47 : 00000000`00000001 00000000`00000400 00000000`00000000 fffff801`40685632 : nt!ObWaitForMultipleObjects+0x314
ffff9282`efb80810 fffff801`401ccd85 : 00000000`746c6644 ffff9282`efb80b00 ffff810e`ec0d7080 000000d2`381ffb78 : nt!NtWaitForMultipleObjects+0xf7
ffff9282`efb80a90 00007ffc`b35f01b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000d2`381ffb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`b35f01b4


THREAD_SHA1_HASH_MOD_FUNC: 1016a04bb0ece1228605d471bd904c08b70d898b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 52dddee60e281e133fbe99702c18168ad5e2685e

THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_IP:
nt!_report_gsfailure+25
fffff801`40270b15 cc int 3

FAULT_INSTR_CODE: cccccccc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!_report_gsfailure+25

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17763.195

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 25

FAILURE_BUCKET_ID: 0xF7_ONE_BIT_MISSING_GSFRAME_nt!_report_gsfailure

BUCKET_ID: 0xF7_ONE_BIT_MISSING_GSFRAME_nt!_report_gsfailure

PRIMARY_PROBLEM_CLASS: 0xF7_ONE_BIT_MISSING_GSFRAME_nt!_report_gsfailure

TARGET_TIME: 2019-01-02T19:27:19.000Z

OSBUILD: 17763

OSSERVICEPACK: 195

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: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 540

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xf7_one_bit_missing_gsframe_nt!_report_gsfailure

FAILURE_ID_HASH: {8f84f302-dd0e-1f96-6f9c-0ea31ad59f42}

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

:)

 

Blue screen of death issue

Hi Malcolm,

Blue screen of death error can be caused either by hardware failure or software compatibility. To help you resolve the blue screen of death issue, we would like to get more information:

• Please provide the complete stop error message that you are getting.
• Were there any changes made prior to the issue?

We recommend following the troubleshooting steps in the article:
Troubleshoot blue screen errors

Should you need further help, you're always welcome to post back.

 

Blue Screen of Deaths on a Daily

I have tried all of the options there, Which is why i included in my post the lists of things that i performed to isolate the cause of bsod. Thanks

 

Blue Screen of Deaths on a Daily

Hi,

Blue screen errors can occur if a serious problem causes Windows to shut down or restart unexpectedly. This error can be caused by both hardware and software issues. To isolate your concern, we'd like to know if there were any changes made
prior to the issue.

In the meantime, we suggest that you follow the steps provided on this link for blue screen error basic
troubleshooting. Once you're on the page, select the option on when do you get the error and proceed with the steps listed.

Let us know how it goes after performing the suggested steps.