[SOLVED] Can someone shed some light on the cause of my Windows 10 BSoD?

[RoboticBread]

PC Specs:
CPU: AMD fx 9590
GPU: GTX 1050
PSU: Corsair CX 750M
SSD: Samsung 500gb SSD
MoBo: ASRock 970A-G/3.1
RAM: 16GB HyperX Fury ddr3 1866MhZ
OS: Windows 10 64-bit

So on to the issue: Over the past few months, my PC has been having occasional BSoD such as HAL_INITIALIZATION_FAILED, PAGE_FOUND_IN_NONPAGED_AREA, and KERNEL_SECURITY_CHECK_FAILURE. However, recently, the blescreens have become much more common, happening even up to twice a day. I have recently wiped and freshly reinstalled my windows, run chkdsk, memory checker, windows powershell, and many other driver-type programs to no avail. The drivers that seem to be affected are my audio drivers (Logitech G430 headset) and ntoskrnl.exe. I have no clue what could be causing these blue screens and I was hoping some of you may be able to help.

Recent dump file:
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: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

SYSTEM_SKU: To Be Filled By O.E.M.

SYSTEM_VERSION: To Be Filled By O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: P1.20

BIOS_DATE: 01/12/2016

BASEBOARD_MANUFACTURER: ASRock

BASEBOARD_PRODUCT: 970A-G/3.1

BASEBOARD_VERSION:

DUMP_TYPE: 2

BUGCHECK_P1: 2

BUGCHECK_P2: ffffec095d7e0730

BUGCHECK_P3: ffffec095d7e0688

BUGCHECK_P4: 0

TRAP_FRAME: ffffec095d7e0730 -- (.trap 0xffffec095d7e0730)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002
rdx=ffff9c8f5c9115f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004c4d7d75 rsp=ffffec095d7e08c8 rbp=ffffec095d7e09a9
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff8004c4c0000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
dxgmms2!_report_gsfailure+0x5:
fffff8004c4d7d75 cd29 int 29h Resetting default scope EXCEPTION_RECORD: ffffec095d7e0688 -- (.exr 0xffffec095d7e0688) ExceptionAddress: fffff8004c4d7d75 (dxgmms2!_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 CPU_COUNT: 8 CPU_MHZ: 125c 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 BUGCHECK_STR: 0x139 PROCESS_NAME: System CURRENT_IRQL: 0 DEFAULT_BUCKET_ID: FAIL_FAST_STACK_COOKIE_CHECK_FAILURE 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: (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 ANALYSIS_SESSION_HOST: DESKTOP-OQVS51N ANALYSIS_SESSION_TIME: 03-14-2020 10:13:37.0315 ANALYSIS_VERSION: 10.0.18362.1 amd64fre LAST_CONTROL_TRANSFER: from fffff800445d33e9 to fffff800445c1510 STACK_TEXT: ffffec095d7e0408 fffff800445d33e9 : 0000000000000139 0000000000000002 ffffec095d7e0730 ffffec095d7e0688 : nt!KeBugCheckEx ffffec095d7e0410 fffff800445d3810 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiBugCheckDispatch+0x69 ffffec095d7e0550 fffff800445d1ba5 : ffffec095d7e0748 0000fffff8004d0c ffffec095d7e0880 0000000000000000 : nt!KiFastFailDispatch+0xd0 ffffec095d7e0730 fffff8004c4d7d75 : fffff8004c4c8c58 ffff9c8f59a06680 fffff800444886d6 ffff9c8f00000044 : nt!KiRaiseSecurityCheckFailure+0x325 ffffec095d7e08c8 fffff8004c4c8c58 : ffff9c8f59a06680 fffff800444886d6 ffff9c8f00000044 ffff9c8f59968000 : dxgmms2!_report_gsfailure+0x5 ffffec095d7e08d0 fffff8004c53a10c : ffffec095d7e0a01 0000000000989680 00000011412585a4 0000000000000000 : dxgmms2!VidSchiProfilePerformanceTick+0x168 ffffec095d7e09f0 fffff8004c4c8786 : 0000000000000000 ffff9c8f5999c000 ffffec095d7e0b19 ffff9c8f5999c000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x28c ffffec095d7e0ac0 fffff8004c549990 : ffff9c8f63884200 ffff9c8f5999c000 ffff9c8f638842f0 ffff9c8f685f35e0 : dxgmms2!VidSchiScheduleCommandToRun+0x2c6 ffffec095d7e0b80 fffff8004c54994a : ffff9c8f5999c400 fffff8004c549880 ffff9c8f5999c000 0000000000000000 : dxgmms2!VidSchiRun_PriorityTable+0x30 ffffec095d7e0bd0 fffff8004452a7b5 : ffff9c8f59a06680 fffff80000000001 ffff9c8f5999c000 00000224acbb3dfe : dxgmms2!VidSchiWorkerThread+0xca ffffec095d7e0c10 fffff800445c8b5a : fffff80041202180 ffff9c8f59a06680 fffff8004452a760 89840fc00000023d : nt!PspSystemThreadStartup+0x55 ffffec095d7e0c60 0000000000000000 : ffffec095d7e1000 ffffec095d7db000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x2a THREAD_SHA1_HASH_MOD_FUNC: f074edfadcd109b3cc8ed68080161b857edc2776 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2b3a8e72952dfec87d8263d742b6393d87524e65 THREAD_SHA1_HASH_MOD: e0edc32d5aba1351b8e9431f7fc9b6a3b4268768 FOLLOWUP_IP: dxgmms2!_report_gsfailure+5 fffff8004c4d7d75 cd29 int 29h

FAULT_INSTR_CODE: cccc29cd

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: dxgmms2!_report_gsfailure+5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.18362.657

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 5

FAILURE_BUCKET_ID: 0x139_MISSING_GSFRAME_dxgmms2!_report_gsfailure

BUCKET_ID: 0x139_MISSING_GSFRAME_dxgmms2!_report_gsfailure

PRIMARY_PROBLEM_CLASS: 0x139_MISSING_GSFRAME_dxgmms2!_report_gsfailure

TARGET_TIME: 2020-03-14T03:49:21.000Z

OSBUILD: 18362

OSSERVICEPACK: 657

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2005-04-22 21:40:32

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

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

ANALYSIS_SESSION_ELAPSED_TIME: 4224

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_missing_gsframe_dxgmms2!_report_gsfailure

FAILURE_ID_HASH: {f40afed2-47dc-8171-8418-ea5cdc2e07a6}

Followup: MachineOwner

 

[Ralston18]

Look in Reliability History for error codes, warnings, and informational events corresponding with the times of the BSODs. Reliability History is more user friendly and easier to use.

Power off, unplug, and open the case.

Clean out dust and debris as necessary. Use canned air and carefully follow the instructions.

Doublecheck that all cards, connectors, jumpers, and RAM are fully and firmly seated.

 

[RoboticBread]

Look in Reliability History for error codes, warnings, and informational events corresponding with the times of the BSODs. Reliability History is more user friendly and easier to use.

Power off, unplug, and open the case.

Clean out dust and debris as necessary. Use canned air and carefully follow the instructions.

Doublecheck that all cards, connectors, jumpers, and RAM are fully and firmly seated.

I fully dusted, cleaned, and re-seated my PC. I also checked in Reliability History and did not see much that explained what happened.
On my first BSoD, it reports that there was "bad_module_info" with all numbers such as the timestamp and exception code just being strings of zeroes. The only thing besides a zero is this bucket ID:48565509f28d3c5915fb08e8f96ea833 (1583869490661074995)

On the second BSoD of the night, I have two instances of it saying "Windows shut down unexpectedly"
First:
Problem Event Name: BlueScreen
Code: 139
Parameter 1: 1d
Parameter 2: fffff8044246e160
Parameter 3: fffff8044246e0b8
Parameter 4: 0
OS version: 10_0_18363
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.18363.2.0.0.768.101
Locale ID: 1033

Second:
Problem Event Name: BlueScreen
Code: 139
Parameter 1: 2
Parameter 2: ffffec095d7e0730
Parameter 3: ffffec095d7e0688
Parameter 4: 0
OS version: 10_0_18363
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.18363.2.0.0.768.101
Locale ID: 1033

Does this mean anything?

 

[Ralston18]

Varying errors and BSODs, to me anyway, make the PSU very suspect.

The PSU is a very crucial component and provides different voltages (3, 5, 12) to other components.

Any degradation of a voltage or power capability will cause problems.

Do you have multimeter and know how to use it? Or have a knowledgeable family member or friend who does?

https://www.lifewire.com/how-to-manually-test-a-power-supply-with-a-multimeter-2626158

Not a complete test per se (system is not under load) but any voltages out of spec may be problematic.