[Bug] Black screen/hang after ExitBootServices booting macOS 15 Sequoia installer — ASUS ROG Zephyrus M16 GU603ZM (i7-12700H + RTX 3060 Laptop, dGPU only)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the attached OpenCore log and the boot sequence around EXITBS:START; the report says kext injection succeeds but does not show the NullMoth driver in the prelinked list. Check whether the driver is expected to load during installer boot and whether the reported GPU and display setup is supported. Done means identifying why boot stops at a black screen or confirming the setup is unsupported and documenting the needed next step.
Written by the indexing model from the issue text.
Description
Send logs report ID
5cc8a9804d1e4cc080e1a7589b739104
Where does it go wrong?
Building or writing the USB stick (1401 on Windows)
What happens
Hardware
- Laptop: ASUS ROG Zephyrus M16 GU603ZM
- BIOS: GU603ZM.311 (2022-12-22), UEFI, Secure Boot: Disabled
- CPU: i7-12700H (Alder Lake-H, 14c)
- dGPU: NVIDIA RTX 3060 Laptop GPU, Device ID 10DE-2520, Subsystem 1A7C1043
- PCI path: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)
- ACPI path: _SB.PC00.PEG1.PEGP
- Resizable BAR: Disabled (BAR1 = 256 MB)
- iGPU: Intel Iris Xe 8086-46A6 — disabled via DeviceProperties (disable-gpu on PciRoot(0x0)/Pci(0x2,0x0))
- BIOS GPU mode: dGPU Only (discrete)
- Internal panel: AUOC199 eDP 2560x1600 (per Windows 1401 scan, routed to NVIDIA in dGPU mode)
- External monitor: G73 DP 2560x1440 (connected to NVIDIA)
- WiFi: Intel AX211 | Ethernet: Realtek RTL8125 | Audio: Realtek ALC285
Environment
- Target macOS: 15 Sequoia (booting from installer USB, not yet installed)
- OpenCore: DBG-109-2026-10-10
- SMBIOS: MacBookPro16,2
- 1401 Probe: v1.1.1 on Windows, scan completed without errors
- Driver: trying to use NullMoth driver (boot-args configured for nvfb/nvaccel)
What happens
- OC boots, all kexts inject successfully, prelinked status = Success
- boot.efi loads (bootbase.efi 583~2210, SDK 15.6)
- OC log ends at:
#[EB|LOG:EXITBS:START] 2026-10-11T14:24:07 - After ExitBootServices, screen goes black — no further verbose output, no installer GUI appears
- One non-fatal error before handoff:
#[EB.LD.OFS|OPEN!] Err(0xE) <"usr\standalone\OS.dmg.root_hash">
but boot continues past it.
Questions
- Is the NullMoth driver kext supposed to load during the installer boot? It does not appear in the OC prelinked injection list. I have the boot-args set (nvfb=1 nvaccel=1 etc.) but I'm unsure if the kext is actually being loaded.
- With iGPU disabled and no known display driver active at kernel level, is black screen after EXITBS expected until the NVIDIA driver kext loads?
- Should I expect the internal eDP panel to light up, or must I use the external DP monitor first?
boot-args
-v debug=0x100 keepsyms=1 -vi2c-force-polling ctrsmt=full nvfb=1 nvaccel=1 nvfbheads=4 -nvkmsnosmooth amfi_get_out_of_my_way=0x1 amfi=0x80 ipc_control_port_options=0
opencore-2026-10-11-142329.txt
App or game (if it is one)
N/A — macOS 15 Sequoia installer, no third-party app
Did you change anything yourself?
- boot-args as listed above (nvfb/nvaccel/nvfbheads/nvkmsnosmooth/amfi flags)
- Disabled iGPU via DeviceProperties: disable-gpu = <01000000> on PciRoot(0x0)/Pci(0x2,0x0)
- Standard kexts: Lilu, VirtualSMC + SMCProcessor + SMCSuperIO, AppleALC, WhateverGreen, itlwm, VoodooI2C, VoodooPS2Controller, USBToolBox + UTBDefault, RTL812xLucy, IntelBluetoothFirmware + BlueToolFixup, NVMeFix, CpuTopologyRebuild, RestrictEvents, BrightnessKeys, Sinetek-rtsx
- BIOS: dGPU Only mode, Resizable BAR Disabled, Secure Boot Disabled
- Followed OpenCore laptop guide; SMBIOS MacBookPro16,2
- Dominant language
- Rust
- Stars
- 2.5k
- Forks
- 233
- Avg merge
- 1h 37m
- Merged PRs (30d)
- 1
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 5/5 Over a week Newbie friendliness 8/100
nullmoth/nvidia-macos-driver#224 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 15/100
nullmoth/nvidia-macos-driver#222 · 4 comments ·
Maintainers usually reply within 2 days
-
bug
Difficulty 5/5 Over a week Newbie friendliness 15/100
nullmoth/nvidia-macos-driver#221 · 1 comment ·
Maintainers usually reply within 2 days
All issues in nullmoth/nvidia-macos-driver
Similar issues
-
agent:triaged bug bughunt pm:pipenv priority:p1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SocketDev/socket-patch#1608 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
adorsys/status-list-server#698 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nannou-org/egui_graph#92 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 Half a day Newbie friendliness 72/100
sujithputta02/Esapay#13 ·
-
Deduplicate normalized_f64_bits (hash_table.rs and bloom_filter.rs)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
tursodatabase/turso#10002 ·
Maintainers usually reply within 1 day