Experienced Hackintosh Builder Stumped

[speedscater1]

So much wrong here.
You are booting with nv_disable=1 which prevents the Nvidia drivers from loading.
As stated previously NvidiaGraphicsFixup.kext is deprecated and of course relates to the graphics card not the integrated graphics.
Your Lilu.kext and WhateverGreen.kext have been updated on your EFI partition but you have duplicates in /Library/Extensions which are a different version.
Decide if you want to inject kexts from Clover or load them from /Library/Extensions.
If you want to inject kexts from Clover you should remove the duplicates from /Library/Extensions.
Your build number is 17G66 which people have struggled with to find matching web drivers.
Your kernel panic appears to be USB related so I would suggest disconnecting all of your USB peripherals and then reattaching them one at a time in order to discover the culprit.
Also follow this guide to correctly configure your USB ports :

The New Beginner's Guide to USB Port Configuration

Important Update: June 2023 From Big Sur 11.3 on the built-in OpenCore XhciPortLimit quirk no-longer worked as described. This became a known "bug", though in reality it was Apple changing their internal code, making a simple "peek and poke" to keep it operating, a difficult task. However, with...

www.tonymacx86.com

Your config.plist still has FakeID IntelGFX 0x12345678 which adversely affects your integrated graphics.
Likewise injecting Intel graphics will prevent their drivers from loading.
iMac18,3 may not be the best choice of SMBIOS, it had AMD graphics.

Thank you for all the advice. Though I've built a couple Hackintosh, theres always more to learn and each system can be a little quirky. I checked my config.plist file and could not find a line that showed I had the nv_disable=1. Would you be able to direct me to it so I can make the adjustment? I'm making the other adjustments right now

 

[speedscater1]

So much wrong here.
You are booting with nv_disable=1 which prevents the Nvidia drivers from loading.
As stated previously NvidiaGraphicsFixup.kext is deprecated and of course relates to the graphics card not the integrated graphics.
Your Lilu.kext and WhateverGreen.kext have been updated on your EFI partition but you have duplicates in /Library/Extensions which are a different version.
Decide if you want to inject kexts from Clover or load them from /Library/Extensions.
If you want to inject kexts from Clover you should remove the duplicates from /Library/Extensions.
Your build number is 17G66 which people have struggled with to find matching web drivers.
Your kernel panic appears to be USB related so I would suggest disconnecting all of your USB peripherals and then reattaching them one at a time in order to discover the culprit.
Also follow this guide to correctly configure your USB ports :

The New Beginner's Guide to USB Port Configuration

Important Update: June 2023 From Big Sur 11.3 on the built-in OpenCore XhciPortLimit quirk no-longer worked as described. This became a known "bug", though in reality it was Apple changing their internal code, making a simple "peek and poke" to keep it operating, a difficult task. However, with...

www.tonymacx86.com

Your config.plist still has FakeID IntelGFX 0x12345678 which adversely affects your integrated graphics.
Likewise injecting Intel graphics will prevent their drivers from loading.
iMac18,3 may not be the best choice of SMBIOS, it had AMD graphics.

Ok So I made all the changes and it wouldn't boot graphics at all and took 6 minutes to boot. After looking into it further it seems like if I don't inject the kexts from clover, it will not boot correctly. I tried to put them into my extension folder and not inject them from clover but thats what resulted in the no graphics.

 

[UtterDisbelief]

Ok So I made all the changes and it wouldn't boot graphics at all and took 6 minutes to boot. After looking into it further it seems like if I don't inject the kexts from clover, it will not boot correctly. I tried to put them into my extension folder and not inject them from clover but thats what resulted in the no graphics.

Hi there,

@P1LGRIM 's advice is spot on though.

Go for a basic install...

High Sierra - any security updates or just the initial 10.13.6? Nvidia drivers differ for each SU issued.

Disconnect the Samsung Evo with Windows until you get a reliable system.

Use one monitor until you get a reliable system, preferably the slower one.

6 minutes to boot indicates the system is waiting on a service or hardware to complete. Disconnect the USB soundcards, if that's what Creative and Logitech are (DACs etc). Use "verbose" boot mode to see where the delays are.

Ensure no XMP or overclocks in place.

Recommend any third-party kexts installed in Library/Extensions are removed and the kextcaches rebuilt using Terminal. Any duplicates can be binned, all others put in EFI/CLOVER/kexts/Other of your Toshiba SSD EFI partition for testing, and Injected.

No InjectNvidia setting.

Only Lilu and Whatevergreen for graphics control.

At this point there should be no reason UniBeast Clover will not boot the system assuming BIOS settings correct. Install Clover on your main drive with the settings we mention and it should work. If not we don't know the whole story.

 

[P1LGRIM]

I checked my config.plist file and could not find a line that showed I had the nv_disable=1. Would you be able to direct me to it so I can make the adjustment?

Look at your panic report:

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0 nv_disable=1

 

[speedscater1]

Hi there,

@P1LGRIM 's advice is spot on though.

Go for a basic install...

High Sierra - any security updates or just the initial 10.13.6? Nvidia drivers differ for each SU issued.

Disconnect the Samsung Evo with Windows until you get a reliable system.

Use one monitor until you get a reliable system, preferably the slower one.

6 minutes to boot indicates the system is waiting on a service or hardware to complete. Disconnect the USB soundcards, if that's what Creative and Logitech are (DACs etc). Use "verbose" boot mode to see where the delays are.

Ensure no XMP or overclocks in place.

Recommend any third-party kexts installed in Library/Extensions are removed and the kextcaches rebuilt using Terminal. Any duplicates can be binned, all others put in EFI/CLOVER/kexts/Other of your Toshiba SSD EFI partition for testing, and Injected.

No InjectNvidia setting.

Only Lilu and Whatevergreen for graphics control.

At this point there should be no reason UniBeast Clover will not boot the system assuming BIOS settings correct. Install Clover on your main drive with the settings we mention and it should work. If not we don't know the whole story.

Ok latest update and Config file attached. For some reason with the current config file settings everything seems to work no problem as well as a decent time for the boot. I made a few adjustments to it. I did find out some odd things however:

1. No more errors on restarts
2. Shuts down properly
3. Restarts properly
4. iCloud works great
5. Keyboard still hangs for a sec but ends up working
6. When I change any Intel settings, the boot hangs at [IGPU] Graphics driver failed to load: Could not register with Framebuffer driver! (Not sure what the deal is there but I just left the intel settings and it works fine
7. Dual screen works fine as long as both are on the 1080ti
8. Still can't split the connection to have one screen dedicated and one screen integrated ( I think it has to do with using Displayport instead if HDMI?
9. Also for some reason I have to inject the kexts with clover, putting them in extension doesn't work.

I guess Im at the point where, "If it ain't broke don't fix it?"

That being said I would like to clean it up if possible, it would be a good learning process. I know the error says I have nv_disable=1 but I don't see it in the config text so I'm unsure as to how to fix that...

Thank you in advance! Great forum and quick responses from the mods.

 

[dfritchie]

Try resetting your NVRAM to get rid of the boot arg.

 

[speedscater1]

Try resetting your NVRAM to get rid of the boot arg.

I just tried that with no success. Cleared it in terminal.

 

[dfritchie]

I had to reset mine from efi shell.