N64 crashes after 10 min

dankcushions

@endersenigma it could still be a heat issue - the gpu is particularly sensitive to heat. mine gets artefacts at v3d_freq=500. i think you should remove all the overclocks, and also update mupen64plus by source.

EndersEnigma

@dankcushions
trying that now, will update when i have some fidelity.

quicksilver

@endersenigma are you using a case? I had the same issue as you: https://retropie.org.uk/forum/topic/16657/mupen-glide-crashing

For me it turns out it was my nespi case causing issues. Once I removed my pi from the nespi case my issue was resolved.

EndersEnigma

@quicksilver
using an open air case with a fan, i also hear that the nespi case causes over heating.

EndersEnigma

@dankcushions

same crash at value
v3d_freq=500

this is quite frustrating.

dankcushions

@endersenigma i told you to remove the overclocks. that's still a VERY aggressive overclock. did you update, also?

quicksilver

@endersenigma have you tried running at stock speed? V3d=500 is still a huge overclock from the standard 300mhz. Your pi might not handle it. What is the exact case and power supply you are using?

The nespi case can cause overheating but that wasn't what happened in my issue. It was due to voltage. Restore your config.txt to default settings and report back

EndersEnigma

So the plot thickens, if I stop moving just before the freeze at 12 min almost exactly. It freezes for about 15 seconds but the audio keeps playing. If I let it sit till the graphics unfreeze then the game works great. The problem does not occur every 12 min after the first. Just right at the first 12 min.

However, if I am moving when the freeze starts or if I start moving' the audio stops and the freeze is permenant until I pull the power.

I have replicated this 4 times now. The next question is "why". Why right at the 12 min mark does this happen? And why doesn't it repeat at all after that first freeze?

EndersEnigma

@dankcushions
Without overclocks the games run very choppy and the audio skips a good bit.

Overclocking just the processor seems to fix that problem (1300) but the games are much smoother with the 3D overclock added.

Yes I have updated all packages and tools.

dankcushions

@endersenigma overclock = better performance, lower stability, if you're getting freezes, you need to disable the overclock until you've ruled that out as the cause.

EndersEnigma

@dankcushions
should i just go through the overclocks one by one till i find the culprit?

dankcushions

@endersenigma again, remove them ALL. then see if the crash happens still. if it does, it's a software bug and can be reported.

EndersEnigma

@dankcushions
gotcha. will do that tomorrow and report back.
Thanks for all the help mate.

EndersEnigma

@dankcushions
So I disabled all overclocks, the games still hang and crash (12-14 min of gameplay in). I am not sure what is causing this issue.

quicksilver

@endersenigma please post a copy of your config.txt just to make sure you didn't miss anything. Also what brand/model is your case and power supply? Please also list all devices hooked up to your pi (USB devices, fans, etc.)

EndersEnigma

@quicksilver
Canakit was my supplier. USB LOGITECH F310 controller is only device connected. Fan is powered by its own plug into the wall.

Config File: ~
#For more options and information see
#http://rpf.io/configtxt
#Some settings may impact device functionality. See link above for details

#uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

#uncomment this if your display has a black border of unused pixels visible
#and your display can output without overscan
#disable_overscan=1

#uncomment the following to adjust overscan. Use positive numbers if console
#goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

#uncomment to force a console size. By default it will be display's size minus
#overscan.
#framebuffer_width=1280
#framebuffer_height=720

#uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

#uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

#uncomment to force a HDMI mode rather than DVI. This can make audio work in
#DMT (computer monitor) modes
#hdmi_drive=2

#uncomment to increase signal to HDMI, if you have interference, blanking, or
#no display
#config_hdmi_boost=4

#uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=1350
#gpu_freq=500
#sdram_freq=500
#over_voltage=5
#v3d_freq=525

#Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

#Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

#Additional overlays and parameters are documented /boot/overlays/README

#Enable audio (loads snd_bcm2835)
dtparam=audio=on
#gpu_mem_256=128
#gpu_mem_512=256
#gpu_mem_1024=256
overscan_scale=1
gpu_mem=512
#dtoverlay=vc4-kms-v3d
#dtoverlay=vc4-fkms-v3d

quicksilver

@endersenigma GPU mem does not need to be higher than 256. No emulator on the pi comes close to using even that much. What case are you using? Do you have a different power supply you can try? I started with the canakit as well and switched. So it may be partially due to that power supply.

EndersEnigma

@quicksilver
the problem is isolated to the N64 emulator. I have no problems with dreamcast or PS1 even when overclocked. I doubt it is the PS but I can see if i have another one to try.

I just installed a new case today.
https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0ahUKEwj4h4vu9uLZAhUK04MKHYaQD9sQjRwIBg&url=https%3A%2F%2Fwww.amazon.com%2FRaspberry-Case-iUniker-Heatsink-Model%2Fdp%2FB01LXSMY1N&psig=AOvVaw3hcp5ycTZxKtvWN6msPblc&ust=1520811605504078

same issue even with new case.

I will drop down the gpu ram and see if that helps at all.

jonnykesh

@quicksilver he is giving half the RAM to the GPU. You are correct 256MB is more than enough. More is not always better.

quicksilver

@endersenigma did you read the thread that I linked earlier? Like I said I said, I had the same exact issue. Only happened with mupen64-glide. It was a voltage issue for me. I would try a different power supply and see if that solves it (I was also using a canakit when I had the issue)