SOLVED Concerning results with Breakin test, but not Memtest86?

[Fire-Dragon-DoL]

Hello,
I'm in a weird situation. I ran memtest86 for 24 hours (more than 3 pass) and it yield no errors.

Then, I start "Breakin" software suggested here: https://www.familybrown.org/dokuwiki/doku.php?id=fester:intro
Which doesn't mention my E5 2650 v2 in the compatibility list.

I get a FAIL on "ecc" within 55s and I can consistently get that error at the same second.
How reliable is this test? Are there any alternatives for CPU testing? The error seems related to the RAM, but memtest86 didn't see any in 24 hours, this one spots it in 50 seconds!

Code:

=================================================================
  New breakin test started
=================================================================
Mobo : Supermicro - X9DR3-F
BIOS : 3.0a
CPU  : 32 x Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz (2600 MHz)
RAM  : 1% - 456.0 MB / 32212.55 MB
HDD  : No hard disk drives found
NIC  : eth1 192.168.1.189 (00:25:90:ec:5b:61)

MSG 00h 00m 03s Running memory performance benchmark
00h 00m 03s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 00m 03s : test:ecc  pass:0 fail:0 lastmsg:
00h 00m 03s : test:hpl  pass:0 fail:0 lastmsg:
00h 00m 03s : test:mcelog  pass:0 fail:0 lastmsg:
00h 00m 03s : test:failid  pass:0 fail:0 lastmsg:
00h 00m 03s : test:hdhealth  pass:0 fail:0 lastmsg:
00h 00m 03s : test:badblocks  pass:0 fail:0 lastmsg:
MSG 00h 00m 03s Starting burnin tests
MSG 00h 00m 03s Disabling burnin test 'hdhealth'
MSG 00h 00m 03s Disabling burnin test 'badblocks'
00h 00m 33s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 00m 33s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 00m 33s : test:hpl  pass:0 fail:0 lastmsg:
00h 00m 33s : test:mcelog  pass:2 fail:0 lastmsg:
00h 00m 33s : test:failid  pass:8 fail:0 lastmsg:
00h 00m 33s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 00m 33s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
ERR 00h 00m 55s Feb  7 22:23:41 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 55s Feb  7 22:23:41 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 55s Feb  7 22:23:41 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 55s Feb  7 22:23:41 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 55s Feb  7 22:23:41 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 55s Feb  7 22:23:41 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 55s Feb  7 22:23:41 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 55s Feb  7 22:23:41 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 55s Feb  7 22:23:41 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 56s Feb  7 22:23:42 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 56s Feb  7 22:23:42 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 56s Feb  7 22:23:42 (none) daemon.err udevd[1122]: failed to create queue file: No space left on device
ERR 00h 00m 56s Feb  7 22:23:42 (none) daemon.err udevd[1122]: failed t
00h 01m 03s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 01m 03s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 01m 03s : test:hpl  pass:0 fail:0 lastmsg:
00h 01m 03s : test:mcelog  pass:2 fail:0 lastmsg:
00h 01m 03s : test:failid  pass:8 fail:0 lastmsg:
00h 01m 03s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 01m 03s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 01m 33s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 01m 33s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 01m 33s : test:hpl  pass:0 fail:0 lastmsg:
00h 01m 33s : test:mcelog  pass:2 fail:0 lastmsg:
00h 01m 33s : test:failid  pass:8 fail:0 lastmsg:
00h 01m 33s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 01m 33s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 02m 03s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 02m 03s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 02m 03s : test:hpl  pass:0 fail:0 lastmsg:
00h 02m 03s : test:mcelog  pass:2 fail:0 lastmsg:
00h 02m 03s : test:failid  pass:8 fail:0 lastmsg:
00h 02m 03s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 02m 03s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 02m 33s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 02m 33s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 02m 33s : test:hpl  pass:0 fail:0 lastmsg:
00h 02m 33s : test:mcelog  pass:2 fail:0 lastmsg:
00h 02m 33s : test:failid  pass:8 fail:0 lastmsg:
00h 02m 33s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 02m 33s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 03m 03s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 03m 03s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 03m 03s : test:hpl  pass:0 fail:0 lastmsg:
00h 03m 03s : test:mcelog  pass:2 fail:0 lastmsg:
00h 03m 03s : test:failid  pass:8 fail:0 lastmsg:
00h 03m 03s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 03m 03s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 03m 33s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 03m 33s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 03m 33s : test:hpl  pass:0 fail:0 lastmsg:
00h 03m 33s : test:mcelog  pass:2 fail:0 lastmsg:
00h 03m 33s : test:failid  pass:8 fail:0 lastmsg:
00h 03m 33s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 03m 33s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 04m 03s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 04m 03s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 04m 03s : test:hpl  pass:0 fail:0 lastmsg:
00h 04m 03s : test:mcelog  pass:2 fail:0 lastmsg:
00h 04m 03s : test:failid  pass:8 fail:0 lastmsg:
00h 04m 03s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 04m 03s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 04m 33s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 04m 33s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 04m 33s : test:hpl  pass:0 fail:0 lastmsg:
00h 04m 33s : test:mcelog  pass:2 fail:0 lastmsg:
00h 04m 33s : test:failid  pass:8 fail:0 lastmsg:
00h 04m 33s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 04m 33s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 05m 03s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 05m 03s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 05m 03s : test:hpl  pass:0 fail:0 lastmsg:
00h 05m 03s : test:mcelog  pass:2 fail:0 lastmsg:
00h 05m 03s : test:failid  pass:8 fail:0 lastmsg:
00h 05m 03s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 05m 03s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 05m 33s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 05m 33s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 05m 33s : test:hpl  pass:0 fail:0 lastmsg:
00h 05m 33s : test:mcelog  pass:2 fail:0 lastmsg:
00h 05m 33s : test:failid  pass:8 fail:0 lastmsg:
00h 05m 33s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 05m 33s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 06m 03s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 06m 03s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 06m 03s : test:hpl  pass:0 fail:0 lastmsg:
00h 06m 03s : test:mcelog  pass:2 fail:0 lastmsg:
00h 06m 03s : test:failid  pass:8 fail:0 lastmsg:
00h 06m 03s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 06m 03s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 06m 33s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 06m 33s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 06m 33s : test:hpl  pass:0 fail:0 lastmsg:
00h 06m 33s : test:mcelog  pass:2 fail:0 lastmsg:
00h 06m 33s : test:failid  pass:8 fail:0 lastmsg:
00h 06m 33s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 06m 33s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 07m 03s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 07m 03s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 07m 03s : test:hpl  pass:0 fail:0 lastmsg:
00h 07m 03s : test:mcelog  pass:2 fail:0 lastmsg:
00h 07m 03s : test:failid  pass:8 fail:0 lastmsg:
00h 07m 03s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 07m 03s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found
00h 07m 33s : temps:30.0C  30.0C  31.0C  36.0C  43.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  29.0C  31.0C  31.0C  31.0C  31.0C
00h 07m 33s : test:ecc  pass:3 fail:1 lastmsg:No ECC errors found
00h 07m 33s : test:hpl  pass:0 fail:0 lastmsg:
00h 07m 33s : test:mcelog  pass:2 fail:0 lastmsg:
00h 07m 33s : test:failid  pass:8 fail:0 lastmsg:
00h 07m 33s : test:hdhealth  pass:1 fail:0 lastmsg:No disk devices found
00h 07m 33s : test:badblocks  pass:1 fail:0 lastmsg:No disk devices found

Last but not least, it keeps complaining of having udevd full, no idea why or how. I used "Rufus" to burn the image on the usb drive, because the suggested software didn't yield anything functional.

EDIT: Starting the 3rd option (start with console, so no standard settings and no SSH I guess), I get no errors. I'll be running it for an hour and try to go back to the first configuration and see what happens.
I'm feeling like this is a problem with the software rather than my ram.

I'll also let memtest86 run for the night again.

 

[Chris Moore]

EDIT: Starting the 3rd option (start with console, so no standard settings and no SSH I guess), I get no errors. I'll be running it for an hour and try to go back to the first configuration and see what happens.
I'm feeling like this is a problem with the software rather than my ram.

I am pretty certain it is a software error, not a hardware error. I wouldn't worry about this test because it is really about testing the thermals. If the system is passing MemTest, the CPU must be working.

 

[Fire-Dragon-DoL]

I am pretty certain it is a software error, not a hardware error. I wouldn't worry about this test because it is really about testing the thermals. If the system is passing MemTest, the CPU must be working.

Looks like I got the error again with the software, even after starting with the console only.

My luck with HW is really bad, so to stay safe, I'll run memtest86 24 hours again, this time the latest uefi based version.

I learned a lot of stuff about ipmi but I had to use internet explorer to access it, due to the java applet requirement. Oh man, don't they have a more up to date thing? Sigh.

I learned a lot of stuff trying to make that memtest86 uefi image work (before finding the motherboard config "uefi", lol)

 

[Fire-Dragon-DoL]

I am pretty certain it is a software error, not a hardware error. I wouldn't worry about this test because it is really about testing the thermals. If the system is passing MemTest, the CPU must be working.

I ran it for additional 24 hours. No issues with memtest, so I'm feeling safe honestly, thanks!

 

[pro lamer]

Just from the top of my noob head: have you ruled out overheating issues? I mean I can't remember if memtest86 stresses the CPU so I am trying to guess that if it did not but breakin did then the CPU may overheat only during breakin running...

Sent from my phone

 

[Fire-Dragon-DoL]

Just from the top of my noob head: have you ruled out overheating issues? I mean I can't remember if memtest86 stresses the CPU so I am trying to guess that if it did not but burnin did then the CPU may overheat only during burnin running...

Sent from my phone

Based on my reading, memtest stresses the CPU too. What other tests would you recommend instead of memtest? I'm clearly open to try a third solution!

 

[Fire-Dragon-DoL]

Just from the top of my noob head: have you ruled out overheating issues? I mean I can't remember if memtest86 stresses the CPU so I am trying to guess that if it did not but burnin did then the CPU may overheat only during burnin running...

Sent from my phone

P.S.
Even with cpu intensive operations, I never saw the CPU going over 52-53 degrees (celsius)

 

[pro lamer]

What other tests would you recommend instead of memtest? I'm clearly open to try a third solution!

Well, there are so many of them... I'll try to answer from my experience then :)

First of all you can try memtest86.org memtest86.com (they have a free version).

Now some guessing:

• E5 2650 v2 has hyper threading. Does breakin use multiple threads/cores? You can try rerunning breakin with ht disabled
• Does breakin use multiple threads/cores? I had problems with some memory testing software when running multithreaded/multicore and limiting the software to one core helped
• I've heard of memtest64 (if you are ok with installing a trial version of Windows 10. Edit: unless there is no such thing. I.e. I'm not sure of the license)
• And more software stressing CPUs...

Sent from my phone

 

[Fire-Dragon-DoL]

Well, there are so many of them... I'll try to answer from my experience then :)

First of all you can try memtest86.org (they have a free version).

Now some guessing:

• E5 2650 v2 has hyper threading. Does breakin use multiple threads/cores? You can try rerunning breakin with ht disabled
• Does breakin use multiple threads/cores? I had problems with some memory testing software when running multithreaded/multicore and limiting the software to one core helped
• I've heard of memtest64 (if you are ok with installing a trial version of Windows 10. Edit: unless there is no such thing. I.e. I'm not sure of the license)
• And more software stressing CPUs...

Sent from my phone

Memtest86.org does not exist anymore (there is the .com one, which is the one I used). I tested with the open source version the first time and no problem.

I can't go through the trouble of installing win10, but it's also pointless: memtest86 has a lower level access which is definitely a better idea in this case.

I don't remember about multithread usage on breakin. Memtest86 made sure to disable it for the tests though

 

[Fire-Dragon-DoL]

Well, there are so many of them... I'll try to answer from my experience then :)

First of all you can try memtest86.org (they have a free version).

Now some guessing:

• E5 2650 v2 has hyper threading. Does breakin use multiple threads/cores? You can try rerunning breakin with ht disabled
• Does breakin use multiple threads/cores? I had problems with some memory testing software when running multithreaded/multicore and limiting the software to one core helped
• I've heard of memtest64 (if you are ok with installing a trial version of Windows 10. Edit: unless there is no such thing. I.e. I'm not sure of the license)
• And more software stressing CPUs...

Sent from my phone

Heads up, following your suggestions, I disabled hyperthreading and... TA-DAH! Breakin is not showing errors anymore.
This, plus the combo with memtest running for so long sets me to a very safe spot at this point!

 

[pro lamer]

Memtest86.org does not exist any more

Thanks, I'll correct it, I was writing from the top of my head. I used memtest86.com v7.x and memtest86+ v5.x

Sent from my phone

 

[pro lamer]

multithread usage on breakin. Memtest86 made sure to disable it

Memtest86.com worked for me multicore and hyper threading was somehow bypassed by this software - the software started exactly 4 threads/processes on a 4 core 8 threaded CPU (i7-7700). In the beginning I was surprised so I emailed the company and they answered thatb by default hyperthreading isn't used. They wrote that they don't use it because it doesn't speed up memory access. Moreover they claimed it slows it down slightly

OTOH the software that didn't work multicore for me was memtest86+ v5.x but later I found on the internet that it is a known case.

sent from my phone