Possible issue with multiprocessing on a 970M Pro3

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   This is going to be a long one, so bear with me...

My hardware:

CPU: AMD Phenom II X6 1090T BE

GPU: Asus GeForce GTX 650 DirectCU 1 GB GDDR5

MB: ASRock 970M Pro3 (Firmware/UEFI version 1.30)

RAM: 2 x 8 GB Kinston HyperX Fury Black DDR3 (officially rated at 1600 MHz CL10)

PSU: Cooler Master V650S

HDD: Samsung 850 EVO SSD 250 GB

Case: BitFenix Prodigy M

CPU Cooler: Arctic Cooling Freezer A11

Fans: 2 x BitFenix Spectre 120 mm

OS: Windows 8.1 64-bit & Linux Mint 17.2 Cinnamon 64-bit

Now, some of you might want to point out right away that those RAM modules are not supported for this motherboard - and you would be right - so let's start with that. When I was choosing the parts I'd use in this project, I did of course check which modules had been tested and proven to work on this motherboard. However, since Kingston's memory search suggested these for the ASRock 970 Pro3 R2.0 - which in my eyes is just an ATX-sized version of my mATX motherboard - I decided to risk it. I put all the parts together, turned the machine on and... zero issues. Win! 

After a couple of months of care-free usage (well, not quite, but those issues were related to having both Windows and Linux on the same machine), I started to do some light overclocking using standard voltages. While going through the motions of testing my OC'd system I ran into an issue with RealBench stress test, which gave an error message of "result mismatch" after every test cycle. What's worse, this happened even at stock settings. My first thought was that maybe the memory modules weren't working as they should after all, even though the overclocked system had passed 8 hours of Prime95 blend test with six workers and 2 GB RAM and a quick, one hour run of Prime95 blend test with six workers and 16 GB RAM without any errors. I decided to test my RAM using MemTest86 v6.2.0 to see if I had just gotten lucky with Prime95.

I started with a quick test using the default values and only let the test 
finish one pass, which it did without errors. As I was trying to pin 
down a problem I was experiencing with RealBench stress test, I thought I
 should probably run the test in parallel mode, since the stress test 
involves heavy multitasking. However, when I reached Test 2 (address test, own address, parallel) the test 
just stopped progressing. It didn't freeze totally, mind you. The timer 
was still running and the icons representing CPU core activity were 
spinning - except for CPU1, which showed a "W" - so I thought I just 
needed to give the test some time. Six hours later only the time on the 
counter had changed. So I tried again. The second time around CPU1 
started working as well, but almost immediately after that the computer 
just rebooted. There was no blue screen or any found memory errors that I
 could see, just a reboot.

I decided to run the default test on each of the separate cores to see 
if CPU1 was somehow anomalous. So I started from CPU0 and checked if the
 CPUs could get past Test 2. This is what I saw:

CPU0: OK

CPU1: MemTest86 freezes before anything is tested. The testing screen 
appears, but the timer is dead from the start and the system doesn't 
respond to anything from the keyboard.

CPU2: See CPU1

CPU3: OK

CPU4: See CPU1

CPU5: See CPU1

Just to be clear: This was at stock settings, and on stock setting I hadn't had any issues running multi-core tasks - except for the RealBench stress test. Roughly ten different benchmark tests (including the RealBench benchmark), Windows, Linux, a couple of games - all had run using up to all six cores without any instability issues.

After encountering this issue with MemTest86 I got a bit worried and 
also ran Windows Memory Diagnostic Tool. I started with the standard test, which finished 1 pass without errors before I decided to switch to the extended test. The extended test got me worried again, since it seemed to stall at 21%. After that I decided to tweak the memory settings a bit. The thing is, the stock values the motherboard set for the RAM were 1333 MHz CL9 (due to Phenom II) and 1.585 V, which were not the official values for these modules, so I decided to change the values to match the ones given by the manufacturer: 1600 MHz CL10 (I manually set all timing values to match the SPD values for this clock frequency) and 1.5 V. Then I ran the extended test again. Turns out the extended test just takes several hours to move past the 21% mark! In the end I ran the test for 26 hours, clearing 4 full passes with no errors found. I'm sure I would have had the same result had I had the patience to wait when I had my RAM at "stock" values. Unfortunately the changes I had made also had zero effect on MemTest86 and RealBench...

While passing a Windows Memory Diagnostic Tool test was no
 guarantee that MemTest86 wouldn't find an error, I was beginning to 
wonder if this was a UEFI-related issue. I had had a bit of trouble 
booting to MemTest86 and for some reason it just didn't want to start 
around 50% of the time. I would just see a sliver of my normal UEFI background
 picture in the upper edge of my monitor and that was it. If this happened,
 a reboot and retry had so far been all that it has taken to get MemTest
 to run. As I had changed the RAM settings, I decided to I run the parallel test again just in case; the system rebooted after reaching Test 2, just like it did before. The log file of this latest pass has this to say about Test 2:

2015-10-06 04:05:05 - MtSupportRunAllTests - Test execution time: 12.856 (Test 1 cumulative error count: 0)

2015-10-06 04:05:05 - GetAMD10Temp - Temperature: 31

2015-10-06 04:05:05 - Running test #2 (Test 2 [Address test, own address])

2015-10-06 04:05:05 - MtSupportRunAllTests - Setting random seed to 0x50415353

2015-10-06 04:05:05 - MtSupportRunAllTests - Start time: 15676 ms

2015-10-06 04:05:05 - ReadMemoryRanges - Available Pages = 4134591

2015-10-06 04:05:05 - MtSupportRunAllTests - Enabling memory cache for test

2015-10-06 04:05:05 - MtSupportRunAllTests - Enabling memory cache complete

2015-10-06 04:05:05 - Start memory range test (0x0 - 0x440000000)

2015-10-06 04:05:05 - Pre-allocating memory ranges >=16MB first...

2015-10-06 04:05:05 - All memory ranges successfully locked

2015-10-06 04:05:05 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 0ms)

2015-10-06 04:05:06 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 4ms)

2015-10-06 04:05:06 - RunMemoryRangeTest - CPU #3 timed out, test time = 0ms (BSP test time = 4ms)

2015-10-06 04:05:07 - RunMemoryRangeTest - CPU #2 completed but did not 
signal (test time = 5ms, event wait time = 1012ms, result = Success) 
(BSP test time = 4ms)

2015-10-06 04:05:07 - RunMemoryRangeTest - Could not start AP#2 
0x0000000005100000 - 0x0000000009100000 (Not Ready). Resetting...

2015-10-06 04:05:08 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 159ms)

2015-10-06 04:05:08 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 172ms)

2015-10-06 04:05:08 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 170ms)

2015-10-06 04:05:09 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 168ms)

2015-10-06 04:05:10 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 167ms)

2015-10-06 04:05:10 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 168ms)

2015-10-06 04:05:11 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 146ms)

2015-10-06 04:05:11 - RunMemoryRangeTest - CPU #4 timed out, test time = 0ms (BSP test time = 146ms)

2015-10-06 04:05:12 - RunMemoryRangeTest - CPU #3 completed but did not 
signal (test time = 142ms, event wait time = 1001ms, result = Success) 
(BSP test time = 146ms)

2015-10-06 04:05:12 - RunMemoryRangeTest - Could not start AP#3 
0x00000000AB035AA0 - 0x00000000ABFD07F0 (Not Ready). Resetting...

2015-10-06 04:05:12 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 32ms)

I asked about this on the PassMark forum and it was suggested that it may be a  UEFI-related bug with the multiprocessing subsystem. I don't know if this is correct or not, but to me it doesn't sound very far fetched. Would anyone here know if this truly is just a firmware issue and if so, could it also explain the problems I'm having with RealBench?

TLDR: CPU cores misbehaving in MemTest86 v6.2.0. Maybe a bug in UEFI, is there any hope of a fix?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
PetrolHead Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 07 Oct 2015 Status: Offline Points: 403	Post Options Post Reply Quote PetrolHead Report Post Thanks(0) Quote Reply Topic: Possible issue with multiprocessing on a 970M Pro3 Posted: 07 Oct 2015 at 8:11am
	This is going to be a long one, so bear with me... My hardware: CPU: AMD Phenom II X6 1090T BE GPU: Asus GeForce GTX 650 DirectCU 1 GB GDDR5 MB: ASRock 970M Pro3 (Firmware/UEFI version 1.30) RAM: 2 x 8 GB Kinston HyperX Fury Black DDR3 (officially rated at 1600 MHz CL10) PSU: Cooler Master V650S HDD: Samsung 850 EVO SSD 250 GB Case: BitFenix Prodigy M CPU Cooler: Arctic Cooling Freezer A11 Fans: 2 x BitFenix Spectre 120 mm OS: Windows 8.1 64-bit & Linux Mint 17.2 Cinnamon 64-bit Now, some of you might want to point out right away that those RAM modules are not supported for this motherboard - and you would be right - so let's start with that. When I was choosing the parts I'd use in this project, I did of course check which modules had been tested and proven to work on this motherboard. However, since Kingston's memory search suggested these for the ASRock 970 Pro3 R2.0 - which in my eyes is just an ATX-sized version of my mATX motherboard - I decided to risk it. I put all the parts together, turned the machine on and... zero issues. Win! After a couple of months of care-free usage (well, not quite, but those issues were related to having both Windows and Linux on the same machine), I started to do some light overclocking using standard voltages. While going through the motions of testing my OC'd system I ran into an issue with RealBench stress test, which gave an error message of "result mismatch" after every test cycle. What's worse, this happened even at stock settings. My first thought was that maybe the memory modules weren't working as they should after all, even though the overclocked system had passed 8 hours of Prime95 blend test with six workers and 2 GB RAM and a quick, one hour run of Prime95 blend test with six workers and 16 GB RAM without any errors. I decided to test my RAM using MemTest86 v6.2.0 to see if I had just gotten lucky with Prime95. I started with a quick test using the default values and only let the test finish one pass, which it did without errors. As I was trying to pin down a problem I was experiencing with RealBench stress test, I thought I should probably run the test in parallel mode, since the stress test involves heavy multitasking. However, when I reached Test 2 (address test, own address, parallel) the test just stopped progressing. It didn't freeze totally, mind you. The timer was still running and the icons representing CPU core activity were spinning - except for CPU1, which showed a "W" - so I thought I just needed to give the test some time. Six hours later only the time on the counter had changed. So I tried again. The second time around CPU1 started working as well, but almost immediately after that the computer just rebooted. There was no blue screen or any found memory errors that I could see, just a reboot. I decided to run the default test on each of the separate cores to see if CPU1 was somehow anomalous. So I started from CPU0 and checked if the CPUs could get past Test 2. This is what I saw: CPU0: OK CPU1: MemTest86 freezes before anything is tested. The testing screen appears, but the timer is dead from the start and the system doesn't respond to anything from the keyboard. CPU2: See CPU1 CPU3: OK CPU4: See CPU1 CPU5: See CPU1 Just to be clear: This was at stock settings, and on stock setting I hadn't had any issues running multi-core tasks - except for the RealBench stress test. Roughly ten different benchmark tests (including the RealBench benchmark), Windows, Linux, a couple of games - all had run using up to all six cores without any instability issues. After encountering this issue with MemTest86 I got a bit worried and also ran Windows Memory Diagnostic Tool. I started with the standard test, which finished 1 pass without errors before I decided to switch to the extended test. The extended test got me worried again, since it seemed to stall at 21%. After that I decided to tweak the memory settings a bit. The thing is, the stock values the motherboard set for the RAM were 1333 MHz CL9 (due to Phenom II) and 1.585 V, which were not the official values for these modules, so I decided to change the values to match the ones given by the manufacturer: 1600 MHz CL10 (I manually set all timing values to match the SPD values for this clock frequency) and 1.5 V. Then I ran the extended test again. Turns out the extended test just takes several hours to move past the 21% mark! In the end I ran the test for 26 hours, clearing 4 full passes with no errors found. I'm sure I would have had the same result had I had the patience to wait when I had my RAM at "stock" values. Unfortunately the changes I had made also had zero effect on MemTest86 and RealBench... While passing a Windows Memory Diagnostic Tool test was no guarantee that MemTest86 wouldn't find an error, I was beginning to wonder if this was a UEFI-related issue. I had had a bit of trouble booting to MemTest86 and for some reason it just didn't want to start around 50% of the time. I would just see a sliver of my normal UEFI background picture in the upper edge of my monitor and that was it. If this happened, a reboot and retry had so far been all that it has taken to get MemTest to run. As I had changed the RAM settings, I decided to I run the parallel test again just in case; the system rebooted after reaching Test 2, just like it did before. The log file of this latest pass has this to say about Test 2: 2015-10-06 04:05:05 - MtSupportRunAllTests - Test execution time: 12.856 (Test 1 cumulative error count: 0) 2015-10-06 04:05:05 - GetAMD10Temp - Temperature: 31 2015-10-06 04:05:05 - Running test #2 (Test 2 [Address test, own address]) 2015-10-06 04:05:05 - MtSupportRunAllTests - Setting random seed to 0x50415353 2015-10-06 04:05:05 - MtSupportRunAllTests - Start time: 15676 ms 2015-10-06 04:05:05 - ReadMemoryRanges - Available Pages = 4134591 2015-10-06 04:05:05 - MtSupportRunAllTests - Enabling memory cache for test 2015-10-06 04:05:05 - MtSupportRunAllTests - Enabling memory cache complete 2015-10-06 04:05:05 - Start memory range test (0x0 - 0x440000000) 2015-10-06 04:05:05 - Pre-allocating memory ranges >=16MB first... 2015-10-06 04:05:05 - All memory ranges successfully locked 2015-10-06 04:05:05 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 0ms) 2015-10-06 04:05:06 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 4ms) 2015-10-06 04:05:06 - RunMemoryRangeTest - CPU #3 timed out, test time = 0ms (BSP test time = 4ms) 2015-10-06 04:05:07 - RunMemoryRangeTest - CPU #2 completed but did not signal (test time = 5ms, event wait time = 1012ms, result = Success) (BSP test time = 4ms) 2015-10-06 04:05:07 - RunMemoryRangeTest - Could not start AP#2 0x0000000005100000 - 0x0000000009100000 (Not Ready). Resetting... 2015-10-06 04:05:08 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 159ms) 2015-10-06 04:05:08 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 172ms) 2015-10-06 04:05:08 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 170ms) 2015-10-06 04:05:09 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 168ms) 2015-10-06 04:05:10 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 167ms) 2015-10-06 04:05:10 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 168ms) 2015-10-06 04:05:11 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 146ms) 2015-10-06 04:05:11 - RunMemoryRangeTest - CPU #4 timed out, test time = 0ms (BSP test time = 146ms) 2015-10-06 04:05:12 - RunMemoryRangeTest - CPU #3 completed but did not signal (test time = 142ms, event wait time = 1001ms, result = Success) (BSP test time = 146ms) 2015-10-06 04:05:12 - RunMemoryRangeTest - Could not start AP#3 0x00000000AB035AA0 - 0x00000000ABFD07F0 (Not Ready). Resetting... 2015-10-06 04:05:12 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 32ms) I asked about this on the PassMark forum and it was suggested that it may be a UEFI-related bug with the multiprocessing subsystem. I don't know if this is correct or not, but to me it doesn't sound very far fetched. Would anyone here know if this truly is just a firmware issue and if so, could it also explain the problems I'm having with RealBench? TLDR: CPU cores misbehaving in MemTest86 v6.2.0. Maybe a bug in UEFI, is there any hope of a fix?

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 22703	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 07 Oct 2015 at 1:26pm
	Welcome to the forums Given that you have been trying to overclock the first thing I would do is clear CMOS, I always recommend this method as it is basically foolproof. Whenever there is a suspicion that a problem could be a UEFI issue this is where you start. Next, make sure you have the latest BIOS for your board. Though make sure you use the instant flash option especially if your system is showing any signs of instability in the OS. The UEFI should only use core 0 for its operation so there should not be a risk of your issues effecting the flash. Now if this does not correct the issue there are a few more things you can do to see where the problem is. Your CPU is a hex core Phenom so if there is an issue with the UEFI it may be that the UEFI is trying to handle your Phenom in the same way it would a 6 core FX CPU which uses a different architecture. What you can do here is use the "CPU Active Core Control" feature in your BIOS and disable the last 2 cores and see if the problem occurs using only 4 cores. If it does not then it is very likely that the UEFI is mishandling your CPU and if it does there is clearly still a problem. At this point you can contact ASRock tech support, inform them about your particular issues and link them to this thread. They are usually pretty good with providing UEFI fixes.

PetrolHead Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 07 Oct 2015 Status: Offline Points: 403	Post Options Post Reply Quote PetrolHead Report Post Thanks(0) Quote Reply Posted: 07 Oct 2015 at 11:28pm
	Thank you for the advice. I did as you instructed, but unfortunately the issue was not resolved. When I ran the MemTest86 in parallel mode after having deactivated the last two cores, I "cleared" Test 2 (CPU1 didn't activate, but stayed in "W" mode) and after reaching Test 3 the computer rebooted. This is what the logfile looks like after Test1 now: 2015-10-07 18:07:23 - MtSupportRunAllTests - Test execution time: 13.186 (Test 1 cumulative error count: 0) 2015-10-07 18:07:23 - GetAMD10Temp - Temperature: 29 2015-10-07 18:07:23 - Running test #2 (Test 2 [Address test, own address]) 2015-10-07 18:07:23 - MtSupportRunAllTests - Setting random seed to 0x50415353 2015-10-07 18:07:23 - MtSupportRunAllTests - Start time: 16141 ms 2015-10-07 18:07:23 - ReadMemoryRanges - Available Pages = 4134596 2015-10-07 18:07:23 - MtSupportRunAllTests - Enabling memory cache for test 2015-10-07 18:07:23 - MtSupportRunAllTests - Enabling memory cache complete 2015-10-07 18:07:23 - Start memory range test (0x0 - 0x440000000) 2015-10-07 18:07:23 - Pre-allocating memory ranges >=16MB first... 2015-10-07 18:07:23 - All memory ranges successfully locked 2015-10-07 18:07:24 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 0ms) 2015-10-07 18:07:24 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 5ms) 2015-10-07 18:07:24 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:24 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:24 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:25 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:25 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 124ms) 2015-10-07 18:07:25 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:25 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:25 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:25 - RunMemoryRangeTest - CPU #2 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:26 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 139ms) 2015-10-07 18:07:26 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:26 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 109ms) 2015-10-07 18:07:26 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 28ms) 2015-10-07 18:07:26 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 2ms) 2015-10-07 18:07:26 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 22ms) 2015-10-07 18:07:27 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:27 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:27 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:27 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:27 - RunMemoryRangeTest - CPU #2 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:27 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:28 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:28 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:28 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:28 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 124ms) 2015-10-07 18:07:29 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:29 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:29 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:29 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:29 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 135ms) 2015-10-07 18:07:30 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:30 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 136ms) 2015-10-07 18:07:30 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:30 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:31 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 134ms) 2015-10-07 18:07:31 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 137ms) 2015-10-07 18:07:31 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:31 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 139ms) 2015-10-07 18:07:31 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 139ms) 2015-10-07 18:07:32 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 136ms) 2015-10-07 18:07:32 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:32 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 139ms) 2015-10-07 18:07:32 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:33 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:33 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 128ms) 2015-10-07 18:07:33 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:33 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:33 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:34 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 140ms) 2015-10-07 18:07:34 - RunMemoryRangeTest - CPU #2 timed out, test time = 0ms (BSP test time = 140ms) 2015-10-07 18:07:34 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 140ms) 2015-10-07 18:07:34 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:34 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:35 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:35 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 136ms) 2015-10-07 18:07:35 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:35 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:35 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:36 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 139ms) 2015-10-07 18:07:36 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 136ms) 2015-10-07 18:07:36 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:36 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:37 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:37 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:37 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 128ms) 2015-10-07 18:07:37 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:37 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:38 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 139ms) 2015-10-07 18:07:38 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 138ms) 2015-10-07 18:07:38 - Cleanup - Releasing all memory ranges... 2015-10-07 18:07:38 - MtSupportRunAllTests - Test execution time: 14.609 (Test 2 cumulative error count: 0) 2015-10-07 18:07:38 - GetAMD10Temp - Temperature: 28 2015-10-07 18:07:38 - Running test #3 (Test 3 [Moving inversions, ones & zeroes]) 2015-10-07 18:07:39 - MtSupportRunAllTests - Setting random seed to 0x50415353 2015-10-07 18:07:39 - MtSupportRunAllTests - Start time: 31573 ms 2015-10-07 18:07:39 - ReadMemoryRanges - Available Pages = 4134596 2015-10-07 18:07:39 - MtSupportRunAllTests - Enabling memory cache for test 2015-10-07 18:07:39 - MtSupportRunAllTests - Enabling memory cache complete 2015-10-07 18:07:39 - Start memory range test (0x0 - 0x440000000) 2015-10-07 18:07:39 - Pre-allocating memory ranges >=16MB first... 2015-10-07 18:07:39 - All memory ranges successfully locked 2015-10-07 18:07:39 - RunMemoryRangeTest - CPU #1 timed out, test time = 0ms (BSP test time = 0ms) 2015-10-07 18:07:40 - RunMemoryRangeTest - CPU #3 completed but did not signal (test time = 1ms, event wait time = 1001ms, result = Success) (BSP test time = 0ms) 2015-10-07 18:07:40 - RunMemoryRangeTest - Could not start AP#3 0x0000000000880000 - 0x0000000000C40000 (Not Ready). Resetting... I'll now follow your last bit of advice and contact the ASRock technical support.

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 22703	Post Options Post Reply Quote Xaltar Report Post Thanks(0) Quote Reply Posted: 08 Oct 2015 at 2:06am
	Even if disabling core helped you still would have needed to contact Tech support, it just would have narrowed down the problem for them a little Good luck, hopefully they will help you get your problem sorted quickly.

PetrolHead Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 07 Oct 2015 Status: Offline Points: 403	Post Options Post Reply Quote PetrolHead Report Post Thanks(0) Quote Reply Posted: 14 Oct 2015 at 10:18am
	Just wanted to report that they replied the next day with three pieces of advice: 1. Check that you have default values in BIOS. (I had already told them I had returned the BIOS to default values.) 2. Try another CPU. (Like I have extra Phenom II's lying around...) 3. Try another software. (AFAIK there's not a huge number of UEFI-compatible memory tests that allow the user to choose to run the test in parallel mode. The number "1" springs to mind...) I replied, explained the situation and asked for suggestions on programs I could use to narrow down the issue, but I haven't heard from them since. Luckily MemTest86+ and RealBench 2.41 stress test are the only programs I seem to have (possibly unrelated) issues with. I don't expect many others to have the same motherboard and CPU combination, which probably means that trying to pin down and fix the issue might not rank high on ASRock's list of priorities... Edited by PetrolHead - 14 Oct 2015 at 10:24am
	Ryzen 5 1500X, ASRock AB350M Pro4, 2x8 GB G.Skill Trident Z 3466CL16, Sapphire Pulse RX Vega56 8G HBM2, Corsair RM550x, Samsung 960 EVO SSD (NVMe) 250GB, Samsung 850 EVO SSD 500 GB, Windows 10 64-bit

PetrolHead Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 07 Oct 2015 Status: Offline Points: 403	Post Options Post Reply Quote PetrolHead Report Post Thanks(0) Quote Reply Posted: 26 Oct 2015 at 6:46pm
	Seems like ASRock tech support won't be of any help. They e-mailed me some time ago and just suggested I use some other program to test my computer. I'll just have to wait and see if the next BIOS update - assuming there will be one - will do more than just make the UEFI menu look a bit nicer.
	Ryzen 5 1500X, ASRock AB350M Pro4, 2x8 GB G.Skill Trident Z 3466CL16, Sapphire Pulse RX Vega56 8G HBM2, Corsair RM550x, Samsung 960 EVO SSD (NVMe) 250GB, Samsung 850 EVO SSD 500 GB, Windows 10 64-bit