Question Win 10 everytime different BSOD

[The_Gentleman]

Good evening,
I am sorry to bother you with that but I need help.

My PC specs:
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\Windows
Hardware: MS-7C02, Micro-Star International Co., Ltd, B450 TOMAHAWK (MS-7C02)
CPU: AuthenticAMD AMD Ryzen 5 2400G with Radeon Vega Graphics AMD8664, level: 23
8 logical processors, active mask: 255
RAM: 14978076672 bytes (13,9GB) - it is single slot RAM Crucial Balistix

My computer crashes every hour like 4-8 times. Every time different BSOD. Also browsers (Edge, Firefox, Chrome) crashes every 5-10 minutes. Aw snap and also complete fall. I checked drivers multiple times. Complete unninstals than instalation via producer web, driver booster. Also made 3 clean installations but nothing helps.



Crash dumps are enabled on your computer.

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

On Mon 10.06.2019 18:51:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061019-6890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC810)
Bugcheck code: 0x1 (0x7FFEAADDC9E4, 0x0, 0xFFFF0000, 0xFFFF930DE2C92B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 Mon 10.06.2019 18:51:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x80C9)
Bugcheck code: 0x1 (0x7FFEAADDC9E4, 0x0, 0xFFFF0000, 0xFFFF930DE2C92B80)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
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 Mon 10.06.2019 18:50:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061019-7031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC810)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80362A2F547, 0xFFFFF10FDD34C9A0, 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 Mon 10.06.2019 18:47:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061019-7062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC810)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8051C837048, 0xFFFFDA0FC5FBE230, 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 Mon 10.06.2019 18:19:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061019-8546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC810)
Bugcheck code: 0x139 (0x3, 0xFFFFC683AA1092B0, 0xFFFFC683AA109208, 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 09.06.2019 19:37:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060919-8156-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF807446E6640)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF807446E6640, 0xFFFFB188009703F8, 0xFFFFB1880096FC40)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operační systém Microsoft® Windows®
company: Microsoft Corporation
description: NT File System Driver
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 a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

Please can you help me with that? Or is some part of my hardware ready for trash bin?

I really appreciate any help.

 

[rgd1101]

make and model of the psu?
what hdd/sdd do you have?

 

[The_Gentleman]

make and model of the psu?
what hdd/sdd do you have?

have 120 gb SSD Kingston, and 2TB Seagate. PSU - EUROCASE 550WA-14

 

[Colif]

You shouldn't use Driver Booster, for 2 reasons

1. it can and will install wrong drivers, I have had it happen twice before i learned not to use it
2. Your motherboard has an updater already. You should Download live update 6 from the utility page of motherboards website - link

can you go to c:/windows/minidump
copy the minidumps to another folder
upload the copies from new folder to a file sharing website and show links here, and I will get the bump files converted to a format I can read.

 

[The_Gentleman]

You shouldn't use Driver Booster, for 2 reasons

1. it can and will install wrong drivers, I have had it happen twice before i learned not to use it
2. Your motherboard has an updater already. You should Download live update 6 from the utility page of motherboards website - link

can you go to c:/windows/minidump
copy the minidumps to another folder
upload the copies from new folder to a file sharing website and show links here, and I will get the bump files converted to a format I can read.

So here is the link
https://www.dropbox.com/sh/bufrx8k98xj4hy2/AADpel_UuKyHkbsVp71wyQx8a?dl=0

 

[gardenman]

Hi, unfortunately the 5 dump files would not work for me. The debugger simply ignored them. Did you copy the files directly from the minidump folder to the desktop then upload them? Or did you open them in Notepad and attempt to resave them? If you opened them in Notepad and resaved them, the newly saved files would be corrupt.

 

[ryzengamer]

Boot you computer with a ubuntu 19 live disk. You have a hardware problem if you have the same problem with ubuntu.

 

[Colif]

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.