BSOD's related to memory / drivers, increasing in frequency

Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan
4) slmgr /dlv
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
6) For step #4 > use the Microsoft snipping tool to create an image > post a one drive or drop box share link into the thread

7) Open this link:
https://www.google.com/url?sa=t&rct=...43idckGZ2Pb66V
8) Run / save MGADIAG.exe > when it opens click continue > use the snipping tool to make images and post one drive or drop box share links into the thread.

Microsoft Windows [Version 10.0.17134.1](c) 2018 Microsoft Corporation. All rights reserved.C:\Windows\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Windows\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.17134.1Image Version: 10.0.17134.1[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\Windows\system32>chkdsk /scanThe type of the file system is NTFS.Volume label is System Drive.Stage 1: Examining basic file system structure ... 619264 file records processed.File verification completed. 12014 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 1183 reparse records processed. 895448 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 1183 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 138093 data files processed.CHKDSK is verifying Usn Journal... 36513360 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 499109609 KB total disk space. 245062568 KB in 467763 files. 321312 KB in 138094 indexes. 0 KB in bad sectors. 747493 KB in use by the system. 65536 KB occupied by the log file. 252978236 KB available on disk. 4096 bytes in each allocation unit. 124777402 total allocation units on disk. 63244559 allocation units available on disk.C:\Windows\system32>slmgr /dlvScript

Host image added to Dropbox:
https://www.dropbox.com/sh/kvbhaxc5b...RaKhXRq5a?dl=0

I inadvertently installed W10 pro instead of the home version. I will begin re-installing.

With the next clean install:
a) Do not install any applications, files, browsers, etc.
b) Do not perform Windows updates: keep the Ethernet/cat5e disconnected and if available use hardware off for wireless
c) Open startup and recovery options system failure and un-check automatically restart
For any future BSOD make sure that the % counter always rises to 100% before rebooting so that there is sufficient time for the creation of the dump files.
d) reboot
e) All drivers should be only Windows installed drivers (default drivers from the clean install without Windows updates)
f) On a computer that is connected to the internet download the BETA log collector to a flash drive
g) For any BSOD on the computer that is not connected run the BETA log collector and post the zip directly into the thread: (use the upload feature: How to Upload and Post Screenshots and Files at Ten Forums | Windows 10 Tutorials)
And find the memory.dmp file > zip > upload directly into the thead
h) For all future files please use the upload feature so that clicking on the link in the thread opens the file.
i) Turn on Windows driver verifier > if there are any BSOD then run the beta log collector and transfer the files using a flash drive or external hard drive to a computer that is connected to the internet > post into the thread
j) If there are no BSOD with the clean install drivers then connect ethernet if available (do not turn on wireless) perform Windows updates. Do not install any drivers, applications, files, browsers, etc. If you only have wireless available then turn on wireless and indicate in the thread the method used to connect to the internet.
k) Turn on Windows driver verifier with the clean install drivers followed by Windows updates.
l) If there are BSOD then run the beta log collector > upload directly into the thread
And find the memory.dmp file and upload directly into the thread.
m) If there are no BSOD with clean install drivers followed by Windows update drivers then open the Asrock website and install one driver at a time followed by Windows updates followed by Windows driver verifier testing.
ASRock > Z68 Pro3 Gen3
n) If all of the drivers from the Asrock website do not BSOD after WIndows updates and Windows driver verifier then install the Intel GPU drivers from the Intel website:
Intel® Driver & Support Assistant
o) Then check the Intel GPU with Windows driver verifier
p) If there are no BSOD so far then use the computer for 36 hours (applications, browsers, files, etc. not yet installed)

Use the customized settings in this link for running Windows driver verifier:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Use the information in this link to turn off or recover from using Windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 | Windows 10 Tutorials

Beta log from the most recent crash attached to this post.

The memory.dmp file is too large to directly attach, so I placed it in the Dropbox folder:
https://www.dropbox.com/sh/kvbhaxc5b...RaKhXRq5a?dl=0

Now clean installed: Operating System: Windows 10 Home 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)

There was one mini dump collected and there was one memory dump.
Debugging of the mini dump displayed problems with the symbols in the database.
The memory dump debugging displayed Intel GPU:

The bugchecks were BE.

1) Turn off Windows updates of non-Microsoft drivers:
Enable or Disable Driver Updates in Windows Update in Windows 10 | Windows 10 Tutorials
Download Intel® Driver & Support Assistant
2) Find a rolled back version of the Intel GPU driver. (Any version other than: 9.17.10.4459)
Downloads for Graphics Drivers
3) Download the rolled back version to the desktop
4) Uninstall the current driver using device manager
5) Install the rolled back version from the desktop
6) Perform the uninstall followed by the install using safe mode

7) If there are any BSOD after the above steps post a new beta log collector and memory dump

There were prior testing of the RAM with Memtest86+ version 5.01.
Memtest86+ - Advanced Memory Diagnostic Tool
The computer has two RAM modules and four DIMM.
Remove both RAM modules and label them A and B.
Label the DIMM modules 1, 2, 3, 4.
Test the RAM module A in each of the four DIMM for 8 or more passes each.
Post images of each RAM / DIMM test result displaying in the notes the letter and the number.
The RAM testing should take approximately 1 - 2 hours / GB RAM.
To fully evaluate the RAM / DIMM /Motherboard there should be a total of eight tests (each RAM module tested in each DIMM)
Each DIMM will be tested twice (once with each RAM module).

The Memtest86+ version 5.01 testing can be performed in the evening/night.
Memtest86+ - Advanced Memory Diagnostic Tool
During the day hours use the computer with only one RAM module in the same DIMM that you plan to test in the evening/night.
This way there will be identical testing of the RAM / DIMM with typical computer use during the day and testing in the evening and overnight with Memtest86+ version 5.01.

Code:

Use !analyze -v to get detailed debugging information.

BugCheck BE, {ffffa2ae04899714, 8a00000003700021, ffffc901ff38e840, a}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Code:

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for igdkmd64.sys

Code:

Name    Intel(R) HD GraphicsPNP Device ID    PCI\VEN_8086&DEV_0102&SUBSYS_01021849&REV_09\3&11583659&0&10
Adapter Type    Intel(R) HD Graphics Family, Intel Corporation compatible
Adapter Description    Intel(R) HD Graphics
Adapter RAM    (1,883,242,496) bytes
Installed Drivers    igdumd64.dll,igd10umd64.dll,igd10umd64.dll
Driver Version    9.17.10.4459
INF File    oem5.inf (iSNBD0 section)
Color Planes    Not Available
Color Table Entries    4294967296
Resolution    1920 x 1080 x 59 hertz
Bits/Pixel    32
Memory Address    0xF7800000-0xF7BFFFFF
Memory Address    0xE0000000-0xEFFFFFFF
I/O Port    0x0000F000-0x0000F03F
IRQ Channel    IRQ 4294967292
I/O Port    0x000003B0-0x000003BB
I/O Port    0x000003C0-0x000003DF
Memory Address    0xA0000-0xBFFFF
Driver    c:\windows\system32\drivers\igdkmd64.sys (9.17.10.4459, 5.13 MB (5,382,856 bytes), 3/9/2017 4:16 AM)

Code:

igdkmd64.sys Thu May 19 12:45:17 2016 (573DFBAD)

Code:

igfx    igfx    c:\windows\system32\drivers\igdkmd64.sys    Kernel Driver    Yes    Manual    Running    OK    Ignore    No    Yes

Beta log with crash dumps immediately before and after GPU driver re-install attached.

Corresponding memory dump:
https://www.dropbox.com/s/z4iw6bgmf0...180609.7z?dl=0

There were two mini dumps and one memory dump.
The bugchecks were:
1E
3B

BSOD are caused by:
a) misbehaving software drivers
b) misbehaving hardware drivers
c) malfunctioning hardware
d) combination of the above

Please look for malfunctioning hardware by testing the DIMM / Motherboard (post #26 step#7) and post images of the results into the thread.

Code:

BugCheck 1E, {ffffffffc0000005, fffff80130c43537, 0, ffffffffffffffff}

Probably caused by : memory_corruption

Code:

BugCheck 3B, {c0000005, fffff805dbf1b570, ffff81047c43dec0, 0}

Probably caused by : memory_corruption

Code:

Name    Intel(R) HD GraphicsPNP Device ID    PCI\VEN_8086&DEV_0102&SUBSYS_01021849&REV_09\3&11583659&0&10
Adapter Type    Intel(R) HD Graphics Family, Intel Corporation compatible
Adapter Description    Intel(R) HD Graphics
Adapter RAM    (1,883,242,496) bytes
Installed Drivers    igdumd64.dll,igd10umd64.dll,igd10umd64.dll
Driver Version    9.17.10.4229
INF File    oem7.inf (iSNBD0 section)
Color Planes    Not Available
Color Table Entries    4294967296
Resolution    1920 x 1080 x 59 hertz
Bits/Pixel    32
Memory Address    0xF7800000-0xF7BFFFFF
Memory Address    0xE0000000-0xEFFFFFFF
I/O Port    0x0000F000-0x0000F03F
IRQ Channel    IRQ 4294967292
I/O Port    0x000003B0-0x000003BB
I/O Port    0x000003C0-0x000003DF
Memory Address    0xA0000-0xBFFFF
Driver    c:\windows\system32\drivers\igdkmd64.sys (9.17.10.4229, 5.13 MB (5,375,448 bytes), 5/26/2015 9:02 PM)

Code:

igdkmd64.sys Tue May 26 22:53:18 2015 (55653FAE)

Code:

igfx         5/26/2015 11:53:18 PM  C:\Windows\system32\DRIVERS\igdkmd64.sys

Two additional crash dumps for further insight in the meantime:

Memory dump:
https://www.dropbox.com/s/7jdkezzsud...180610.7z?dl=0

There were 4 mini dumps collected by the latest zip.
None of them displayed a definitive misbehaving driver.
The bugchecks were:
7E
1E
A
3B
All displayed probably caused by memory corruption.

When available please post images of the results for the two tests of each DIMM.

Code:

Debug session time: Sat Jun  9 11:53:18.661 2018 (UTC - 5:00)
System Uptime: 0 days 1:13:14.407
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`fa8d0cf0 ffffc881`27a9dac8 ffffc881`27a9d310
Probably caused by : memory_corruption

Code:

Debug session time: Sat Jun  9 10:04:18.448 2018 (UTC - 5:00)
System Uptime: 0 days 0:18:17.194
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff801`30c43537 00000000`00000000 ffffffff`ffffffff
Probably caused by : memory_corruption

Code:

Debug session time: Sat Jun  9 10:39:34.155 2018 (UTC - 5:00)
System Uptime: 0 days 0:34:51.902
Bugcheck code 0000000A
Arguments 00000000`00000060 00000000`00000002 00000000`00000000 fffff802`b6bf008a
Probably caused by : memory_corruption

Code:

Debug session time: Sat Jun  9 09:41:21.692 2018 (UTC - 5:00)
System Uptime: 0 days 0:00:23.446
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff805`dbf1b570 ffff8104`7c43dec0 00000000`00000000
Probably caused by : memory_corruption