1) The computer has been having BSOD.
2) The V2 log collector collected BSOD from 3/14 to 8/31.
3) All bugchecks were 139:
KERNEL_SECURITY_CHECK_FAILURE
Code:
Operating System: Windows 10 Pro 64-bit (10.0, Build 14393) (14393.rs1_release_1.180402-1758)
Code:
Installed Physical Memory (RAM) 128 GB
4) For all steps / tests post images into the thread.
5) If there are any problems posting images use share links (One drive, Drop box Google drive, or Amazon).
6) All modifications, software and hardware can be modified after troubleshooting has been completed.
7) The computer has 8 RAM modules that are 16 GB each.
Remove all RAM modules.
Label all modules and DIMM.
Re-seat two modules.
If the owners manual has a recommended DIMM when two modules are used please use these slots.
8) Open administrative command prompt and type or copy and paste:
9) sfc /scannow
10) dism /online /cleanup-image /scanhealth
11) dism /online /cleanup-image /restorehealth
12) sfc /scannow
13) chkdsk /scan
14) wmic recoveros set autoreboot = false
15) wmic recoveros set DebugInfoType = 7
16) bcdedit /enum {badmemory}
17) 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
18) Make sure that there is no over clocking while troubleshooting.
19) Sometimes there are problems in the bios that produce bsod.
20) The BIOS: Version/Date American Megatrends Inc. 1003, 9/13/2016
Upgrade the BIOS: 1003 > 1903
This should be the most up to date non-beta BIOS
Code:
Improve system performance
Improved DRAM stability
Fix Logitech devices issue.
Fix Intel I211 Lan issue*
Fixed memtest86 issue
Fixed Plextor device issue
Improve system performance
Add in turn-off function of LED under S3/S4/S5 status.
Fixed Samsung device (SM961, printer) issues.
Improve system stability
ROG RAMPAGE V EDITION 10 Driver & Tools | Motherboards | ASUS USA
21) To ensure that there are no improper bios settings please reset the bios.
22) Sometimes there can be failure to boot after resetting the bios.
23) Backup the computer files to another drive or to the cloud.
24) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free
25) Create a brand new restore point.
Create System Restore Point in Windows 10
How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computer’s CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
26) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread
b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread
27) Read this link on Windows driver verifier: (do not use the tool until it is communicated in the thread)
Enable and Disable Driver Verifier in Windows 10
28) Learn how to use the Windows advanced troubleshooting menu to turn off and recover from using the tool.
29) For any BSOD:
a) run the V2 log collector to collect new log files
b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive
30) Run setupdiag > post a share link into the thread
31) List and uninstall all non-Microsoft antivirus software
(This includes always on and manual software.)
(This includes running the applicable antivirus uninstall tools for any AV that could have been incompletely unistalled)
32) List and uninstall all non-Microsoft firewall software
33) List all Microsoft and non-Microsoft drive encryption software.
Uninstall all non-Microsoft disk encryption software
34) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.
C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
Type: Y
reboot
35) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10
36) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of
37) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10
Code:
8/31/2019 12:28 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffff868189718ec0
P4: ffff868189718e18
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\083119-13312-01.dmp
\\?\C:\Windows\TEMP\WER-15328-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_1bd1463518e34089fbe377c87355e85305993_00000000_cab_128c7975

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0d11362a-04be-461f-b685-89cdf064eca5
Report Status: 2048
Hashed bucket:
8/31/2019 12:28 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffff868189718ec0
P4: ffff868189718e18
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\083119-13312-01.dmp
\\?\C:\Windows\TEMP\WER-15328-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_1bd1463518e34089fbe377c87355e85305993_00000000_03dc48d0

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0d11362a-04be-461f-b685-89cdf064eca5
Report Status: 4
Hashed bucket:
8/29/2019 12:36 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffff8a816e0aaec0
P4: ffff8a816e0aae18
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\082919-13406-01.dmp
\\?\C:\Windows\TEMP\WER-20078-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_93bc744d8af15f59b0d381f5dd3476df56c25d9c_00000000_cab_14587445

Analysis symbol: 
Rechecking for solution: 0
Report Id: 8b2d843a-2480-4e2e-98db-2344986a6335
Report Status: 2048
Hashed bucket:
8/29/2019 12:35 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffff8a816e0aaec0
P4: ffff8a816e0aae18
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\082919-13406-01.dmp
\\?\C:\Windows\TEMP\WER-20078-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_93bc744d8af15f59b0d381f5dd3476df56c25d9c_00000000_03dc5b9d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 8b2d843a-2480-4e2e-98db-2344986a6335
Report Status: 4
Hashed bucket:
3/13/2019 12:21 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffffb0001ed7aec0
P4: ffffb0001ed7ae18
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\031319-16000-01.dmp
\\?\C:\Windows\TEMP\WER-18109-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_999a4d753fa6d387632abe4214dd2f2e1ddeab20_00000000_cab_14d08220

Analysis symbol: 
Rechecking for solution: 0
Report Id: 43be3051-1f2b-433f-99aa-4c35243bebc9
Report Status: 2048
Hashed bucket:
3/13/2019 12:20 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffffb0001ed7aec0
P4: ffffb0001ed7ae18
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\031319-16000-01.dmp
\\?\C:\Windows\TEMP\WER-18109-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_999a4d753fa6d387632abe4214dd2f2e1ddeab20_00000000_03385330

Analysis symbol: 
Rechecking for solution: 0
Report Id: 43be3051-1f2b-433f-99aa-4c35243bebc9
Report Status: 4
Hashed bucket:
3/14/2019 12:01 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffffb5000e36b320
P4: ffffb5000e36b278
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\031419-15484-01.dmp
\\?\C:\Windows\TEMP\WER-17484-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_29c475b222e743e6a73c22e2e67b7ec99adbbc8c_00000000_cab_15287937

Analysis symbol: 
Rechecking for solution: 0
Report Id: 7dc353b2-3414-4726-9155-75b3d09181f8
Report Status: 2048
Hashed bucket:
3/14/2019 12:01 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffffb5000e36b320
P4: ffffb5000e36b278
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\031419-15484-01.dmp
\\?\C:\Windows\TEMP\WER-17484-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_29c475b222e743e6a73c22e2e67b7ec99adbbc8c_00000000_03445023

Analysis symbol: 
Rechecking for solution: 0
Report Id: 7dc353b2-3414-4726-9155-75b3d09181f8
Report Status: 4
Hashed bucket:
7/4/2019 6:17 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffffb800153abdb0
P4: ffffb800153abd08
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\070419-25750-01.dmp
\\?\C:\Windows\TEMP\WER-27796-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_be9c04102e3bd54df8057737c1fe76dbea439_00000000_cab_169888e6

Analysis symbol: 
Rechecking for solution: 0
Report Id: 89dfbe5b-3855-43e2-809a-091e826e3c86
Report Status: 2048
Hashed bucket:
7/4/2019 6:17 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffffb800153abdb0
P4: ffffb800153abd08
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\070419-25750-01.dmp
\\?\C:\Windows\TEMP\WER-27796-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_be9c04102e3bd54df8057737c1fe76dbea439_00000000_02807927

Analysis symbol: 
Rechecking for solution: 0
Report Id: 89dfbe5b-3855-43e2-809a-091e826e3c86
Report Status: 4
Hashed bucket:
5/19/2019 7:01 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffffcd81e4e05ec0
P4: ffffcd81e4e05e18
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\051919-18062-01.dmp
\\?\C:\Windows\TEMP\WER-20125-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_23e1261f10bf8bbedafd74e2d5599761d27bdba_00000000_cab_15cc7a8f

Analysis symbol: 
Rechecking for solution: 0
Report Id: d14526fa-42b8-4df6-a8bc-b454be8e8a42
Report Status: 2048
Hashed bucket:
5/19/2019 7:01 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffffcd81e4e05ec0
P4: ffffcd81e4e05e18
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\051919-18062-01.dmp
\\?\C:\Windows\TEMP\WER-20125-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_23e1261f10bf8bbedafd74e2d5599761d27bdba_00000000_02785d14

Analysis symbol: 
Rechecking for solution: 0
Report Id: d14526fa-42b8-4df6-a8bc-b454be8e8a42
Report Status: 4
Hashed bucket:
Code:
Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1803.
Installation Failure: Windows failed to install the following update with error 0x8007001F: Feature update to Windows 10, version 1803.
Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1803.
Installation Failure: Windows failed to install the following update with error 0x8007001F: Feature update to Windows 10, version 1803.
Code:
Windows failed fast startup with error status 0xC00000D4.
Code:
The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.