Bronxteck

i believe Viking1304 no longer hacks. that may be why your not getting responses.

when was the last time you have cleaned out the dust from inside the machine? also maybe it needs new thermal paste on the cpu / gpu heatsinks.

the solution is usually to stop restarting from windows and do a shutdown instead. then turn it back on and boot OSX.

https://sourceforge.net/p/cloverefiboot/code/commit_browser you can look there for the changes between your old version and the changes made to the newer versions to determine if clover had something changed to impact your results. i would guess if they updated something in graphics detection then maybe thats why it works?

" using DETECT mode in the clover, which let the OSX to load Kexts from the L/E first. " That is not completely correct. "Detect" will only work for detecting fakesmc in L/E and if so then load. clover is hard coded to first pull from "Other" folder best option is to use "Inject"

you can try contacting @ insanelydeepak

try adding FAT-64.efi and partitiondxe.efi to your clover drivers folder

Virtualsmc.efi driver is only needed for filevault. for normal booting all you need is virtualsmc.kext in clover/kext/other folder. if you are not using fakesmc.kext.

smchelper is only needed if you use fakesmc kext. virtualsmc does not need it.

@Nancy10 you might have removed the Microsoft folder in your EFI volume while testing EFI folders. if you have your old one just copy the Microsoft folder back to your current EFI volume.

make sure they are both on the same wifi.

your PM961 NVMe drive is known to have compatibility issues with osx. if you have access to another brand maybe try with that. or at least check if the SSD is running it's latest firmware. sometimes having windows installed during OSX installation can cause issues with Mojave. you can try pulling the nvme during install and install to an external drive. if it installs then you clone the install back to the nvme after reinstalling it. catmater what SSD are you using in your setup?

4k alignment should not be an issue.

did you try the basic steps like check if the switch on the machine is off or if it is disabled in bios?

it is possible but you would have to have voodoohda do a iopcimatch to the device id that you want voodoohda to hook to. it can be configured inside the voodoohda.plist. you would have to change IOPCIClassMatch to IOPCIMatch then put the device id you want to hook to. so replace 0x04020000&0xfffe0000 with whichever device Id your HDMI is which you can probably get from DPCIManager app. so applehda will take one device and voodoohda will take over the other. but I do not know if whatevergreen.kext will interfere if you are using it. also you would not be using the applehda disabler as that would kill applealc. and voodoohda does not work with all HDMI. maybe the scenario is reversed and voodoohda is feeding the speakers not the HDMI but since he is running both I guess he has to look at what kext is loading what device. then adjust accordingly.