macOS on RTX 4070 SUPER: installation and driver checkpoints
ItsOOGWAY · Recorded PC guides · 02
macOS on RTX 4070 SUPER: installation and driver checkpoints
A focused companion to my NVIDIA RTX 4070 SUPER walkthrough: how the Windows preparation, macOS installation, and third-party graphics-driver checks fit together on this Ryzen PC.
Resources from this video
Project links & documentation
Every resource URL from this video’s description is collected here. Recorded-release links identify the build used; current project pages may describe newer versions.
Watch the recorded video
Watch on YouTube ↗ · Screenshots below come from this final recording.
Video chapters
- 0:00 RTX 4070 SUPER on macOS
- 0:17 Hardware and preparation
- 1:03 Download and select Tahoe
- 1:42 Hardware scan and OpenCore
- 2:24 BIOS guide and installer USB
- 3:46 BIOS and USB boot
- 4:31 Disk Utility and installation
- 6:48 Setup stall and first desktop
- 7:20 Install the NVIDIA driver
- 8:44 Driver status and basic checks
- 9:23 USB boot and recovery
- 9:54 Final result
Before you start
- Back up important files and identify the intended macOS storage target separately from the USB installer.
- Check your exact GPU, board, network hardware and chosen macOS version in the project documentation. A matching graphics-card name alone is insufficient.
- Keep the OpenCore USB available throughout installation, driver changes and restarts.
Stage 01
Confirm the RTX hardware before building
Open the linked Windows release, extract its complete folder, and launch the assistant with administrator privileges. Select the recorded macOS choice, then run Check this PC. Read the board, processor and graphics entries before continuing. In this take the assistant identifies the RTX 4070 SUPER alongside the Ryzen system.
Continue through Build the Mac setup and read its result. The OpenCore configuration prepares the system to boot the installer. It does not by itself prove that an NVIDIA graphics driver is installed and running inside macOS.
Stage 02
Create the USB with the generated BIOS plan nearby
Read Your BIOS steps and save a copy you can access after restarting. Use those instructions for your motherboard. In Create the macOS stick, verify the device name, drive letter and capacity before selecting Erase and create.
The USB and the later macOS destination are different targets. Writing the stick erases that USB; it does not identify which internal volume is safe to erase later. Wait for the assistant to report that the stick is ready.
Stage 03
Boot through the prepared OpenCore USB
Restart into the motherboard firmware and follow the generated plan. Save the required changes and select the USB’s UEFI entry from the one-time boot menu. The recording then passes through startup text and reaches macOS Recovery.
The AORUS startup screen is part of the transition, not an error diagnosis. If your machine stops here, keep the exact last message and revisit your generated BIOS instructions and current project troubleshooting before changing several settings together.
Stage 04
Choose the macOS volume carefully
In Recovery, open Disk Utility → View → Show All Devices. The example target is an existing volume named Hackintosh, about 130 GB, on a disk with other volumes. Identify your own target by name, capacity and hierarchy.
The pictured erase dialog is before the format changes. Select APFS for the intended destination; do not copy the old NTFS selection visible in the screenshot. Erase only the intended target, close Disk Utility, and install Tahoe onto it. Keep the USB attached during restarts.
The setup later stalls in this session and the creator restarts before reaching the desktop. This is a recorded outcome, not a universal instruction to restart a slow installer after a fixed wait.
Stage 05
Review the driver and OpenCore changes
Once macOS opens, launch the Mac companion from the USB’s NullMoth folder. Check its system information, GPU and detected OpenCore boot source. Review the proposed changes before starting: this step affects driver files and boot/security configuration.
Follow the prompts for your actual package, including administrator authorization, extension approval in Privacy & Security, and the required restart. Continue using the intended OpenCore USB. This older driver session must not be relabelled as a verified end-to-end 2.3.5 driver test.
Stage 06
Read the status without overclaiming performance
Reopen the companion after restarting. The visible result reports loaded NullMoth components and an NVIDIA Metal device. The GPU is identified, but the installed-package field has no version record. Device detection, loaded components and real application testing are separate checks.
The video includes basic desktop use and a short playback example. It does not establish performance across games or professional apps, sleep/wake reliability, multiple-display support, or successful booting after disconnecting the USB. Record those checks separately on your machine.
If your result differs
| Situation | Next useful check |
|---|---|
| RTX is detected but the driver is not running | Recheck the boot source, extension approval and restart. A GPU name in the scan is not the final driver-status check. |
| The system cannot boot without the USB | This recording keeps using the USB. It does not demonstrate an internal EFI migration; retain the working boot route. |
| A newer release looks different | Keep the recorded and current versions separate. Read the release notes rather than mixing old commands with a new companion. |
This post focuses on the graphics checkpoints. For the broader preparation sequence, the related macOS installation guide covers the same machine from Windows through the first desktop.
Comments
Post a Comment