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

Nvidia memory junction temperature broken in V264

Open
#3,976 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale

Research direction

Compare memory junction temperature reporting in V264 with V263, since the report says reverting fixes the constant 43°C reading. Start by identifying the release change that affects this sensor; the issue does not name files or tests. Done when the reported temperature reflects the GPU reading in V264.

Written by the indexing model from the issue text.

Description

After updating to V264, memory junction temp reporting on my nvidia gpu was broken. Sensor still exists, but it's constantly reported as 43C even when in reality it is at 80C.

Reverting back to V263 fixes the issue.

Dominant language
No language data
Stars
21.1k
Forks
619
PR merge metrics
No merged PRs in 30d

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 Rem0o/FanControl.Releases

All issues in Rem0o/FanControl.Releases

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.