Question Occasional BSODs with latest build (3700x+x470)

[ReD-EyeD]

Started to have random BSODs recently and here is a WhoCrashed log:

Spoiler: WhoCrashed

Crash Dump Analysis

Crash dumps are enabled on your computer.

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

On Fri 06.03.2020 13:33:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\030620-7421-01.dmp
This was probably caused by the following module: amdppm.sys (0xFFFFF8034845A9BA)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8034845A9BA, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 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 Fri 06.03.2020 13:33:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: amdppm.sys (0xFFFFF8034845A9BA)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8034845A9BA, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 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 Mon 02.03.2020 2:21:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\030220-7359-01.dmp
This was probably caused by the following module: hal.dll (hal+0x1B95)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD1, 0x2, 0xFFFFF80214F131D6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that invalid system memory has been referenced.
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 02.03.2020 1:22:36 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\030220-8312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0xA (0xFFFFB3FDFF0049FE, 0x2, 0x0, 0xFFFFF8024EF542F9)
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.



On Sun 01.03.2020 13:13:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\030120-7687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0xA (0x57A51F, 0x2, 0x0, 0xFFFFF80318E3C2D1)
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.



On Tue 25.02.2020 12:34:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022520-7812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0x139 (0x3, 0xFFFF8184F01FE810, 0xFFFF8184F01FE768, 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.

The thing is that it mostly happened while playing Legends of Runeterra beta so I kinda shrugged it off as a faulty game, but some of these happened outside of it even tho I can pretty much 100% recreate it (especially
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe error) or the game just closes without any error, but it's not really about the game.
As far as I can tell it's a driver problem of some sort. My build is Ryzen 3700x + ASUS TUF x470 gaming plus with 2x16gb of 3200/16 memory

I tried most of the ways to solve this issue and I need Dr. House of PC issues now.
I scanned all the system files, ran multiple driver verifier checkers, reinstalled the windows, updated motherboard bios with it's online self updater, I'm using the latest chipset/network/audio drivers available on the official site, DDU'd video drivers many times and tested the system with Memtest64 and windows original memtest with 0 erros.
I have no idea what I should do next, please help me.

Edit: Minidumps https://drive.google.com/open?id=102B7B5EcMRG8T1fQhHDJ1yGjee-_mZYE
Also saw a solution with
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\amdppm
Change Start to have a value of 4.
What it does exactly and should I do it even?

Full system specs are: Ryzen 3700x, ASUS TUF x470 gaming plus, 32gb 3200/cl16, gtx1070, some thermaltake toughpower gold 750w, Samsung evo 860 ssd

 

[ReD-EyeD]

@Colif So, I got my first BSOD on this new windows. Happened just like the previous one during the youtube video and random scrolling here and there.
WhoCrashed log:

Spoiler: WhoCrashed

On Tue 10.03.2020 23:37:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031020-8906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0xA (0x4B5A7CC940, 0xFF, 0x72, 0xFFFFF80249E3D23F)
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.



On Tue 10.03.2020 23:37: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+0x81A9)
Bugcheck code: 0xA (0x4B5A7CC940, 0xFF, 0x72, 0xFFFFF80249E3D23F)
Error: IRQL_NOT_LESS_OR_EQUAL
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.

Packed minidump: https://drive.google.com/open?id=1fUYOkfSNj21vQ0YTiAD5XiYQmppepntO


Edit:
I was testing with Prime95 and got this bsod as something new:

Spoiler: WhoCrashed

On Wed 11.03.2020 0:49:43 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031120-7781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x192 (0xFFFF8488A657C080, 0xFFFFE639875FA0B0, 0x0, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
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 lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
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.



On Wed 11.03.2020 0:49:43 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32kbase.sys (win32kbase!GreEnterCriticalRegionAndAcquirePushLockExclusive+0x107)
Bugcheck code: 0x192 (0xFFFF8488A657C080, 0xFFFFE639875FA0B0, 0x0, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
file path: C:\Windows\system32\win32kbase.sys
product: Операционная система Microsoft® Windows®
company: Microsoft Corporation
description: Базовый драйвер ядра Win32k
Bug check description: This indicates that a lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
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 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.

The thing is that it showed some error on some threads during Small FFT L1/L2/L3 test, but I'm not sure if it's a reliable source of detecting problems. Here is the prime95 dump:
https://drive.google.com/open?id=1mG6Qk62ImN09o9nzlZRKZIGHsf5ydyRT

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://apterousbusiness.htmlpasta.com/

File information:	031020-8906-01.dmp (Mar 10 2020 - 16:37:41)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: System)
Uptime:	2 Day(s), 20 Hour(s), 36 Min(s), and 02 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

Edit:
Result for 2nd dump: https://parlandosell.htmlpasta.com/

File information:	031120-7781-01.dmp (Mar 10 2020 - 17:49:43)
Bugcheck:	KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
Probably caused by:	memory_corruption (Process: Taskmgr.exe)
Uptime:	0 Day(s), 1 Hour(s), 10 Min(s), and 55 Sec(s)

 

[ReD-EyeD]

@gardenman Thank you, but I just edited the post adding another dump. Can you please run it too?

Edit: So all bsods shows

Probably caused by:

memory_corruption

Does this mean it's a memory problem or it can be anything still?

 

[ReD-EyeD]

So I was doing another memtest86+ run and encountered this after 10+ hours

https://imgur.com/lZo5Dx5

View: https://i.imgur.com/lZo5Dx5.jpg

So this is memory or it can still be anything?
Is there a difference between A1-B1 dual ram slots and A2-B2 placement?
Can lowering the ram frequency possibly fix this problem? I'm afraid it can be somehow connected to this mobo (asus tuf x470-plus gaming) being made for different cpus and was bios updated later to the 3rd gen Ryzen (mine is 3700x). I changed it to 2933 (from 3200) in bios for test purposes, but no idea if it can even change anything here.

 

[Colif]

specs
CPU - Ryzen 3700x
Motherboard - ASUS TUF x470 gaming plus
GPU - GTX 1070
16gd RAM
Razer Deathadder Elite

Any errors in Memtest are too many so I would rma ram.

A2/B2 are the slots it suggests for 2 ram sticks, should only use the other 2 slots if you have 3 or more sticks. Many boards may not boot if there isn't a stick in A2 as that is the slot you would use if you only have 1 stick.

https://dlcdnets.asus.com/pub/ASUS/...GAMING/E13882_TUF_X470-PLUS_GAMING_UM_WEB.pdf

I believe 2933 is the speed Ryzen runs to achieve 3k. IS the ram on the Motherboard qlv list as that can tell you if it will work or not.

 

[ReD-EyeD]

@Colif So another night long memtest showed no error with the second XMP profile for 2933/17 memory. I guess it's a good thing. And at least yet I haven't encountered any bsods, but they're pretty random in the first place so who knows.
The thing I'm concerned about is prime95 showing "hardware error" on some threads when I try to FFT L1/L2/L3 test. The threads load pretty normally in other programs so I guess it's just prime95 being unreliable tool.

 

[Colif]

installed winrar to look at the prime95 dump, it didn't work as expected. I assumed it was a report from Prime95, not a minidump.

is that the 1st or 3rd test? I haven't ever needed to use it

what is showing in stress.txt file in the prime95 folder?

 

[ReD-EyeD]

@Colif No, the prime95 rar is a windows minidump, I just double checked it.

It's a second Small FFT test.

Sorry, but I'm not sure what you mean by stress.txt, because stress.txt only has basic Q&A text:

Spoiler: stress.txt

STRESS TESTING YOUR COMPUTER

BACKGROUND
----------

Today's computers are not perfect. Even brand new systems from major
manufacturers can have hidden flaws. If any of several key components such
as CPU, memory, cooling, etc. are not up to spec, it can lead to incorrect
calculations and/or unexplained system crashes.

Overclocking is the practice of increasing the speed of the CPU and/or
memory to make a machine faster at little cost. Typically, overclocking
involves pushing a machine past its limits and then backing off just a
little bit.

For these reasons, both non-overclockers and overclockers need programs
that test the stability of their computers. This is done by running
programs that put a heavy load on the computer. Though not originally
designed for this purpose, Prime95 is an excellent way of placing a heavy
load on a computer system and includes a "torture test" to allow users to do
so without interfering in the prime search.


RESOURCES
---------

This program is a good stress test primarily for CPUs and RAM, as well as
cooling systems and power supplies. The torture tests run continuously, checking
the calculations are within certain parameters while they are in progress and
comparing your computer's final results to results that are known to be correct.
Any mismatch and you've got a problem!

You'll need other programs to stress test other system components, monitor
the state of the system while testing and help identify the source of any faults
that arise.

Other stress tests for CPUs, memory, graphics cards etc:
OCCT - http://www.ocbase.com
Linpack - http://www.techpowerup.com/download/linpack-xtreme/
Realbench - http://rog.asus.com/tag/realbench/
MemTest64 - http://www.techpowerup.com/memtest64/
FurMark - http://geeks3d.com/furmark/
GpuTest - https://www.geeks3d.com/gputest/
PassMark BurnInTest - https://www.passmark.com/products/bit.htm
Aida64 - https://www.aida64.com/

Utilities and monitoring software:
Intel XTU - https://downloadcenter.intel.com/download/24075
Ryzen Master - https://www.amd.com/en/technologies/ryzen-master
Afterburner - https://www.msi.com/page/afterburner
HWiNFO - https://www.hwinfo.com/
CPU-Z - https://www.cpuid.com/softwares/cpu-z.html
GPU-Z - https://www.techpowerup.com/gpuz/

Useful websites and forums with pertinent information:
http://www.overclockers.com
http://www.overclock.net
http://www.anandtech.com
http://www.tomshardware.com
http://www.hardocp.com
http://linustechtips.com/main/
http://ark.intel.com
http://www.amd.com/en/products/specifications/processors

A number of subreddits exist where assistance may be found - please make sure
you understand the scope of each and read their rules before posting:
http://www.reddit.com/r/pchelp
http://www.reddit.com/r/buildapchelp
http://www.reddit.com/r/techsupport
http://www.reddit.com/r/overclocking
http://www.reddit.com/r/Intel
http://www.reddit.com/r/AMD


WHAT TO DO IF A PROBLEM IS FOUND?
---------------------------------

The exact cause of a hardware problem can be very hard to find.

If you are not overclocking, the most likely cause is memory. It is not uncommon
for memory to not run correctly at its rated speed (incorrectly "binned"). This is
most easily tested by swapping it with memory from another compatible computer and
retesting. If that is not possible you can try underclocking memory or increasing
memory voltage a tiny bit. Overheating is another possible source of problems.
You can check the temperatures using monitoring software like HWiNFO to make sure
the CPU is below it's rated temperature limit. If not, the cooler may be incorrectly
mounted or disconnected from the system while in transit, or the thermal paste
between the CPU and the cooler may not have been applied properly - YouTube is an
excellent place to find videos demonstrating correct cooler/paste application methods.
Occasionally, the power supply is incapable of supplying sufficient power to the
system under heavy load, you can often diagnose this by monitoring the 12v, 5v and
3.3v voltages - you will typically observe a substantial drop in these voltages when
putting the system under load and generally means the PSU itself needs to be replaced
with a more capable unit.

If you are overclocking, the most likely problems are either the CPU core
voltage being set too low or drooping too far under heavy low. You should
either increase the voltage or adjust the load line calibration to deal
with these issues. Another frequently seen issue is the motherboard failing
to set a suitable voltage for the memory controller when an XMP profile is
enabled.

The above causes are far from a comprehensive list of possible causes. Diagnosing
the exact cause can be a very difficult process.

NB: You should always thoroughly research the voltage tolerances of any
specific component before you start changing it. Memory controllers integrated
into modern CPUs in particular are very sensitive to increased running voltages
and can functionally degrade very quickly if set too high. Also make sure you
have accurate temperature monitoring in place while stress testing with increased
voltages and clock speeds as heat outputs increase exponentially - 1st generation
Ryzen CPUs specifically develop heat-related stability problems when running at
temperatures above 70degC.


CAN I IGNORE THE PROBLEM?
-------------------------

Ignoring the problem is a matter of personal preference. There are
two schools of thought on this subject.

Most programs you run will not stress your computer enough to cause a
wrong result or system crash. If you ignore the problem, then certain
workloads may stress your machine resulting in a system crash. Also,
stay away from distributed computing projects where an incorrect calculation
might cause you to return wrong results. Bad data will not help these
projects! In conclusion, if you are comfortable with a small risk of an
occasional system crash then feel free to live a little dangerously! Keep in
mind that the faster prime95 finds a hardware error the more likely it is that
other programs will experience problems.

The second school of thought is, "Why run a stress test if you are going
to ignore the results?" These people want a guaranteed 100% rock solid
machine. Passing these stability tests gives them the ability to run
CPU intensive programs with confidence.


FREQUENTLY ASKED QUESTIONS
--------------------------

Q) My machine is not overclocked. If I'm getting an error, then there must
be a bug in the program, right?

A) The torture test is comparing your machines results against
KNOWN CORRECT RESULTS. If your machine cannot generate correct
results, you have a hardware problem. HOWEVER, if you are failing
the torture test in the SAME SPOT with the SAME ERROR MESSAGE
every time, then ask for help at http://mersenneforum.org - it is
possible that a recent change to the torture test code may have
introduced a software bug.

Q) How long should I run the torture test?

A) I recommend running it for somewhere between 6 and 24 hours.
The program has been known to fail only after several hours and in
some cases several weeks of operation. In most cases though, it will
fail within a few minutes on a flaky machine. When overclocking it is
entirely feasible to run short 10-15min tests at each increase in
clock speed to quickly assess the feasibility of running at those
speeds, then run longer tests later.

Q) Prime95 reports errors during the torture test, but other stability
tests don't. Do I have a problem?

A) Stability tests are not equal in their ability to detect problems.
Some don't apply a heavy enough load for their results to be reliable,
while others apply loads so heavy that only extremely edge-case
real-world workloads would compare. There also may be significant
differences between stress tests regarding the CPU features they make
use of, so specific tests that don't make use of them may not be valid
for specific use cases where those features are required (e.g. AVX
instructions, virtualization technologies).

Q) A forum member said "Don't bother with prime95, it always pukes on me,
and my system is stable!. What do you make of that?"

or

"We had a server at work that ran for 2 MONTHS straight, without a reboot
I installed Prime95 on it and ran it - a couple minutes later I get an error.
You are going to tell me that the server wasn't stable?"

A) If a system can be easily crashed or made to generate incorrect
results to mathematical functions simply by running a program on it,
it is impossible to argue that it is reliable. The consequences of
that unreliability are up to the user to be aware of, but many faults
go unnoticed for a long time. Glitches in games may be assumed to be
bugs in the programming. Vital data in long term storage may already
have been corrupted without anyone knowing about it. The question to
ask yourself is whether or not the responsibilities of that system are
unimportant enough to make continuing without remedial action worth
the risk.

Edit: This is what was in result.txt

Spoiler: 123

[Wed Mar 11 00:42:30 2020]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 1.672505351e+017, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 1.054495759e+015, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Wed Mar 11 00:47:48 2020]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Wed Mar 11 00:49:28 2020]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Wed Mar 11 00:54:50 2020]
FATAL ERROR: Rounding was 8.69211825e+015, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Wed Mar 11 12:42:04 2020]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Wed Mar 11 12:43:02 2020]
FATAL ERROR: Rounding was 4.476615642e+015, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 9.050484873e+011, expected less than 0.4
Hardware failure detected, consult stress.txt file.

 

[Colif]

errors in small fft's are most likely cpu related
errors in large fft's are memory and NB/IMC related
if vcore is way too low it can error in large or small or crash
small fft's are these 8k,14k,20k and so on
large fft's are these 768k.986k,1024k and so on
running blend switches between small and large,so depending
on what size it fails at will determine what needs to be done
to fix it.

https://www.overclock.net/forum/10-amd-cpus/1117110-prime-95-hardware-failure-detected.html

The "Small FFTs" test uses relatively small FFTs which can fit into the CPU cache. As a result, the small FFT test is the one which accesses your main memory the least but it still makes some memory accesses. Prime95 automatically creates a FFT size range which will fit into the L2 cache of your CPU.

Prime 95 guide - http://www.playtool.com/pages/prime95/prime95.html

answer appears to be bump up vcore,

Prime 95 tests CPU & RAM
Memtest tests CPU & RAM
Both have errors,
error 7 in memtest is

This is a variation of the moving inversions algorithm that shifts the data pattern left one bit for each successive address. The starting bit position is shifted left for each pass. To use all possible data patterns 32 passes are required. This test is quite effective at detecting data sensitive errors but the execution time is long.

https://www.memtest86.com/tech_individual-test-descr.html

I was excpecting a report something like this - https://www.passmark.com/forum/memtest86/45115-memtext86-quitting-at-test-7-due-to-too-many-errors

 

[ReD-EyeD]

@Colif It went without errors for 10 hours with the new 2933 profile and seems to be working fine for now.

I thought about adding the voltage too, but I guess lowering the frequency works too. I also got suggested to do this:

BIOS > Advanced Mode (F7):
Ai Tweaker > DIGI+ VRM > VDDCR CPU Power Phase Control = Extreme
Advanced > AMD CBS > Zen Common Options > Global C-state Control = Disabled
Power Supply Idle Control = Typical Current Idle [/QUOTE]

and/or changing infinity fabric frequency.

I guess everything points to power saving and other voltage problems. I'm so glad that the problem window thightens

 

[ReD-EyeD]

@Colif
Just crashed while I was away from pc with barely anything on and then after I tried to copy the minidump to other place and share it, it bsoded again.
Can you please check it? These are the new error codes that I haven't seen before:

Spoiler: 123

On Fri 20.03.2020 20:54:58 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032020-6796-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF805202E4A89)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF805202E4A89, 0xFFFFCF8EB0594D48, 0xFFFFCF8EB0594590)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Операционная система Microsoft® Windows®
company: Microsoft Corporation
description: Диспетчер фильтров файловых систем Майкрософт
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.



On Fri 20.03.2020 20:54:58 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (0xFFFFF805202E4A89)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF805202E4A89, 0xFFFFCF8EB0594D48, 0xFFFFCF8EB0594590)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Операционная система Microsoft® Windows®
company: Microsoft Corporation
description: Диспетчер фильтров файловых систем Майкрософт
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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.



On Fri 20.03.2020 19:57:32 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032020-6875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80462573358, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

https://drive.google.com/open?id=1GShQV9Rr1D7AUEWja-HqehVckHA7G74M
minidump

I'm going crazy already. What's that even can be? PSU? RAM? CPU? Motherboard? Software? Hardware? T_T

Edit:
It seems that it crashes on idle than anything.

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://bustierraccoondog.htmlpasta.com/

File information:	032020-6875-01.dmp (Mar 20 2020 - 12:57:32)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: RzSDKService.exe)
Uptime:	0 Day(s), 8 Hour(s), 40 Min(s), and 07 Sec(s)

File information:	032020-6796-01.dmp (Mar 20 2020 - 13:54:58)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	memory_corruption (Process: SearchProtocolHost.exe)
Uptime:	0 Day(s), 0 Hour(s), 56 Min(s), and 24 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

the new format of ada is um... interesting (thats at Gardenman)
the errors on Extra 5 say he has no page file but thats impossible if his system is creating minidumps. Can't have one without other.

top one crashed Razer chroma drivers...

maybe update synapse since your copy is from 2016. Not sure if synapse 3 would match your keyboard.

 

[ReD-EyeD]

the new format of ada is um... interesting (thats at Gardenman)
the errors on Extra 5 say he has no page file but thats impossible if his system is creating minidumps. Can't have one without other.

top one crashed Razer chroma drivers...

maybe update synapse since your copy is from 2016. Not sure if synapse 3 would match your keyboard.

Well, I'm specifically using the older synapse because the new one had some verifying problems. I honestly don't think that it's an issue here.
The problem here is that I had one bsod during the windows installation and it happens 99% of the time during low to low-mid load and I can run stress tests like RealBench or Cinebench without errors.

 

[Colif]

idle is when windows runs all its background tests. I see a lot of people where the errors happen when PC just idling.

I go get a 2nd opinion. It could still be that ram problem.

 

[ReD-EyeD]

The reason why I'm sitting on Synapse 2 instead of 3 is because I had similar problem with 3rd version too so I downgraded it and apparently it didn't help.

 

[Jentry]

Did you ever figure this out? I feel like your problem precisely describes mine, thus I won't go into too much additional detail.

I have a brand new computer with fairly high specs. I can run things such as The Witcher 3 on max settings without a problem, but card/board games seem to cause trouble. Legends of Runeterra either crashes without warning or BSOD within 10 minutes of play. I also have the same errors playing Thronebreaker (a card game) and it happened during my first game of Settlers of Catan, at the precise moment that a victory screen was supposed to appear... I've only played a few games of Catan, but it hasn't happened since.

Additionally, I sent the computer back and they replaced the Ram and the CPU, so if there's a defective part, those likely aren't the issue. I don't think it's the GPU either, as I ran a test without the GPU, and the same problems occur.

I've reinstalled Windows many times, and although I've attempted to tinker with many things including driver updates and virtual ram, I believe I'm currently running it fresh out of the box (aside from Windows 10 updates).

CPU: Intel(R) Core™ Processor i9-9900K 3.60GHZ 16MB Intel Smart Cache LGA1151
Motherboard: MSI MPG Z390 GAMING EDGE AC ATX w/ ARGB, 802.11ac Wi-Fi, USB 3.1, 3 PCIe x16, 3 PCIe x1, 6 SATA3, 2 M.2 SATA/PCIe
Ram: 32GB (8GBx4) DDR4/3200MHz Dual Channel Memory (Team T-Force Delta RGB)
SSD/HDD: 512GB ADATA 6000LNP M.2 NVME SSD + 3TB SATA III Hard Drive Combo (Combo Drive)
GPU: GeForce RTX™ 2080 Ti 11GB GDDR6 (Turing) [VR Ready] (Single Card)
PSU: 1,000 Watts - Standard 80 Plus Gold Power Supply
Chassis: LIAN LI PC-O11 Dynamic ATX Mid-Tower Dual chamber
OS: Windows 10 (up-to-date)

 

[gardenman]

Hi Jentry, this thread is 3 months old. It would be best to start your own thread here: https://forums.tomshardware.com/forums/windows-10.13/post-thread

 

[ReD-EyeD]

@Jentry
Yes, I actually solved my problem, but it's not similar to yours I guess. My cpu was a faulty one from the very first zen2 releases and switching it solved everything for me. Hope you can resolve your problem.

 

[Colif]

His was also an AMD 3700X, it says it in topic.

Glad you found an answer, even if it wasn't an obvious one.