TechnoBabble28
-
Posts
40 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by TechnoBabble28
-
-
I had been running on 6.5.3 for many months without issue and without any sort of zenstates or c-states modifications. I never had any issues with my Ryzen build other than some bad RAM sticks early on.
I updated to the F23 gigabyte BIOS a few months back but never looked through it until the other day. After disabling global c-states and adjusting the power supply power to "typical", 6.7 rc1 was stable for several days. It only started crashing again once I updated to rc2. I am using FCP to gather logs so when it inevitably crashes in the next 16 hours or so I can hopefully see what's going on. I also see that gigabyte released a F25 BIOS a little while ago but I am hesitant to change to the new BIOS until I figure out why the system is crashing. From what I can see, the biggest change is some tweaks for athalon based systems and an AGESA update from 1.0.0.4 to 1.0.0.6. It also mentions a requirememt to update the chipset driver which I cannot do.
I know one of you mentioned a mellanox card and having some problems. I am also running a mellanox card but haven't encountered any issues. However, I do not have any VMs running and I am not using the mellanox card for internet, only direct file transfers between my desktop and server.
-
I was stable on 6.7rc1 for a couple days then went to rc2. RC2 has crashed twice now all within 24 hours of uptime. I am now running FCP in troubleshooting mode to capture logs and will upload once it happens again.
-
Server has been up and running for almost 18 hours as of now. That's the longest it's stayed on thus far. So far so good. Nothing unusual in the logs.
-
I saw that while I was looking for the global c-states setting and set mine to typical also. Figured it was worth a shot. It's still up so far, fingers crossed.
-
Quote
Let me know the results. I would really like to stay with 6.7 for BBR.
Will do. Just rebooted into 6.7. I think my longest up-time previously was about 12.5 hours so we will see if we make it that far.
-
1
-
-
You sir were correct. It was buried in the overclocking settings under "advanced cpu core settings". Have just disabled it and will re-update to 6.7.
-
1
-
-
I have no such option anywhere in the Bios for global c-states. These are my only c-states settings.
-
Changed Status to Closed
-
Nope, that just hard locks the system every 20 minutes lol. I think ill just go back to 6.5.3. That's a bummer since the new dashboard is pretty nice. I'll close this thread.
-
C6 was set to auto in this new Bios version so i have reset it to disabled. Will see if that fixes the problem.
-
Bios was updated to lasted at the beginning of December and i haven't had any issues with it. I am running a zenstates script to fix the turbo boost issue and had previously disabled c-states in bios when i first set the system up. However, I have not checked the c-states since this bios update to see if they have been changed, mainly because everything was stable in 5.6.3 even after the bios update. I will check that now.
-
Quote
Are you running a windows 10 VM with GPU Passthrew? If so, I had this problem going from 5.6.0 to 6.6.0 threw 6.6.6 and it was Windows 10 VM that was at fault. Here is my bug report and what I did to fix it.
I don't run any VM's, this is purely just a media server running Plex and a couple supporting dockers.
-
My system is hard locking anywhere from 4 hours to ~12 after startup. I am unable to reach it via ssh or a browser so my only recourse is to do a hard restart. I have attached the log files below as well as a screen shot of the dashboard when it locked overnight. I left the dashboard up before i went to bed so i could see what was happening and when everything locked. I came from 6.5.3 and had no issues previously.
[6.7.0-rc1] System Hard Lock
-
-
-
-
-
in Prereleases
Posted
I kept trying each RC until I found a stable one. RC4 had been the most stable with an uptime of about 2 weeks which usually means I am in the clear. I just upgraded to RC5 a couple days ago and that has been solid as well so far.