Blue screen windows 10

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-A3HTQTR
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\WINDOWS
Hardware: MS-7B86, Micro-Star International Co., Ltd, B450 GAMING PLUS MAX (MS-7B86)
CPU: AuthenticAMD AMD Ryzen 7 3700X 8-Core Processor AMD8664, level: 23
16 logical processors, active mask: 65535
RAM: 17128202240 bytes (16,0GB)




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

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Thu 10/09/2020 19:14:16 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\091020-8640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800322A45DE, 0xFFFFCD0182BAA920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Thu 10/09/2020 17:23:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\091020-10906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80713CA45DE, 0xFFFF8F00A6C99920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Wed 09/09/2020 15:49:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\090920-8968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802618A45DE, 0xFFFFBB013CFBD920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.