Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iMac 2020, 5700XT - graphical glitch?
- Thread starter torifile
- Start date
- Sort by reaction score
I haven't been able to spend much time with mine but I've seen it once. I'm leaning towards it being a software/driver issue, but if it is hardware, I trust Apple Care+ will take care of it. I understand the frustration and if it were a frequent or constant thing (which so far it isn’t), I’d be more upset. But I love the machine and feel confident that if this isn’t something software can fix, I’ll be made whole one way or another.
(Given how much money I spend with Apple every year, I have no shame or reservation in going full Karen if need be.)
(Given how much money I spend with Apple every year, I have no shame or reservation in going full Karen if need be.)
I wish I knew what going full Karen means
Being an obnoxious pain in the rear, demanding to speak to a manager, and escalating demands up the chain of command until the desired result is met.
Hi there, mine is on way back and get replacement, no for just the white lines where no bother me at all, but the graphic card crashed 3 times since got it on 26/08/2020 . the first 2 times with video on 4k the screen for a second turn multicolour and computer go to wake up, means type password on screen after wake up, today happened again but just scrolling Facebook pictures, screen turn multicolour and crash, had the crash report and is related.
Process: WindowServer [222]
Path: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier: WindowServer
Version: 600.00 (451.4)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: WindowServer [222]
User ID: 88
Date/Time: 2020-09-01 09:57:21.031 +0100
OS Version: Mac OS X 10.15.6 (19G2021)
Report Version: 12
Bridge OS Version: 4.6 (17P6610)
Anonymous UUID: 5FD66E16-59B2-F9A5-95E8-6A399BF0E6D7
Sleep/Wake UUID: 9090BCCB-99EB-4AEB-BBB4-9E6F49D8798E
Time Awake Since Boot: 17000 seconds
Time Since Wake: 5100 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000800000058
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [222]
VM Regions Near 0x800000058:
CoreAnimation 00000001bf136000-00000001c2976000 [ 56.2M] r--/r-- SM=PRV
-->
STACK GUARD 0000700009683000-0000700009684000 [ 4K] ---/rwx SM=NUL stack guard for thread 5
Application Specific Information:
StartTime:2020-08-31 20:35:44
PU:AMD
MetalDevice for accelerator(0x3b33): 0x7f94349282f8 (MTLDevice: 0x7f93e8028000)
IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/EGP0@0/IOPP/EGP1@0/IOPP/GFX0@0/AMDRadeonX6000_AmdRadeonControllerNavi10/ATY,Ikaheka@0
Talked by phone with apple and they replace this, because is config order keep this till the new arrives in couple weeks
someone had same experience with 5700XT crashed ( apart white lines )
Process: WindowServer [222]
Path: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier: WindowServer
Version: 600.00 (451.4)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: WindowServer [222]
User ID: 88
Date/Time: 2020-09-01 09:57:21.031 +0100
OS Version: Mac OS X 10.15.6 (19G2021)
Report Version: 12
Bridge OS Version: 4.6 (17P6610)
Anonymous UUID: 5FD66E16-59B2-F9A5-95E8-6A399BF0E6D7
Sleep/Wake UUID: 9090BCCB-99EB-4AEB-BBB4-9E6F49D8798E
Time Awake Since Boot: 17000 seconds
Time Since Wake: 5100 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000800000058
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [222]
VM Regions Near 0x800000058:
CoreAnimation 00000001bf136000-00000001c2976000 [ 56.2M] r--/r-- SM=PRV
-->
STACK GUARD 0000700009683000-0000700009684000 [ 4K] ---/rwx SM=NUL stack guard for thread 5
Application Specific Information:
StartTime:2020-08-31 20:35:44
PU:AMD
MetalDevice for accelerator(0x3b33): 0x7f94349282f8 (MTLDevice: 0x7f93e8028000)
IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/EGP0@0/IOPP/EGP1@0/IOPP/GFX0@0/AMDRadeonX6000_AmdRadeonControllerNavi10/ATY,Ikaheka@0
Talked by phone with apple and they replace this, because is config order keep this till the new arrives in couple weeks
someone had same experience with 5700XT crashed ( apart white lines )
Wow that’s an impressive catch! Ironically, I asked Max on his YouTube channel in a comment post with one of his earlier iMac 5700XT videos if he’s ever seen the graphic glitch and he said no. Perhaps the YouTube reviewers are too busy demonstrating content on camera rather than paying close attention to what’s happening on the iMac screen!?
Joining the club. Got mine today. Core i7, 5700 XT, shipped from Ireland. Seeing white line 1-2 times per hour. Also top left rounded corner rendering issue. Will give it 2 weeks to be fixed via software update, if not, will have to sadly return what is otherwise a great machine. Seen some horror stories with Apple Support in Europe (MacBook keyboard issues) and this is the last thing I'd want to be dealing with given the price paid.
Big Sur is currently incompatible with the 2020 iMac. Fingers crossed the next beta adds support for this machine.
I posted this back when I first saw the rounded corners issue: https://discussions.apple.com/thread/251717086
It's not an extensive thread by any means. And at that point, I hadn't experienced the white lines issue so it's mostly about the corners. From there, I pointed to this thread here.
However, that was enough to get Apple's attention and they called me. That's why I was saying that it's worth posting your experiences there. Either in an existing thread or do a new post.
Here's another post I found that again points to Macrumors: https://discussions.apple.com/thread/251720089
It certainly seems to be software. But, also, something to consider: maybe in Windows nothing exposes it as a hardware flaw? In other words, maybe there is something about the way macOS renders its windows and screens and the card can not cope with that even though on paper it should?
This is 5700 XT 16 GB? Asking because there's a reference to X6000. Could be some universal driver stuff I guess.
Your experience will certainly vary based on who you talk to. If you call the regular Apple customer service and your case is escalated within that "system", it will likely result in the kind of answer you got. In my case, I was contacted by Apple (they called me unexpectedly, to be honest) and it was someone who had clearly done technical information gathering before. This is why I would recommend posting your experiences in the official Apple forum. Provide as many details as you can. And if Apple contacts you based on that post, it will be someone who will at least forward all the information gathered to the right people. Instead of giving you a boilerplate reply.
I was just recording my screen when the glitch happened, I've seen it. Saved the video and went to check it but to my surprise it wasn't there. It's not visible on the from-screen-captured video. Checked frame by frame and it's just not there (was recording with Kap).
If you look back at all the videos about this, they're all via external camera. Not sure what to think of it anymore.
It hasn't been a full day since I switched my resolution to 2048, but figured I'd give an update anyway. I have yet to see the flashing white line. I used the iMac on and off for a few hours in the afternoon, didn't see anything. After I got back from dinner and the wallpaper changed to the darker Catalina wallpaper, as well as dark mode kicking in, I used the machine from about 8pm til midnight continuously, and also did not see the flashing white line.
It's by no means definitive as to what is going on. I've been at the default resolution and not experienced the glitch for several hours at a time so this might just be the case. But a few more days might give a better idea. I'm still leaning/hoping towards it being a software glitch. This takes some getting used to. I don't really like this resolution, my icons are the size of Triscuits
It's by no means definitive as to what is going on. I've been at the default resolution and not experienced the glitch for several hours at a time so this might just be the case. But a few more days might give a better idea. I'm still leaning/hoping towards it being a software glitch. This takes some getting used to. I don't really like this resolution, my icons are the size of Triscuits
What frame rate was your resulting video?
I have tried to capture the white lines with Quicktime screen recording just running for a while. When I saw the lines, I went back and reviewed the screen capture frame by frame. Nothing. Then I realized it was recorded at 55.05fps. Assuming that's the best Quicktime can do running at 5k.
If the lines happen within a single frame (or two or three), it would make sense that you can't necessarily capture them at ~55fps. How could somebody then capture them on their iPhone? Luck? The frame rate being high enough or more even at 30fps to capture 60fps more consistently? Enough "optical lag" of some sort? Not sure.
Or, the issue is simply something like this:
1. Clearly something is going on that's more software level. This is manifested in the form of the rounded/sharp corner issue. This can easily be captured with Quicktime screen recording because it's more on/off instead of a single frame event. So, this, for sure, is present in the screen buffer directly, as viewed.
2. Not familiar enough with the hardware but perhaps the issues at software level (in the visible screen buffer) cause issues later on in that hardware chain? And that manifests as white lines when the card does not know what to do with the data being thrown at it? But we can not capture that with screen recording because that happens as/after the data exits the frame buffer? Don't know enough about how these cards work.
Somehow it reminds me of failed "garbage collection". Extra data or something going on that does not get cleaned up. It is white lines, not any kind of irregular glitches in technicolor (which would suggest random data). So, that's all bits on always.
It begins with a rather alarming "GPU Not Found" message. Same exact macOS build as mine, too. Hmm. If you can, post this to the official Apple forum. If you haven't already. To get some Apple eyeballs potentially looking at that. I haven't experienced anything like this. Yet, anyway. Thanks for posting.
Is 3:0.0 the PCIe bus number, device number and function number of the GPU? Look in ioreg.
"GPU Not Found" means there might have been an issue reading from the PCIe bus - if the PCIe bus reads return all 0xFFFF then it means the PCIe device disappeared. Did this happen near sleep or wake time? Maybe the driver needs to wait longer before performing the read. Or maybe a glitch occurred to cause the read to fail.
The glitch happens in the signal between the GPU and the display. There are two signals to the display, one for the left half and one for the right half. That's why you don't see the glitch span the middle of the screen.
You can use SwitchResX to create custom resolutions if 2048 makes things too large for you.It hasn't been a full day since I switched my resolution to 2048, but figured I'd give an update anyway. I have yet to see the flashing white line. I used the iMac on and off for a few hours in the afternoon, didn't see anything. After I got back from dinner and the wallpaper changed to the darker Catalina wallpaper, as well as dark mode kicking in, I used the machine from about 8pm til midnight continuously, and also did not see the flashing white line.
It's by no means definitive as to what is going on. I've been at the default resolution and not experienced the glitch for several hours at a time so this might just be the case. But a few more days might give a better idea. I'm still leaning/hoping towards it being a software glitch. This takes some getting used to. I don't really like this resolution, my icons are the size of Triscuits
The default resolutions of "Looks like 2560x1440" uses the 5120x2880 resolution/timing.
So, take 5120x2880 and subtract 32 from the width and 18 from the height (16:9 * 2) to get a new resolution. Create a scaled resolution with the result: 5088x2862. macOS will then give you a resolution that "Looks like 2544x1431".