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

[Bug] Apps Like DaVinchi resolve and Final Cut Pro won't work In GTX 1630

Open
#407 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
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
macos, rust
Domain
backend

Research direction

Start by reviewing the submitted diagnostic reports (IDs listed in the issue) and determine whether they contain useful crash details for DaVinci Resolve, Final Cut Pro, or Affinity. The issue names no source files or tests, and it does not identify what changed or how to reproduce the failures. Done means identifying a reproducible cause and a specific driver change that addresses it.

Written by the indexing model from the issue text.

Description

bug
Send logs report ID

Sent. Report ID NM-9REBX4JR, NM-H9J3J6NH, NM-2M9R8ZMH, NM-RQ2B2E2S, NM-8TXJXQYP, NM-GYNDC1JH, NM-FC50PGVN, NM-1VVZHAFQ, NM-87RXWMD9, NM-1R5SFXBY, NM-50WC3TVP, NM-HPSFW87W, NM-154FZJS7, NM-QVGHKB4X, NM-1F18XPYE, NM-CDFEKV4F

Where does it go wrong?

An app or game

What happens

Whenever try to open creatives apps like DaVinchi, Final Cut Pro and affinity the apps won't work. FInalcut pro opens and sometimes it works when using a very low res footage but 1080p footage can't handled and it crashes.

affinity is open but its too laggy to use plus davinchi crashes before opens and I can't find any logs to understand what happens

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)

DaVinchi Resolve 21, Finalcut pro, Affinity

Did you change anything yourself?

No response

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.