Contribute
Register

[SOLVED] High Sierra 10.13.4 / 980-TI / NVidia 387.10.10.10.30.106 Hard Freeze

Status
Not open for further replies.
Joined
Apr 20, 2011
Messages
60
Motherboard
Gigabyte Auros z390 Ulta
CPU
i9-9900K
Graphics
HD 630
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
== SOLVED ==

I am running High Sierra 10.13.4, and upgraded from Nvidia 387.10.10.10.30.103 to the recently released Nvidia 387.10.10.10.30.106 drivers. I am running Nvidia graphics fixup 1.2.5.

After installing the drivers, I got a full system hang on reboot, consistently when the boot marker was in the middle of the screen (just before my screen momentarily blacks out when the web drivers load).

I tried the following boot flag combinations:
  1. -v
    • This allowed me to boot a littler further and see the initial login screen, then complete freeze up (even though wifi was connected, computer would not respond to pings; cursor was not blinking, etc)
  2. -v -ngfxoff (disables kext loading for Nvidia Graphics mixup)
    • This had no effect
  3. -v -ngfxoff nvda_drv=0
    • This disabled the Nvidia drivers. I could see the slow UI painting / flickering that one sees usually when using the legacy non-accelerated.graphics. My computer still froze up at the same spot. Unfortunately, I could not see a log anywhere with details about what went wrong :'(
Finally, I booted with "-v -x" to get in to safe mode. Then, I downloaded the previous Nvidia drivers with the following curl command:

Code:
curl -O https://images.nvidia.com/mac/pkg/387/WebDriver-387.10.10.10.30.103.pkg

I installed the package without any issues. After rebooting with the rolled back drivers, my system continued to function as normal, corroborating the hypothesis that the .106 upgrade was the cause of the new freeze.

================

This is my system build:

- i7 6700k
- ASUS H170 Pro Gaming Mobo
- NVidia 980-ti graphics card
- PCI TP-LINK Archer Archer T8E IEEE 802.11ac

Installation method:

- Clover
- Using AFPS on boot disk

My full kext list is attached.

My (gently redacted) config.plist is attached, also.

I will continue to update this post as I learn more.


=== UPDATE ===

I ran the webdriver.sh installer as Vulgo suggested, and I updated NvidiaGraphicsFixup to 1.2.6. After both of these steps, my system is booting with the newer .106 drivers! I wish I could say exactly what fixed the problem, but I don't fully know. Thank you Vulgo!
 

Attachments

  • kexts.txt
    20.6 KB · Views: 273
  • config.redacted.plist
    5.3 KB · Views: 275
Last edited:
You could try this
Code:
bash <(curl -s https://vulgo.github.io/webdriver) 387.10.10.10.30.106
Source
 
387.10.10.10.30.103
You could try this
Code:
bash <(curl -s https://vulgo.github.io/webdriver) 387.10.10.10.30.106
Source

That's for a different problem :) Rolling back from 387.10.10.10.30.106 to 387.10.10.10.30.103 helped because upgrading to 387.10.10.10.30.106 caused the freeze. I do not need to patch the installer because 387.10.10.10.30.103 is released for 10.13.4, my current OS version.
 
I do not need to patch the installer because 387.10.10.10.30.103 is released for 10.13.4, my current OS version
No patching of the installer is involved. The freeze is a configuration/macOS problem.
 
No patching of the installer is involved. The freeze is a configuration/macOS problem.

Okay, after reading the script, it looked like it downloaded, patched, and installed the nvidia driver. Looks like it approves kexts and does some uninstallation?

Also it added this to my config.plist:

Code:
            <dict>
                <key>Comment</key>
                <string>webdriver.sh: Disable NVIDIA Required OS</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                TlZEQVJlcXVpcmVkT1MA
                </data>
                <key>Name</key>
                <string>NVDAStartupWeb</string>
                <key>Replace</key>
                <data>
                AAAAAAAAAAAAAAAAAAAA
                </data>
            </dict>

Well, between that and updating NvidiaGraphicsFixup to 1.2.6, I'm successfully running 387..106 now, without freezes. Thank you for the help, Vulgo!
 
Looks like it approves kexts and does some uninstallation?
I can recreate boot failure with some certainty by switching between driver versions, SIP settings, installation methods etc. The script is a best effort to make things 'just work'.
Also it added this to my config.plist
Tries to keep acceleration after an OS upgrade. NvidiaGraphicsFixup has the ngfxcompat=1 boot argument for the same purpose and also works to prevent freezes at boot due to kernel cache problems.
 
Quick question - I'm currently on an H170N-WiFi motherboard with 980Ti Founder's Edition card stable on 10.13.3. Had issues with 10.13.4 and 10.13.5 with the nVidia web drivers to no avail because of the IOConsoleUsers: gIOScreenLockState 3 error. I'm running two monitors (one through DVI, one through HDMI). I'm able to boot on verbose mode, but if I boot normally, I get the aforementioned gIOScreenLockState 3 error.

I've attached my config.plist file from the most recent version of Clover with Emulated NVRAM I'm using. My kexts include the latest versions of: AppleALC, CodecCommander, FakeSMC, Lilu, NvidiaGraphicsFixup, realTekALC, RealTekRTL8111, Shiki, and USBInjectAll.

Is there any glaring mistake I'm making which could be causing the gIOScreenLockState error?

Appreciate anyone taking the time to reply and help!
 

Attachments

  • config.plist
    9.8 KB · Views: 209
@rishk789 it looks like we are running similar builds. I've been holding off on the 10.13.5 upgrade until I have a mechanism to carbon-copy the drive and restore. Are you able to boot up in safe mode? Downgrade to an older version of the driver? Upgrade again using Vulgo's script?
 
@rishk789 well I just updated my system. It upgraded without a hitch! And I can use the native Nvidia drivers now with my 980 TI... which is weird. They seem to work flawlessly. I didn't expect that.
 
Status
Not open for further replies.
Back
Top