BSOD problems maybe

[Wraithsiege]

Today i got a bsod while opening a youtube video. The bluescreen just pooped out and it stayed for about a minute before rebooting again. I wouldnt be concerned but this is not the first time it happened. It happened yesterday while i was on youtube again. I got 2 different error messages during bsod (check for viruses already and didnt updated the drivers for a week so drivers shouldnt be a problem. The first bsod gave message System Thread Exception Not Handled while second one gave Kernel Security Check Failure. What is happening. Also specs on my profile

[r.linder]

Typical issue with storage. Run chkdsk and other similar commands that check your HDD.

[Wraithsiege]

Publicado originalmente por Escorve:

Typical issue with storage. Run chkdsk and other similar commands that check your HDD.

Just run the diskcheck and downloaded hdsentinel but no errors were found. The drive is still 100% health

[[☥] - CJ -]

Download WhoCrashed, analyze the crash dump and see what actually caused the bluescreen.

[Wraithsiege]

Publicado originalmente por ☥ - CJ - 8/6/19:

Download WhoCrashed, analyze the crash dump and see what actually caused the bluescreen.

Computer name: DESKTOP-JL2K4TL
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\Windows
Hardware: MS-7A37, Micro-Star International Co., Ltd., MSI, B350M MORTAR (MS-7A37)
CPU: AuthenticAMD AMD Ryzen 7 1700 Eight-Core Processor AMD8664, level: 23
16 logical processors, active mask: 65535
RAM: 51491004416 bytes (48.0GB)




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 8/18/2019 16:47:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081819-20953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x139 (0x1D, 0xFFFFF405BAFEF5E0, 0xFFFFF405BAFEF538, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 8/18/2019 16:47:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VidMmInterface+0x29F1F)
Bugcheck code: 0x139 (0x1D, 0xFFFFF405BAFEF5E0, 0xFFFFF405BAFEF538, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 8/17/2019 18:24:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081719-22796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x44289)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80677844289, 0xFFFFA981C7F5CD08, 0xFFFFAD800C6BF930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
This is all info i could get

[[☥] - CJ -]

Hmmm...

DirectX Graphics...

So possibly GPU Driver related that popped up because of the youtube vid and GPU Acceleration..

So to start troubleshooting id start with the GPU drivers
Doing a clean uninstall/latest driver install with DDU in Safe Mode would be one thing to get out of the way.

For the hell of it, id clear your browser history/cache in addition to doing an all options Disk Clean to further remove temporary files and so forth.

2 things to start with.

Trying to reproduce the Youtube crash beforehand might be useful since its happened before.