V5 beta feedback - problems

[Bandit]

Hello. Thanks for the fantastic Memtest.
Here I would like to report, for your development, issues I have discovered with V5 beta, hoping it will be helpful to you (and us).
Big pictures included - scroll below them for more text.

About the log file requested here:
http://www.passmark.com/forum/showth...Version-5-Beta
Suggest you mention it is a Linux formatted USB drive. On Windows it just comes up as needing formatting, so I recommend using the fantastic DiskInternals Linux Reader
http://www.diskinternals.com/linux-reader/

I would attach the log files, but there is a limit of 3 attached files per post, so after the pics there is no more room, so I'll just include them at the end of this post.

I have a GigaByte GA-Z77x-UD5H v1.1 motherboard with F15 BIOS http://ca.gigabyte.com/products/product-page.aspx?pid=4440&dl=1#bios
and 32Gb Patriot Viper 2133MHz ram
http://www.patriotmemory.com/product/detail.jsp?prodline=5&catid=34&prodgroupid=232&id= 1326&type=1
and Intel 3770K CPU
CPU: Intel Core i7-3770K @ 3.50GHz
CPU Clk: 3492 MHz
L1 Cache: 64K (136843 MB/s)
L2 Cache: 256K (95106 MB/s)
L3 Cache: 8192K (71565 MB/s)
Total Physical Memory: 31815M (44285 MB/s)
DIMM #0: PC3-16000 DDR3 XMP (1000 MHz) / 11-11-11-28 / Patriot Memory (PDP Systems) / 2133 CL11 Series
DIMM #1: PC3-16000 DDR3 XMP (1000 MHz) / 11-11-11-28 / Patriot Memory (PDP Systems) / 2133 CL11 Series
DIMM #2: PC3-16000 DDR3 XMP (1000 MHz) / 11-11-11-28 / Patriot Memory (PDP Systems) / 213C1 V3 Series
DIMM #3: PC3-16000 DDR3 XMP (1000 MHz) / 11-11-11-28 / Patriot Memory (PDP Systems) / 213C1 V3 Series



When using Memtest V5, one can not seem to select "All Memory" - you can pound on any key you like, but not get the * to select "All Memory"



When setting the CPU to use Sequential, Memtest v5 starts but then immediately halts on execution (see below pic)
It does not halt if left to autostart or other CPU selections, just Sequential


===========================
2013-08-07 13:18:25 - MemTest86 V5.0 Build: 1000 (64-bit)
2013-08-07 13:18:25 - Intializing screen for graphics
2013-08-07 13:18:25 - Getting CPUID
2013-08-07 13:18:25 - Getting cache size
2013-08-07 13:18:25 - get_cache_size - Vendor ID: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
2013-08-07 13:18:25 - get_cache_size - max_cpuid = 13
2013-08-07 13:18:25 - Measuring CPU/cache/mem speed
2013-08-07 13:18:25 - cpuspeed - rdtsc instruction supported: 1
2013-08-07 13:18:25 - cpu_cache_speed - CPU speed: 3492.1MHz
2013-08-07 13:18:25 - cpu_cache_speed - measuring L1 cache speed at 0x907E0000 (32 KB)
2013-08-07 13:18:25 - cpu_cache_speed - L1 cache speed: 136843 MB/s
2013-08-07 13:18:25 - cpu_cache_speed - measuring L2 cache speed at 0x8FCB7000 (256 KB)
2013-08-07 13:18:25 - cpu_cache_speed - L2 cache speed: 95106 MB/s
2013-08-07 13:18:25 - cpu_cache_speed - measuring L3 cache speed at 0x8F2D4000 (8192 KB)
2013-08-07 13:18:26 - cpu_cache_speed - L3 cache speed: 71565 MB/s
2013-08-07 13:18:26 - get_mem_speed - measuring mem speed at 0x886DB000 (68096 KB)
2013-08-07 13:18:26 - get_mem_speed - mem speed: 44285 MB/s
2013-08-07 13:18:26 - Getting memory size
2013-08-07 13:18:26 - mem_size - Number of entries: 139
2013-08-07 13:18:26 - mem_size - Total memory size(33361141760 bytes)
2013-08-07 13:18:26 - Getting memory SPD info
2013-08-07 13:18:26 - Searching PCI for SMBus Controller
2013-08-07 13:18:26 - Found SMBus device: VID:8086 DID:1E22 Bus:00 Dev:1F Fun:03 IO Add:F040 MMIO Add:0 Rev:04 [Intel Panther Point (PCH)]
2013-08-07 13:18:26 - Successfully located the PI MpService protocol.
2013-08-07 13:18:26 - This platform has 8 logical processors of which 8 are enabled.
2013-08-07 13:18:26 - Unable to enable processor 0: Invalid Parameter
2013-08-07 13:18:26 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:18:26 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:18:26 - 00000000 Y BSP 00000007 0 0 0
2013-08-07 13:18:26 - Enabling processor 1
2013-08-07 13:18:26 - ProcID Enabled Type Status Pkg Core Thread

[David (PassMark)]

Thanks for the feedback.

Suggest you mention it is a Linux formatted USB drive.

It actually isn't a Linux formatted drive. It is a USB drive with a GPT partition table and a FAT16 file system. We played around with MBR style partitions, but it seems some motherboard refuse to boot UEFI code from MBR. So we switched to GPT. The type of partition within GPT is a 'EFI System Partition'.

Windows reads FAT16 drives just fine. So it is either the, admittedly unusual, combination of GPT and FAT16 causing the problem, or the fact it is a EFI System Partition that causes the problem. We'll have a deeper look into it. We didn't notice the problem before as we were using MBR up until recently.

one can not seem to select "All Memory"

This option just resets the upper and lower limit values. You aren't meant to select it. We'll change the wording on the option to make this more clear.

When setting the CPU to use Sequential, Memtest v5 starts but then immediately halts on execution (see below pic). It does not halt if left to autostart or other CPU selections, just Sequential

We will see if we can reproduce the problem.

[keith]

When setting the CPU to use Sequential, Memtest v5 starts but then immediately halts on execution (see below pic)
It does not halt if left to autostart or other CPU selections, just Sequential

Do you have the rest of the log file? It seems that it was truncated from your post.

[Bandit]

more glitches found

Thanks for the feedback.

It actually isn't a Linux formatted drive. It is a USB drive with a GPT partition table and a FAT16 file system. We played around with MBR style partitions, but it seems some motherboard refuse to boot UEFI code from MBR. So we switched to GPT. The type of partition within GPT is a 'EFI System Partition'.

Windows reads FAT16 drives just fine. So it is either the, admittedly unusual, combination of GPT and FAT16 causing the problem, or the fact it is a EFI System Partition that causes the problem. We'll have a deeper look into it. We didn't notice the problem before as we were using MBR up until recently.

We will see if we can reproduce the problem.

OK, FYI it was Windows XPPRoSP3 that did not recognize it, but using LinuxReader it did.

More usage on my part has shown 2 other glitches:

Using anything other than the default 1 CPU (which stays on CPU core 1 on my system) causes hangs at some point, so using Round Robin or Parallel will cause Memtest to hang, sometimes it will run for some time, but it never makes it thru a whole 1 pass, usually hanging on test 9, sometimes before.

FYI: If in the BIOS I set the limit of CPU cores to 4 (it has a range of 1 to 4, but that is indicating actual cores, not including HyperThreading), then Memtest will only show 4 cores, rather than the 8 it shows here in these pics. I have not tested to see if when I do that it would cause Memtest to not hang (or even using < 4 cores).

The PASS progress 'bar' immediately shows 100% after the first test, even though it is just finished the first test.
You can see from the pic that the actual number indicator still shows 0 for passes completed, which is correct.

[Bandit]

logs

Do you have the rest of the log file? It seems that it was truncated from your post.

Sure. I would upload it, rather than post it here, but this forum's uploader software refuses anything other than a file that is .jpg .jpeg .png
It also prohibits more than 15000 characters, so I'll have to put the info into several reply posts here.
I tried just renaming it to a .png or .jpg but the forum's uploader software checks to see if it's a valid file, so that didn't work either.

=====================

2013-08-07 13:18:25 - MemTest86 V5.0 Build: 1000 (64-bit)
2013-08-07 13:18:25 - Intializing screen for graphics
2013-08-07 13:18:25 - Getting CPUID
2013-08-07 13:18:25 - Getting cache size
2013-08-07 13:18:25 - get_cache_size - Vendor ID: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
2013-08-07 13:18:25 - get_cache_size - max_cpuid = 13
2013-08-07 13:18:25 - Measuring CPU/cache/mem speed
2013-08-07 13:18:25 - cpuspeed - rdtsc instruction supported: 1
2013-08-07 13:18:25 - cpu_cache_speed - CPU speed: 3492.1MHz
2013-08-07 13:18:25 - cpu_cache_speed - measuring L1 cache speed at 0x907E0000 (32 KB)
2013-08-07 13:18:25 - cpu_cache_speed - L1 cache speed: 136843 MB/s
2013-08-07 13:18:25 - cpu_cache_speed - measuring L2 cache speed at 0x8FCB7000 (256 KB)
2013-08-07 13:18:25 - cpu_cache_speed - L2 cache speed: 95106 MB/s
2013-08-07 13:18:25 - cpu_cache_speed - measuring L3 cache speed at 0x8F2D4000 (8192 KB)
2013-08-07 13:18:26 - cpu_cache_speed - L3 cache speed: 71565 MB/s
2013-08-07 13:18:26 - get_mem_speed - measuring mem speed at 0x886DB000 (68096 KB)
2013-08-07 13:18:26 - get_mem_speed - mem speed: 44285 MB/s
2013-08-07 13:18:26 - Getting memory size
2013-08-07 13:18:26 - mem_size - Number of entries: 139
2013-08-07 13:18:26 - mem_size - Total memory size(33361141760 bytes)
2013-08-07 13:18:26 - Getting memory SPD info
2013-08-07 13:18:26 - Searching PCI for SMBus Controller
2013-08-07 13:18:26 - Found SMBus device: VID:8086 DID:1E22 Bus:00 Dev:1F Fun:03 IO Add:F040 MMIO Add:0 Rev:04 [Intel Panther Point (PCH)]
2013-08-07 13:18:26 - Successfully located the PI MpService protocol.
2013-08-07 13:18:26 - This platform has 8 logical processors of which 8 are enabled.
2013-08-07 13:18:26 - Unable to enable processor 0: Invalid Parameter
2013-08-07 13:18:26 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:18:26 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:18:26 - 00000000 Y BSP 00000007 0 0 0
2013-08-07 13:18:26 - Enabling processor 1
2013-08-07 13:18:26 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:18:26 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:18:26 - 00000001 Y AP 00000006 0 0 1
2013-08-07 13:18:26 - Enabling processor 2
2013-08-07 13:18:26 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:18:26 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:18:26 - 00000002 Y AP 00000006 0 1 0
2013-08-07 13:18:27 - Enabling processor 3
2013-08-07 13:18:27 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:18:27 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:18:27 - 00000003 Y AP 00000006 0 1 1
2013-08-07 13:18:27 - Enabling processor 4
2013-08-07 13:18:27 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:18:27 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:18:27 - 00000004 Y AP 00000006 0 2 0
2013-08-07 13:18:27 - Enabling processor 5
2013-08-07 13:18:27 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:18:27 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:18:27 - 00000005 Y AP 00000006 0 2 1
2013-08-07 13:18:27 - Enabling processor 6
2013-08-07 13:18:27 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:18:27 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:18:27 - 00000006 Y AP 00000006 0 3 0
2013-08-07 13:18:27 - Enabling processor 7
2013-08-07 13:18:27 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:18:27 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:18:27 - 00000007 Y AP 00000006 0 3 1
2013-08-07 13:18:27 - This platform has 8 logical processors of which 8 are enabled.
2013-08-07 13:18:30 - Installing default tests
2013-08-07 13:19:36 - Test start time = 2013-08-07 13:19:36
2013-08-07 13:19:36 - CPU selection mode = 3
2013-08-07 13:19:36 - Starting pass #0
2013-08-07 13:19:36 - Running test #0 (Test 0 [Address test, walking ones, no cache])
2013-08-07 13:19:36 - ReadMemoryRanges - Available Pages = 8063286
2013-08-07 13:19:36 - RunMemoryRangeTest - Switching BSP from Proc# 0 --> 1
2013-08-07 13:19:36 - RunMemoryRangeTest - Switching BSP from Proc# 1 --> 2
2013-08-07 13:19:36 - RunMemoryRangeTest - Switching BSP from Proc# 2 --> 3
2013-08-07 13:19:36 - RunMemoryRangeTest - Switching BSP from Proc# 3 --> 4
2013-08-07 13:19:36 - RunMemoryRangeTest - Switching BSP from Proc# 4 --> 5
2013-08-07 13:19:36 - RunMemoryRangeTest - Switching BSP from Proc# 5 --> 6
2013-08-07 13:19:36 - RunMemoryRangeTest - Switching BSP from Proc# 6 --> 7
2013-08-07 13:19:36 - RunMemoryRangeTest - Switching BSP from Proc# 7 --> 0
2013-08-07 13:19:36 - RunMemoryRangeTest - Switching BSP from Proc# 0 --> 1
2013-08-07 13:20:09 - MemTest86 V5.0 Build: 1000 (64-bit)
2013-08-07 13:20:09 - Intializing screen for graphics
2013-08-07 13:20:09 - Getting CPUID
2013-08-07 13:20:09 - Getting cache size
2013-08-07 13:20:09 - get_cache_size - Vendor ID: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
2013-08-07 13:20:09 - get_cache_size - max_cpuid = 13
2013-08-07 13:20:09 - Measuring CPU/cache/mem speed
2013-08-07 13:20:09 - cpuspeed - rdtsc instruction supported: 1
2013-08-07 13:20:09 - cpu_cache_speed - CPU speed: 3492.1MHz
2013-08-07 13:20:09 - cpu_cache_speed - measuring L1 cache speed at 0x906E5000 (32 KB)
2013-08-07 13:20:10 - cpu_cache_speed - L1 cache speed: 136842 MB/s
2013-08-07 13:20:10 - cpu_cache_speed - measuring L2 cache speed at 0x8FF3E000 (256 KB)
2013-08-07 13:20:10 - cpu_cache_speed - L2 cache speed: 94692 MB/s
2013-08-07 13:20:10 - cpu_cache_speed - measuring L3 cache speed at 0x8F55B000 (8192 KB)
2013-08-07 13:20:10 - cpu_cache_speed - L3 cache speed: 71485 MB/s
2013-08-07 13:20:10 - get_mem_speed - measuring mem speed at 0x8890D000 (68096 KB)
2013-08-07 13:20:10 - get_mem_speed - mem speed: 44030 MB/s
2013-08-07 13:20:10 - Getting memory size
2013-08-07 13:20:10 - mem_size - Number of entries: 143
2013-08-07 13:20:10 - mem_size - Total memory size(33361141760 bytes)
2013-08-07 13:20:10 - Getting memory SPD info
2013-08-07 13:20:10 - Searching PCI for SMBus Controller
2013-08-07 13:20:10 - Found SMBus device: VID:8086 DID:1E22 Bus:00 Dev:1F Fun:03 IO Add:F040 MMIO Add:0 Rev:04 [Intel Panther Point (PCH)]
2013-08-07 13:20:10 - Successfully located the PI MpService protocol.
2013-08-07 13:20:10 - This platform has 8 logical processors of which 8 are enabled.
2013-08-07 13:20:10 - Unable to enable processor 0: Invalid Parameter
2013-08-07 13:20:10 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:10 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:10 - 00000000 Y BSP 00000007 0 0 0
2013-08-07 13:20:11 - Enabling processor 1
2013-08-07 13:20:11 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:11 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:11 - 00000001 Y AP 00000006 0 0 1
2013-08-07 13:20:11 - Enabling processor 2
2013-08-07 13:20:11 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:11 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:11 - 00000002 Y AP 00000006 0 1 0
2013-08-07 13:20:11 - Enabling processor 3
2013-08-07 13:20:11 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:11 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:11 - 00000003 Y AP 00000006 0 1 1
2013-08-07 13:20:11 - Enabling processor 4
2013-08-07 13:20:11 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:11 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:11 - 00000004 Y AP 00000006 0 2 0
2013-08-07 13:20:11 - Enabling processor 5
2013-08-07 13:20:11 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:11 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:11 - 00000005 Y AP 00000006 0 2 1
2013-08-07 13:20:11 - Enabling processor 6
2013-08-07 13:20:11 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:11 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:11 - 00000006 Y AP 00000006 0 3 0
2013-08-07 13:20:11 - Enabling processor 7
2013-08-07 13:20:11 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:11 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:11 - 00000007 Y AP 00000006 0 3 1
2013-08-07 13:20:11 - This platform has 8 logical processors of which 8 are enabled.
2013-08-07 13:20:21 - Installing default tests
2013-08-07 13:20:21 - Test start time = 2013-08-07 13:20:21
2013-08-07 13:20:21 - CPU selection mode = 0
2013-08-07 13:20:21 - Starting pass #0
2013-08-07 13:20:21 - Running test #0 (Test 0 [Address test, walking ones, no cache])
2013-08-07 13:20:21 - ReadMemoryRanges - Available Pages = 8063935
2013-08-07 13:20:26 - MtSupportRunAllTests - Test execution time: 4.392
2013-08-07 13:20:26 - Running test #1 (Test 1 [Address test, own address] )
2013-08-07 13:20:26 - ReadMemoryRanges - Available Pages = 8063935
2013-08-07 13:20:56 - MemTest86 V5.0 Build: 1000 (64-bit)
2013-08-07 13:20:56 - Intializing screen for graphics
2013-08-07 13:20:56 - Getting CPUID
2013-08-07 13:20:56 - Getting cache size
2013-08-07 13:20:56 - get_cache_size - Vendor ID: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
2013-08-07 13:20:56 - get_cache_size - max_cpuid = 13
2013-08-07 13:20:56 - Measuring CPU/cache/mem speed
2013-08-07 13:20:56 - cpuspeed - rdtsc instruction supported: 1
2013-08-07 13:20:56 - cpu_cache_speed - CPU speed: 3492.1MHz
2013-08-07 13:20:56 - cpu_cache_speed - measuring L1 cache speed at 0x906E5000 (32 KB)
2013-08-07 13:20:56 - cpu_cache_speed - L1 cache speed: 136634 MB/s
2013-08-07 13:20:56 - cpu_cache_speed - measuring L2 cache speed at 0x8FF3E000 (256 KB)
2013-08-07 13:20:56 - cpu_cache_speed - L2 cache speed: 93986 MB/s
2013-08-07 13:20:56 - cpu_cache_speed - measuring L3 cache speed at 0x8F55B000 (8192 KB)
2013-08-07 13:20:56 - cpu_cache_speed - L3 cache speed: 71485 MB/s
2013-08-07 13:20:56 - get_mem_speed - measuring mem speed at 0x8890E000 (68096 KB)
2013-08-07 13:20:56 - get_mem_speed - mem speed: 44030 MB/s
2013-08-07 13:20:56 - Getting memory size
2013-08-07 13:20:56 - mem_size - Number of entries: 143
2013-08-07 13:20:56 - mem_size - Total memory size(33361141760 bytes)
2013-08-07 13:20:56 - Getting memory SPD info
2013-08-07 13:20:56 - Searching PCI for SMBus Controller
2013-08-07 13:20:56 - Found SMBus device: VID:8086 DID:1E22 Bus:00 Dev:1F Fun:03 IO Add:F040 MMIO Add:0 Rev:04 [Intel Panther Point (PCH)]

[Bandit]

logs part 2

2013-08-07 13:20:57 - Successfully located the PI MpService protocol.
2013-08-07 13:20:57 - This platform has 8 logical processors of which 8 are enabled.
2013-08-07 13:20:57 - Unable to enable processor 0: Invalid Parameter
2013-08-07 13:20:57 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:57 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:57 - 00000000 Y BSP 00000007 0 0 0
2013-08-07 13:20:57 - Enabling processor 1
2013-08-07 13:20:57 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:57 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:57 - 00000001 Y AP 00000006 0 0 1
2013-08-07 13:20:57 - Enabling processor 2
2013-08-07 13:20:57 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:57 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:57 - 00000002 Y AP 00000006 0 1 0
2013-08-07 13:20:57 - Enabling processor 3
2013-08-07 13:20:57 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:57 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:57 - 00000003 Y AP 00000006 0 1 1
2013-08-07 13:20:57 - Enabling processor 4
2013-08-07 13:20:57 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:57 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:57 - 00000004 Y AP 00000006 0 2 0
2013-08-07 13:20:57 - Enabling processor 5
2013-08-07 13:20:57 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:57 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:57 - 00000005 Y AP 00000006 0 2 1
2013-08-07 13:20:57 - Enabling processor 6
2013-08-07 13:20:57 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:57 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:57 - 00000006 Y AP 00000006 0 3 0
2013-08-07 13:20:57 - Enabling processor 7
2013-08-07 13:20:57 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:20:57 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:20:57 - 00000007 Y AP 00000006 0 3 1
2013-08-07 13:20:57 - This platform has 8 logical processors of which 8 are enabled.
2013-08-07 13:21:44 - MemTest86 V5.0 Build: 1000 (64-bit)
2013-08-07 13:21:44 - Intializing screen for graphics
2013-08-07 13:21:44 - Getting CPUID
2013-08-07 13:21:44 - Getting cache size
2013-08-07 13:21:44 - get_cache_size - Vendor ID: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
2013-08-07 13:21:44 - get_cache_size - max_cpuid = 13
2013-08-07 13:21:44 - Measuring CPU/cache/mem speed
2013-08-07 13:21:44 - cpuspeed - rdtsc instruction supported: 1
2013-08-07 13:21:44 - cpu_cache_speed - CPU speed: 3492.1MHz
2013-08-07 13:21:44 - cpu_cache_speed - measuring L1 cache speed at 0x9034D000 (32 KB)
2013-08-07 13:21:44 - cpu_cache_speed - L1 cache speed: 136217 MB/s
2013-08-07 13:21:44 - cpu_cache_speed - measuring L2 cache speed at 0x8FEB3000 (256 KB)
2013-08-07 13:21:44 - cpu_cache_speed - L2 cache speed: 94184 MB/s
2013-08-07 13:21:44 - cpu_cache_speed - measuring L3 cache speed at 0x8EBCE000 (8192 KB)
2013-08-07 13:21:44 - cpu_cache_speed - L3 cache speed: 71565 MB/s
2013-08-07 13:21:45 - get_mem_speed - measuring mem speed at 0x8890E000 (68096 KB)
2013-08-07 13:21:45 - get_mem_speed - mem speed: 44030 MB/s
2013-08-07 13:21:45 - Getting memory size
2013-08-07 13:21:45 - mem_size - Number of entries: 161
2013-08-07 13:21:45 - mem_size - Total memory size(33361141760 bytes)
2013-08-07 13:21:45 - Getting memory SPD info
2013-08-07 13:21:45 - Searching PCI for SMBus Controller
2013-08-07 13:21:45 - Found SMBus device: VID:8086 DID:1E22 Bus:00 Dev:1F Fun:03 IO Add:F040 MMIO Add:0 Rev:04 [Intel Panther Point (PCH)]
2013-08-07 13:21:45 - Successfully located the PI MpService protocol.
2013-08-07 13:21:45 - This platform has 8 logical processors of which 8 are enabled.
2013-08-07 13:21:45 - Unable to enable processor 0: Invalid Parameter
2013-08-07 13:21:45 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:21:45 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:21:45 - 00000000 Y BSP 00000007 0 0 0
2013-08-07 13:21:45 - Enabling processor 1
2013-08-07 13:21:45 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:21:45 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:21:45 - 00000001 Y AP 00000006 0 0 1
2013-08-07 13:21:45 - Enabling processor 2
2013-08-07 13:21:45 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:21:45 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:21:46 - 00000002 Y AP 00000006 0 1 0
2013-08-07 13:21:46 - Enabling processor 3
2013-08-07 13:21:46 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:21:46 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:21:46 - 00000003 Y AP 00000006 0 1 1
2013-08-07 13:21:46 - Enabling processor 4
2013-08-07 13:21:46 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:21:46 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:21:46 - 00000004 Y AP 00000006 0 2 0
2013-08-07 13:21:46 - Enabling processor 5
2013-08-07 13:21:46 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:21:46 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:21:46 - 00000005 Y AP 00000006 0 2 1
2013-08-07 13:21:46 - Enabling processor 6
2013-08-07 13:21:46 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:21:46 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:21:46 - 00000006 Y AP 00000006 0 3 0
2013-08-07 13:21:46 - Enabling processor 7
2013-08-07 13:21:46 - ProcID Enabled Type Status Pkg Core Thread
2013-08-07 13:21:46 - -------- -------- ---- -------- ----- ---- ------
2013-08-07 13:21:46 - 00000007 Y AP 00000006 0 3 1
2013-08-07 13:21:46 - This platform has 8 logical processors of which 8 are enabled.
2013-08-07 13:21:51 - Installing default tests
2013-08-07 13:22:26 - Test start time = 2013-08-07 13:22:26
2013-08-07 13:22:26 - CPU selection mode = 1
2013-08-07 13:22:26 - Starting pass #0
2013-08-07 13:22:26 - Running test #0 (Test 0 [Address test, walking ones, no cache])
2013-08-07 13:22:26 - ReadMemoryRanges - Available Pages = 8062768
2013-08-07 13:22:53 - MtSupportRunAllTests - Test execution time: 27.408
2013-08-07 13:22:53 - Running test #1 (Test 1 [Address test, own address] )
2013-08-07 13:22:53 - ReadMemoryRanges - Available Pages = 8062768
2013-08-07 13:23:21 - MtSupportRunAllTests - Test execution time: 27.399
2013-08-07 13:23:21 - Running test #2 (Test 2 [Moving inversions, ones&zeroes] )
2013-08-07 13:23:21 - ReadMemoryRanges - Available Pages = 8062768
2013-08-07 13:25:09 - MtSupportRunAllTests - Test execution time: 108.347
2013-08-07 13:25:09 - Running test #3 (Test 3 [Moving inversions, 8 bit pat] )
2013-08-07 13:25:09 - ReadMemoryRanges - Available Pages = 8062768
2013-08-07 13:31:28 - MtSupportRunAllTests - Test execution time: 378.529
2013-08-07 13:31:28 - Running test #4 (Test 4 [Moving inversions, random pattern] )
2013-08-07 13:31:28 - ReadMemoryRanges - Available Pages = 8062768
2013-08-07 13:35:31 - MtSupportRunAllTests - Test execution time: 243.244
2013-08-07 13:35:31 - Running test #5 (Test 5 [Block move, 64 moves] )
2013-08-07 13:35:31 - ReadMemoryRanges - Available Pages = 8062768
2013-08-07 13:42:43 - MtSupportRunAllTests - Test execution time: 432.322
2013-08-07 13:42:43 - Running test #6 (Test 6 [Moving inversions, 32 bit pat] )
2013-08-07 13:42:43 - ReadMemoryRanges - Available Pages = 8062768
2013-08-07 14:06:35 - MtSupportRunAllTests - Test execution time: 1431.966
2013-08-07 14:06:35 - Running test #7 (Test 7 [Random number sequence] )
2013-08-07 14:06:35 - ReadMemoryRanges - Available Pages = 8062768
2013-08-07 14:11:33 - MtSupportRunAllTests - Test execution time: 297.644
2013-08-07 14:11:33 - Running test #8 (Test 8 [Modulo 20, ones&zeros] )
2013-08-07 14:11:33 - ReadMemoryRanges - Available Pages = 8062768

[Bandit]

ram info log

MemTest86 V5.0 Build: 1000
PassMark (R) Software
www.passmark.com

Memmory summary:
Number of Memory Devices: 4
Total Physical Memory: 31815M

DIMM Slot: 1
==============
Ram Type: DDR3
Maximum Clock Speed (MHz): 1000 (XMP)
Maximum Transfer Speed (MHz): DDR3-2000
Maximum Bandwidth (MB/s): PC3-16000
Memory Capacity (MB): 8192
Jedec Manufacture Name: Patriot Memory (PDP Systems)
SPD Revision: 1.1
Registered: No
ECC: No
DIMM Slot #: 1
Manufactured: Year 2112
Module Part #: 2133 CL11 Series
Module Revision: 0x0000
Module Serial #: 0x00000000
Module Manufacturing Location: 0x02
# of Row Addressing Bits: 16
# of Column Addressing Bits: 10
# of Banks: 8
# of Ranks: 2
Device Width in Bits: 8
Bus Width in Bits: 64
Module Voltage: 1.5V
CAS Latencies Supported: 5 6 7 8 9
Timings @ Max Frequency (JEDEC): 9-9-9-24
Maximum frequency (MHz): 800
Maximum Transfer Speed (MHz): DDR3-1600
Maximum Bandwidth (MB/s): PC3-12800
Minimum Clock Cycle Time, tCK (ns): 1.250
Minimum CAS Latency Time, tAA (ns): 11.250
Minimum RAS to CAS Delay, tRCD (ns): 11.250
Minimum Row Precharge Time, tRP (ns): 11.250
Minimum Active to Precharge Time, tRAS (ns): 30.000
Minimum Row Active to Row Active Delay, tRRD (ns): 6.000
Minimum Auto-Refresh to Active/Auto-Refresh Time, tRC (ns): 48.125
Minimum Auto-Refresh to Active/Auto-Refresh Command Period, tRFC (ns): 300.000
DDR3 Specific SPD Attributes
Write Recover Time, tWR (ns): 15.000
Internal Write to Read Command Delay, tWTR (ns): 7.500
Internal Read to Precharge Command Delay, tRTP (ns): 7.500
Minimum Four Activate Window Delay (ns): 30.000
RZQ / 6 Supported: Yes
RZQ / 7 Supported: Yes
DLL-Off Mode Supported: Yes
Maximum Operating Temperature (C): 0-95C
Refresh Rate at Extended Operating Temperature Range: 1X
Auto-Self Refresh Supported: No
On-die Thermal Sensor Readout Supported: No
Partial Array Self Refresh Supported: No
Thermal Sensor Present: No
Non-standard SDRAM Type: Standard Monolithic
Module Type: UDIMM
Module Height (mm): 29 - 30
Module Thickness (mm): front 1-2 , back 1-2
Module Width (mm): 133.5
Reference Raw Card Used: Raw Card B Rev. 1
DRAM Manufacture ID: 0x0000
# of Registers: 0
Register Revision: 0x00
XMP Enthusiast / Certified Profile (Revision: 1.3)
Module voltage: 1.500V
Clock speed (MHz): 1000
Transfer Speed (MHz): DDR3-2000
Bandwidth (MB/s): PC3-16000
Minimum clock cycle time, tCK (ns): 1.000
Supported CAS latencies: 6 7 8 9 10 11
Minimum CAS latency time, tAA (ns): 10.375
Minimum RAS to CAS delay time, tRCD (ns): 10.375
Minimum row precharge time, tRP (ns): 10.375
Minimum active to precharge time, tRAS (ns): 28.000
Supported timing at highest clock speed: 11-11-11-28
Minimum Row Active to Row Active Delay, tRRD (ns): 5.625
Minimum Active to Auto-Refresh Delay, tRC (ns): 46.875
Minimum Recovery Delay, tRFC (ns): 281.375
Minimum Write Recovery time, tWR (ns): 15.000
Minimum Write to Read CMD Delay, tWTR (ns): 8.500
Minimum Read to Pre-charge CMD Delay, tRTP (ns): 8.500
Minimum Four Activate Window Delay, tFAW (ns): 30.000
Maximum Average Periodic Refresh Interval, tREFI (us): 3.875
Write to Read CMD Turn-around Time Optimizations: No adjustment
Read to Write CMD Turn-around Time Optimizations: No adjustment
Back 2 Back CMD Turn-around Time Optimizations: No adjustment
System CMD Rate Mode: 3T

DIMM Slot: 2
==============
Ram Type: DDR3
Maximum Clock Speed (MHz): 1000 (XMP)
Maximum Transfer Speed (MHz): DDR3-2000
Maximum Bandwidth (MB/s): PC3-16000
Memory Capacity (MB): 8192
Jedec Manufacture Name: Patriot Memory (PDP Systems)
SPD Revision: 1.1
Registered: No
ECC: No
DIMM Slot #: 2
Manufactured: Year 2112
Module Part #: 2133 CL11 Series
Module Revision: 0x0000
Module Serial #: 0x00000000
Module Manufacturing Location: 0x02
# of Row Addressing Bits: 16
# of Column Addressing Bits: 10
# of Banks: 8
# of Ranks: 2
Device Width in Bits: 8
Bus Width in Bits: 64
Module Voltage: 1.5V
CAS Latencies Supported: 5 6 7 8 9
Timings @ Max Frequency (JEDEC): 9-9-9-24
Maximum frequency (MHz): 800
Maximum Transfer Speed (MHz): DDR3-1600
Maximum Bandwidth (MB/s): PC3-12800
Minimum Clock Cycle Time, tCK (ns): 1.250
Minimum CAS Latency Time, tAA (ns): 11.250
Minimum RAS to CAS Delay, tRCD (ns): 11.250
Minimum Row Precharge Time, tRP (ns): 11.250
Minimum Active to Precharge Time, tRAS (ns): 30.000
Minimum Row Active to Row Active Delay, tRRD (ns): 6.000
Minimum Auto-Refresh to Active/Auto-Refresh Time, tRC (ns): 48.125
Minimum Auto-Refresh to Active/Auto-Refresh Command Period, tRFC (ns): 300.000
DDR3 Specific SPD Attributes
Write Recover Time, tWR (ns): 15.000
Internal Write to Read Command Delay, tWTR (ns): 7.500
Internal Read to Precharge Command Delay, tRTP (ns): 7.500
Minimum Four Activate Window Delay (ns): 30.000
RZQ / 6 Supported: Yes
RZQ / 7 Supported: Yes
DLL-Off Mode Supported: Yes
Maximum Operating Temperature (C): 0-95C
Refresh Rate at Extended Operating Temperature Range: 1X
Auto-Self Refresh Supported: No
On-die Thermal Sensor Readout Supported: No
Partial Array Self Refresh Supported: No
Thermal Sensor Present: No
Non-standard SDRAM Type: Standard Monolithic
Module Type: UDIMM
Module Height (mm): 29 - 30
Module Thickness (mm): front 1-2 , back 1-2
Module Width (mm): 133.5
Reference Raw Card Used: Raw Card B Rev. 1
DRAM Manufacture ID: 0x0000
# of Registers: 0
Register Revision: 0x00
XMP Enthusiast / Certified Profile (Revision: 1.3)
Module voltage: 1.500V
Clock speed (MHz): 1000
Transfer Speed (MHz): DDR3-2000
Bandwidth (MB/s): PC3-16000
Minimum clock cycle time, tCK (ns): 1.000
Supported CAS latencies: 6 7 8 9 10 11
Minimum CAS latency time, tAA (ns): 10.375
Minimum RAS to CAS delay time, tRCD (ns): 10.375
Minimum row precharge time, tRP (ns): 10.375
Minimum active to precharge time, tRAS (ns): 28.000
Supported timing at highest clock speed: 11-11-11-28
Minimum Row Active to Row Active Delay, tRRD (ns): 5.625
Minimum Active to Auto-Refresh Delay, tRC (ns): 46.875
Minimum Recovery Delay, tRFC (ns): 281.375
Minimum Write Recovery time, tWR (ns): 15.000
Minimum Write to Read CMD Delay, tWTR (ns): 8.500
Minimum Read to Pre-charge CMD Delay, tRTP (ns): 8.500
Minimum Four Activate Window Delay, tFAW (ns): 30.000
Maximum Average Periodic Refresh Interval, tREFI (us): 3.875
Write to Read CMD Turn-around Time Optimizations: No adjustment
Read to Write CMD Turn-around Time Optimizations: No adjustment
Back 2 Back CMD Turn-around Time Optimizations: No adjustment
System CMD Rate Mode: 3T

DIMM Slot: 3
==============
Ram Type: DDR3
Maximum Clock Speed (MHz): 1000 (XMP)
Maximum Transfer Speed (MHz): DDR3-2000
Maximum Bandwidth (MB/s): PC3-16000
Memory Capacity (MB): 8192
Jedec Manufacture Name: Patriot Memory (PDP Systems)
SPD Revision: 1.1
Registered: No
ECC: No
DIMM Slot #: 3
Manufactured: <unknown>
Module Part #: 213C1 V3 Series
Module Revision: 0x0000
Module Serial #: 0x00000000
Module Manufacturing Location: 0x02
# of Row Addressing Bits: 16
# of Column Addressing Bits: 10
# of Banks: 8
# of Ranks: 2
Device Width in Bits: 8
Bus Width in Bits: 64
Module Voltage: 1.5V
CAS Latencies Supported: 5 6 7 8 9
Timings @ Max Frequency (JEDEC): 9-9-9-24
Maximum frequency (MHz): 800
Maximum Transfer Speed (MHz): DDR3-1600
Maximum Bandwidth (MB/s): PC3-12800
Minimum Clock Cycle Time, tCK (ns): 1.250
Minimum CAS Latency Time, tAA (ns): 11.250
Minimum RAS to CAS Delay, tRCD (ns): 11.250
Minimum Row Precharge Time, tRP (ns): 11.250
Minimum Active to Precharge Time, tRAS (ns): 30.000
Minimum Row Active to Row Active Delay, tRRD (ns): 6.000
Minimum Auto-Refresh to Active/Auto-Refresh Time, tRC (ns): 48.125
Minimum Auto-Refresh to Active/Auto-Refresh Command Period, tRFC (ns): 300.000
DDR3 Specific SPD Attributes
Write Recover Time, tWR (ns): 15.000
Internal Write to Read Command Delay, tWTR (ns): 7.500
Internal Read to Precharge Command Delay, tRTP (ns): 7.500
Minimum Four Activate Window Delay (ns): 30.000
RZQ / 6 Supported: Yes
RZQ / 7 Supported: Yes
DLL-Off Mode Supported: Yes
Maximum Operating Temperature (C): 0-95C
Refresh Rate at Extended Operating Temperature Range: 1X
Auto-Self Refresh Supported: No
On-die Thermal Sensor Readout Supported: No
Partial Array Self Refresh Supported: No
Thermal Sensor Present: No
Non-standard SDRAM Type: Standard Monolithic
Module Type: UDIMM
Module Height (mm): 29 - 30
Module Thickness (mm): front 1-2 , back 1-2
Module Width (mm): 133.5
Reference Raw Card Used: Raw Card B Rev. 1
DRAM Manufacture ID: 0x0000
# of Registers: 0
Register Revision: 0x00
XMP Enthusiast / Certified Profile (Revision: 1.3)
Module voltage: 1.500V
Clock speed (MHz): 1000
Transfer Speed (MHz): DDR3-2000
Bandwidth (MB/s): PC3-16000
Minimum clock cycle time, tCK (ns): 1.000
Supported CAS latencies: 6 7 8 9 10 11
Minimum CAS latency time, tAA (ns): 10.375
Minimum RAS to CAS delay time, tRCD (ns): 10.375
Minimum row precharge time, tRP (ns): 10.375
Minimum active to precharge time, tRAS (ns): 28.000
Supported timing at highest clock speed: 11-11-11-28
Minimum Row Active to Row Active Delay, tRRD (ns): 5.625
Minimum Active to Auto-Refresh Delay, tRC (ns): 46.875
Minimum Recovery Delay, tRFC (ns): 281.375
Minimum Write Recovery time, tWR (ns): 15.000
Minimum Write to Read CMD Delay, tWTR (ns): 8.500
Minimum Read to Pre-charge CMD Delay, tRTP (ns): 8.500
Minimum Four Activate Window Delay, tFAW (ns): 30.000
Maximum Average Periodic Refresh Interval, tREFI (us): 3.875
Write to Read CMD Turn-around Time Optimizations: No adjustment
Read to Write CMD Turn-around Time Optimizations: No adjustment
Back 2 Back CMD Turn-around Time Optimizations: No adjustment
System CMD Rate Mode: 3T

DIMM Slot: 4
==============
Ram Type: DDR3
Maximum Clock Speed (MHz): 1000 (XMP)
Maximum Transfer Speed (MHz): DDR3-2000
Maximum Bandwidth (MB/s): PC3-16000
Memory Capacity (MB): 8192
Jedec Manufacture Name: Patriot Memory (PDP Systems)
SPD Revision: 1.1
Registered: No
ECC: No
DIMM Slot #: 4
Manufactured: <unknown>
Module Part #: 213C1 V3 Series
Module Revision: 0x0000
Module Serial #: 0x00000000
Module Manufacturing Location: 0x02
# of Row Addressing Bits: 16
# of Column Addressing Bits: 10
# of Banks: 8
# of Ranks: 2
Device Width in Bits: 8
Bus Width in Bits: 64
Module Voltage: 1.5V
CAS Latencies Supported: 5 6 7 8 9
Timings @ Max Frequency (JEDEC): 9-9-9-24
Maximum frequency (MHz): 800
Maximum Transfer Speed (MHz): DDR3-1600
Maximum Bandwidth (MB/s): PC3-12800
Minimum Clock Cycle Time, tCK (ns): 1.250
Minimum CAS Latency Time, tAA (ns): 11.250
Minimum RAS to CAS Delay, tRCD (ns): 11.250
Minimum Row Precharge Time, tRP (ns): 11.250
Minimum Active to Precharge Time, tRAS (ns): 30.000
Minimum Row Active to Row Active Delay, tRRD (ns): 6.000
Minimum Auto-Refresh to Active/Auto-Refresh Time, tRC (ns): 48.125
Minimum Auto-Refresh to Active/Auto-Refresh Command Period, tRFC (ns): 300.000
DDR3 Specific SPD Attributes
Write Recover Time, tWR (ns): 15.000
Internal Write to Read Command Delay, tWTR (ns): 7.500
Internal Read to Precharge Command Delay, tRTP (ns): 7.500
Minimum Four Activate Window Delay (ns): 30.000
RZQ / 6 Supported: Yes
RZQ / 7 Supported: Yes
DLL-Off Mode Supported: Yes
Maximum Operating Temperature (C): 0-95C
Refresh Rate at Extended Operating Temperature Range: 1X
Auto-Self Refresh Supported: No
On-die Thermal Sensor Readout Supported: No
Partial Array Self Refresh Supported: No
Thermal Sensor Present: No
Non-standard SDRAM Type: Standard Monolithic
Module Type: UDIMM
Module Height (mm): 29 - 30
Module Thickness (mm): front 1-2 , back 1-2
Module Width (mm): 133.5
Reference Raw Card Used: Raw Card B Rev. 1
DRAM Manufacture ID: 0x0000
# of Registers: 0
Register Revision: 0x00
XMP Enthusiast / Certified Profile (Revision: 1.3)
Module voltage: 1.500V
Clock speed (MHz): 1000
Transfer Speed (MHz): DDR3-2000
Bandwidth (MB/s): PC3-16000
Minimum clock cycle time, tCK (ns): 1.000
Supported CAS latencies: 6 7 8 9 10 11
Minimum CAS latency time, tAA (ns): 10.375
Minimum RAS to CAS delay time, tRCD (ns): 10.375
Minimum row precharge time, tRP (ns): 10.375
Minimum active to precharge time, tRAS (ns): 28.000
Supported timing at highest clock speed: 11-11-11-28
Minimum Row Active to Row Active Delay, tRRD (ns): 5.625
Minimum Active to Auto-Refresh Delay, tRC (ns): 46.875
Minimum Recovery Delay, tRFC (ns): 281.375
Minimum Write Recovery time, tWR (ns): 15.000
Minimum Write to Read CMD Delay, tWTR (ns): 8.500
Minimum Read to Pre-charge CMD Delay, tRTP (ns): 8.500
Minimum Four Activate Window Delay, tFAW (ns): 30.000
Maximum Average Periodic Refresh Interval, tREFI (us): 3.875
Write to Read CMD Turn-around Time Optimizations: No adjustment
Read to Write CMD Turn-around Time Optimizations: No adjustment
Back 2 Back CMD Turn-around Time Optimizations: No adjustment
System CMD Rate Mode: 3T

[David (PassMark)]

Thanks for the log.
For future reference, E-mail would have also been OK.

[Bandit]

more feedback

Me again with some more feedback.
It doesn't seem like memtest is getting correct ram info.
Ram I have in there is 2133Mhz PC3-17000:

http://www.patriotmemory.com/product...roupid=232&id= 1326&type=1

http://www.patriotmemory.com/product...G213C1QKRD.pdf

but memtest says it is 2000 and PC3-16000.

Now this could be errors in the SPD info on the module or something(s) other than memtest, but I thought I'd let you know. (I don't normally get such hi-performance ram but it was in the clearance rack for $100 for 32Gb, regular/current price of $290. Somebody made a mistake which they discovered after I paid for it, so lucky me)





Here is a photo of round robin CPU when memtest hangs when it reaches test 9.
I would upload a new log, but memtest hasn't made any new logs since the 'original' one you already have - seems it crashes before it can make a log.

Now in this test I had also overclocked the CPU to 4.2GHz (stock is 3.5 with turbo to 3.9,, but we all know 3770K is good for 4.2 easily), but I note that Memtest still reports it as 3500MHz and the ram speed does not increase. I *know* it's at 4200 because the BIOS reports it as such as do other utils. Memory is just the default XMP profile.

[David (PassMark)]

The log get appended to.
You can E-mail us any additional logs (or updated log).

For Test #9 how long did you wait? There is a long pause in this test to see if the bits 'fade'.

[Bandit]

test 9 wait time

The log get appended to.
You can E-mail us any additional logs (or updated log).

For Test #9 how long did you wait? There is a long pause in this test to see if the bits 'fade'.

Yes, there are many long pauses, and I waited for several hours.
But the spinning \|/-_ cycling indicator under the CPU number bank was frozen also, and when just using the 1 CPU 0 it still 'spins' while the bits are fading. Also, there is a countdown timer showing how long the fade test is delapsing (if that's not real word then I invent it now) and that is frozen also. Obviously a static pic won't show that, but if I were to video it, it'd look the same as a static pic since memtest was frozen.

Anything else I can help debug?

[keith]

It doesn't seem like memtest is getting correct ram info.
Ram I have in there is 2133Mhz PC3-17000:

http://www.patriotmemory.com/product...roupid=232&id= 1326&type=1

http://www.patriotmemory.com/product...G213C1QKRD.pdf

but memtest says it is 2000 and PC3-16000.

XMP specifies 2 profiles: Enthusiast (lower performance) and Extreme (higher performance). In your case, the 2000MHz and PC3-16000 comes from the Enthusiast profile. It might be that the 2133MHz and PC3-17000 values comes from the Extreme profile but isn't displayed because MemTest86 seems to think it is disabled. You can confirm if this is the case by running CPU-Z or our own RAMMon utility.(http://www.passmark.com/products/rammon.htm)

Now in this test I had also overclocked the CPU to 4.2GHz (stock is 3.5 with turbo to 3.9,, but we all know 3770K is good for 4.2 easily), but I note that Memtest still reports it as 3500MHz and the ram speed does not increase. I *know* it's at 4200 because the BIOS reports it as such as do other utils. Memory is just the default XMP profile.

The text on the top is the brand string reported by the CPU, and will not change regardless of the actual clock speed. The clock speed on the left side, however, is measured by MemTest86 itself so it is interesting that it does not match your overclocked speed. We will need to investigate further into this.

Using anything other than the default 1 CPU (which stays on CPU core 1 on my system) causes hangs at some point, so using Round Robin or Parallel will cause Memtest to hang, sometimes it will run for some time, but it never makes it thru a whole 1 pass, usually hanging on test 9, sometimes before.

Seems that there may be issues with your motherboard's UEFI firmware implementation of multiprocessor services, as your log indicates that it freezes right after switching CPUs. You can try updating the firmware, but I doubt that the mobo vendor would have a fix for an issue like this. Can you try running in single CPU mode on any processor other than the first? Please e-mail the log file to help[atpassmarkdotcom]

The PASS progress 'bar' immediately shows 100% after the first test, even though it is just finished the first test.
You can see from the pic that the actual number indicator still shows 0 for passes completed, which is correct.

The behaviour of the PASS progress bar was changed so that it is based on the number of tests currently completed (as opposed to the total number of tests to perform). This was so that any percentage less than 100% indicates test failure(s) as opposed to tests that have yet to be completed.

[Bandit]

updates

XMP specifies 2 profiles: Enthusiast (lower performance) and Extreme (higher performance). In your case, the 2000MHz and PC3-16000 comes from the Enthusiast profile. It might be that the 2133MHz and PC3-17000 values comes from the Extreme profile but isn't displayed because MemTest86 seems to think it is disabled. You can confirm if this is the case by running CPU-Z or our own RAMMon utility.(http://www.passmark.com/products/rammon.htm)

The mobo only has a choice of Profile1, which is the Extreme.
There is no OS on the system yet, so I would have to wait to try either utility.

Some other things I've noticed in v4.3 - when running a test, it doesn't respond to keyboard (MS 4000 USB) such as when hitting 'c' or 'ESC' unless it's on the very 1st test.

The text on the top is the brand string reported by the CPU, and will not change regardless of the actual clock speed. The clock speed on the left side, however, is measured by MemTest86 itself so it is interesting that it does not match your overclocked speed. We will need to investigate further into this.

Yes, I should have been more specific in my wording and not rounded off the 3492MHz.
I do note that, interestingly, the ram speed also does not increase/change with CPU clock speed change.

But choosing a different CPU test mode (single core vs parallel vs etc) causes a little ram speed change. Even v4.3 shows a change between CPU modes.
The ram speed measuring must have changed also, since v4.3 shows 29395MBs and V5 shows 42372MBs for the same BIOS settings. That's quite a bit of difference.
(note these are for the system ram, not CPU L1/L2/L3 cache)

Changing CPU multiplier all the way from 35 stock to 50 overclock actually does not change the ram speed much at all. Although they vary slightly each time a few MHz, they always stay around L1=136840, L2=94300, L3=71565, main=44000; v4.3 reports L1=99300, L2=53150, L3=35500, main=29364.

Seems that there may be issues with your motherboard's UEFI firmware implementation of multiprocessor services, as your log indicates that it freezes right after switching CPUs. You can try updating the firmware, but I doubt that the mobo vendor would have a fix for an issue like this. Can you try running in single CPU mode on any processor other than the first? Please e-mail the log file to help[atpassmarkdotcom]

Could be a firmware bug. I am using the latest F15 official BIOS. Not the first bug in the firmware I discovered. There was also the problem in F15betas where if an XMP profile was enabled AND anything other than the default 64Mb of onboard ram used for the iGPU, the system would not POST. This is fixed in the official non-beta F15 BIOS version, already 2 months old but which they are too lazy to post, and the issue did not exist in the F14 version.

I tried at least 2 passes on every other of the 8 CPU's in single CPU mode and no problems. I have emailed the log file.
I also discovered something else: I ran a full 1 pass test in parallel CPU mode. It completed fine with no error results. So, then I tried to run it again right away, and THAT's when Memtest froze and would not continue. So it seems like it's an issue with starting another round of tests even when a full pass had been completed.

BTW, what is the issue with false positives in parallel CPU mode?

The behaviour of the PASS progress bar was changed so that it is based on the number of tests currently completed (as opposed to the total number of tests to perform). This was so that any percentage less than 100% indicates test failure(s) as opposed to tests that have yet to be completed.

I vote strongly for retaining the 'old v4 PASS progress bar behaviour. Memtest is in use by millions of users who are used to the existing behaviour. Changing it confuses people, who will look at it and think that v5 has some super fast testing process and it is already done when in reality it is only done test 1. It could also be interpreted incorrectly as the existing test ongoing is 100% completed, when it is not yet.
If you were to change it so that it said FAILS: or ERRORS: then the bar did not progress unless there were errors, that would make sense. Or add a line that said FAILS: or ERRORS: , but kept the existing PASS: completion progress I think would be best. Memtest needs to retain the quick at-a-glance overall progress bar behaviour that everyone knows. Don't make the mistake like MS did with removing the START orb in Win8 and are now taking flak and having to bring it back. Otherwise you will also be answering 10 billion forum posts either about "why was it changed" or "it's not working correctly" or "insert question here".

[David (PassMark)]

Some other things I've noticed in v4.3 - when running a test, it doesn't respond to keyboard

There are a bunch of problems with USB keyboards in V4.x.
A USB keyboard working depends on the BIOS correctly emulating old PS/2 style keyboards. Not all BIOSs do this, or it properly. New Macs don't do it all all for example. So you'll never be able to run DOS on a new Mac.

The problem should disappear in V5 as USB is directly supported. No emulation is required anymore.

choosing a different CPU test mode (single core vs parallel vs etc) causes a little ram speed change

It shouldn't make any change. Might be just random fluctuations.

Changing CPU multiplier all the way from 35 stock to 50 overclock actually does not change the ram speed much at all

Doesn't surprise me greatly. The CPU should already be a lot faster than main RAM. For example, in Windows, if I run a RAM benchmark, then the CPU ticks over at just 10% load. So by overclocking the CPU you won't be gaining much in RAM speeds.

We'll have a look at the log for some of the other issues.

[David (PassMark)]

We put out a new beta release today that should address some of the issues.

Here is a list of issues you raised and current state,

Issue #1: CPU mode effects the bandwidth benchmark
We don't think this is possible. Any variation in measurements is more likely just random variations.

Issue #2: Main ram benchmark is reporting bigger numbers compared to V4
Looks like this was a bug. It should be corrected in the new beta.

Issue #3: Missing second XMP profile.
As best we can see in the log the second profile is disabled in the RAM itself. Needs independent checking with another utility (see above).

Issue #4: Progress bar behaviour
We have changed this in the new release.

Issue #5: False positives text
This was some text we added back in V4. On a very small number of machines, multi-threading would give false positives. For the moment we'll leave the text in place. But if we don't see it on any UEFI machines we can eventually remove it.

Issue #6: Lockups / freezes when switching tests
Looks like this is a firmware issue as best we can see. The lockup occurs inside a firmware call to force a CPU switch to a new CPU. If this theory is correct, you would never see a lockup when running on an individual CPU without rotation or threading.

We are going to put in a bit more debugging code anyway, so there should be a bit more detail in future debug logs for us to look at.

Issue #7: CPU clock speed not reporting correct value when overclocking
MemTest86 was originally coded in the days before CPUs had 'turbo' mode and unclocking power saving modes. So the code is a bit ignorant as to these features. For example we only report a single clock speed, but we really should be reporting a base clock speed and a turbo clock speed, as either or both might be overclocked. Correctly detecting both these clock speeds across all CPU types is tricky. Doubly so, when you don't have an operating system, but do have buggy firmware to deal with. Anyway, we'll see if it is possible to include both clock speeds.