Raspberry Pi 3 B+ lockups

[e-raser]

@leon22 Click on my user ID and you will see an option to send a private message, but you may find it more convenient to email me at [email protected].

I PM´d dom yesterday, think I´ll need to wait until tomorrow.

[leon22]

Hi!

I have the same problem with my new Pi 3 B+! Always crashes with OpenElec during video playback or other operations like updating the library! So I bought my Model over Amazon -> how can I pm you or should I send it back to Amazon and order a new one?

Thank you!

PS: I did no Firmware updates or speed changes in config file

OpenELEC does not support RPi3+ - do you mean LibreELEC, or are you using Berryboot?

Yes, I mean LibreElec! (make the habit )

[leon22]

Since yesterday there is an LibreElec Update available due the issues with 3B+; so I was not the only one

Link: https://libreelec.tv/2018/04/libreelec- ... -8-2-5-mr/

Edit: But unfortunately it doesn't solves the problem (crash during library update 5 minutes ago)

[milhouse]

Since yesterday there is an LibreElec Update available due the issues with 3B+; so I was not the only one

Link: https://libreelec.tv/2018/04/libreelec- ... -8-2-5-mr/

Edit: But unfortunately it doesn't solves the problem (crash during library update 5 minutes ago)

Until we know this isn't a Kodi or LibreELEC issue, it may be best to start a thread on the LibreELEC forum. You should have a crash log in /storage/.kodi/temp/kodi_crash.log, please upload it to a pastebin site and include a link to the log in your post.

[leon22]

Since yesterday there is an LibreElec Update available due the issues with 3B+; so I was not the only one

Link: https://libreelec.tv/2018/04/libreelec- ... -8-2-5-mr/

Edit: But unfortunately it doesn't solves the problem (crash during library update 5 minutes ago)

Until we know this isn't a Kodi or LibreELEC issue, it may be best to start a thread on the LibreELEC forum. You should have a crash log in /storage/.kodi/temp/kodi_crash.log, please upload it to a pastebin site and include a link to the log in your post.

Thx, and I already created a thread on the LibreElec forum but there is no kodi_crash.log!

[LitterBugs]

Mine is still hanging every 24 hours or so even reduced to 1200/450. I'm swinging by MicroCenter today to swap it out.

Regards,
LitterBug

The local MicroCenter sells both Allied Electronics and Element 14 Pi 3 B+ models. There are actually some minor differences between the two. Wish I had taken pictures of my Allied that had been problematic to maybe identify differences in components.

Starting from scratch with a new Element 14 unit on stock clocking.

Regards,
LitterBug

[jimbojones]

Just wanted to report that I have also been experiencing hangups and stability issues since I upgraded from the 3B to the 3B+ (I reported it first hereviewtopic.php?f=28&t=211060).

I'm running my Pi as a PiHole DNS Server (which uses the Stubby daemon to get DNS-over-TLS), an OpenVPN server, a UniFi Controller, a SMB NAS using a USB WD PiDrive, and qBitTorrent box. This setup was running perfectly fine on my 3B, and I honestly don't remember the last time I had to reboot my 3B, but since swapping the sd card into a 3B+ I have had to do hard reboots (take the power cable out) on at least a weekly basis after my pi has hung. Sometimes it has occurred whilst i have been actively using the pi by connecting to the OpenVPN server or on an active ssh session, but many times it has occurred pretty randomly when I have been away from home and not using it.

I'm going to try changing the sdram frequency and see if that makes a difference, but it's a real shame we have to slow down our devices to fix this issue. Just a note, my pi also came in just a plastic static bag from the PiHut, and not in a box like all my previous Pi's came in (not sure if relevant, but I noticed a few people in this thread reporting issues with their 3B+'s had received their pi's without boxes).

[e-raser]

Regarding shipping boxes: probably not relevant. You can read on some of the posts above (page 5 or 6) those boxes are okay related to anti static functions. I don‘t think this is an issue. But hey how really knows, remember the flash of death on one of the last Pi‘s (I think series 2)? Hardware‘s tricky sometimes. But current indications don‘t point into that direction as you can read.

[horgh]

Still no crashes for me while running memtester.

I'm going to stop running these tests as I think I'm reaching undervolting where I assume I will see instability for other reasons. Please let me know if it would be useful in continuing to decrease these values and running memtester or doing any other tests.

14h at

Code: Select all

over_voltage_sdram_p=1
over_voltage_sdram_i=1

13h at

Code: Select all

over_voltage_sdram_p=0
over_voltage_sdram_i=1

9.5h at

Code: Select all

over_voltage_sdram_p=0
over_voltage_sdram_i=0

7h at

Code: Select all

over_voltage_sdram_p=-1
over_voltage_sdram_i=0

[Mig2008pt]

Hi, I am new to the raspberry pi community, this is my first raspberry pi, bought the 3B+ version with the official charger, i am using 2 SD cards, one for Retropie and another for Node-Red, MQTT and home automation related activities. I m experiencing the same problem, the board will freeze after a while of use, after 15 min. 30 min. 2 h. it is always the same, everything freezes, red light remains on, processor only a bit warm. Only have it for a couple days but like this i can't rely on this board. I am new to linux and this kind of boards, didn't know these are so problematic, looking into this forum I now see that this is not normal. hoping that the fault is found and problem is fixed. I will try every fix that is suggested here to see if change something. I wish i could help with with something more, but as i said, I m a beginner in this topic. Thanks

[crocky]

Thanks - you would be a good candidate for an exchange if you weren't so far away. Can we try adjusting some of the SDRAM parameters instead?

1. Start by installing memtester and capturing some of the current settings:

Code: Select all

[email protected]:~$ sudo apt-get install memtester
[email protected]:~$ vcgencmd get_config int | grep -E "(volt|sdram)"

2. Then put sdram_freq back to 500 and set over_voltage_sdram_p=4 and over_voltage_sdram_i=4, and reboot.
3. Run memtester to generate some heavy SDRAM traffic:

Code: Select all

[email protected]:~$ memtester 512M

If that is stable then you could back off either of the values and repeat, otherwise you could try pushing the over-voltages to 6.

I have waited until I managed to get a SD from a known good brand, I have that now and have put the latest stretch on it.

sdram_freq=500
over_voltage_sdram_p=4
over_voltage_sdram_i=4

and it is currently running memtester 512M and is in Loop7:

How long should I let it run?

I was running the-script on it before and it used to lockup every evening. The same the-script running on a raspberry pi 2 worked without a failure.

[PhilE]

Thank you to everybody who is running such exhaustive tests. Our priority is to increase our stock of failing boards beyond the one that we have (there are three more inbound).

If anyone has a board that fails "sudo MEMTESTER_TEST_MASK=0x1000 memtester 128M" in a few minutes with the default settings (no sdram_freq, arm_freq, over_voltage* etc.) who hasn't already PMd or emailed me ([email protected]), especially if you are in the UK, then please get in touch.

For everybody else, I suggest you fall back to "arm_freq=1200" and "sdram_freq=450" and wait for an update. With these settings your 3B+ should still be quicker under a sustained heavy workload than a 3B without a heatsink due to better heat spreading.

[Mig2008pt]

Thank you to everybody who is running such exhaustive tests. Our priority is to increase our stock of failing boards beyond the one that we have (there are three more inbound).

If anyone has a board that fails "sudo MEMTESTER_TEST_MASK=0x1000 memtester 128M" in a few minutes with the default settings (no sdram_freq, arm_freq, over_voltage* etc.) who hasn't already PMd or emailed me ([email protected]), especially if you are in the UK, then please get in touch.

For everybody else, I suggest you fall back to "arm_freq=1200" and "sdram_freq=450" and wait for an update. With these settings your 3B+ should still be quicker under a sustained heavy workload than a 3B without a heatsink due to better heat spreading.

Tested the command "sudo MEMTESTER_TEST_MASK=0x1000 memtester 128M" some times and it froze every time at:
"Bit Flip : testing 85"
"Bit Flip : testing 165"

Had to hard boot every time, this is the complete report for the third time. if froze at "Bit Flip: testing 11"
"
.***. Monday, 16 April 2018, 11:43:47 am UTC
***** Linux 4.14.30-v7+ armv7l GNU/Linux
`***'
|*| Filesystem Size Used Avail Use% Mounted on
|*| /dev/root 15G 7.6G 6.3G 55% /
..|*|.. Uptime.............: 0 days, 00h00m47s
.*** * ***. Memory.............: 549312kB (Free) / 766776kB (Total)
*******@@** Running Processes..: 113
`*****@@**' IP Address.........: 192.168.1.93
`*******' Temperature........: CPU: 52°C/125°F GPU: 51°C/123°F
`"""' The RetroPie Project, https://retropie.org.uk

[email protected]:~ $ vcgencmd get_config int
arm_freq=1400
audio_pwm_mode=514
config_hdmi_boost=5
core_freq=400
desired_osc_freq=0x33e140
desired_osc_freq_boost=0x3c45b0
disable_commandline_tags=2
disable_l2cache=1
display_hdmi_rotate=-1
display_lcd_rotate=-1
force_eeprom_read=1
force_pwm_open=1
framebuffer_ignore_alpha=1
framebuffer_swap=1
gpu_freq=300
hdmi_force_cec_address=65535
init_uart_clock=0x2dc6c00
lcd_framerate=60
over_voltage_avs=37500
over_voltage_avs_boost=0x23186
over_voltage_sdram_p=2
overscan_scale=1
pause_burst_frames=1
program_serial_random=1
sdram_freq=500
sdram_schmoo=0x2000020
[email protected]:~ $ sudo MEMTESTER_TEST_MASK=0x1000 memtester 128M
memtester version 4.3.0 (32-bit)
Copyright (C) 2001-2012 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffff000
using testmask 0x1000
want 128MB (134217728 bytes)
got 128MB (134217728 bytes), trying mlock ...locked.
Loop 1:
Stuck Address : ok
Bit Flip : testing 11
"
I will try now the same command with the 1200 and 450 values for arm_freq and sdram_freq.

[PhilE]

That's impressive. In a gap between tests, while the 3B+ is idle, can you run:

Code: Select all

$ vcgencmod read_ring_osc 1
$ vcgencmod read_ring_osc 2

[jamesh]

Mine is still hanging every 24 hours or so even reduced to 1200/450. I'm swinging by MicroCenter today to swap it out.

Regards,
LitterBug

The local MicroCenter sells both Allied Electronics and Element 14 Pi 3 B+ models. There are actually some minor differences between the two. Wish I had taken pictures of my Allied that had been problematic to maybe identify differences in components.

Starting from scratch with a new Element 14 unit on stock clocking.

Regards,
LitterBug

Surprised there are differences- they are all made in the same factory on the same production line so all components should be electrically the same. There might be colour difference - when you make >200k boards sometimes components colour change between batches.

[LitterBugs]

Surprised there are differences- they are all made in the same factory on the same production line so all components should be electrically the same. There might be colour difference - when you make >200k boards sometimes components colour change between batches.

The display and camera connectors were definitely different. The allied have yellow stick-on protectors over the connectors too. (like I said, minor differences) Can't rule out that different batches may have slightly different memory or memory from different batches. Pictures would have been a good idea for comparison. Sometimes the tiny details can have a huge impact....

At any rate, the replacement has been running on stock clocks over 24 hours now with no problems. Same SD with the same image reset to default clocking, same 2.5A power supply, Same powered USB SDR receiver, etc...

Regards,
LitterBug

[jamesh]

Surprised there are differences- they are all made in the same factory on the same production line so all components should be electrically the same. There might be colour difference - when you make >200k boards sometimes components colour change between batches.

The display and camera connectors were definitely different. The allied have yellow stick-on protectors over the connectors too. (like I said, minor differences) Can't rule out that different batches may have slightly different memory or memory from different batches. Pictures would have been a good idea for comparison. Sometimes the tiny details can have a huge impact....

At any rate, the replacement has been running on stock clocks over 24 hours now with no problems. Same SD with the same image reset to default clocking, same 2.5A power supply, Same powered USB SDR receiver, etc...

Regards,
LitterBug

Excellent news that the new ones is working. Does appear to be a very few outlier SoC's with this issue. Once we get yours in we should be able to make some decent progress finding the right settings.

[Mig2008pt]

That's impressive. In a gap between tests, while the 3B+ is idle, can you run:

Code: Select all

$ vcgencmod read_ring_osc 1
$ vcgencmod read_ring_osc 2

couldn't ran the commands;

[email protected]:~ $ $ vcgencmod read_ring_osc 1
-bash: $: command not found
[email protected]:~ $ $ vcgencmod read_ring_osc 2
-bash: $: command not found

I´m new to this things, must be doing it wrong, don't know...

With arm_freq=1200 and sdram_freq=450 set, ran the command "sudo MEMTESTER_TEST_MASK=0x1000 memtester 128M" again and it did 31 Loops without freezing. will keep these values set while the final solution is found
"
Loop 31:
Stuck Address : ok
Bit Flip : ok

[email protected]:~ $ /opt/vc/bin/vcgencmd measure_temp
temp=56.9'C
[email protected]:~ $ vcgencmd get_config int
arm_freq=1200
audio_pwm_mode=514
config_hdmi_boost=5
core_freq=400
desired_osc_freq=0x33e140
desired_osc_freq_boost=0x3c45b0
disable_commandline_tags=2
disable_l2cache=1
display_hdmi_rotate=-1
display_lcd_rotate=-1
force_eeprom_read=1
force_pwm_open=1
framebuffer_ignore_alpha=1
framebuffer_swap=1
gpu_freq=300
hdmi_force_cec_address=65535
init_uart_clock=0x2dc6c00
lcd_framerate=60
over_voltage_avs=31250
over_voltage_avs_boost=0x200b2
overscan_scale=1
pause_burst_frames=1
program_serial_random=1
sdram_freq=450
"

[RaTTuS]

Code: Select all

for a in 1 2 ; do  vcgencmd read_ring_osc $a; done

[Mig2008pt]

Code: Select all

for a in 1 2 ; do  vcgencmd read_ring_osc $a; done

[email protected]:~ $ for a in 1 2 ; do vcgencmd read_ring_osc $a; done
read_ring_osc(1)=16.794MHz (@1.2000V)
read_ring_osc(2)=3.064MHz (@1.2000V)
[email protected]:~ $ for a in 1 2 ; do vcgencmd read_ring_osc $a; done
read_ring_osc(1)=16.789MHz (@1.2000V)
read_ring_osc(2)=3.063MHz (@1.2000V)
[email protected]:~ $ for a in 1 2 ; do vcgencmd read_ring_osc $a; done
read_ring_osc(1)=16.799MHz (@1.2000V)
read_ring_osc(2)=3.062MHz (@1.2000V)
[email protected]:~ $ for a in 1 2 ; do vcgencmd read_ring_osc $a; done
read_ring_osc(1)=16.758MHz (@1.2000V)
read_ring_osc(2)=3.065MHz (@1.2000V)
[email protected]:~ $

This is what retrieves with the values currently set to "arm_freq=1200" and sdram_freq=450, Now i will try the command with the pi running the default frequency values, where the problem is at.

[Mig2008pt]

Whit the default values the command "for a in 1 2 ; do vcgencmd read_ring_osc $a; done" retrieves;

[email protected]:~ $ for a in 1 2 ; do vcgencmd read_ring_osc $a; done
read_ring_osc(1)=16.766MHz (@1.2000V)
read_ring_osc(2)=3.062MHz (@1.2000V)
[email protected]:~ $ for a in 1 2 ; do vcgencmd read_ring_osc $a; done
read_ring_osc(1)=16.794MHz (@1.2000V)
read_ring_osc(2)=3.063MHz (@1.2000V)

Ran the command "sudo MEMTESTER_TEST_MASK=0x1000 memtester 128M" and stoped it after few seconds before it freezes again, the values retrieve this time were;

[email protected]:~ $ sudo MEMTESTER_TEST_MASK=0x1000 memtester 128M
memtester version 4.3.0 (32-bit)
Copyright (C) 2001-2012 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffff000
using testmask 0x1000
want 128MB (134217728 bytes)
got 128MB (134217728 bytes), trying mlock ...locked.
Loop 1:
Stuck Address : ok
Bit Flip : setting 37^C
[email protected]:~ $ for a in 1 2 ; do vcgencmd read_ring_osc $a; done
read_ring_osc(1)=16.781MHz (@1.2000V)
read_ring_osc(2)=3.049MHz (@1.2000V)
[email protected]:~ $ for a in 1 2 ; do vcgencmd read_ring_osc $a; done
read_ring_osc(1)=16.781MHz (@1.2000V)
read_ring_osc(2)=3.055MHz (@1.2000V)

Now it is frozen again after MEMTESTER TEST with only reaching the Bit Flip : setting 6

[leon22]

Hi!


Here my test results (suggested by a member of the LibreElec board):

Code: Select all

 memtester 512M

Code: Select all

memtester version 4.3.0 (32-bit)
Copyright (C) 2001-2012 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffff000
want 512MB (536870912 bytes)
got  512MB (536870912 bytes), trying mlock ...locked.
Loop 1:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 2:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 3:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 4:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 5:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 6:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 7:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 8:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 9:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 10:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 11:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 12:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 13:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 14:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 15:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 16:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

No errors after 16 loops!

Code: Select all

vcgencmd get_throttled
throttled=0x0

So I tend to send my 3B+ back to Amazon to get a new one without this issues! What do you think?

Greets

[PhilE]

You don't say if you are running memtester with any custom frequency settings or the defaults.

[asavah]

3b+ from RS Components

Original RPF psu, small copper heatsink on the SoC.

Slightly overclocked as follows:

Code: Select all

arm_freq=1400
core_freq=500
desired_osc_freq=0x33e140
desired_osc_freq_boost=0x3c45b0
gpu_freq=500
over_voltage=2
over_voltage_avs=0x155cc
over_voltage_avs_boost=0x2f4d6
over_voltage_sdram=5
sdram_freq=580
sdram_schmoo=0x2000020

Code: Select all

vcgencmd get_throttled
throttled=0x0

MEMTESTER_TEST_MASK=0x1000 ./memtester 128M has been running for 2 hours, no issues.

[leon22]

You don't say if you are running memtester with any custom frequency settings or the defaults.

Defaults!