New Build - Multiple BSODs

Hello,

A friend of mine recently built a PC (August 2019) from scratch. He has had problems with it since he built it. He asked for my assistance, so it is currently sitting here on my desk, half-together..

Problems: Multiple BSODs - cant run for more than an hour without it crashing.

Actions I have taken:
I have updated the BIOS to the most recent version.

Ensured that all drivers are up-to-date based on the Motherboard Manufacturer's website

Switched out the video card with a known working video card - system still crashes

Identified that memory he installed was not on the motherboard manufacturers QVL list, so we replaced the memory with memory that is on the QVL list

Since the issues persisted even after swapping out ram and graphics card, we thought the Motherboard was at fault, so I RMA'd the motherboard, received the replacement motherboard last week, and still, the issues persist.

I download the Windows debugging tool and tried to debug following the tutorial here, but I just don't have the knowledge to figure out what is going on, and would really appreciate the help of anyone willing to take a look.

Computer specs are:
Windows VS. 1903 OS Build 18362.356
AMD Ryzen 5 3600
ASROCK X570 Phantom Gaming 4 (replaced under RMA - Bios flashed to 2.03)
16GB (Currently only one stick installed, so 8 GB) memory (Crucial Technology)
EVGA RTX 2060 Super Graphics Card
Kingston 480 GB SSD

Attaching the Zip File here. Thank you in advance to anyone willing to help - please feel free to ask any questions you may have.

Update:
BIOS - ASRock > X570 Phantom Gaming 4

Please post a share link for C:\windows\memory.dmp (one drive, drop box, or google drive)

Code:

Crash dump found at C:\Windows\MEMORY.DMP
Creation date: 10/19/2019 16:00:37
Size on disk: 588 MB

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) bcdedit /enum {badmemory}

10) 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

11) Make sure that there is no over clocking while troubleshooting.

12) Turn off Windows fast startup:

Turn On or Off Fast Startup in Windows 10

13) Update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

14) 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

15) 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

Thanks to all for your responses - much appreciated. I thought I had been thorough in my explanation, but clearly I fell short on a couple things:

1) Power Supply: We first suspected power supply was the issue, so we replaced the power supply with a known working supply out of one of my builds, but the issue persisted. Originally, the computer had a Corsair 650W Gold power supply. We replaced it with an 8 year old Seasonic 750W Gold unit that came out of a know working rig, and had the same issue. It has now been reverted back to the original Corsair 650W Gold Power Supply.

2) Case: Case is a brand new corsair case - I am sorry, I don't have the model #..

3) CPU Cooler: It is using a coolermaster AIO liquid-cooler - the model with two fans. CPU temps are running ~35' at idle. While running games, CPU temp goes up to mid 40s. Running Prime95 for a period of 2 hours, the CPU temp did hit a max of 81.6', but it has never come anywhere close to that temp in real-life experience.

4:Other attached peripherals: A Corsair Gaming Mouse and a Corsair K68 Mechanical Keyboard. (Sorry, the mouse doesn't have model # listed on it, so not sure on that one..) Monitor is an old dell 22" monitor I had sitting around.

The Bios was an an older version previously, but point well taken that 2.03 is a beta bios. As such, this morning I reverted back 2.0, the latest non-beta version off asrock's website.

It is still getting BSODs and random reboots.

I just did a search for the memory.dmp file, and it appears that it was written back in October, so it looks like I need to go in and enable the system to write memory dumps - I guess I didn't do that after the latest windows reinstall. I will enable that feature, and will attach any new dump file to this post (or a link if too large).

Following the instructions posted by Zbook, below are the results from the command-line actions - it does appear that there may be some corrupt files, but I am not sure, and welcome more knowledgeable analysis.

Next Steps: I will update my system specs. Also, will attach the most recent v2 collector log. Thanks again, to everyone, for your help. Much appreciated.

Microsoft Windows [Version 10.0.18362.356]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>DISM /ONLINE/CLEANUP-IMAGE/SCANHEALTH

Deployment Image Servicing and Management tool
Version: 10.0.18362.1


Error: 87

The online/cleanup-image/scanhealth option is unknown.
For more information, refer to the help by running DISM.exe /?.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>DISM /ONLINE /CLEANUP-IMAGE /SCANHEALTH

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.356

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\Windows\system32>DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.356

[===========================89.5%=================== ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>SFC /SCANNOW

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>CHKDSK /SCAN
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
246784 file records processed.
File verification completed.
4405 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
192 reparse records processed.
306500 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
192 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
29859 data files processed.
CHKDSK is verifying Usn Journal...
41514512 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

468190207 KB total disk space.
79244328 KB in 109408 files.
75128 KB in 29860 indexes.
0 KB in bad sectors.
371151 KB in use by the system.
65536 KB occupied by the log file.
388499600 KB available on disk.

4096 bytes in each allocation unit.
117047551 total allocation units on disk.
97124900 allocation units available on disk.

C:\Windows\system32>WMIC RECOVEROS SET AUTOREBOOT = FALSE
Updating property(s) of '\\DESKTOP-6JCQ00G\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\Windows\system32>WMIC recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-6JCQ00G\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\Windows\system32>

Code:

Windows Resource Protection found corrupt files but was unable to fix some of them.

Find a flash drive that you can formt (> or = 8 GB)

Create a bootable Windows 10 iso:

https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10


Perform an in place upgrade repair using the Windows 10 iso:

Repair Install Windows 10 with an In-place Upgrade


The last dump file was 10/19.
The last BSOD was 11/30.

Thank you. I just realized that you had asked for a link to that October memory dump. Here is a link to the file on Google Drive:

MEMORY.DMP - Google Drive

Based on your above recommendation, I created a bootable USB and went through the Windows repair process, then re-ran the command-line options, with the below results, which appear to indicate to me, at least, that the Windows file corruption issues are corrected. I am going to test today to see if I still get the BSODs when attempting to play a game.

Thank you again for your help. If this corrects the problem, I will come back and delete my attachments, etc, and let you know.



Microsoft Windows [Version 10.0.18363.476]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /Scannow

Beginning 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 /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.476

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.476

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning 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>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
301312 file records processed.
File verification completed.
6077 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
243 reparse records processed.
410894 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
243 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
54792 data files processed.
CHKDSK is verifying Usn Journal...
37771520 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

468190207 KB total disk space.
104633492 KB in 178075 files.
134464 KB in 54793 indexes.
0 KB in bad sectors.
422247 KB in use by the system.
65536 KB occupied by the log file.
363000004 KB available on disk.

4096 bytes in each allocation unit.
117047551 total allocation units on disk.
90750001 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = fALSE
Updating property(s) of '\\DESKTOP-6JCQ00G\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\WINDOWS\system32>WMIC RECOVEROS SET DEBUGINFOTYPE = 7
Updating property(s) of '\\DESKTOP-6JCQ00G\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\WINDOWS\system32>BCDEDIT /ENUM {BADMEMORY}

RAM Defects
-----------
identifier {badmemory}

C:\WINDOWS\system32>

Test your CPU with CPUSTRES - https://docs.microsoft.com/en-us/sys...loads/cpustres
1. Run CPUSTRES.exe.

2. The activity level of thread 1 is Low. Change it to Maximum.

3. The thread priority of thread 1 is Normal. Change it to Lowest.

4. Click thread 2. Its activity level is Low. Change it to Maximum.

5. Change the process affinity mask to a single logical processor. To do
so, open the Process menu and choose Affinity. (It doesn’t matter
which processor.) Alternatively, use Task Manager to make the
change.

Ran CPUStres following the instructions above, on Core 0. After less than 5 minutes, I received the dreaded BSOD. Currently uploading memory.dmp to Google Drive, but since it is 8gp (full dump), it shows that it is going to take 2 hours to upload. (Didn't realize my upload bandwidth was so slim!)

I will share once that upload is complete. In the meantime, here is the v2collector log that I also just ran.

Thanks again for the help!Attachment 257454

Run Memtest86 version 8.2 (or newer version if available) for four passes.
Repeat the test so that eight passes are performed.
MemTest86 - Official Site of the x86 Memory Testing Tool
Use a camera or smart phone camera to take pictures and post images into the thread.
In case there are any problems uploading images use share links (one drive, drop box, or google drive)
Memtest86 has a feature to produce a text report.
Please post this in addition to the images.

Run the scannow and restorehealth commands and post new results into the thread.