[SOLVED] Kernal System dxgkrnl BSOD? (Minidump included)

[vtron4242]

Hello all,
I've been experiencing frequent kernal related BSODs as well as a few memory management BSODs. I've ran the minidump file in WinDbg and wanted to see if yall can help me interpret the code.
I've tried reinstalling my OS on my SSD as well as downloading new drivers, running memtest 86 (found 0 errors) and sfc file checker in CMD.

Code:
*******************************************************************************

*                                                                             *

*                        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: 0000000000000002, Stack cookie instrumentation code detected a stack-based

    buffer overrun.

Arg2: ffffbc8f974f35f0, Address of the trap frame for the exception that caused the bugcheck

Arg3: ffffbc8f974f3548, Address of the exception record for the exception that caused the bugcheck

Arg4: 0000000000000000, Reserved



Debugging Details:

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





KEY_VALUES_STRING: 1



    Key  : Analysis.CPU.mSec

    Value: 6139



    Key  : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-VLOQI4R



    Key  : Analysis.DebugData

    Value: CreateObject



    Key  : Analysis.DebugModel

    Value: CreateObject



    Key  : Analysis.Elapsed.mSec

    Value: 57143



    Key  : Analysis.Memory.CommitPeak.Mb

    Value: 92



    Key  : Analysis.System

    Value: CreateObject



    Key  : WER.OS.Branch

    Value: vb_release



    Key  : WER.OS.Timestamp

    Value: 2019-12-06T14:06:00Z



    Key  : WER.OS.Version

    Value: 10.0.19041.1





ADDITIONAL_XML: 1



OS_BUILD_LAYERS: 1



BUGCHECK_CODE:  139



BUGCHECK_P1: 2



BUGCHECK_P2: ffffbc8f974f35f0



BUGCHECK_P3: ffffbc8f974f3548



BUGCHECK_P4: 0



TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)

Unable to read trap frame at ffff8000`00000000



EXCEPTION_RECORD:  ffffbc8f974f3548 -- (.exr 0xffffbc8f974f3548)

ExceptionAddress: fffff802659b3fe5 (dxgkrnl!_report_gsfailure+0x0000000000000005)

   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)

  ExceptionFlags: 00000001

NumberParameters: 1

   Parameter[0]: 0000000000000002

Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXPNP: 1 (!blackboxpnp)





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT:  1



PROCESS_NAME:  wallpaper32.exe



WATSON_BKT_EVENT:  BEX



ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.



EXCEPTION_CODE_STR:  c0000409



EXCEPTION_PARAMETER1:  0000000000000002



EXCEPTION_STR:  0xc0000409



STACK_TEXT:

ffffbc8f`974f32c8 fffff802`61807769     : 00000000`00000139 00000000`00000002 ffffbc8f`974f35f0 ffffbc8f`974f3548 : nt!KeBugCheckEx

ffffbc8f`974f32d0 fffff802`61807b90     : ffffac0d`6844c080 ffffac0d`7008c060 00000000`00000000 ffffac0d`7008c050 : nt!KiBugCheckDispatch+0x69

ffffbc8f`974f3410 fffff802`61805f23     : 001fffff`56c70001 00000006`6844c000 ffffac0d`7008c080 ffffac0d`56c7f040 : nt!KiFastFailDispatch+0xd0

ffffbc8f`974f35f0 fffff802`659b3fe5     : fffff802`659b54f6 ffffbc8f`974f3d60 fffff802`6172c1af fffff802`65a5103c : nt!KiRaiseSecurityCheckFailure+0x323

ffffbc8f`974f3788 fffff802`659b54f6     : ffffbc8f`974f3d60 fffff802`6172c1af fffff802`65a5103c ffffbc8f`00000000 : dxgkrnl!_report_gsfailure+0x5

ffffbc8f`974f3790 fffff802`659b5546     : ffffbc8f`974f3860 00000000`00000000 ffffbc8f`974f3d98 ffffbc8f`974f3d70 : dxgkrnl!_GSHandlerCheckCommon+0x5a

ffffbc8f`974f37c0 fffff802`617fe642     : fffff802`65a5103c ffffbc8f`974f3d60 fffff802`659b5504 fffff802`65b39cd1 : dxgkrnl!_GSHandlerCheck_SEH+0x42

ffffbc8f`974f37f0 fffff802`6172bf97     : ffffbc8f`974f3d60 00000000`00000000 ffffbc8f`974f49d8 fffff802`65b39cd1 : nt!RtlpExecuteHandlerForException+0x12

ffffbc8f`974f3820 fffff802`6172ab86     : ffffbc8f`974f4738 ffffbc8f`974f4470 ffffbc8f`974f4738 ffffffff`ffffffff : nt!RtlDispatchException+0x297

ffffbc8f`974f3f40 fffff802`618078ac     : 00000000`00001000 ffffbc8f`974f47e0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186

ffffbc8f`974f4600 fffff802`61803a43     : 00000000`00000000 ffffac0d`6886f200 ffffac0d`73ce5220 fffff802`65a8af75 : nt!KiExceptionDispatch+0x12c

ffffbc8f`974f47e0 fffff802`616ee8d7     : 00000000`00000001 ffffac0d`00000000 ffffe589`0f137820 00000000`00000001 : nt!KiPageFault+0x443

ffffbc8f`974f4978 fffff802`65a8b294     : ffffbc8f`974f4b80 ffffe589`0f137820 00000000`00000001 ffffe589`0f137800 : nt!ExfReleaseRundownProtection+0x7

ffffbc8f`974f49a8 fffff802`65b39cd1     : ffffe589`ffffffff ffffac0d`73ce5220 00000000`00000000 400064c0`40004c40 : dxgkrnl!DXGALLOCATIONREFERENCE::~DXGALLOCATIONREFERENCE+0x114

ffffbc8f`974f49d8 00000000`0000125c     : 00000000`0969db30 00000000`0000025c 00000000`0000002b 00000000`75fb2e8c : dxgkrnl!DxgkUnlock2+0xaa3b1

ffffbc8f`974f4b38 00000000`0969db30     : 00000000`0000025c 00000000`0000002b 00000000`75fb2e8c 00000000`00000000 : 0x125c

ffffbc8f`974f4b40 00000000`0000025c     : 00000000`0000002b 00000000`75fb2e8c 00000000`00000000 00000000`0959e2c0 : 0x969db30

ffffbc8f`974f4b48 00000000`0000002b     : 00000000`75fb2e8c 00000000`00000000 00000000`0959e2c0 00000000`00000000 : 0x25c

ffffbc8f`974f4b50 00000000`75fb2e8c     : 00000000`00000000 00000000`0959e2c0 00000000`00000000 00000000`00000000 : 0x2b

ffffbc8f`974f4b58 00000000`00000000     : 00000000`0959e2c0 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75fb2e8c





SYMBOL_NAME:  dxgkrnl!_report_gsfailure+5



MODULE_NAME: dxgkrnl



IMAGE_NAME:  dxgkrnl.sys



IMAGE_VERSION:  10.0.19041.685



STACK_COMMAND:  .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET:  5



FAILURE_BUCKET_ID:  0x139_MISSING_GSFRAME_dxgkrnl!_report_gsfailure



OS_VERSION:  10.0.19041.1



BUILDLAB_STR:  vb_release



OSPLATFORM_TYPE:  x64



OSNAME:  Windows 10



FAILURE_ID_HASH:  {1685fa82-f4b9-d129-b6b1-78c3bba339a9}



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

Here are my system specs as well
AMD 5 2500x 3.60 GHz
Gskills Ripjaw 16 GB Ram
ASUS Geforcce GTX 1060 super

 

[Colif]

direct X. 99% of the time this crashes the cause is gpu drivers

try running DDU in safe mode, uninstall all Nvidia drivers and either get new ones direct from Nvidia, or run windows update after startup and allow windows to install older Nvidia drivers - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

 

[vtron4242]

direct X. 99% of the time this crashes the cause is gpu drivers

try running DDU in safe mode, uninstall all Nvidia drivers and either get new ones direct from Nvidia, or run windows update after startup and allow windows to install older Nvidia drivers - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

Downloading DDU now, Should I risk updating my BIOS as well? Currently on 3.30, Asrocks latest is 6.60. I'd have to jump version to version instead of straight to newest version as well... Thank you for help

 

[Colif]

what motherboard is it?

 

[vtron4242]

ASrock B450M Pro

Update: did what you mentioned with DDU, appears to be okay at the time being. will update

Thanks again!

 

[johnbl]

you should put the memory dump on a server, share it and post a link.
when the stack is corrupted you need to look at the raw stack to see if you can see what did the corruption.

you can dump the raw stack

dqs ffffbc8f974f32c8 - 300 ffffbc8f974f32c8 + 300

sometimes this can be helpful. sometimes you get audio drivers that cause the problem and you can go into device manager and disable audio devices that do not have speakers attached to them.

certain AMD chips have a bug in the actual cpu related to DMA transfers, this bug is a won't fix and they just expect the bios to be patched to prevent reserve certain memory address so windows and other driver will not use them. often you see a DMA request in the raw stack right before the crash in the memory dumps.