Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] Roblox (and Minecraft) artifacts on graphics, frame buffering, kernel panics, display configuration resetting after every reboot

Open
#306 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, rust

Research direction

Start by reviewing the three Send logs report IDs (NM-XP2RBAH5, NM-55KCQE8V, NM-3MD1QNZ0) and the graphics driver’s issue triage guidance. The report describes graphics artifacts in Roblox and Minecraft, apparent kernel panics after 10–15 minutes, and display settings resetting after reboot, but names no files or failing tests. Done means identifying a reproducible cause and a maintainer-confirmed fix.

Written by the indexing model from the issue text.

Description

bug
Send logs report ID

NM-XP2RBAH5, NM-55KCQE8V, NM-3MD1QNZ0

Where does it go wrong?

An app or game

What happens

The operating system kernel panics (or atleast that's what I think is happening) after 10-15 minutes of usage, Roblox's graphics render a lot more glow than normal, there is a lot of buffers in frames and whenever I restart, my display configuration breaks (both monitors set itself to 60hz, and the displays' arrangements reset)

Written by you
  • I wrote this report myself. AI-written issues are closed without review (see CONTRIBUTING.md).
App or game (if it is one)

Roblox (Minecraft) and entire operating system

Did you change anything yourself?

No

Dominant language
Rust
Stars
2.5k
Forks
233
Avg merge
21h 20m
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nullmoth/nvidia-macos-driver

All issues in nullmoth/nvidia-macos-driver

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.