sirkillalotic

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

sirkillalotic's Achievements

Noob

Noob (1/14)

0

Reputation

  1. welp, after waiting 10 minutes it started working...
  2. Greetings, I have my unraid server set on port 8080... Up until recently I was using the docker container and was able to connect via port 8080, something happened and I updated and it no longer works, but I can connect to my other apps on other ports just fine. Now I switched to the plugin, and the same issue exists, I can connect to my other apps, but I can't connect to the unraid port 8080 to see the UI. Is this a bug, do I need to change a setting? I left the default settings enabled.
  3. So is there still a limit with transcodes with this driver?
  4. @testdasi Interesting, I didn't know that...I was getting 15300 with passmark using the 2133 ram for a 1080ti and 17600 using 3600 setting. So I'm just talking about the benchmark. I'll try the 3200 and see what happens Interesting how only the VM's crash (both) and Unraid stays up
  5. Thanks for the replies, will post diagnostics ASAP As for the overclocking. The ram I bought was rated 3600, the board recognized it was 2133, so I manually set it to 3600. By not doing this the graphics was taking a SEVERE hit in performance. adjusting it made it nearly bare metal. So you are saying my 4 slots of 3600 need to be set to 2667? or maybe I should just experiment with dropping down the ram little by little? The unraid OS isn't crashing, just the VM's. Also when running against Baremetal the system runs great on 3600.
  6. Hello, I have a fresh build using msi pro carbon 570x and the ryzen 3900x. 32gb 3600 ram. I converted my machine to an img. Got everything working but when I put a heavy load (loading up ark video game) I get this system thread exception and not just this machine but my other separately cpu pinned fresh install os gets this error as soon as this one does and vice versa. I'll even have the converted vm off and the fresh vm has the same problem.(yes both machines will get the error at the same exact time). I also have the cores isolated so that unraid can only use 2 separate cores. I am passing though a 1080ti using vbios. I'm stuck to what's wrong and spent hours upon hours googling and tinkering. I'm on unraid 6.8.3