[RPi4] Crashing Repeatedly During Movie

rickylovespi · April 7, 2025 at 2:40 AM

Hello,

I tried watching this movies on my Raspberry Pi 4, and on at least twice but I think 3 times during the movie, the screen suddenly went black, forcing me to reset the device and pick back up where I left off. I have posted the mediainfo and system log below.

I very much appreciate any help in isolating the problem!

Thanks

mediainfo:

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings : CABAC / 9 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 9 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 2 h 3 min
Bit rate : 15.7 Mb/s
Width : 1 200 pixels
Height : 720 pixels
Display aspect ratio : 5:3
Frame rate mode : Constant
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.759
Stream size : 13.6 GiB (98%)
Title : npuer @ NPUBits
Writing library : x264 core 161 r3027+53 2464769 t_mod_New [(8 & 10)-bit@all X86_64]
Encoding settings : cabac=1 / ref=9 / deblock=1:-3:-3 / analyse=0x3:0x133 / me=umh / subme=11 / psy=1 / fade_compensate=0.00 / psy_rd=1.18:0.00 / mixed_ref=1 / me_range=64 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-2 / threads=24 / lookahead_threads=5 / sliced_threads=0 / nr=0 / decimate=0 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / fgo=0 / bframes=16 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=24 / scenecut=40 / intra_refresh=0 / rc_lookahead=250 / rc=crf / mbtree=0 / crf=17.4000 / qcomp=0.63 / qpmin=0:0:0 / qpmax=69:69:69 / qpstep=4 / vbv_maxrate=62500 / vbv_bufsize=78125 / crf_max=0.0 / nal_hrd=none / filler=0 / ip_ratio=1.30 / pb_ratio=1.20 / aq=3:0.68 / aq-sensitivity=10.00 / aq-factor=1.00:1.00:1.00 / aq2=0 / aq3=0 / zones=175911,177774,crf=22.0
Language : English
Default : Yes
Forced : No
Color range : Limited
Matrix coefficients : BT.709

system log:

Actually it was too long to paste straight in (43000 characters), so if you can specify which section of the log that is necessary I should be able to just paste that in, or put it on pastebin I guess.

**chewitt** · April 7, 2025 at 6:14 AM

Please provide a full debug log.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

rickylovespi · April 15, 2025 at 5:42 AM

Quote from chewitt

Please provide a full debug log.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

Hi Chewitt, I tried to replicate the problem just now and it didn't seem to crop back up again. That said, I have a couple questions:

1. Is there a way to have debug logging enabled without the distracting debug OSD, so I can watch movies in debug logging mode without the distraction?
2. I hear these debug logs are "volatile". Does that mean they only last for one crash, and then if I turn the pi off manually, the logs from the crash will be gone?

Thanks

**chewitt** · April 15, 2025 at 9:54 AM

XML

<?xml version="1.0" encoding="utf-8" ?>
<advancedsettings version="1.0">
  <loglevel hide="false">1</loglevel>
</advancedsettings>

That ^ content will enable debug logging without the OSD.

The current log is /storage/.kodi/temp/kodi.log and previous log is kodi.old.log, there are kodi crashlog(s) in the same folder. The current and previous log are rotated with each reboot so they are persistent but not preserved. Crashlogs are preserved.

rickylovespi · May 10, 2025 at 4:23 AM

I have experienced the crash again multiple times during the viewing of the same movie, here is the log from that: https://paste.libreelec.tv/striking-fly.log

I did not have debug logs on because I was watching the movie

I guess I'll have to try the commands to hide it.

**HiassofT** · May 10, 2025 at 9:42 AM Best Answer

Use a proper power supply - I recommend the official one from RPi.

Code

RPi throttled=0x50005
...
Feb 27 17:26:05.089246 LibreELEC kernel: hwmon hwmon0: Undervoltage detected!

so long,

Hias

sittich · May 10, 2025 at 5:06 PM

Not only that (proper power supply). Additionally, obtain contact spray and contactoil. I have frequently encountered issues with my Raspberry Pi crashing due to poor connections between plugs and sockets. This is often the case when the atmospheric humidity is high. The moisture slowly but steadily infiltrates the contact points over a period of months, causing corrosion, such as sulfide layers, which lead to increased contact resistance, resulting in voltage drops when high currents are drawn.

Spray the plug and/or socket with contact spray (using the long spray tube) and allow it to act according to the manufacturer's instructions. This will dissolve the solid corrosion. It may be necessary to follow up with a contact cleaner, as the contact spray itself leaves residues once it dries.
Finally, lightly mist the plug or socket with contactoil. This ensures that no moisture can seep in between. If too much is accidentally sprayed, excess can be absorbed with toilet paper.

This is my approach, including with connectors for DSL, HDMI connectors, particularly those that have not been used for an extended period, etc.
The use of contactoil at the end of the cleaning procedure is my secret tip!

rickylovespi · May 10, 2025 at 8:01 PM

Quote from HiassofT
Use a proper power supply - I recommend the official one from RPi.
Code
RPi throttled=0x50005
...
Feb 27 17:26:05.089246 LibreELEC kernel: hwmon hwmon0: Undervoltage detected!
so long,
Hias

Thank you!

It turns out that I did have a proper 5.1V 3A power supply that came with it, but at some point the wires got mixed up with a USB-C cable which was plugged into the USB port of my nintendo switch! I guess it was operating on 5V 1A or so. That would do it!