[SOLVED] Windows 10 BSOD problems

Aug 29, 2019
4
0
10
0
Hi, I'm having problem with my PC because it is constantly crashing while playing games with or without BSOD. The thing is I have gone without crashes for like 3 weeks and now it started happening again.
My mobo: GA-78LMT-S2P
CPU: AMD FX-4300
GPU: GTX 460 SE
RAM: HyperX Fury Black 2x4GB DDR3 1333

I also checked my most recent dump file:
***
  • *
  • Bugcheck Analysis *
  • *
***

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000000, A stack-based buffer has been overrun.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the bugcheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.18362.295 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: GA-78LMT-S2P

BIOS_VENDOR: Award Software International, Inc.

BIOS_VERSION: F3

BIOS_DATE: 10/18/2012

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: GA-78LMT-S2P

BASEBOARD_VERSION: x.x

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

TRAP_FRAME: 0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD: 0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

CPU_COUNT: 4

CPU_MHZ: ee9

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x139

PROCESS_NAME: javaw.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: PEPEGA

ANALYSIS_SESSION_TIME: 08-29-2019 10:44:31.0800

ANALYSIS_VERSION: 10.0.18362.1 x86fre

DPC_STACK_BASE: FFFFF8017AE72FB0

LAST_CONTROL_TRANSFER: from fffff80174fc873b to fffff80174fbfcc0

STACK_TEXT:
fffff8017ae72c08 fffff80174fc873b : 0000000000000139 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx
fffff8017ae72c10 fffff80174e6a985 : fffff801746a2f80 ffffe684842cd000 ffffe68484d531b0 fffff80100000002 : nt!guard_icall_bugcheck+0x1b
fffff8017ae72c40 fffff80174e69fdf : 0000000000000012 0000000000da7a64 000000000004ab5a 0000000000000072 : nt!KiExecuteAllDpcs+0x305
fffff8017ae72d80 fffff80174fc6d05 : 0000000000000000 fffff801746a0180 fffff80175923cf0 0000000744787678 : nt!KiRetireDpcList+0x1ef
fffff8017ae72fb0 fffff80174fc6af0 : fffff801758cdc30 fffff801758b82ca 0000000000000000 0000000002e24000 : nt!KxRetireDpcList+0x5
ffff948b9f8c3ac0 fffff80174fc63a5 : 0000000744787678 fffff80174fc1d41 0000000744787678 ffff948b9f8c3b80 : nt!KiDispatchInterruptContinue
ffff948b9f8c3af0 fffff80174fc1d41 : 0000000744787678 ffff948b9f8c3b80 fffff80175923cf0 ffffe6848e879160 : nt!KiDpcInterruptBypass+0x25
ffff948b9f8c3b00 0000000063e79050 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
0000000002d2d930 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x63e79050


THREAD_SHA1_HASH_MOD_FUNC: 9b657848d6634a809cbaa934a63abb18951a6c02

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1dbe5c0504694af4cb20d1f2d69573680edf6206

THREAD_SHA1_HASH_MOD: cb5f414824c2521bcc505eaa03e92fa10922dad8

FOLLOWUP_IP:
nt!guard_icall_bugcheck+1b
fffff801`74fc873b 90 nop

FAULT_INSTR_CODE: ccccc390

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!guard_icall_bugcheck+1b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 35707659

IMAGE_VERSION: 10.0.18362.295

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1b

FAILURE_BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_bugcheck

BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_bugcheck

PRIMARY_PROBLEM_CLASS: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_bugcheck

TARGET_TIME: 2019-08-29T08:34:38.000Z

OSBUILD: 18362

OSSERVICEPACK: 295

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: 1998-05-30 23:12:57

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.18362.295

ANALYSIS_SESSION_ELAPSED_TIME: 1454

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_0_legacy_gs_violation_nt!guard_icall_bugcheck

FAILURE_ID_HASH: {9bee41a7-2ef9-07ca-7e59-7d5a0c6e2d05}

Followup: MachineOwner
---------
 
Last edited:

gardenman

Admirable
Herald
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/eN79.html

File information:082919-43343-01.dmp (Aug 29 2019 - 04:34:38)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:ntkrnlmp.exe (Process: javaw.exe)
Uptime:0 Day(s), 2 Hour(s), 13 Min(s), and 41 Sec(s)

File information:082819-40578-01.dmp (Aug 28 2019 - 09:18:17)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 07 Min(s), and 56 Sec(s)

Comment: The overclocking driver "AODDriver2.sys" was found on your system. (AMD Overdrive)

Comment: The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)

PRODUCT: GA-78LMT-S2P
There's multiple revisions of your motherboard. I'm not sure which one you have therefore I can't recommend the page for the motherboard to check for BIOS updates.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
 

gardenman

Admirable
Herald
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/eN79.html

File information:082919-43343-01.dmp (Aug 29 2019 - 04:34:38)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:ntkrnlmp.exe (Process: javaw.exe)
Uptime:0 Day(s), 2 Hour(s), 13 Min(s), and 41 Sec(s)

File information:082819-40578-01.dmp (Aug 28 2019 - 09:18:17)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 07 Min(s), and 56 Sec(s)

Comment: The overclocking driver "AODDriver2.sys" was found on your system. (AMD Overdrive)

Comment: The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)

PRODUCT: GA-78LMT-S2P
There's multiple revisions of your motherboard. I'm not sure which one you have therefore I can't recommend the page for the motherboard to check for BIOS updates.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Aug 29, 2019
4
0
10
0
Little update, I uninstalled both of those programs after reading some other posts. I also found out that my network driver could cause errors so I updated it and nothing happened yet.
 

ASK THE COMMUNITY

TRENDING THREADS