I have a 2011, 15" MacBook Pro (running 10.6.8) with the defunct, AMD(?) graphics chip. I'm trying to connect to a 23" Apple Cinema Display using a brand-new Mini DisplayPort to DVI adapter (LogiLink CV0037), **but it doesn't work.** I am aware that my laptop has a Thunderbolt port, not a Mini DisplayPort. However, everything I've read seems to indicate that a Mini DisplayPort to DVI adapter should work perfectly fine for what I'm trying to do, given Thunderbolt's 'backward compatibility'. The most likely culprit in my mind is that I've permanently disabled the faulty graphics chip by following these video instructions , which might be interacting with how my machine connects with the display. Is this likely correct? Is the AMD(?) chip required to run external displays? Are there any other obvious possibilities? Also, it's worth noting: Both the display and adapter do in fact work. I plugged the display into an older 17" MBP with a mini-DisplayPort with no problems. Also when I pull the adapter out of either the 15" or 17", the laptop screen goes blue for a few seconds, suggesting that the 15" MacBook Pro is also detecting something, just not integrating the display connection fully(?).

I was running a google meet call in Firefox and had a few other tabs open, including a gitlab one with an embedded video (which _might_ have been part of the cause of this) when I noticed considerable lagging in the responsiveness of windows, not just firefox. I found the following conspicuous messages in the console app: IOGraphicsAccelerator::newUserClient(): process plugin-container (PID 1934) has too many contexts (510) + queues (0) + device (171) + shared (171) created. Possibly leaking? It also affects opening browser tabs in e.g. Safari and general system responsiveness. I couldn't find much on this kind of error message other than the plugin-container process seems to belong to Firefox. This is a Macbook Pro with macOS Catalina 10.15.7.

my MacBook Pro (Retina, 13-inch, Mid 2014) Big Sur 11.2.2 freezes regularly after login. I can only run it in safe mode. I had the problem before the update to Big Sur, I updated it hoping it would fix it, but I still have the same issue. Things I tried: Things I already tried: -Etrecheck: all good -Reboot in recovery and repair disk. -Reset the SMC, the PRAM/NVRAM -Went through all the tips in this article (but go to an expensive mac store) -Uninstalled a bunch of old apps I have some crash reports mentioning WindowServer, I used Ulbow to check the log relative to those 2 minutes in which the crash took place. It seems like every time it crashes I have a Windowserver crash report (see below) My suspect is that I have an issue with GPU. Any suggestion on how to determine if it is my GPU being faulty (maybe just dusty and old) or some software conflict? How to determine the problem? I have a full back up from time machine on an external drive in case I need to format, but I was hoping to make a couple of tests first. How to move on? Thanks in advance for your precious help. Here some failures in the log in the minute where Console is signalling a crash of WindowServer

Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.xpc.launchd.domain.user.loginwindow.500.4294967295): entering bootstrap mode
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.imklaunchagent): This service is defined to be constantly running and is inherently inefficient.
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.coreservices.UASharedPasteboardProgressUI): Unknown key for Boolean: DrainMessagesAfterFailedInit
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.UserEventAgent-LoginWindow): This service is defined to be constantly running and is inherently inefficient.
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.xpc.launchd.domain.user.loginwindow.500.4294967295): com.apple.universalaccessd (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.xpc.launchd.domain.user.loginwindow.500.4294967295): com.apple.VoiceOver (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.xpc.launchd.domain.user.loginwindow.500.4294967295): com.apple.accessibility.AXVisualSupportAgent (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.xpc.launchd.domain.user.loginwindow.500.4294967295): com.apple.AskPermissionUI (lint): UserName is not supported for non-System services.
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.xpc.launchd.domain.user.loginwindow.500.4294967295): com.apple.AssistiveControl (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.xpc.launchd.domain.user.loginwindow.500.4294967295): com.apple.DwellControl (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.xpc.launchd.domain.user.loginwindow.500.4294967295): com.apple.universalaccesscontrol (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.coreservices.useractivityd): Unknown key for Boolean: DrainMessagesAfterFailedInit
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.xpc.launchd.domain.user.loginwindow.500.4294967295): exiting bootstrap mode
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.coreservices.useractivityd): Service exited due to SIGKILL | sent by useractivityd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.quicklook.ThumbnailsAgent): Service exited due to SIGKILL | sent by com.apple.quicklook.ThumbnailsAg
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.CloudDocs.MobileDocumentsFileProvider): Service exited due to SIGKILL | sent by com.apple.CloudDocs.MobileDocume
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.corespotlightd): Service exited due to SIGKILL | sent by corespotlightd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.followupd): Service exited due to SIGKILL | sent by followupd
Mar  8 16:18:01 danieles-MacBook-Pro WindowServer: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.Dock.agent): Service exited with abnormal code: 1
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.ScreenTimeAgent): Service exited due to SIGKILL | sent by ScreenTimeAgent
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.ContextStoreAgent): Service exited due to SIGKILL | sent by ContextStoreAgent
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.CryptoTokenKit.ahp.agent): Service exited due to SIGKILL | sent by ctkahp
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.parsec-fbf): Service exited due to SIGTERM | sent by launchd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.remindd): Service exited due to SIGTERM | sent by launchd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.amp.mediasharingd): Service exited due to SIGTERM | sent by launchd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.appstoreagent): Service exited due to SIGTERM | sent by launchd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.CloudDocsDaemon.container-metadata-extractor): Service exited due to SIGTERM | sent by launchd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.storedownloadd): Service exited due to SIGTERM | sent by launchd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.askpermissiond): Service exited due to SIGTERM | sent by launchd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.networkserviceproxy): Service exited due to SIGTERM | sent by launchd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.amsaccountsd): Service exited due to SIGTERM | sent by launchd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.CalendarNotification.CalNCService): Service exited due to SIGTERM | sent by launchd
Mar  8 16:18:01 danieles-MacBook-Pro com.apple.xpc.launchd (com.apple.akd): Service exited due to SIGKILL | sent by akd
Mar  8 16:18:01 danieles-MacBook-Pro mdsync: objc: Class MDSPathFilter is implemented in both /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata and /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mdsync. One of the two will be used. Which one is undefined.

I had this common GPU issue on a 2011 MBP that I was able to solve with the super detailed post by the user "LаngLаngС" (thanks so much!) as found here: https://apple.stackexchange.com/questions/267581/gpu-problem-boot-hangs-on-grey-screen/295805#295805 Unfortunately a new problem occured that prevents me from running the script. I'll explain: To solve the GPU issue I everything as written in LangLangC's post and I also had the executable sh script on my desktop – so when I had to boot the Mac again, I did this in single user mode with CMD + S, and then typed "sh /force-iGPU-boot.sh" and then reboot. This would boot my machine always as normal with the internal GPU. So far so good – until yesterday. When trying to reboot again from Single User Mode, I got this new prefix "sh 3.2#" and the lines looked different. It says that the volume is "read only"-. When I try to execute "sh /force-iGPU-boot.sh" it says, file or directory not found. I cant run "sudo" commands as it says "command not found". When I try to remount with "mount -uw" it doesn't work – it always says "device is write locked. When I type exit or reboot the system actually seems to boot "normal" – if there wasn't the GPU issue! Meaning that if I cannot run the script "force-iGPU-boot.sh" from the single user mode, I cannot boot the GUI Mac OSX properly. Unfortunately I also cannot execute the sudo commands. I also tried to boot the Mac in target mode and "repair" the drive with the disk utility of another Mac, but that never worked either. I was googling a lot and tried a lot but nothing worked yet. Since I am not very familiar with these kinds of issues, I was hoping to find an answer here, where I found the first answers to my GPU problem. Basically my "new problem" is that I cannot run the automated script that I saved on the desktop or the sudo commands from the single user mode. This is the output of sw_vers: https://ibb.co/g41TtQQ macOS 10.13.6 Is anyone able to offer suggestion to run this script?

I tried installing nvidia-smi with home-brew, but it is not working out, this is my output -bash: nvidia-smi: command not found I have CUDA 7.5 installed and this is the output of my nvcc -V command Mine is a 15" Macbook Pro Retina, with Nvidia 750M GPU > nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2015 NVIDIA Corporation Built on Thu_Sep_24_00:26:39_CDT_2015 Cuda compilation tools, release 7.5, V7.5.19 Output of kextstat command kextstat | grep -i cuda 140 0 0xffffff7f82675000 0x2000 0x2000 com.nvidia.CUDA (1.1.0) 5AFE550D-6361-3897-912D-897C13FF6983 OS version 10.11.4

Whenever I connect my Intel MacBook Pro to an external 4K-display and playback video on YouTube or on a video call, for example, CPU usage on kernel_task gradually increases until all 8 cores are at almost 100% and the whole system slows down. The video becomes choppy and I am forced to terminate whatever video-playback is running or disconnect the external display. This seems to be independent of the video resolution of what I am playing. The only difference seems to be that when I connect my external display, the graphics changes to use the AMD-chip, when I disconnect the display it falls back to the Intel-chip. So when using the more powerful graphics-chip the video playback capabilities are worse than when using the less powerful one. Is there anybody with the same problem? Is there any way to fix this behaviour? **2019 Intel MacBook Pro 16"** - Graphics: AMD Radeon Pro 5500M 8GB and Intel UHD Graphics 630 1536 MB - RAM: 32GB - CPU: 2,3 GHz 8-Core Intel Core i9 **Details** - Connected via USB-C to a display that also charges the Mac. - Mac is not in low-power mode.

I have Xcode 15 installed in Sonoma on a mid 2014 MBP 15" (not officially supported hardware — uses OCLP). There is a big issue with rendering Storyboards, which corrupts not just the rendering of Xcode, but all visible desktops and workspaces as well. They are not workable. There are no crashes, and rendering can be restored to normal simply by hiding the Storyboard editor and making sure all corrupt areas are re-rendered, which suggests the issue is simply with rendering instructions and isolated to graphics buffers. This only happens when external monitors are connected.

I have a MacBook Pro 15" early 2011 running macOS Catalina with dosdude1's Catalina patcher. The dedicated GPU is inactivated with the non-permanent solution circulating elsewhere. Ever since I upgraded (perhaps already in Mojave, but not sure about that) I'm unable to use Google Maps and most other map services in Firefox and Safari. In Google Maps, the map view renders correctly, but I'm unable to click any points of interest, and if I move around the map it lags heavily and soon turns black; basically unusable. However, in Opera Google Maps works perfectly fine! The computer does heat up and the fans start spinning, but at least Google Maps is fully functional and runs smoothly. Apple's own Maps app also runs without any trouble at all. I also have two MacBook Pro 13" mid-2012 also running Catalina (officially supported), where Google Maps works perfectly fine on both Firefox and Safari, so it doesn't seem to be due to lacking browser support. Any idea what could be causing this? I assume the inactivated GPU may have something to do with it, but why does it work fine in Opera?

Being new to Mac and experienced with Windows, I'm running macOS Catalina (10.15.4) and I have an external GPU for my A.I. and data science training. However, one of the applications I use (Azure Storage Explorer) seems to have an issue with the GPU, as I can read this in their release notes : > The Electron shell used by Storage Explorer has trouble with some GPU (graphics processing unit) hardware acceleration. If Storage Explorer is displaying a blank (empty) main window, you can try launching Storage Explorer from the command line and disabling GPU acceleration by adding the --disable-gpu switch My questions: - Is there an option to mark an application so that it just does not use the GPU by default? - If not, is there a way to add that --disable-gpu automatically to the application, so that I don't have to add it every time ? - If none of the above work: how can I even start the application (which is installed in the Applications folder) from the terminal? __Edited__: - I have found the answer to the 3rd question, but obviously still hope to get a solution by finding an answer to Q1: do shell script "open -a '/Applications/AzureStorageExplorer.app/Contents/MacOS/Microsoft Azure Storage Explorer' --args --disable-gpu"

My MacBook Pro's built-in display started flickering (screen goes black) a few weeks ago. Most of the time the flickering stops by itself randomly after a couple of minutes. The thing is, when I connect to an external display using HDMI, the flickering on the built-in display stops, and both displays function normally. Are there any suggestions for troubleshooting this issue?

So, I have a MacBook Pro 15” and I recently bought an LG 27” 4K monitor. When I connected the monitor, system report said that the original resolution is 4K but the picture looks like 1920x1080 (using 4 pixels for 1 displayed pixel) on the screen. The text was too big for me. I was then able to access scaling options and opted for the option that looks like 1440p with the original resolution of 5k. This seems to give the best image and size for this external monitor. Now, I want to understand why the image is clear at what looks like 2560 x 1440 on my 4K monitor since the pixel distribution is not a modulus of 0. In my understanding, there is no way to distribute a 5k picture on a 4K monitor and yet get a clear picture. Since 5k is only 1.33 times bigger than 4k horizontally and vertically, how does it render? Is the picture quality worse than I think?

I don't like TeamViewer taking up space on the Dock. I followed this tutorial to hide the dock icon, leaving me with only a menubar icon, which works great. TeamViewer is set to start at login. However, in a MacBook Pro with discrete graphics, when logging into another computer, TeamViewer forces a switch to discrete graphics, and even after logging out of said computer, it stays that way, which is of course awful for battery life. I am forced to quit TeamViewer so I can go back to integrated graphics and decent battery life. However, if I try to launch TeamViewer again, it doesn't work -- I get a request to type my password to install a helper tool, and then nothing. What should I do to simulate whatever procedure is performed during system boot that allows TeamViewer to start?

I'm looking to update from the stock graphics card in my my Mac Pro 3,1 (2008). The logic board only has two 6-pin ATX connectors, and the card I'm looking at (a GeForce GTX 760) requires one 6-pin and one 8-pin ATX connector. From my research the power supply should be able to handle it, as I don't have any other PCI devices. There are 6-pin to 8-pin ATX adapters available, but I'm not sure the tracks on the logic board would be rated for the higher power, and may burn out. I do, however have a spare molex 4-pin power connector for an IDE disk drive. What is the rated power for one of these type connectors, and is there any way to use that, or a combination of that and the other 6-pin ATX connector to provide enough power to the card? Thanks!

I have Mac Pro 5,1 (Mid-2010) and I want to upgrade it's GPU to increase the performance of Windows under Bootcamp. I do not care about GPU power in OSX. Which GPUs are supported in OS X/macOS ? (I also do not care about boot screen)

I have a late 2014 5K iMac with 256GB SSD drive. Last night my iMac started making noises similar to that of a disk drive when it's performing reading and writing operations. After poking around I found that the noise must be related to the GPU because: - The noises increase when scrolling a webpage or change workspaces and then subside when I stop. - Running a web GPU benchmark or watching a video will make the noise constant until I close it - Also changing the brightness causes the noise I doesn't sound like a bad fan as it's a very clicky noise versus a whine or hum. I ran the hardware diagnostic test (Holding D when you restart) which resulted in no errors. I tried to blow some air in the GPU vents which didn't change anything. I feel if I take the iMac in and describe the issue they will send the iMac away for few weeks and it will be sent back saying there isn't any issues. Any suggestions? Here is what it sounds like . It also makes this sound when the display is off, so it could be like @Allan said that it is the power supply.

I have a 2019 MacBook Air and sometimes, this problem happens when I try to open the laptop; it glitches. I think this happens because I restored the Mac and deleted all my old files last week. But this really only happened a few times in the past week and only happend twice. I don’t know if I have to fix it or if it’s covered under warranty.

I'm currently running 10.13.6 and have a MacBook pro 8,3, 2.2 GHz. How can I upgrade my GPU for my 2011 17" early to run Mojave? I've heard I could replace the logic board with a newer GPU and processor but can't seem to find the company. I also heard they offer a 1 year guarantee.

My MacPro (Late 2013, OSX Yosemite) has two AMD FirePro D500 GPUs and three Cinema HD Displays. When I look at the System report all of the Displays show up under one GPU and the other GPU has nothing. Is the other GPU (slot-1) being utilized at all? How do I tell? Can I move a display to the unused GPU? Will this help performance for rendering or calculations? AMD FirePro D500: Chipset Model: AMD FirePro D500 Type: GPU Bus: PCIe Slot: Slot-1 PCIe Lane Width: x16 VRAM (Total): 3072 MB Vendor: ATI (0x1002) Device ID: 0x679e Revision ID: 0x0000 ROM Revision: 113-C3861J-687 gMux Version: 4.0.11 [3.2.8] EFI Driver Version: 01.0B.687 AMD FirePro D500: Chipset Model: AMD FirePro D500 Type: GPU Bus: PCIe Slot: Slot-2 PCIe Lane Width: x16 VRAM (Total): 3072 MB Vendor: ATI (0x1002) Device ID: 0x679e Revision ID: 0x0000 ROM Revision: 113-C3861J-687 gMux Version: 4.0.11 [3.2.8] EFI Driver Version: 01.0B.687 Displays: Cinema HD: Display Type: LCD Resolution: 2560 x 1600 Pixel Depth: 32-Bit Color (ARGB8888) Display Serial Number: [redacted] Main Display: Yes Mirror: Off Online: Yes Rotation: Supported Adapter Type: Apple Mini DisplayPort To Dual-Link DVI Adapter Adapter Firmware Version: 1.03 Cinema HD: Display Type: LCD Resolution: 2560 x 1600 Pixel Depth: 32-Bit Color (ARGB8888) Display Serial Number: [redacted] Mirror: Off Online: Yes Rotation: Supported Adapter Type: Apple Mini DisplayPort To Dual-Link DVI Adapter Adapter Firmware Version: 1.03 Cinema HD: Display Type: LCD Resolution: 2560 x 1600 Pixel Depth: 32-Bit Color (ARGB8888) Display Serial Number: [redacted] Mirror: Off Online: Yes Rotation: Supported Adapter Type: Apple Mini DisplayPort To Dual-Link DVI Adapter Adapter Firmware Version: 1.01

Sorry this might be a bad question, but why isn't the iGPU being used at all for playing video? Shouldn't it be used at least a little for encoding/decoding video? I have hardware acceleration and everything seems to be enabled on chrome: Here is a test of youtube running on chrome, with gpu showing 0% on stats.app and activity monitor. Chrome dev tools > Media shows video encoder and decoder are not available(?). So is everything being software encoded/decoded, which explains the higher CPU usage? My specs: - MacBook Pro 2015 13 inch - Intel Core i7-5557U 3.10GHz - Intel Iris Graphics 6100 - 16GB DDR3 Would greatly appreciate an explanation for this. Thank you!

I have a 2019 Macbook Pro with an AMD Radeon Pro 5500M graphics processor plus Intel integrated graphics. When I connect the laptop to a StarTech Triple Monitor USB 3.0 Docking Station that has 2 monitors (27" 2560x1440) connected to it, I see only the Intel integrated graphics being used. use case: I'm trying to run X-plane 12. This complains it can't use the external monitors because they don't have enough available VRAM. The Radeon Pro 5500M has enough VRAM available, so the computer must be using the Intel integrated graphics to drive the external monitors. Is it possible for the AMD Radeon Pro 5500M to control external monitors hooked up via a USB dock, or would I have to connect the monitors directly?