N64 crashes after 10 min

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)

jonnykesh

@endersenigma who told you to give 512MB RAM to the GPU?

EndersEnigma

@jonnykesh
no change in performance, even the higher demand emulators from 256 to 512. More is better if you are checking to see where the bottleneck is. Since this is a great way to see if its a ram issue by giving more to the gpu, its a great way to troubleshoot if the amount of ram is an issue. My tests show its not in ram or gram. It doesnt seem to be in processor capability either as I have dumbed that down as well in my tests with minimal change till i get into the triple digits. I'm guessing its just a GPU limitation since I have ruled out just about everything else.

quicksilver

@endersenigma who told you that more is better? You are robbing your CPU of memory. Your GPU will never come close to using 512mb of ram. I'm not saying it's the solution to your current issue but you should leave it a 256.

EndersEnigma

@quicksilver
Is there a PS you would recommend since you had this exact same issue before?

EndersEnigma

@quicksilver
i had it set at 256, then 512 and now im running it at 640 just for kicks. No change in performance better or worse. I have also gone up and down on my proc speed (with my gram set lower of course) and the issue still persists. I dont even think the 3D freq setting is having much of an effect bringing it from 350-450 either. Not sure what is causing this stupid freeze problem in only one emulator. Since your case and possibly power supply seem to be behind your issue, I will try a new PS as soon as I can order one.

quicksilver

@endersenigma https://www.amazon.com/Mackertop-HSTNN-LA43-PA-1150-22HA-779573-001-761247-002/dp/B01HB44IE6

This is the one I switched to. However, even with this adaptor I still had issues until I took my pi out of my nespi case. Have you tried disconnecting your fan? (Again, no overclock until you figure out the issue).

quicksilver

@endersenigma increasing your clock speeds is NOT going to help with stability. Restore your default clock speed and mem split and leave it there until you figure out the issue.

EndersEnigma

@quicksilver
yep, all overclocks have been disabled and gram has been dropped back down to 256. I have disconnected the fan, no change. My old case didnt have a fan (i rigged one up that was powered externally, heat wasn't the issue, had the freeze before and after the fan).

Running stock config currently, ordering a new PS. I am skeptical about it being the power supply as it doesn't act like a power supply issue from other non-pi systems i have worked on. Only way to know is to try a different one out. Any other ideas in the mean time? Other than enjoy N64 13.5 minuets at a time? :P

EndersEnigma

I am almost curious if I should wipe that version of the N64 and install clean from binary, and see if the problem replicates prior to installing from source.

quicksilver

@endersenigma it's worth a shot. Although that didn't fix my issue. Was mupen64-glide ever stable for you in the past?

EndersEnigma

@quicksilver
Only mario 64. Instead of crashing it just slows down for about 10 seconds then goes back to normal. every other game I have crashes at the 13-15 minute mark. Exactly as you described it in your post. I have only had my PI 4 days and N64 has always been unstable.

EndersEnigma

@quicksilver
would 4.3amp fry the pi3? I have one of those at 5v 4.3 amp

quicksilver

@endersenigma I wouldn't use that. I seriously doubt amperage is your issue because you don't have a lot hooked up to your pi.

EndersEnigma

Did a complete uninstall of the N64 emulator, rebooted, installed N64 from Binary, rebooted. Same problem. updated from source. rebooted, same problem. Outside of doing a complete reformat of my pi and starting from scratch, I am not sure what else to do.

@dankcushions
Do you have any input? I have tried everything I know how to try. Awaiting new power supply as we speak, but it doesn't act like any power supply issue from my experience.