Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

I just went through this myself! When I updated to the latest BIOS, my system wouldn't boot after I loaded the XMP profile. It was the strangest thing.

You can set the XMP Profile, then manually lower the speed. This keeps all the other timings at the XMP setting and you can tune down the speed to the point it is stable. In my case, I have DDR4 3600 MHz, but the system was unstable. I had to bring it down to 3500 for stability.

At that point I could adjust the voltages up to 1.5V or so, and then that allowed me to go back up to 3600 to boot. After I got it to 3600, I could bring down the voltages to around 1.38V. But my system still wasn't stable. I experienced random crashes in Big Sur.

I suspected a bad RAM module, so this last weekend, I systematically went through each pair combination in order to find out which module wasn't allowing me to load the XMP profile. To my surprise, all pair combinations worked. Then, when I put back all 4 modules, it booted just fine at 3600, and the whole system is stable since.

Crazy.

From what I've seen, overclocking RAM will always result in macOS complaining about USB drives ejecting when waking from sleep.
 
I don't see any major differences to my EFI. You use different kexts (some not necessary) but there's no reason why my EFI doesn't boot for you.
@LiveSorcerer : double-check your BIOS settings and make sure they are the same as PC's. The biggest thing is the CFG-lock, and make sure this is disabled. After that, you can reset the CMOS (you will have to reload all your BIOS settings after you reset it) and reset the NVRAM.

For more help, try booting in verbose, then post an image of where it is stopping during boot.
 
I don't see any major differences to my EFI. You use different kexts (some not necessary) but there's no reason why my EFI doesn't boot for you.
So, I'm going to see this weekend to compare mine with yours and retest yours again.
 
From what I've seen, overclocking RAM will always result in macOS complaining about USB drives ejecting when waking from sleep.

I didn't know that. I don't have a problem currently, but sometimes I get that when I am transferring files off my camera flash card. I do that in Lightroom, and the program auto-ejects the card after completion. When I pull out the card from the reader, I sometimes get the error message that the disk was ejected improperly. Good to know that it may be associated with the RAM overclock!
 
Please post your config.plist.


Here is my config.plist. I disabled SSDT-USBW, the problems are still there.

Code:
X:~|⇒  pmset -g
System-wide power settings:
Currently in use:
 hibernatemode        0
 womp                 0
 networkoversleep     0
 sleep                15 (sleep prevented by apsd, sharingd)
 Sleep On Power Button 1
 ttyskeepawake        1
 hibernatefile        /var/vm/sleepimage
 disksleep            10
 displaysleep         3


Code:
X:~|⇒  pmset -g log | grep -e "Sleep.*due to" -e "Wake.*due to" | tail -n 20
2020-11-24 20:07:24 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:08:09 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 16 secs
2020-11-24 20:08:25 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:09:10 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 15 secs
2020-11-24 20:09:25 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:10:10 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 15 secs
2020-11-24 20:10:25 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:11:10 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 16 secs
2020-11-24 20:11:26 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:12:11 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 15 secs
2020-11-24 20:12:26 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:13:11 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 15 secs
2020-11-24 20:13:26 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:14:11 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 16 secs
2020-11-24 20:14:27 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:15:12 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 15 secs
2020-11-24 20:15:27 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:16:12 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 16 secs
2020-11-24 20:16:28 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 34 secs
2020-11-24 20:17:02 -0700 Wake                    DarkWake to FullWake from Normal Sleep [CDNVA] : due to HID Activity Using AC (Charge:0%)
 

Attachments

  • config.plist
    36.5 KB · Views: 35
Here is my config.plist. I disabled SSDT-USBW, the problems are still there.

Code:
X:~|⇒  pmset -g
System-wide power settings:
Currently in use:
hibernatemode        0
womp                 0
networkoversleep     0
sleep                15 (sleep prevented by apsd, sharingd)
Sleep On Power Button 1
ttyskeepawake        1
hibernatefile        /var/vm/sleepimage
disksleep            10
displaysleep         3


Code:
X:~|⇒  pmset -g log | grep -e "Sleep.*due to" -e "Wake.*due to" | tail -n 20
2020-11-24 20:07:24 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:08:09 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 16 secs
2020-11-24 20:08:25 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:09:10 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 15 secs
2020-11-24 20:09:25 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:10:10 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 15 secs
2020-11-24 20:10:25 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:11:10 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 16 secs
2020-11-24 20:11:26 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:12:11 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 15 secs
2020-11-24 20:12:26 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:13:11 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 15 secs
2020-11-24 20:13:26 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:14:11 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 16 secs
2020-11-24 20:14:27 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:15:12 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 15 secs
2020-11-24 20:15:27 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 45 secs
2020-11-24 20:16:12 -0700 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 16 secs
2020-11-24 20:16:28 -0700 DarkWake                DarkWake from Normal Sleep [CDN] : due to XDCI CNVW/ Using AC (Charge:0%) 34 secs
2020-11-24 20:17:02 -0700 Wake                    DarkWake to FullWake from Normal Sleep [CDNVA] : due to HID Activity Using AC (Charge:0%)


There's no need to disable SSDT-USBW.

Please try this config.plist and see if it makes any difference. Do you have a CNVi card installed?
 

Attachments

  • config.plist
    35.7 KB · Views: 36
Does anyone use istats or hwmonitor in Big Sur?
Is the Fan sensor working, which informs the RPM?
In the case using OpenCore 0.6.3.

I use iStat Menus. The fan sensors don't really work. I only get rpm readings for one fan but I don't know which one.

You would need to customize SMCSuperIO.kext to get the sensors working right. I don't know how to do this.
 
There's no need to disable SSDT-USBW.

Please try this config.plist and see if it makes any difference. Do you have a CNVi card installed?
Same Results.

I did not install the CNVI card, the only wifi card install is BCM943602 w/ PCIE adapter. The USB cable is 2pins, it that cause the problem?
 

Attachments

  • TB2euQnfTnI8KJjSszbXXb4KFXa_!!86827518.jpg
    TB2euQnfTnI8KJjSszbXXb4KFXa_!!86827518.jpg
    71.8 KB · Views: 30
Back
Top