I had a GTX 1080, but I need Mojave for work and since NVIDIA can't get their act together...
So I rolled back to my older Sapphire Radeon R9 380X 4 GB NITRO, since AMD and Apple seem to be BFFs now. It worked out of the box, I was able to upgrade to Mojave without a problem...
The update broke them for me, too. I uninstalled the drivers. Restarted. Installed them with the update-script again. Restarted. Everything back to normal. I think you have to do a clean install, since the patching without it doesn't quite work. That's my analysis at least.
Reporting the same problem. When coming from macOS and booting Windows, G-Sync is disabled. Coming from Windows directly into Windows leaves G-Sync enabled.
Workaround: unplug monitor cable and plug back in.
If I were to upgrade the CPU, would I have to re-do all the iMessage setup? Or can I keep all the IDs even with a new CPU? What Did you search for? Did you encounter any success with an i7 for example? I am considering upgrading the CPU, but keeping my mainboard.
Edit: I found a...
Hey CarluenaDoctor! Thank you for your reply.
I have two Sandisk SSDs for the OSes (120GB SanDisk Plus 2.5" (6.4cm) SATA 6Gb/s TLC Toggle (SDSSDA-120G-G26)). 16 GB RAM. My Graphics card (Sapphire ATI HD 7850 Grafikkarte 1GB) wasn't a problem with the previous install (El Capitan, if I remember...
I recently redid my old gaming rig to incorporate Windows and macOS in the boot loader to be able to play and work with the same machine.
My steps were as follows (everything was installed on fresh SSDs):
- Disconnect all drives, except the macOS drive
- Install macOS and make sure...
I have no idea why people update. I did it because I can't resist an update (stupid me). :-D
I figure newer is better? Just FYI with 3923 it works flawlessly. I booted my machine several time successfully.
Awesome, thanks. I also created a new Clover drive (https://www.tonymacx86.com/threads/test-drive-how-to-create-a-clover-usb.127134/), booted into the system and just updated the already installed clover to v3923. This fixed it. So it probably was a bug in v3922.