Search results

Hi @rlrhett how is it going? Sorry to invade your thread like this but I've just found an old topic of yours about external USB drives causing random crashes. Have you ever figured that out? Was there a solution? I started having the exact same issue and I've been trying to solve it for a week...

for any future warriors: i got the Paragon APFS for Windows trial for 10 days and was able to mount my Mojave SSD via Windows 10. then I mounted my EFI partition using MiniTool and explorer++ to be able to modify it. checking Clover installer log I was able to trace my fully functional EFI...

hi stefan! please, how were you able to access the system disk via windows? i’m stuck exactly at the same situation

Congrats on the build, @flyingace!! :) Glad to know you managed to do it, I know how time consuming it is, but also rewarding hehe. I have the same VT-d option listed as it is, running smooth for three years now! As far as I know, there's nothing to worry about anymore. Hope you have a great...

Hey flyingace, just saw your posts on both threads. I know how you feel, been there! I'm aware this might be a silly question, but we know much of these processes are so complex we might forget to watch for the little things. What USB stick are you using? Have you tried using another one? I've...

This is so frustrating to read and absolutely unnecessary. I feel what you're doing. This is not called helping.

This guide works til this day. Had Mojave already running on my first SSD, went to installing Windows on my second one. Had to remove all other SATA drives from BIOS for the installer to work. No problems with Clover or boot priority.

Same problem happening. Did anybody solve it somehow?

SUCCESS! Problem solved by making a fresh EFI configuration with Multibeast. It was probably only nVidia leftovers on config.plist :)

Tried resetting CMOS, no success. Same thing happens. How do I check if there’s anything left from nVidia on config.plist?

Hi, I have the exact same issue! Did you ever figure how to solve it??

Hey everyone, I really need help. When I enable CSM in BIOS, computer powers on perfectly, boots clover, starts loading Mojave then loses signal on 75% apple logo. When I disable CSM, I lose signal on pre boot/clover screen, but screen comes up perfectly into macOS. CPU i7 4790K + GA-B85M-D3PH...

Worked for me. Thank you! :) Had a High Sierra build working for 2+ years with nVidia GTX 1050 Ti. Finally decided to upgrade to Mojave. Uninstalled CUDA, removed nVidia Web Drivers then phisically removed GPU. Onboard graphics worked natively, though it showed the same error as mentioned on...

Had the same issue but followed your last suggestion. It worked :)

That sounds painful. I feel you bro. I've been living with that unsolved problem for a year until just now. Did you try turning on CSM at BIOS? This just solved everything for me. Boot speed is the same. I had your same doubts about how to edit config.plist while trying both manually and via...

Same dilemma, same configs. Didn't buy the RTX though. Would you let us know how it went? Thanks :)

Finally! Worked for me!!! After some long days of trial and error, selecting answers all over these forums, your solution worked for me. Can't believe it. I already had my Hackintosh running smoothly on an SSD for more than a year now. A few days ago I tried to install Windows 10 onto an second...

I had the same problem. When I inserted the Windows USB and powered on, clover automatically started some sort of NTFS boot. I actually was able to install any version of Windows, but with a couple of minutes into it it would crash: black BSoD, black screen with cursor, or even no signal input...

These cables. Been there. Congrats on the new Hackintosh and welcome! This community is really great. By the way, did the graphics card work straight "out of the box"? I have an nVidia GTX 1050 Ti so I didn't upgrade to Mojave yet.

Thank you! All of a sudden my Hackintosh had stopped booting while freezing on loading screen (it was working last night). Though it didn't automatically update to 10.13.5, entering safe mode and installing the alternate graphic driver solved the issue. Didn't update the OS to the latest version...