[Bug] RTX 5060 Ti 16GB: reproducible shutdown/restart hang on macOS 15.8.1 with NullMoth 1.9.0
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reading the shutdown and restart handling in the Rust driver and checking the submitted report ID, “NM hclo,” for relevant logs. Reproduce on macOS 15.8.1 with driver 1.9.0 and the listed RTX 5060 Ti setup, then trace where shutdown hangs; done means both shutdown and restart complete reliably without breaking normal graphics or Metal acceleration.
Written by the indexing model from the issue text.
Description
Send logs report ID
NM hclo
Where does it go wrong?
Something else
What happens
Problem
On macOS Sequoia 15.8.1 with NullMoth NVIDIA driver 1.9.0, my RTX 5060 Ti 16GB works normally after boot and Metal acceleration is enabled.
However, both Shut Down and Restart are consistently broken.
When I choose Shut Down or Restart from macOS, the desktop freezes on the last displayed frame. The machine remains powered on and never completes the shutdown/restart process.
I have to hold the power button to force the machine off.
This issue is reproducible every time.
After one failed restart followed by a forced power-off, the next boot also showed abnormal GPU initialization: the motherboard VGA debug LED stayed on and the display only showed a _ cursor / minimal output.
Normal graphics operation and Metal acceleration work correctly. The problem appears specifically during the shutdown/restart process.
Hardware
- CPU: AMD Ryzen 5 9600X
- GPU: NVIDIA GeForce RTX 5060 Ti 16GB
- Motherboard: Gigabyte B650EM
- macOS disk / OpenCore: External SSD
- Display connected directly to the RTX 5060 Ti
Software / Environment
- macOS: Sequoia 15.8.1
- NullMoth NVIDIA Driver: 1.9.0
- OpenCore: DBG-109-2026-09-30
- SMBIOS: iMacPro1,1
- Metal: Enabled / working
- NVIDIA GPU detected correctly with 16GB VRAM
Relevant BIOS settings:
- Above 4G Decoding: Enabled
- CSM: Disabled
- Secure Boot: Disabled
App or game (if it is one)
No response
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nullmoth/nvidia-macos-driver
-
[Bug] `nullmoth-wsreset.sh` never restarts WindowServer at the real login window: `/dev/console` is `_windowserver`, not `root` (guard + test blind spot)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nullmoth/nvidia-macos-driver#141 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
nullmoth/nvidia-macos-driver#28 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
nullmoth/nvidia-macos-driver#308 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
nullmoth/nvidia-macos-driver#307 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 5/5 Over a week Newbie friendliness 30/100
nullmoth/nvidia-macos-driver#306 ·
Maintainers usually reply within 2 days
All issues in nullmoth/nvidia-macos-driver
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
good first issue gpu serve
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
biomejs/biome#12475 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
documentation E-easy good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 91/100
Maintainers usually reply within 1 day