Solving NVIDIA Driver Install & Loading Problems

[P1LGRIM]

From Terminal:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext realtekALC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_XHCIMux.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleIntelE1000e.kext
KernelCache ID: 9FABB1D3B054E99F888491D3E43842CF

There are a few things that you could try :
In Clover Change Drivers64UEFI/OsxAptoFixDrv-64 for OsxAptoFix2Drv-64 or the solution from nickwoodhams.com.
Replace VBoxHfs-64.efi with HFSPlus.efi.
Install EmuVariableUefi-64 and RC scripts.

But I would be inclined to make a fresh install with the correct Clover/FakeSMC.kext/Web drivers etc and no extras like the FakeSMC sensors.

 

[wckdkarma]

There are a few things that you could try :
In Clover Change Drivers64UEFI/OsxAptoFixDrv-64 for OsxAptoFix2Drv-64
Replace VBoxHfs-64.efi with HFSPlus.efi.
Install EmuVariableUefi-64 and RC scripts.

But I would be inclined to make a fresh install with the latest Clover/FakeSMC.kext/Web drivers etc and no extras like the FakeSMC sensors.

Ok. I will try both!
Just so I'm clear, when I make a fresh install with latest Clover/FakeSMC.kext/Web drivers etc, would you recommend that I start off with OsxAptoFixDrv-64, HFSPlus.efi, EmuVariableUefi-64 and RC scripts?
And then.... if a fresh install doesn't work.....?

 

[P1LGRIM]

Just so I'm clear, when I make a fresh install with latest Clover/FakeSMC.kext/Web drivers etc, would you recommend that I start off with OsxAptoFixDrv-64, HFSPlus.efi, EmuVariableUefi-64 and RC scripts?

I would use HFSPlus.efi for sure.
EmuVariableUefi-64 and RC scripts are to emulate NVRAM if your motherboard does not support it natively, I do not know if this is the case for you but they will do no harm either way.
OsxAptoFix2Drv-64 ought to work but there are alternatives to try if it doesn't.

And then.... if a fresh install doesn't work.....?

Cross your bridges when you come to them.

 

[wckdkarma]

I would use HFSPlus.efi for sure.
EmuVariableUefi-64 and RC scripts are to emulate NVRAM if your motherboard does not support it natively, I do not know if this is the case for you but they will do no harm either way.
OsxAptoFix2Drv-64 ought to work but there are alternatives to try if it doesn't.


Cross your bridges when you come to them.

Thank you for all of your help!!! I'll post back once I've done my homework ;-)

 

[mutatio]

Thanks mutatio! Yes. I've reinstalled it a couple of times.
I can boot without the card installed but as soon as I install it I get:
"OsxAptioFix2Drv: Starting overrides for \System\Library\CoreServices\boot.efi
Using reloc block: no, hibernate wake: no
Error allocating 0x2479a pages at 0x0000000014ac0000 alloc type 2
Couldn't allocate runtime area
Boot failed, sleeping for 10 seconds before exiting..."

I've tried OsxAptioFixDrv and still get an error message. I'm pretty sure I've used the OsxAptioFixDrv2 since upgrading to Sierra, which again, was running great until last week.
I really don't know what the error means and my google searches don't seem to be turning up anything relevant to my build.

I really appreciate the input. I'm running out of time to get this back up and running. Starting to wonder if I should just get a different graphics card. I don't want to but I feel like I'm running out of options.

Worth noting that the default settings for Clover, as I understand, are to upgrade newer components of the install. I'm not sure off the cuff if a default install will reinstall the OsxAptioFixDrv2 file if it detects that it is the same one already on the disk. For the sake of thoroughness, it might be worthwhile to delete that file from your EFI Clover folder and then do an upgrade/install of Clover with OsxAptioFixDrv2 selected.

 

[louis002]

#6 really helped me out! I spent 4 hours on this and finally came across something that worked. Thanks!

 

[vulgo]

Thank you for all of your help!!! I'll post back once I've done my homework ;-)

None of these should be here except for FakeSMC.kext and AppleIntelE1000e.kext, you should remove the others.

9:299  0:004  Preparing kexts injection for arch=x86_64 from EFI\\CLOVER\\kexts\\Other\
9:300  0:000  Preparing kexts injection for arch=x86_64 from EFI\\CLOVER\\kexts\\10.12\
9:303  0:003    Extra kext: EFI\\CLOVER\\kexts\\10.12\\ACS6x.kext\
9:307  0:004    Extra kext: EFI\\CLOVER\\kexts\\10.12\\AppleIntelE1000e.kext\
9:314  0:006    Extra kext: EFI\\CLOVER\\kexts\\10.12\\ArcMSR.kext\
9:318  0:003    Extra kext: EFI\\CLOVER\\kexts\\10.12\\ATTOCelerityFC8.kext\
9:326  0:008    Extra kext: EFI\\CLOVER\\kexts\\10.12\\ATTOExpressSASHBA2.kext\
9:341  0:014    Extra kext: EFI\\CLOVER\\kexts\\10.12\\ATTOExpressSASRAID2.kext\
9:347  0:006    Extra kext: EFI\\CLOVER\\kexts\\10.12\\CalDigitHDProDrv.kext\
9:352  0:005    Extra kext: EFI\\CLOVER\\kexts\\10.12\\FakePCIID_XHCIMux.kext\
9:356  0:003    Extra kext: EFI\\CLOVER\\kexts\\10.12\\FakePCIID.kext\
9:359  0:003    Extra kext: EFI\\CLOVER\\kexts\\10.12\\FakeSMC_ACPISensors.kext\
9:364  0:004    Extra kext: EFI\\CLOVER\\kexts\\10.12\\FakeSMC_CPUSensors.kext\
9:367  0:003    Extra kext: EFI\\CLOVER\\kexts\\10.12\\FakeSMC_GPUSensors.kext\
9:372  0:004    Extra kext: EFI\\CLOVER\\kexts\\10.12\\FakeSMC_LPCSensors.kext\
9:393  0:021    Extra kext: EFI\\CLOVER\\kexts\\10.12\\FakeSMC.kext\
9:400  0:006    Extra kext: EFI\\CLOVER\\kexts\\10.12\\HighPointIOP.kext\
9:405  0:005    Extra kext: EFI\\CLOVER\\kexts\\10.12\\HighPointRR.kext\
9:414  0:009    Extra kext: EFI\\CLOVER\\kexts\\10.12\\PromiseSTEX.kext\
9:419  0:005    Extra kext: EFI\\CLOVER\\kexts\\10.12\\realtekALC.kext\
9:424  0:004    Extra kext: EFI\\CLOVER\\kexts\\10.12\\SoftRAID.kext\

 

[wckdkarma]

Worth noting that the default settings for Clover, as I understand, are to upgrade newer components of the install. I'm not sure off the cuff if a default install will reinstall the OsxAptioFixDrv2 file if it detects that it is the same one already on the disk. For the sake of thoroughness, it might be worthwhile to delete that file from your EFI Clover folder and then do an upgrade/install of Clover with OsxAptioFixDrv2 selected.

Thank you! I just tried that but I still get the error.
I get the error trying to boot from my install USB also..and a new install USB
I get the error trying to boot from previous installation USBs (El Capitan and Yosemite)
I've used different USB ports.
Nothing seems to work.

 

[vulgo]

Nothing seems to work.

As it was working before resetting your motherboard by CMOS reset, re-flashing or updating might help. Disabling additional integrated and add-in hardware is the way to go. Failing that there are variants of the Aptio memory fix for boards that consistently have this problem, here is one for example.

 

[wckdkarma]

As it was working before resetting your motherboard by CMOS reset, re-flashing or updating might help. Disabling additional integrated and add-in hardware is the way to go. Failing that there are variants of the Aptio memory fix for boards with many devices, here is one for example.

Thank you vulgo. I will try that after work today!