Random Immediate Reboot no BSOD

This thread has been open over 4 months.
The logs displayed recent BSOD.
The settings were not maintained.
There were no dump files.
There was a recent three week gap.

How come the settings were not maintained?

Were the steps in post #45 completed?
Please post images into the thread.

zbook said:

How come the settings were not maintained?

Which settings?

zbook said:

Were the steps in post #45 completed?

Is that necessary given I've replaced the RAM?

1) How come system failure was changed to complete memory dump?
2) How come automatically restart was checked?
3) How come the RAM is overclocked?

Ryzen 5 3600 System Memory Specification 3200MHz
RAM Speed: 3600

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

c) make sure C: is highlighted

5) Open administrative command prompt and type or copy and paste:
6) sfc /scannow
7) dism /online /cleanup-image /scanhealth
8) dism /online /cleanup-image /restorehealth
9) sfc /scannow
10) chkdsk /scan
11) wmic recoveros set autoreboot = false
12) wmic recoveros set DebugInfoType = 7
13) wmic recoveros get autoreboot
14) wmic recoveros get DebugInfoType
15) bcdedit /enum {badmemory}

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

17) Make sure that there is no over clocking while troubleshooting


18) Once the RAM is < or = 3600 test the RAM overnight:

Run Memtest86 version 8.3 (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.


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

Code:

22/04/2020 08:12 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 3b
P2: c0000005
P3: fffff80702912210
P4: ffff948811e6e360
P5: 0
P6: 10_0_18363
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042220-11828-01.dmp
\\?\C:\Windows\TEMP\WER-17546-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58FD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58FE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58FF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER590F.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_5e1a6b95f819615979107ab8a636764a23dcd49a_00000000_cab_d2e968f0-bd62-49ae-89ab-3b881d7a8833

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9f2e1c12-40bc-4da1-9144-78fb6754e74c
Report Status: 4
Hashed bucket: 
Cab Guid: 0
22/04/2020 08:16 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 3d
P2: ffffa4019affbce8
P3: ffffa4019affb530
P4: 0
P5: 0
P6: 10_0_18363
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042220-10984-01.dmp
\\?\C:\Windows\TEMP\WER-15031-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AC4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AD5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AD6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AE6.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3d_da853b3251dddfcdb2497b9df4e7b6da49bf35a2_00000000_cab_07049f4a-91fa-423d-b612-ffd88d99ed42

Analysis symbol: 
Rechecking for solution: 0
Report Id: da8a2173-3e81-40d5-bc71-a60059507185
Report Status: 4
Hashed bucket: 
Cab Guid: 0
18/04/2020 05:59 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 50
P2: ffff8b88157d9080
P3: 11
P4: ffff8b88157d9080
P5: 2
P6: 10_0_18363
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\041820-10968-01.dmp
\\?\C:\Windows\TEMP\WER-21078-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69A6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69A7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69AA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69BB.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_7db3a46eae23c670d2ab896c4b52833efa30dde3_00000000_cab_6a1b2904-7fc3-45fe-b6e0-0f8fe2cdf222

Analysis symbol: 
Rechecking for solution: 0
Report Id: 49faae31-51c3-4810-8317-5149079bd066
Report Status: 4
Hashed bucket: 
Cab Guid: 0
18/04/2020 08:50 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: 0
P3: 2
P4: 0
P5: fffff801056953d4
P6: 10_0_18363
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\041820-10796-01.dmp
\\?\C:\Windows\TEMP\WER-14781-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5573.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5574.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5577.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5587.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_af35e938c2d59a74345aab49c15543a7f36fd_00000000_cab_9758e9dc-a29d-459b-be33-859b0de22d84

Analysis symbol: 
Rechecking for solution: 0
Report Id: f02086ec-386e-47c4-9ff5-b655bac11bef
Report Status: 4
Hashed bucket: 
Cab Guid: 0
20/04/2020 07:07 PM	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: f7
P2: ccf7257dfc6e
P3: ccf7257dfc6e
P4: ffff3308da820391
P5: 0
P6: 10_0_18363
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042020-10734-01.dmp
\\?\C:\Windows\TEMP\WER-14562-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49BB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49CB.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49CA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49DB.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_f7_a53754a7c7c8cccd12b4bc74531f9a9de181f_00000000_cab_770b8c53-9d2d-4ffd-b669-59b7c9f4abd3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3828953f-cb7f-4f58-b2a3-43a8ba07b208
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

22/04/2020 08:12 PM	Windows Error Reporting	Fault bucket 0x3B_c0000005_win32kbase!GdiHandleEntryDirectory::ReleaseEntryLock, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 6af71200-d94c-4c52-ac6f-7c0571685365

Problem signature:
P1: 3b
P2: c0000005
P3: fffff80702912210
P4: ffff948811e6e360
P5: 0
P6: 10_0_18363
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042220-11828-01.dmp
\\?\C:\Windows\TEMP\WER-17546-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58FD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58FE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58FF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER590F.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_5e1a6b95f819615979107ab8a636764a23dcd49a_00000000_cab_d2e968f0-bd62-49ae-89ab-3b881d7a8833

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9f2e1c12-40bc-4da1-9144-78fb6754e74c
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
22/04/2020 08:17 PM	Windows Error Reporting	Fault bucket 0x3D_nt!KiInterruptHandler, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 5c7b5fd7-5c42-40ca-aade-0c6c3cc9c3fc

Problem signature:
P1: 3d
P2: ffffa4019affbce8
P3: ffffa4019affb530
P4: 0
P5: 0
P6: 10_0_18363
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042220-10984-01.dmp
\\?\C:\Windows\TEMP\WER-15031-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AC4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AD5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AD6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AE6.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3d_da853b3251dddfcdb2497b9df4e7b6da49bf35a2_00000000_cab_07049f4a-91fa-423d-b612-ffd88d99ed42

Analysis symbol: 
Rechecking for solution: 0
Report Id: da8a2173-3e81-40d5-bc71-a60059507185
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
20/04/2020 07:12 PM	Windows Error Reporting	Fault bucket 0xF7_ONE_BIT_nt!PerfInfoLogSysCallExit, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 6fefeb90-489d-41d5-b74c-6b1c32d6604e

Problem signature:
P1: f7
P2: ccf7257dfc6e
P3: ccf7257dfc6e
P4: ffff3308da820391
P5: 0
P6: 10_0_18363
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042020-10734-01.dmp
\\?\C:\Windows\TEMP\WER-14562-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49BB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49CB.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49CA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49DB.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_f7_a53754a7c7c8cccd12b4bc74531f9a9de181f_00000000_cab_770b8c53-9d2d-4ffd-b669-59b7c9f4abd3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3828953f-cb7f-4f58-b2a3-43a8ba07b208
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0

Code:

18/04/2020 05:59 PM	Windows Error Reporting	Fault bucket AV_INVALID_ANALYSIS_INCONCLUSIVE!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: a8f9f0d9-de78-48c2-be23-a10d4cb61e01

Problem signature:
P1: 50
P2: ffff8b88157d9080
P3: 11
P4: ffff8b88157d9080
P5: 2
P6: 10_0_18363
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\041820-10968-01.dmp
\\?\C:\Windows\TEMP\WER-21078-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69A6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69A7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69AA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69BB.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_7db3a46eae23c670d2ab896c4b52833efa30dde3_00000000_cab_6a1b2904-7fc3-45fe-b6e0-0f8fe2cdf222

Analysis symbol: 
Rechecking for solution: 0
Report Id: 49faae31-51c3-4810-8317-5149079bd066
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
18/04/2020 08:50 PM	Windows Error Reporting	Fault bucket AV_nt!MiIncrementSubsectionViewCount, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 6504f94c-f24a-4089-b7b3-acc5493cfa97

Problem signature:
P1: a
P2: 0
P3: 2
P4: 0
P5: fffff801056953d4
P6: 10_0_18363
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\041820-10796-01.dmp
\\?\C:\Windows\TEMP\WER-14781-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5573.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5574.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5577.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5587.tmp.txt
\\?\C:\Windows\Temp\WER8DAA.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_af35e938c2d59a74345aab49c15543a7f36fd_00000000_cab_9758e9dc-a29d-459b-be33-859b0de22d84

Analysis symbol: 
Rechecking for solution: 0
Report Id: f02086ec-386e-47c4-9ff5-b655bac11bef
Report Status: 2147483648
Hashed bucket: 
Cab Guid: 0

zbook said:

1) How come system failure was changed to complete memory dump?
2) How come automatically restart was checked?
3) How come the RAM is overclocked?

I didn't change those settings, I reinstalled Windows. The RAM is running at XMP values. The only thing technically overclocked here is the infinity fabric, because only up to 3200MHz is officially supported. I can disable XMP but with the previous RAM it made no difference.

Attachment 276154

Code:

Microsoft Windows [Version 10.0.18363.815](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 and successfully repaired them.
For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, 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 toolVersion: 10.0.18362.1Image Version: 10.0.18363.815[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.
C:\Windows\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management toolVersion: 10.0.18362.1Image Version: 10.0.18363.815[==========================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 ...  357376 file records processed.
File verification completed.  6205 large file records processed.  0 bad file records processed.
Stage 2: Examining file name linkage ...  2968 reparse records processed.  469902 index entries processed.
Index verification completed.  0 unindexed files scanned.  0 unindexed files recovered to lost and found.  2968 reparse records processed.
Stage 3: Examining security descriptors ...Security descriptor verification completed.  56264 data files processed.CHKDSK is verifying Usn Journal...  40794784 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.
No further action is required. 124372991 KB total disk space.  56654556 KB in 223487 files.    150184 KB in 56265 indexes.         0 KB in bad sectors.    470455 KB in use by the system.     65536 KB occupied by the log file.  67097796 KB available on disk.      4096 bytes in each allocation unit.  31093247 total allocation units on disk.  16774449 allocation units available on disk.
C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\GREYSCALE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk3\\Partition4"'Property(s) update successful.
C:\Windows\system32>wmic recoveros set debuginfotype = 7
Updating property(s) of '\\GREYSCALE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk3\\Partition4"'Property(s) update successful.
C:\Windows\system32>wmic recoveros get autorebootAutoRebootFALSEC:\Windows\system32>wmic recoveros get debuginfotypeDebugInfoType7
C:\Windows\system32>bcdedit /enum {badmemory}RAM Defects-----------identifier              {badmemory}
C:\Windows\system32>

First scannow:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:

Code:

Windows Resource Protection did not find any integrity violations.

Please turn off XMP during the troubleshooting.

Post images of virtual memory / paging file settings highlighting C:


For Memtest86
a) post images of two tests with four passes each
b) post text reports of each test

Attachment 276157

Move the dot from No paging file to System managed size
Check the box to Automatically manage paging file size for all drives
Reboot to maintain settings

Do not change these settings.
Do not change the startup and recovery system failure settings.

Make a new restore point after modifying the settings.



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/...3-c48669e4c983

Here are the memtest86 results. Faulty CPU? XMP was disabled by the way, I think it's just listing the XMP settings. It was running at 2666MHz.

Attachment 276467Attachment 276468

Code:

Summary

Report Date
2020-04-27 08:57:13

Generated by
MemTest86 V8.3 Free (64-bit)

Result
FAIL



System Information

EFI Specifications
2.70

System


Manufacturer
Gigabyte Technology Co., Ltd.

Product Name
AX370-Gaming K5

Version
Default string

Serial Number
Default string

BIOS


Vendor
American Megatrends Inc.

Version
F50a

Release Date
11/27/2019

Baseboard


Manufacturer
Gigabyte Technology Co., Ltd.

Product Name
AX370-Gaming K5-CF

Version
x.x

Serial Number
Default string

CPU Type
AMD Ryzen 5 3600 6-Core

CPU Clock
3601 MHz

# Logical Processors
12

L1 Cache
12 x 64K (201103 MB/s)

L2 Cache
12 x 512K (79037 MB/s)

L3 Cache
1 x 32768K (22465 MB/s)

Memory
16350M (15174 MB/s)

DIMM Slot #0
8GB DDR4 XMP PC4-28800


Crucial Technology / BLE8G4D36BEEAK.M8FE1 / E1C346E5


16-18-18-38 / 3602 MHz / 1.350V

DIMM Slot #1
8GB DDR4 XMP PC4-28800


Crucial Technology / BLE8G4D36BEEAK.M8FE1 / E1C33F09


16-18-18-38 / 3602 MHz / 1.350V



Result summary

Test Start Time
2020-04-27 05:28:40

Elapsed Time
3:27:03

Memory Range Tested
0x0 - 41F380000 (16883MB)

CPU Selection Mode
Parallel (All CPUs)

ECC Polling
Enabled

# Tests Passed
47/48 (97%)


Lowest Error Address
0x3A347AFA0 (14900MB)

Highest Error Address
0x3A347AFA0 (14900MB)

Bits in Error Mask
0000000000200000

Bits in Error
1

Max Contiguous Errors
1


Test
# Tests Passed
Errors

Test 0 [Address test, walking ones, 1 CPU]
4/4 (100%)
0

Test 1 [Address test, own address, 1 CPU]
4/4 (100%)
0

Test 2 [Address test, own address]
4/4 (100%)
0

Test 3 [Moving inversions, ones & zeroes]
4/4 (100%)
0

Test 4 [Moving inversions, 8-bit pattern]
3/4 (75%)
1

Test 5 [Moving inversions, random pattern]
4/4 (100%)
0

Test 6 [Block move, 64-byte blocks]
4/4 (100%)
0

Test 7 [Moving inversions, 32-bit pattern]
4/4 (100%)
0

Test 8 [Random number sequence]
4/4 (100%)
0

Test 9 [Modulo 20, ones & zeros]
4/4 (100%)
0

Test 10 [Bit fade test, 2 patterns, 1 CPU]
4/4 (100%)
0

Test 13 [Hammer test]
4/4 (100%)
0


Last 10 Errors

2020-04-27 06:09:04 - [Data Error] Test: 4, CPU: 1, Address: 3A347AFA0, Expected: 40404040, Actual: 40604040


Test 13 [Hammer test] Warning

Note: Your RAM may be vulnerable to high frequency row hammer bit flips. However the conditions needed to induce these errors occur only very rarely in normal PC usage, and so this should not be of concern to most users.



Certification

This document certifies that the Tests described above have been carried out by a suitably qualified technician on the System described above.


Signed

___________________________
Put your company name here:
Level 5, 63 Foveaux St, Surry Hills, 2010, Sydney, Australia
Phone + 61 2 9690 0444 Fax + 61 2 9690 0445


E-Mail: info@passmark.com

Label each RAM module and DIMM.

Test each RAM module in the same DIMM for two tests of four passes each to distinguish good from malfunctioning RAM.

Please post images and text reports for each test.

zbook said:

Test each RAM module in the same DIMM for two tests of four passes each to distinguish good from malfunctioning RAM.

How can you say this RAM is malfunctioning if it's brand new? If the problem persists across two different sets of DIMMs, doesn't that indicate that the CPU, cache or motherboard is the problem?