I keep having random BSOD's on a newly built PC.

[Isthisthereallife88]

Spec:

AMD Ryzen 3600
MSI Gaming Plus X570
16GB DDR4 3200mhz Ballistic LT
AMD Navi 5700 GPU
Windows Pro 10
256gb SSD Sandisk
4TB Blue WD
750Watt EVGA G2 PSU(About 4-5 years old, voltage read outs in spec according to HWiNFO64)

I tried rebuilding the PC, reinstalling Windows, etc...made sure bios were up to date, drivers, windows updates, chipset drivers, etc...

Sometimes it goes days without issue, sometimes a couple crashes a day, once while gaming it rebooted. Last BSOD I was doing nothing, no programs were running. Happens when browsing even.

I am at a lose. I stress tested each part, ran Memtest64 multiple hours, etc....I had more dump files but reinstalled windows recently and forgot to save the others.

Most are this, I added the logs to the zip, I have the dump files if someone needs those(What would be a good site to upload, they are kinda big, almost a gig each)

Error codes:

crash dump file: C:\Windows\Minidump\071420-10703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0xA (0xF0, 0xFF, 0x0, 0xFFFFF80251902684)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

crash dump file: C:\Windows\Minidump\070920-10500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF806848ACD8D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

In system reliability monitor I also have these:

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 117
Parameter 1: ffffb00777e10010
Parameter 2: fffff80469be5140
Parameter 3: 0
Parameter 4: 584
OS version: 10_0_19041
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033

Description
Faulting Application Path: C:\Program Files\AMD\CNext\CNext\Radeonsoftware.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: Radeonsoftware.exe
Application Version: 10.1.2.1788
Application Timestamp: 5ebeeeda
Fault Module Name: Radeonsoftware.exe
Fault Module Version: 10.1.2.1788
Fault Module Timestamp: 5ebeeeda
Exception Code: c0000005
Exception Offset: 0000000000412967
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 0f1e
Additional Information 2: 0f1e8efbe4eda39817605f485fdb728a
Additional Information 3: 5660
Additional Information 4: 5660461604a3439ca36702825f42be79

Extra information about the problem
Bucket ID: d84648fad39bfe72ed8c29f0f8d5748f (2129122838783030415)


Description
Faulting Application Path: C:\Program Files\MAGIX\Music Maker\29\MusicMaker.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: MusicMaker.exe
Application Version: 29.0.0.13
Application Timestamp: 5ef5ddd0
Fault Module Name: StackHash_f242
Fault Module Version: 10.0.19041.207
Fault Module Timestamp: cad89ab4
Exception Code: c0000374
Exception Offset: PCH_89_FROM_ntdll+0x000000000009B8E4
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033
Additional Information 1: f242
Additional Information 2: f242b260fb4a7da5f7ef138692ce332e
Additional Information 3: 10fc
Additional Information 4: 10fc5cfff419397ccccfb7e6f861c637

Extra information about the problem
Bucket ID: 6fb7c85851cfb974490bd736dc851eca (1804772706319933130)

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: D:\Games\Beyond - Two Souls\BeyondTwoSouls_Steam.exe

Problem signature
Problem Event Name: AppHangB1
Application Name: BeyondTwoSouls_Steam.exe
Application Version: 0.0.0.0
Application Timestamp: 5eb531da
Hang Signature: a3b3
Hang Type: 134217728
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: a3b35f40fe8f6d457629ab4b326d3650
Additional Hang Signature 2: 7139
Additional Hang Signature 3: 713945ec161489c3dafbfee2d60db731
Additional Hang Signature 4: a3b3
Additional Hang Signature 5: a3b35f40fe8f6d457629ab4b326d3650
Additional Hang Signature 6: 7139
Additional Hang Signature 7: 713945ec161489c3dafbfee2d60db731

Faulting Application Path: C:\Users\Chris\AppData\Local\Temp\OCCT\DX11\OCCTGPUDX11.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: OCCTGPUDX11.exe
Application Version: 0.0.0.0
Application Timestamp: 5e60286a
Fault Module Name: OCCTGPUDX11.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5e60286a
Exception Code: c0000005
Exception Offset: 000249b0
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 2beb
Additional Information 2: 2beba6fb4680d73a8c78ca7c24ccdb46
Additional Information 3: ab31
Additional Information 4: ab31236752fcb0c711def892810629b8

Extra information about the problem
Bucket ID: e3680713d173b5f688ea8a118f9b3d0b (1795399209488956683)

Problem signature
Problem Event Name: BlueScreen
Code: a
Parameter 1: 73a
Parameter 2: 2
Parameter 3: 0
Parameter 4: fffff80773ad4025
OS version: 10_0_19041
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033

Problem signature
Problem Event Name: BlueScreen
Code: 3b
Parameter 1: c0000005
Parameter 2: fffff801104fc186
Parameter 3: ffffa000ad1d2920
Parameter 4: 0
OS version: 10_0_19041
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033

Problem signature
Problem Event Name: BlueScreen
Code: 21
Parameter 1: 0
Parameter 2: 1
Parameter 3: 40a70088
Parameter 4: 3e544b42
OS version: 10_0_19041
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files\AMD\RyzenMaster\bin\AMD Ryzen Master.exe

Problem signature
Problem Event Name: AppHangB1
Application Name: AMD Ryzen Master.exe
Application Version: 2.2.0.1543
Application Timestamp: 5eb3a5dd
Hang Signature: a219
Hang Type: 134217728
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: a21953a7b88fee53a417342e86a42587
Additional Hang Signature 2: c0ca
Additional Hang Signature 3: c0ca9b136bfa65e94e1f7cc3503835be
Additional Hang Signature 4: a219
Additional Hang Signature 5: a21953a7b88fee53a417342e86a42587
Additional Hang Signature 6: c0ca
Additional Hang Signature 7: c0ca9b136bfa65e94e1f7cc3503835be

Description
Faulting Application Path: C:\Program Files\AMD\CNext\CNext\Radeonsoftware.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: Radeonsoftware.exe
Application Version: 10.1.2.1788
Application Timestamp: 5ebeeeda
Fault Module Name: StackHash_82d2
Fault Module Version: 10.0.19041.207
Fault Module Timestamp: cad89ab4
Exception Code: c0000374
Exception Offset: PCH_41_FROM_ntdll+0x000000000009B8E4
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 82d2
Additional Information 2: 82d282955d17328fcf5fc17cd9508182
Additional Information 3: 9e39
Additional Information 4: 9e393c05655ec838eac256f9994dad98

Extra information about the problem
Bucket ID: 2e3d00efc1ff05ef24bc7c51cd70b4ff (1494205867161072895)

Problem signature
Problem Event Name: BlueScreen
Code: 1e
Parameter 1: ffffffffc0000005
Parameter 2: fffff806848acd8d
Parameter 3: 0
Parameter 4: ffffffffffffffff
OS version: 10_0_19041
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033

Problem signature
Problem Event Name: BlueScreen
Code: 3b
Parameter 1: c0000005
Parameter 2: fffff805732fc186
Parameter 3: ffffae016f7d2920
Parameter 4: 0
OS version: 10_0_19041
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033

Faulting application name: javaw.exe, version: 13.28.0.11, time stamp: 0x5d9f0a9a
Faulting module name: jvm.dll, version: 0.0.0.0, time stamp: 0x5d9f0a4f
Exception code: 0xc0000005
Fault offset: 0x0037393f
Faulting process id: 0x920
Faulting application start time: 0x01d650b571e848cf
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\3DMark\bin\x64\jre\bin\javaw.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\3DMark\bin\x64\jre\bin\server\jvm.dll
Report Id: 9e80fd06-4343-4a8b-a0ae-9ea676654c30
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: SecHealthUI.exe, version: 10.0.19041.1, time stamp: 0x9626f340
Faulting module name: SecHealthUIDataModel.dll, version: 10.0.19041.1, time stamp: 0x77c55a4e
Exception code: 0xc0000005
Fault offset: 0x0000000000185c6c
Faulting process id: 0x854
Faulting application start time: 0x01d64b2dbb736032
Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.SecHealthUI_cw5n1h2txyewy\SecHealthUI.exe
Faulting module path: C:\Windows\SystemApps\Microsoft.Windows.SecHealthUI_cw5n1h2txyewy\SecHealthUIDataModel.dll
Report Id: 96417058-91f8-4962-832f-0a4c469f0047
Faulting package full name: Microsoft.Windows.SecHealthUI_10.0.19041.1_neutral__cw5n1h2txyewy
Faulting package-relative application ID: SecHealthUI

 

[MrPepka]

1. Run Driver Verifier Manager through type "verifier" in search bottom
2. Select "Create custom settings (for code developers)"
3. Tick all standard settings and 1 additional setting (Low resource simulation)
4. Select "Select driver names from a list"
5. Tick all 3rd party drivers and 1 Microsoft driver (ntoskrnl.exe)
6. Accept changes and reboot computer

 

[Isthisthereallife88]

1. Run Driver Verifier Manager through type "verifier" in search bottom
2. Select "Create custom settings (for code developers)"
3. Tick all standard settings and 1 additional setting (Low resource simulation)
4. Select "Select driver names from a list"
5. Tick all 3rd party drivers and 1 Microsoft driver (ntoskrnl.exe)
6. Accept changes and reboot computer

Ok did that, I guess I just wait for a bsod now?

 

[Isthisthereallife88]

1. Run Driver Verifier Manager through type "verifier" in search bottom
2. Select "Create custom settings (for code developers)"
3. Tick all standard settings and 1 additional setting (Low resource simulation)
4. Select "Select driver names from a list"
5. Tick all 3rd party drivers and 1 Microsoft driver (ntoskrnl.exe)
6. Accept changes and reboot computer

Ok, so my PC just froze, no blue screen or error in maintenance monitor, had to manually restart, this came up, took the photo with a camera.

It said this in Event viewer though:

svchost (10068,D,0) Unistore: An attempt to write to the file "C:\Users\Chris\AppData\Local\Comms\UnistoreDB\store.vol" at offset 1990656 (0x00000000001e6000) for 4096 (0x00001000) bytes failed after 0.000 seconds with system error 1450 (0x000005aa): "". The write operation will fail with error -1011 (0xfffffc0d). If this error persists then the file may be damaged and may need to be restored from a previous backup.

 

[Isthisthereallife88]

Ok it did it again, created a dump this time. It just went black though, no reponse, or bsod screen...had to manually restart again. Updated the log.

On Tue 7/14/2020 6:16:38 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071420-17937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0xEF (0xFFFF800642EE6380, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Sorry for the multiple posts, mods can delete them if see fit.

 

[philc43]

I can see evidence of the use of KMSpico in your logfiles. This usually indicates to me that the operating system or other software has been illegally installed and activation is being avoided. As analysts we refuse to work on such systems because it is against the forum rules and as there could be unknown consequences that may contribute to BSOD events.

 

[Isthisthereallife88]

I can see evidence of the use of KMSpico in your logfiles. This usually indicates to me that the operating system or other software has been illegally installed and activation is being avoided. As analysts we refuse to work on such systems because it is against the forum rules and as there could be unknown consequences that may contribute to BSOD events.

Yes, I have used it on once before without these issues, I did legally buy a copy of windows, twice actually, both times windows deactivated it after a while without warning(guessing from changing hardware, that's what I been told). Fine though, it's understandable, thanks anyways, I'll look elsewhere for help.

 

[philc43]

What type of Windows license did you buy? If it was a retail version you should be able to transfer it to new hardware. What you can't do is use it on multiple systems.

 

[Isthisthereallife88]

What type of Windows license did you buy? If it was a retail version you should be able to transfer it to new hardware. What you can't do is use it on multiple systems.

It was from my last build, Asus Intel board, i5, and 290, etc..it was originally a 7 key that upgraded so I guess it was a pretty old copy, I bought it a while back.

I couldn't seem to activate it so my friend gave me that activator, he used it fine so I didn't even think that could be the issue...I can buy a new copy and try again but I was thinking maybe it was a bad gpu or ram(even though memtest86 seemed to check out fine, even though the bsods are labeled memory).

Should I try a reinstalling everything again with a new legit key? I still have the key if there is a way.

 

[philc43]

I would recommend a clean install using a legitimate key - once it is correctly activated and if you get any further BSOD events post a new set of logfiles and we can start afresh with the troubleshooting support.

 

[Isthisthereallife88]

I would recommend a clean install using a legitimate key - once it is correctly activated and if you get any further BSOD events post a new set of logfiles and we can start afresh with the troubleshooting support.

Alright thank you, will do that soon then, thanks for the advice this far.