BSOD sporadic and usually playing games

BishieBishie · 11 Jul 2019

Hi guys

So I have been having sporadic blue screens and they are usually during game play. I play multiple different games, but what I have noticed is that Battlefield 5 or Planetside 2 will crash straight to desktop no error, then when I play another game, soon I may get a bluescreen. This happened daily for a while and I was quite anxious because my PC is important to me. So with some googling I did these things.

These problems only came about after recently updated to 1903

Memtest no errors
Reseated GPU and RAM
Checked cables
DDU and reinstalled graphics drivers
Checked drivers outdated and updated everything in device manager

I really hope you can help, thank you.

Attachment 239953

zbook · 11 Jul 2019

Hi BishieBishie ,

1) Only one of the mini dump files was able to be debugged.

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

3) The BSOD bugchecks were:
50
BE
1E

4) What is the age of the computer and which parts are under warranty?
5) Some RAM manufacturers offer lifetime warranties.
6) What is the name of the RAM manufacturer and are the RAM modules under warranty?
7) 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.)

8) Uninstall Driver Easy

Code:

Driver Easy 5.6.12                                             5.6.12         Easeware

9) Perform a system restore to a date before installing drivers with driver easy.
If there is no restore point or no working restore point then reinstall all drivers displayed on the motherboard website.
Another option that is sometimes needed is a clean install followed by installation of drivers from the motherboard website

10) Open administrative command prompt and type or copy and paste:
11) sfc /scannow
12) dism /online /cleanup-image /restorehealth
13) chkdsk /scan
14) wmic recoveros set autoreboot = false
15) wmic memorychip get manufacturer, capacity, partnumber, speed, memorytype, devicelocator, formfactor
16) bcdedit /enum all
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) Read these links on windows driver verifier: (do not use the tool until it is communicated in the thread)
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...9e4c983?auth=1

20) Open administrative powershell and copy and paste:

Code:

[Cmdletbinding()] 
Param( 
    [string]$Computername = "localhost" 
) 
cls 
$PysicalMemory = Get-WmiObject -class "win32_physicalmemory" -namespace "root\CIMV2" -ComputerName $Computername 
 
Write-Host "Memore Modules:" -ForegroundColor Green 
$PysicalMemory | Format-Table Tag,BankLabel,@{n="Capacity(GB)";e={$_.Capacity/1GB}},Manufacturer,PartNumber,Speed -AutoSize 
 
Write-Host "Total Memory:" -ForegroundColor Green 
Write-Host "$((($PysicalMemory).Capacity | Measure-Object -Sum).Sum/1GB)GB" 
 
$TotalSlots = ((Get-WmiObject -Class "win32_PhysicalMemoryArray" -namespace "root\CIMV2" -ComputerName $Computername).MemoryDevices | Measure-Object -Sum).Sum 
Write-Host "`nTotal Memory Slots:" -ForegroundColor Green 
Write-Host $TotalSlots 
 
$UsedSlots = (($PysicalMemory) | Measure-Object).Count  
Write-Host "`nUsed Memory Slots:" -ForegroundColor Green 
Write-Host $UsedSlots 
 
If($UsedSlots -eq $TotalSlots) 
{ 
    Write-Host "All memory slots are filled up, none is empty!" -ForegroundColor Yellow 
}

21) When these have completed > right click on the top bar or title bar of the administrative powershell 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

Code:

25/06/2019 20:31	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff8054333caa3
P4: 0
P5: ffffffffffffffff
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\062519-7750-01.dmp
\\?\C:\WINDOWS\TEMP\WER-12343-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CF9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D0A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D0B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D4A.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_b94ae113ba6a9c79b3c4452d8411b5691d456b8_00000000_cab_9b8b5a92-e36c-4514-b04b-3d79651d8c8d

Analysis symbol: 
Rechecking for solution: 0
Report Id: b8a7b4b0-ce07-4569-8a1b-f9ab573307b2
Report Status: 4
Hashed bucket: 
Cab Guid: 0
11/07/2019 23:21	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 50
P2: ffff8189dc0fb3ea
P3: 0
P4: fffff8023801cdeb
P5: 2
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\071219-7171-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10796-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER377B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER378B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER379A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER37CA.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_f1ff9bf9fe19397cf9f21689b5c91b79ff691ee0_00000000_cab_06241346-3ad9-4eca-856b-a8fdc01cd120

Analysis symbol: 
Rechecking for solution: 0
Report Id: 812c8b42-d47b-4e67-b4ab-7895f37ee300
Report Status: 4
Hashed bucket: 
Cab Guid: 0
25/06/2019 23:29	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 50
P2: ffffb3036c9ed080
P3: 0
P4: fffff80144e1a426
P5: 2
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\062619-7859-01.dmp
\\?\C:\WINDOWS\TEMP\WER-9531-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32F6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32F7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3316.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3355.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_19476e478e080553887f321f9838f894fa46c_00000000_cab_b8e38211-466f-4fd8-b517-b5135eedb720

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0d92429b-6799-4cc0-b39b-30a4f123ef4d
Report Status: 4
Hashed bucket: 
Cab Guid: 0
29/06/2019 21:45	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: be
P2: ffffa20c06a1d024
P3: 8a00000000200121
P4: ffff9d0fbb109670
P5: a
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\062919-8906-01.dmp
\\?\C:\WINDOWS\TEMP\WER-12640-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E12.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E13.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E22.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E42.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_be_b6eee575c5a821407aad4bdb4e1d3e3da1e64ff8_00000000_cab_a63a8378-6e67-469e-a9c9-f0af2b0bb75a

Analysis symbol: 
Rechecking for solution: 0
Report Id: abfbb110-fce5-4d94-b6a4-9e3ebc27cd05
Report Status: 4
Hashed bucket: 
Cab Guid: 0
25/06/2019 23:29	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 01c4b65d-ac1e-4c00-bfc0-413a0ae06355

Problem signature:
P1: 50
P2: ffffb3036c9ed080
P3: 0
P4: fffff80144e1a426
P5: 2
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\062619-7859-01.dmp
\\?\C:\WINDOWS\TEMP\WER-9531-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32F6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32F7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3316.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3355.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_19476e478e080553887f321f9838f894fa46c_00000000_cab_b8e38211-466f-4fd8-b517-b5135eedb720

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0d92429b-6799-4cc0-b39b-30a4f123ef4d
Report Status: 4
Hashed bucket: 
Cab Guid: 0
25/06/2019 20:32	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 8be5488a-3e8f-45d4-9047-c056e4b6876f

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff8054333caa3
P4: 0
P5: ffffffffffffffff
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\062519-7750-01.dmp
\\?\C:\WINDOWS\TEMP\WER-12343-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CF9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D0A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D0B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D4A.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_b94ae113ba6a9c79b3c4452d8411b5691d456b8_00000000_cab_9b8b5a92-e36c-4514-b04b-3d79651d8c8d

Analysis symbol: 
Rechecking for solution: 0
Report Id: b8a7b4b0-ce07-4569-8a1b-f9ab573307b2
Report Status: 4
Hashed bucket: 
Cab Guid: 0
29/06/2019 21:46	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: dcf5e280-a08d-43cc-ba4b-4aa5d81e943f

Problem signature:
P1: be
P2: ffffa20c06a1d024
P3: 8a00000000200121
P4: ffff9d0fbb109670
P5: a
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\062919-8906-01.dmp
\\?\C:\WINDOWS\TEMP\WER-12640-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E12.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E13.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E22.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E42.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_be_b6eee575c5a821407aad4bdb4e1d3e3da1e64ff8_00000000_cab_a63a8378-6e67-469e-a9c9-f0af2b0bb75a

Analysis symbol: 
Rechecking for solution: 0
Report Id: abfbb110-fce5-4d94-b6a4-9e3ebc27cd05
Report Status: 4
Hashed bucket: 
Cab Guid: 0
11/07/2019 23:22	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: e5883a15-dcda-42e2-95fd-afe641d05b60

Problem signature:
P1: 50
P2: ffff8189dc0fb3ea
P3: 0
P4: fffff8023801cdeb
P5: 2
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\071219-7171-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10796-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER377B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER378B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER379A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER37CA.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_f1ff9bf9fe19397cf9f21689b5c91b79ff691ee0_00000000_cab_06241346-3ad9-4eca-856b-a8fdc01cd120

Analysis symbol: 
Rechecking for solution: 0
Report Id: 812c8b42-d47b-4e67-b4ab-7895f37ee300
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

25/06/2019 20:43	Windows Error Reporting	Fault bucket 0x1E_c0000005_R_dxgmms2!VidSchiProfilePerformanceTick, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 8be5488a-3e8f-45d4-9047-c056e4b6876f

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff8054333caa3
P4: 0
P5: ffffffffffffffff
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\062519-7750-01.dmp
\\?\C:\WINDOWS\TEMP\WER-12343-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CF9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D0A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D0B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D4A.tmp.txt
\\?\C:\Windows\Temp\WER3161.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_b94ae113ba6a9c79b3c4452d8411b5691d456b8_00000000_cab_9b8b5a92-e36c-4514-b04b-3d79651d8c8d

Analysis symbol: 
Rechecking for solution: 0
Report Id: b8a7b4b0-ce07-4569-8a1b-f9ab573307b2
Report Status: 268435460
Hashed bucket: 
Cab Guid: 0

Code:

25/06/2019 23:32	Windows Error Reporting	Fault bucket AV_R_INVALID_nt!PsLookupThreadByThreadId, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 01c4b65d-ac1e-4c00-bfc0-413a0ae06355

Problem signature:
P1: 50
P2: ffffb3036c9ed080
P3: 0
P4: fffff80144e1a426
P5: 2
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\062619-7859-01.dmp
\\?\C:\WINDOWS\TEMP\WER-9531-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32F6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32F7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3316.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3355.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_19476e478e080553887f321f9838f894fa46c_00000000_cab_b8e38211-466f-4fd8-b517-b5135eedb720

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0d92429b-6799-4cc0-b39b-30a4f123ef4d
Report Status: 268435460
Hashed bucket: 
Cab Guid: 0
11/07/2019 23:33	Windows Error Reporting	Fault bucket AV_R_INVALID_win32kbase!EtwTraceMessageCheckDelay, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: e5883a15-dcda-42e2-95fd-afe641d05b60

Problem signature:
P1: 50
P2: ffff8189dc0fb3ea
P3: 0
P4: fffff8023801cdeb
P5: 2
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\071219-7171-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10796-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER377B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER378B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER379A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER37CA.tmp.txt
\\?\C:\Windows\Temp\WERE13F.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_f1ff9bf9fe19397cf9f21689b5c91b79ff691ee0_00000000_cab_06241346-3ad9-4eca-856b-a8fdc01cd120

Analysis symbol: 
Rechecking for solution: 0
Report Id: 812c8b42-d47b-4e67-b4ab-7895f37ee300
Report Status: 268435460
Hashed bucket: 
Cab Guid: 0
29/06/2019 21:49	Windows Error Reporting	Fault bucket PAGE_NOT_ZERO_0xBE, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: dcf5e280-a08d-43cc-ba4b-4aa5d81e943f

Problem signature:
P1: be
P2: ffffa20c06a1d024
P3: 8a00000000200121
P4: ffff9d0fbb109670
P5: a
P6: 10_0_18362
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\062919-8906-01.dmp
\\?\C:\WINDOWS\TEMP\WER-12640-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E12.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E13.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E22.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E42.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_be_b6eee575c5a821407aad4bdb4e1d3e3da1e64ff8_00000000_cab_a63a8378-6e67-469e-a9c9-f0af2b0bb75a

Analysis symbol: 
Rechecking for solution: 0
Report Id: abfbb110-fce5-4d94-b6a4-9e3ebc27cd05
Report Status: 268435460
Hashed bucket: 
Cab Guid: 0

BishieBishie · 12 Jul 2019

Hi zbook thanks for helping

Here is the link to the memory dump: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

The computer was built in November, all parts apart from storage are new and under warranty, including the trident z F4-3200C14D-16GTZSW. The storage is about 4 years old. Samsung 860 evo and a mechanical WD black drive 1tb.

Easy driver did not install any drivers, any updates I have done was through the device manager, I only used it to see if it picked up anything out of date, it is now uninstalled, but I do not have a restore point before it's installation.

Code:

Microsoft Windows [Version 10.0.18362.239]
(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 /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

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

C:\WINDOWS\system32>chkdsk /scaMicrosoft Windows [Version 10.0.18362.239]
Invalid parameter - /scaMicrosoft

C:\WINDOWS\system32>(c) 2019 Microsoft Corporation. All rights reserved.
2019 was unexpected at this time.

C:\WINDOWS\system32>
C:\WINDOWS\system32>C:\WINDOWS\system32>sfc /scannow
'C:\WINDOWS\system32' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>
C:\WINDOWS\system32>Beginning system scan.  This process will take some time.
'Beginning' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>
C:\WINDOWS\system32>Beginning verification phase of system scan.
'Beginning' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>Verification 100% complete.
'Verification' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>
C:\WINDOWS\system32>Windows Resource Protection found corrupt files but was unable to fix some of them.
'Windows' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>For online repairs, details are included in the CBS log file located at
online was unexpected at this time.

C:\WINDOWS\system32>windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
The system cannot find the path specified.

C:\WINDOWS\system32>repairs, details are included in the log file provided by the /OFFLOGFILE flag.
'repairs' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>
C:\WINDOWS\system32>C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Access is denied.

C:\WINDOWS\system32>
C:\WINDOWS\system32>Deployment Image Servicing and Management tool
'Deployment' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>Version: 10.0.18362.1
'Version:' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>
C:\WINDOWS\system32>Image Version: 10.0.18362.239
'Image' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>
C:\WINDOWS\system32>[==========================100.0%==========================]
'[' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

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

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

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

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

 487755775 KB total disk space.
 250860252 KB in 244214 files.
    163368 KB in 55365 indexes.
         0 KB in bad sectors.
    697923 KB in use by the system.
     65536 KB occupied by the log file.
 236034232 KB available on disk.

      4096 bytes in each allocation unit.
 121938943 total allocation units on disk.
  59008558 allocation units available on disk.

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

C:\WINDOWS\system32>wmic memorychip get manufacturer, capacity, partnumber, speed, memorytype, devicelocator, formfactor
Capacity    DeviceLocator  FormFactor  Manufacturer  MemoryType  PartNumber         Speed
8589934592  DIMM 1         8           Unknown       0           F4-3200C14-8GTZSW  3200
8589934592  DIMM 1         8           Unknown       0           F4-3200C14-8GTZSW  3200


C:\WINDOWS\system32>bcdedit /enum all

Firmware Boot Manager
---------------------
identifier              {fwbootmgr}
displayorder            {bootmgr}
                        {f0ec1f1f-eb8a-11e8-9df1-8315ba22680f}
timeout                 1

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager
locale                  en-GB
inherit                 {globalsettings}
default                 {current}
resumeobject            {f3ee345e-8e19-11e9-830b-d4f588903966}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Firmware Application (101fffff)
-------------------------------
identifier              {f0ec1f1f-eb8a-11e8-9df1-8315ba22680f}
description             Hard Drive

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-GB
inherit                 {bootloadersettings}
recoverysequence        {f3ee3460-8e19-11e9-830b-d4f588903966}
displaymessageoverride  CommandPrompt
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {f3ee345e-8e19-11e9-830b-d4f588903966}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {f3ee3460-8e19-11e9-830b-d4f588903966}
device                  ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{f3ee3461-8e19-11e9-830b-d4f588903966}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-GB
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{f3ee3461-8e19-11e9-830b-d4f588903966}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {f3ee345e-8e19-11e9-830b-d4f588903966}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  en-GB
inherit                 {resumeloadersettings}
recoverysequence        {f3ee3460-8e19-11e9-830b-d4f588903966}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  en-GB
inherit                 {globalsettings}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {emssettings}
bootems                 No

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Local

RAM Defects
-----------
identifier              {badmemory}
badmemorylist           0x214c11
                        0x38fad8

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

Device options
--------------
identifier              {f3ee3461-8e19-11e9-830b-d4f588903966}
description             Windows Recovery
ramdisksdidevice        partition=\Device\HarddiskVolume1
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

Code:

Memore Modules:

Tag               BankLabel    Capacity(GB) Manufacturer PartNumber        Speed
---               ---------    ------------ ------------ ----------        -----
Physical Memory 1 P0 CHANNEL A            8 Unknown      F4-3200C14-8GTZSW  3200
Physical Memory 3 P0 CHANNEL B            8 Unknown      F4-3200C14-8GTZSW  3200


Total Memory:
16GB

Total Memory Slots:
4

Used Memory Slots:
2

I did have my CPU slightly undervolted but I have reversed that to stock now. I also deactivated Voicemeter banana, as that was another programme installed around the time of the first crash. Maybe with the headsets drivers and voicemeter there could be a incompatibility there?

I will also go check my mobo page for any drivers

Thanks again! Bishie.

zbook · 12 Jul 2019

The logs displayed that Windows had found bad memory and blocked those areas on the RAM modules.

This was confirmed by the administrative command prompt commands.

Please contact the manufacturer for a Return Merchandise Authorization (RMA).

BishieBishie · 12 Jul 2019

Thank you. If you don't mind me asking, what are the chances if I go for the same ram, they also end up with issues?

zbook · 12 Jul 2019

Code:

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

1) Open administrative command prompt and type or copy and paste:
2) dism /online /cleanup-image /restorehealth
3) sfc /scannow
4) 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

5) Malfunctioning hardware should be ruled in / ruled out whenever possible.

6) If the replacement is good then other problems can be troubleshooted.

Code:

Event[5036]:
  Log Name: System
  Source: Microsoft-Windows-Memory-Diagnostic-Task-Handler
  Date: 2019-06-29T03:35:14.060
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-2464162272-4256741442-386707367-1001
  User Name: DESKTOP-KG15NIE\tucke
  Computer: DESKTOP-KG15NIE
  Description: 
Windows removed bad memory regions from this PC.

Code:

RAM Defects
-----------
identifier              {badmemory}
badmemorylist           0x214c11
                        0x38fad8

BishieBishie · 12 Jul 2019

Is it possible XMP is to blame? X470 Taichi doesn't have my ram listed on quality vendor list, though Gskill advertise as being compatible. None XMP speeds for the Taichi board don't go over 2933

zbook · 12 Jul 2019

RAM modules should be on the Qualified Vendor List (QVL).

Otherwise there may be unexpected problems.

BishieBishie · 13 Jul 2019

I went for the same ram but different colour. They are listed on QVL for mobo but not the exact model. The ram maker has my mobo on their QVL however. So we shall see in a few days. Will keep you posted if I get more crashes.

BishieBishie · 28 Aug 2019

So I thought I would give an update a few month on as to what has happened.

New RAM came and I changed it out, then my PC would not boot. So I panicked and as it seemed beyond me called a repair guy. He came and tried a few things then took it away. He called me day later and said it was repaired and he had fixed something related to power control to memory, installed the new RAM and since it has worked fine. No BSOD, few game crashes in Watch Dogs 2 that seem Nvidia driver related, the game seemed to cause the driver to stop. Now I am pretty sure he was legit, but I keep thinking maybe I messed something up and his fix was not an actual fix. It hasn't bothered me as the PC is working pretty decent, until today.

Shadow of the tomb raider crashed with an exception code of 0xc0000005. It has only done this once, but in event viewer there is a few apps crashing over the last month with this code. This something to worry about or just an isolated issue do you think?

Thanks again for your earlier help.