[SOLVED] Recurring BSODs, Any Help is appreciated

[JustOneMan]

Hi all, thanks for taking the time to look at this. I had dealt with several persistent BSODs from January to March of this year, then after a windows reinstall, was error free for three months. Then this past week, the BSODs have begun recurring. Typically they happen when playing a game (Overwatch is the most common culprit, but I've experienced them in Red Dead Redemption 2, and VR titles like Blade and Sorcery or Pavlov VR), but today I've had several BSODs in the course of working/browsing. Today I've had BSODs connected to installation of some troubleshooting software (Win 10 ISO image, malwarebytes installation), and running the DISM tool and chkdsk.

My experiences/repair attempts have been very similar to users @_Treadstone (see: https://forums.tomshardware.com/thr...ating-to-ntoskrnl-exe-for-months-now.3581744/ ) and @_Red-EyeD (see: https://forums.tomshardware.com/thr...atest-build-3700x-x470.3579352/#post-21610090 ). Error codes have been all over the place – page faults, kernel exceptions, heap errors, write violations, etc. Pretty sure I’ve seen most if not all of the codes referenced by @_Treadstone above.

In addition to a fresh windows repair and reinstall, I’ve rolled back/ reinstalled GPU drivers, gone through 8 passes of Memtest (no errors), run sfc /scannow, chkdsk /f, DISM tool options (all clean eventually, though I did experience some BSODs when attempting to run them), windows memory test (no errors). I’ve run Furmark as a GPU stress, as well as testing the processor via Intel Extreme Tuning Utility as well as the Intel Diagnostic Tool and all have come up fine.

I have not had much success with Driver Verifier. Deselecting all Microsoft Drivers and enabling verifier leads to a BSOD loop at boot and eventual system restore. My next step was to use DDU to do a clean uninstall of the graphics drivers and then reinstall, but am willing to try anything short of a blood sacrifice (although I could be convinced depending on whose blood we’re talking).

When I first built the PC (October 2018), I ran into some similar issues that I eventually traced to the voltage settings in the BIOS for my mother board (see: http://forum.asrock.com/forum_posts.asp?TID=6860&PN=1&title=z370-extreme4-xmp-bug). Earlier this week, I checked the voltages and noticed they had reverted back to default (possibly during a BIOS update, maybe during windows reinstall? I don’t know). I’ve changed them as per the post linked above, but the BSODs persist.

Specs:

OS: Windows 10 Home 64-bit

MB: ASRock Motherboard Motherboards Z370 EXTREME4

CPU: Intel Core i7-8700K Desktop Processor 6 Cores up to 4.7GHz Turbo Unlocked LGA1151 300 Series 95W

CPU Cooler: Noctua NH-D15 6 heatpipe with Dual NF-A15 140mm fans

RAM: Corsair Vengeance LPX 16GB (2x8GB) DDR4 DRAM 3200MHz C16 Desktop Memory Kit - Black (CMK16GX4M2B3200C16)

GPU: NVIDIA GeForce GTX 1080 Ti (EVGA)

SSD: 232GB Samsung SSD 840 EVO 250GB (SATA (SSD)) ß Windows

232GB Samsung SSD 840 EVO 250GB (SATA (SSD))

465GB Samsung SSD 970 EVO 500GB (PCIe M.2 NVMe (SSD))

PSU: EVGA 750 B3, 80+ Bronze 750W, Fully Modular, EVGA ECO Mode, 5 Year Warranty, Compact 160mm Size, Power Supply 220-B3-0750-V1

Misc: Intel Wireless Gigabit W11100 VR Device ß Wireless VR Adapter



Here is a link to a google drive folder with all the minidumps I have going back to late February through the middle of me typing this post, when I had the last BSOD (6/17/20 @ 2:44 PM EST). There is also the latest large memory.dmp file, as well as DXDiag logs, a SPECCY system snapshot, and some miscellaneous system info (services, hosts, drivers, etc.): https://drive.google.com/drive/folders/1PkfIfCuJuvsCdq3HYvasSWTXJNHrKzZI?usp=sharing

This is driving me up the wall. Any help would be greatly appreciated!

 

[Colif]

I wish Microsoft could write a driver testing tool that doesn't end up with boot loops.

Those 2 threads seem familiar. I don't recall if we ever got any answer for them.

Can you download and run Driverview - http://www.nirsoft.net/utils/driverview.html
All it does is looks at drivers installed; it won't install any
When you run it, go into view tab and set it to hide all Microsoft drivers, will make list shorter.

Now its up to you, you can look through the drivers and try to find old drivers, or you can take a screenshot from (and including)Driver name to (and including)Creation date.
upload it to an image sharing website and show link here

All Iwill do is look at driver versions (or dates if you lucky to have any) to see what might have newer versions.


your google drive link doesn't work, I am not sure what you have done to it. If I hover over it it shows a mail to option?

 

[JustOneMan]

Ok, Google drive link should be fixed above - not sure why it ended up as a mailto. Here it is again: https://drive.google.com/drive/folders/1PkfIfCuJuvsCdq3HYvasSWTXJNHrKzZI?usp=sharing. In any case, my PC had been running Windows 1909 and wasn't giving the option to upgrade to 2004, so I went to Microsoft's site and manually updated. I blue screened mid-update and was unable to boot... ultimately had to reinstall Windows. The only flash drive I had with a windows install was 1909, and I did experience a BSOD after the install. No minidump as I hadn't re-activated them yet, but the larger memory dump file is in the Google drive (MEMORY_061720_2056.dmp). That was prior to several windows/driver updates however. I am now running 2004 and haven't had any crashes yet, even played some games for a couple of hours last night.

I wonder if the staggered deployment of the 2004 update is causing some conflicts. Maybe some third-party updates are designed with 2004 in mind, so when pushed to a 1909 machine there are conflicts?

In any case, I've added the DriverView screenshot to the google drive folder. If anything jumps out let me know, but don't spend too much time on it. If I experience more crashes I'll update the thread. Fingers crossed until then. Thanks for the help!

 

[gardenman]

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

Spoiler

File information:	061720-9781-01.dmp (Jun 17 2020 - 14:42:27)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 27 Min(s), and 10 Sec(s)

File information:	061720-7593-01.dmp (Jun 17 2020 - 12:24:49)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: amd64_micr...)
Uptime:	0 Day(s), 0 Hour(s), 31 Min(s), and 27 Sec(s)

File information:	061720-7546-01.dmp (Jun 17 2020 - 13:25:48)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 1 Hour(s), 00 Min(s), and 07 Sec(s)

File information:	061720-6921-01.dmp (Jun 17 2020 - 14:12:41)
Bugcheck:	KERNEL_MODE_HEAP_CORRUPTION (13A)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 58 Sec(s)

File information:	061720-6859-01.dmp (Jun 17 2020 - 14:08:56)
Bugcheck:	UNEXPECTED_KERNEL_MODE_TRAP (7F)
Probably caused by:	memory_corruption (Process: chrome.exe)
Uptime:	0 Day(s), 0 Hour(s), 16 Min(s), and 16 Sec(s)

File information:	061720-6718-01.dmp (Jun 17 2020 - 13:51:51)
Bugcheck:	POOL_CORRUPTION_IN_FILE_AREA (DE)
Probably caused by:	memory_corruption (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 06 Min(s), and 37 Sec(s)

File information:	061720-6687-01.dmp (Jun 17 2020 - 13:41:02)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: MediaCreationTool2004.exe)
Uptime:	0 Day(s), 0 Hour(s), 13 Min(s), and 36 Sec(s)

File information:	061720-6453-01.dmp (Jun 17 2020 - 11:52:28)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	win32kfull.sys (Process: explorer.exe)
Uptime:	0 Day(s), 13 Hour(s), 22 Min(s), and 42 Sec(s)

File information:	031120-7078-01.dmp (Mar 11 2020 - 00:02:45)
Bugcheck:	KERNEL_MODE_HEAP_CORRUPTION (13A)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process: vrwebhelper.exe)
Uptime:	0 Day(s), 13 Hour(s), 36 Min(s), and 08 Sec(s)

File information:	022620-8562-01.dmp (Feb 26 2020 - 02:04:23)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: svchost.exe)
Uptime:	2 Day(s), 6 Hour(s), 53 Min(s), and 33 Sec(s)

Comment: The overclocking driver "IOCBios2.sys" was found on your system. (Intel Extreme Tuning Utility)

One crash was caused by NVIDIA. The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

Possible Motherboard page: https://www.asrock.com/MB/Intel/Z370 Extreme4/index.asp
You have the latest BIOS installed, version 4.20.

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

 

[Colif]

I can't tell what caused number 1
amd64_microsoft-windows-servicingstack is used for windows updates. (thats what crashed on 2nd BSOD)
error 3 was GPU related
Not sure about error 4
Error 5 (Chrome crashed) - I would guess its your lan drivers - You have these - Jun 11 2018 e1i65x64.sys Intel(R) Gigabit Adapter driver
I can't tell what caused 6
Error 7 - i haven't seen media creation tool crash before - but it was the victim
I wish they were all as clear as the Nvidia one.
Last 2 aren't so obvious

Nvidia - He has newest drivers so either older ones or use the drivers he gets from Windows Update is best place to start
Update this as well as your installed version is from 2018 - Intel Management Engine driver ver:11.8.65.3606_ME_SW_DCH (that can be found on link in next sentence) - it helps if its similar age as Bios.
Update Lan driver - Newer ones are found here - https://www.asrock.com/mb/Intel/Z370 Extreme4/index.asp#Download

 

[JustOneMan]

Thanks, @Colif and @gardenman for your help! One question about the lan driver - you mention it helps if its a similar age as the BIOS. On the mobo page I see Intel Lan driver ver:12.18.9.7w, dated August 5, 2019, but on Intel's page they have one from January 23, 2020. The BIOS itself is dated November 6, 2019. And, for maximum confusion, updating through Windows device manager has left me with a driver from 1/24/2019... do you recommend I update from the motherboard site, intel's site, or just leave it with what Windows just gave me (and claims is up to date)?

Still no crashes since 6/17. Maybe solved, I don't know. Are there any customs/traditions with trophy awards? I feel like I should wait a few days to make sure its all good before I start handing out prizes.

 

[Colif]

No, Intel management Engine Interface needs to be about same age as bios, not LAN

Let windows do what it wants with LAN drivers.

 

[JustOneMan]

I was out of town from 6/19 to 6/21, and had another BSOD yesterday (6/22). All I had open was a single tab on chrome. Otherwise I've been stable, even through multiple gaming/work sessions.

Here is the minidump (larger dump was not created for some reason): https://drive.google.com/file/d/1ySHoapSCFZXuS3lXcutNgS_uMVW2_g4L/view?usp=sharing

And the latest DXDiag (are these useful?): https://drive.google.com/file/d/18ilGz-vSMnbGpXuANXzb2LXdYHUc5spn/view?usp=sharing

Thanks in advance!

 

[gardenman]

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

File information:	062220-4359-01.dmp (Jun 22 2020 - 19:55:02)
Bugcheck:	KERNEL_MODE_HEAP_CORRUPTION (13A)
Probably caused by:	Pool_Corruption (Process: SearchProtocol)
Uptime:	0 Day(s), 23 Hour(s), 44 Min(s), and 32 Sec(s)

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

 

[Colif]

one reoccurring fix I find for that error code is GPU drivers
having newest GPU drivers isn't ideal with Nvidia

we have been here already. Perhaps run ddu and run windows update afterwards. Don't install Geforce Experience as you don't want to get the same drivers again.

 

[JustOneMan]

Thanks for your continued help, @Colif and @gardenman! I've run DDU in safe mode and let Windows roll back to NVIDIA driver 432.00. Just had another BSOD while sitting on a menu screen of a game. Here is the minidump: https://drive.google.com/file/d/1xK-NtUvjneyRpgnD1DrrOa-Eo2XEJubC/view?usp=sharing.

I also have had numerous application crashes in menu or loading screens that don't result in a BSOD but I think may be related (several of them have DXDiag log entries I think - do you look at DXDiag log files?). Should I run DDU again and roll back to an earlier driver? Or try running on one of the later drivers from NVIDIA?

 

[gardenman]

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

File information:	062620-4906-01.dmp (Jun 26 2020 - 12:31:19)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 2 Hour(s), 54 Min(s), and 33 Sec(s)

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

 

[Colif]

That one doesn't appear to be GPU related so I wouldn't bother with ddu this time.

I wonder what dxdiag log files look like. I have seen the text outputs that show details, unsure about log files.

Try running the smart scans and benchmarks on your ssd - https://www.samsung.com/semiconductor/minisite/ssd/download/tools/ (Download Magician)

 

[JustOneMan]

I was mistaken - they're not the log files, but the file that DXDiag produces with the 'Save All Information' button. Here it is if you need it:

https://drive.google.com/file/d/1Fanb4Vq-NMxP0gLz5gHB0jgv5RWB6xXm/view?usp=sharing

Magician recognizes my SSDs but says my drives do not support the scan feature. It indicates that the firmware is up to date and is able to run benchmarks and all the other functions, but does not run any of the diagnostic scans. I believe both the 840 and 970 drives that I have support the SMART scan, so I'm not sure what's going on.

 

[JustOneMan]

Two more crashes in the last few hours. The first occurred when I was away from the machine. I'm not sure what, if any, programs were open:

https://drive.google.com/file/d/1a0UdRDdKlsbuoAjIl0LSxeHXtGBWR1eL/view?usp=sharing

My wife was browsing through some images on an external USB hard drive when the second crash occurred. This was a few minutes after both monitors simply displayed a black image (not shut off) and the forced a hardware reset when she was looking at pictures:

https://drive.google.com/file/d/109GpQ-FWaPk-u9p4TPRuwZuwfuoqZzmp/view?usp=sharing

And one more. Tried running SSDLife (https://ssd-life.com/ ) since Magician wasn't scanning properly. KMode exception, went into repair mode and I had to do a system restore to this morning:

https://drive.google.com/file/d/1y3TSP-xYa3fnBEGTNmMZByG1g1XGhP0O/view?usp=sharing

Thanks again.

 

[gardenman]

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

Spoiler

File information:	062620-4140-01.dmp (Jun 26 2020 - 13:09:08)
Bugcheck:	CACHE_MANAGER (34)
Probably caused by:	ntkrnlmp.exe (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 37 Min(s), and 17 Sec(s)

File information:	062620-4109-01.dmp (Jun 26 2020 - 18:45:27)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 20 Min(s), and 07 Sec(s)

File information:	062620-3953-01.dmp (Jun 26 2020 - 19:45:21)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	Unknown_Image (Process: steamwebhelper)
Uptime:	0 Day(s), 0 Hour(s), 59 Min(s), and 27 Sec(s)

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

 

[JustOneMan]

Well, I ran MemTestPro (https://hcidesign.com/memtest/ ) and it came up with several memory errors before the test crashed. Haven't retested using MemTest86 or windows memory diagnostics, but they were all clean as of a couple of months ago. I'm guessing/hoping one of my RAM sticks is faulty - I've started an RMA process. Really hope its not the CPU.

Will update when I learn more.

 

[JustOneMan]

Well, Prime95 showed errors on its 'Blend' test (which stresses CPU and RAM) after a few minutes. When I disabled the Blend test and went with one that stressed only CPU, it ran error free for two hours.

So I pulled out one of the RAM sticks and tried MemTestPro - no errors after 125% coverage, which the developers claim should account for 95% of bad RAM errors (with both RAM sticks installed, I saw an error after a few minutes).

Swapped the sticks and re-ran MemTestPro on the other stick. Over 100% with no errors. Bad slot on the motherboard? Going to try both sticks in the A2/B2 slots they were in, just in case it was not seated correctly.

Will report back unless my PC bricks itself. If that happens I'm off to vodka city.

 

[JustOneMan]

Ok... RAM sticks seem to both be good, but the A2 slot was faulty, or I reseated the RAM incorrectly again - the system only recognized 8 GB of my 16. A1/B1 configuration is running ok so far - up past 20% on MemTestPro.

But the memory speed seems to be capped at 2133 instead of 3200 (where its rated), and whenever I start the PC now, it hangs and gives me a message saying "The system has failed to boot several times before" and give me the option to enter BIOS or let the machine continue. If I do nothing, the machine continues to Windows without further issue. If I go into BIOS and try to increase the memory speed, it "fails to boot" and then goes into Windows. But CPU-Z identifies my RAM speed at 2133.

I will be running MemTestPro or Prime95 all night to see if this is stable. But it would be nice to have my PC start without failing several times and to be able to run my RAM at its advertised speeds.

 

[JustOneMan]

Just shut down and moved the RAM sticks from A1/B1 back to slots A2/B2 (manufacturer recommended, furthest from CPU). Started back up without any issue, though it seemed to have skipped the boot screen with the BIOS options - wonder if fast boot turned itself on. Sticks still running at 2133 rather than 3200, but MemTestPro is reporting no errors at 20% when it reported some almost immediately. I can live with slower RAM if I have to, and I'll be doing some extensive testing over the next few days, but maybe the RAM was just improperly seated this whole time? Maybe I kicked the tower or my dog ran into it or something and knocked a stick partially loose? I've got no idea how else to explain this.

In any case, I will report back if things go all blue on me again or when I'm satisfied that this was the problem. Thanks for all your help.

 

[Colif]

Sorry i been busy elsewhere...
IS ram running in xmp as maybe that explains speed difference.

 

[JustOneMan]

I've done extensive testing using Prime95 and MemTestPro now that the sticks are definitely properly seated. No errors on either of them, and no BSODs in other use. 95% sure the RAM being loose was the problem now. Part of me is going to wonder if the issues I was having from January to March were also related to loose RAM sticks or if that was actually mismatched drivers or something. Its worth noting that when I fixed the issues earlier in the year, I was testing the memory sticks and got stuck in a boot loop requiring a full reinstall of Windows. After the reinstall (two reinstalls, actually) I had no issues for three months. Maybe one of my memory slots is slightly damaged and the stick just comes loose over time? I'll make sure to check whenever I dust the internals, I suppose.

@Colif, I am running in XMP. CPU-Z still indicates my RAM is running at 2133, but Windows task manager says its at 3200, as does the BIOS. Some light googling shows that CPU-Z can misread RAM speed sometimes, so I think I should be good. Do you know of any other software to check RAM speed? In any case, thanks to you and @gardenman for all of your assistance, and apologies for not checking the RAM itself sooner.

TL;DR - Make sure to check to make sure your RAM is seated well before going down a rabbit hole of reboots, restores, and forum threads.

 

[JustOneMan]

Well, it wasn't the RAM being seated wrong. BSOD's have been occurring again since 7/6. I have since used DDU and installed the latest NVIDIA drivers (and gone back to the Windows install). The BSOD's have occurred either while playing Overwatch, or shortly after an Overwatch session that ended in a game crash - about thirty seconds later I'll get a BSOD. Interestingly, if I let the PC reboot and get back into Windows, I usually end up with a second BSOD within about 20 minutes. RAM not clearing properly? Anyway, here are the minidumps:


7/6 (1): https://drive.google.com/file/d/1_BeLOnWIpir6mb3zUddCkSQnh4E_73hy/view?usp=sharing

7/6 (2): https://drive.google.com/file/d/1ZOohMAZBq3tCz8BTiUSRpTZCZ1yphQCd/view?usp=sharing

7/7: https://drive.google.com/file/d/1pRKpRyq4ebxgm63U7BGNCzlL-mEBHznw/view?usp=sharing

7/8: https://drive.google.com/file/d/1n4i2xTX17Qf5-sZg-mVzQWWwZGcwv3VG/view?usp=sharing

7/9: https://drive.google.com/file/d/15T63wPMIcaAnGBjrqCIt0vfsoC2XpVQi/view?usp=sharing

7/10 (1): https://drive.google.com/file/d/1L3K-BsjLVEaNQ_ZiXs9m6NNNjo_E3cx2/view?usp=sharing

7/10 (2): https://drive.google.com/file/d/1AaVrvEnHk3jmG6feheADZTXfydM7mPzq/view?usp=sharing

7/11: https://drive.google.com/file/d/1Eg3eUPWUmWIhxQvtvVFuwRtuHnQ_Pa8s/view?usp=sharing

The good news is that I feel like less of an idiot now that I'm certain it wasn't just an improperly seated RAM stick. The bad news is that I'm still trying to figure this nonsense out. I'm currently running the latest NVIDIA drivers, but am going to start rolling back to see if hopefully I can find something stable.

Thanks in advance for any help!

 

[gardenman]

I'm sorry you're still having problems. I'll go ahead and read the dumps. I'm not sure when Colif will be here to look them over.

Results: https://pastebin.com/YmnZtxT8

Spoiler

File information:	071120-4421-01.dmp (Jul 11 2020 - 00:24:48)
Bugcheck:	KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:	dxgmms2.sys (Process: System)
Uptime:	1 Day(s), 0 Hour(s), 08 Min(s), and 23 Sec(s)

File information:	071020-4828-01.dmp (Jul 10 2020 - 00:14:37)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 12 Hour(s), 19 Min(s), and 45 Sec(s)

File information:	071020-4437-01.dmp (Jul 10 2020 - 00:15:55)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 45 Sec(s)

File information:	070920-5437-01.dmp (Jul 9 2020 - 11:54:21)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	ntkrnlmp.exe (Process: naturallocomot)
Uptime:	1 Day(s), 11 Hour(s), 11 Min(s), and 44 Sec(s)

File information:	070820-4750-01.dmp (Jul 8 2020 - 00:42:02)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 4 Hour(s), 30 Min(s), and 04 Sec(s)

File information:	070720-5125-01.dmp (Jul 7 2020 - 15:48:02)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	Pool_Corruption (Process: steamtours.exe)
Uptime:	0 Day(s), 1 Hour(s), 38 Min(s), and 34 Sec(s)

File information:	070620-5718-01.dmp (Jul 6 2020 - 14:09:44)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: chrome.exe)
Uptime:	0 Day(s), 0 Hour(s), 25 Min(s), and 07 Sec(s)

File information:	070620-5062-01.dmp (Jul 6 2020 - 14:35:12)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: Overwatch.exe)
Uptime:	0 Day(s), 0 Hour(s), 12 Min(s), and 27 Sec(s)

The first crash mentions DirectX which is usually the GPU or drivers.

The remaining dumps are not pointing at any specific driver which sometimes means it's a hardware issue. As for what hardware, I don't know. Do as much hardware testing as you can. I know you already have been doing so.

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

 

[Colif]

Yeah, 1st one is GPU drivers, and this is 3rd time. Last time I said

we have been here already. Perhaps run ddu and run windows update afterwards. Don't install Geforce Experience as you don't want to get the same drivers again.

and yet you have newest drivers from Nvidia now - Jun 21 2020 - nvlddmkm.sys - Nvidia Graphics Card driver - so you must have installed Geforce experience again?

very few drivers on PC so that reduces choices. I have to say it could be all GPU drivers. The remaining BSOD don't really tell me anything.

this might be newer than what you have - Intel Management Engine driver ver:11.8.65.3606_ME_SW_DCH - https://www.asrock.com/mb/Intel/Z370 Extreme4/index.asp#Download - it could help.
Not sure about the Western Digital driver from 2015
Oct 09 2015 - wdcsam64.sys - Western Digital SCSI Arcitecture Model (SAM) WDM driver https://support.wdc.com/ - probably for an ssd.
Intel LAN driver on asrock website might be newer than what you have as well.

ram speed - According to BIOS, you are running at 3200mhz. Could run this if you want to know for sure - https://www.passmark.com/products/performancetest/pt_advmem.php

can you run memtest86 to get a 2nd opinion on the ram?
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. Memtest is created as a bootable USB so that you don’t need windows to run it