MP 1,1-5,1 Screen settings error

[Krisz]

Hello!
my machine is crazy, can someone help me?
I'll try to explain what it's about, but unfortunately I'm using google translate, so it won't be easy for me
For a few days, my computer has been doing strange things when I change the screen (use as a separate display)
A full HD monitor and an LG 4k UHD TV are connected to the machine (the TV is connected to the machine via a home theater amplifier)
the point is that when I switch from a monitor to a separate display, I get a dark image on both the TV display and the monitor! Most of the times, the machine will turn off and then turn itself back on!
I can't figure out what could be wrong, it worked fine until now, except that for some reason it didn't want to recognize that the TV knows 120 Hertz! maximum 60 Hz that could be selected from the list! I solved this error with the ResExtreme program! It has worked well so far.
in the display settings for the monitor, there is an option for 3840x2160, which I don't understand because the maximum resolution of my monitor is 1080p!
For some reason, it identifies the monitor as having resolutions like my UHD TV
Sometimes I get a kernel panic screen after the machine turns back on!
I don't know how clearly I managed to describe it, but I'll make a video about it if necessary!
I appreciate all the help!

 

[Krisz]

Can't anyone help?
After restarting I get this error code!

mp_kdp_enter() NMI pending on cpus: 0 1
panic(cpu 4 caller 0xffffff80177d9744): mp_kdp_enter() timed-out during locked wait after NMI;expected 12 acks but received 10 after 34827750 loops in 1728999779 ticks @mp.c:1767
Panicked task 0xffffff9040721000: 3 threads: pid 96: watchdogd
Backtrace (CPU 4), panicked thread: 0xffffff86a882d000, Frame : Return Address
0xffffffc03fcd3820 : 0xffffff8017679a3d
0xffffffc03fcd3870 : 0xffffff80177dcd16
0xffffffc03fcd38b0 : 0xffffff80177cc083
0xffffffc03fcd3900 : 0xffffff8017619a90
0xffffffc03fcd3920 : 0xffffff8017679e0d
0xffffffc03fcd3a40 : 0xffffff80176795c6
0xffffffc03fcd3aa0 : 0xffffff8017f14e33
0xffffffc03fcd3b90 : 0xffffff80177d9744
0xffffffc03fcd3bf0 : 0xffffff8017679699
0xffffffc03fcd3c40 : 0xffffff80177dcd16
0xffffffc03fcd3c80 : 0xffffff80177cc083
0xffffffc03fcd3cd0 : 0xffffff8017619a90
0xffffffc03fcd3cf0 : 0xffffff8017679e0d
0xffffffc03fcd3e10 : 0xffffff801763d1a9
0xffffffc03fcd3ee0 : 0xffffff8017c7e964
0xffffffc03fcd3f40 : 0xffffff8017d86f0b
0xffffffc03fcd3fa0 : 0xffffff801761a256

Process name corresponding to current thread (0xffffff86a882d000): watchdogd
Boot args: agdpmod=pikera enable-gva-support shikigva=80 unfairgva=1 mbasd=1 -no_compat_check no32exec=0

Mac OS version:
21H1123

Kernel version:
Darwin Kernel Version 21.6.0: Mon Feb 19 20:24:34 PST 2024; root:xnu-8020.240.18.707.4~1/RELEASE_X86_64
Kernel UUID: FAD66064-42E1-3834-A041-64EB64CDD8CD
KernelCache slide: 0x0000000017400000
KernelCache base: 0xffffff8017600000
Kernel slide: 0x0000000017410000
Kernel text base: 0xffffff8017610000
__HIB text base: 0xffffff8017500000
System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: NO (0xe00002bc)
Hibernation exit count: 0

System uptime in nanoseconds: 439409503192
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000000664ed8f056
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000000192e48c310 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff803e5f2000 - 0xffffffa03e5f2000
. PGZ : 0xffffff803e5f2000 - 0xffffff80425f3000
. VM : 0xffffff80425f3000 - 0xffffff850e926000
. RO : 0xffffff850e926000 - 0xffffff86a7f8c000
. GEN0 : 0xffffff86a7f8c000 - 0xffffff8b742bf000
. GEN1 : 0xffffff8b742bf000 - 0xffffff90405f2000
. GEN2 : 0xffffff90405f2000 - 0xffffff950c925000
. GEN3 : 0xffffff950c925000 - 0xffffff99d8c58000
. DATA : 0xffffff99d8c58000 - 0xffffffa03e5f2000
Metadata: 0xffffffcad7c77000 - 0xffffffcaf7c77000
Bitmaps : 0xffffffcaf7c77000 - 0xffffffcb03c77000



I just can't figure out what's wrong!
It lists unreal resolutions for my monitor and when I switch from one display to two displays, most of the time I get a black screen and after a few seconds the machine turns off and then turns itself back on

 

[tsialex]

NMI Panic Info logs are usually related to the northbridge overheating, you should stop using the Mac Pro until you inspect the northbridge heatsink push-pins.

Even if your northbridge T-diode temperature seems within the expected range usually around 68º to 72º with 75ºC being the limit where the fans start to ramp up, you need to confirm that the push-pins are working and the thermal paste is not a cement or you will damage the CPU tray.

 

[Krisz]

NMI Panic Info logs are usually related to the northbridge overheating, you should stop using the Mac Pro until you inspect the northbridge heatsink push-pins.

Even if your northbridge T-diode temperature seems within the expected range usually around 68º to 72º with 75ºC being the limit where the fans start to ramp up, you need to confirm that the push-pins are working and the thermal paste is not a cement or you will damage the CPU tray.

Thanks for the help! Could a fault in the north bridge cause abnormal resolutions? It identifies my full HD monitor in such a way that 4k resolution can also be selected! And often when I choose the separate screen or switch back to mirroring, the machine turns off and then back on!
I've never seen anything like this before! It doesn't do it under Windows, but there was a case where Mac OS didn't start after Windows! It only worked after turning it off and on again
I'm afraid that my boot is damaged because it's been doing it ever since I reinstalled Windows!

 

[tsialex]

Thanks for the help! Could a fault in the north bridge cause abnormal resolutions?

I don't think so, but NonMaskableInterrupts related kernel panics are serious business and the overheating of the northbridge could damage permanently the CPU tray.

It identifies my full HD monitor in such a way that 4k resolution can also be selected! And often when I choose the separate screen or switch back to mirroring, the machine turns off and then back on!

There are any crash logs when this happens?

I've never seen anything like this before! It doesn't do it under Windows, but there was a case where Mac OS didn't start after Windows! It only worked after turning it off and on again
I'm afraid that my boot is damaged because it's been doing it ever since I reinstalled Windows!

Very weird. Maybe is a combo of display EDID wrong info with incorrect config.plist choices. I'd start making your Mac Pro working reliably with Mojave.

 

[Krisz]

There are any crash logs when this happens?

Yes, I think every time

Very weird. Maybe is a combo of display EDID wrong info with incorrect config.plist choices. I'd start making your Mac Pro working reliably with Mojave.

I downloaded the preconfigured Open Core easy installation from this page! I'm using 0.9.4 because for some reason Windows won't start with versions 0-9.5 and above

Mojave does not support my video card (rx 6600 xt)

 

[Krisz]

There are any crash logs when this happens?

Yes, I think every time

Very weird. Maybe is a combo of display EDID wrong info with incorrect config.plist choices. I'd start making your Mac Pro working reliably with Mojave.

I downloaded the preconfigured Open Core easy installation from this page! I'm using 0.9.4 because for some reason Windows won't start with versions 0-9.5 and above

Mojave does not support my video card (rx 6600 xt)

I'm trying to find the cause of the error and I noticed something strange!
As I wrote at the beginning, the Mac Pro is connected to a home theater amplifier and the amplifier is connected to the TV!
I just tried that the Mac Pro is connected directly to the TV and there are so many changes that when I switch to the separate usage display and return to mirroring the monitor, the machine does not freeze!
I'm trying to find the cause of the error and I noticed something strange!
As I wrote at the beginning, the Mac Pro is connected to a home theater amplifier and the amplifier is connected to the TV!
I just tried that the Mac Pro is connected directly to the TV and there are so many changes that when I switch to the separate usage display and return to mirroring the monitor, the machine does not freeze!
in the image settings, you want to optimize the monitor for the LG TV at all costs! And so screen modes appear that the monitor cannot actually display because it is full HD!
No matter what I do, the monitor always goes back to the wrong resolutions! I've been using the machine this way for years and have never had a problem with it! And it still works fine under Windows10!

 

[Krisz]

I'm trying to find the cause of the error and I noticed something strange!
As I wrote at the beginning, the Mac Pro is connected to a home theater amplifier and the amplifier is connected to the TV!
I just tried that the Mac Pro is connected directly to the TV and there are so many changes that when I switch to the separate usage display and return to mirroring the monitor, the machine does not freeze!
I'm trying to find the cause of the error and I noticed something strange!
As I wrote at the beginning, the Mac Pro is connected to a home theater amplifier and the amplifier is connected to the TV!
I just tried that the Mac Pro is connected directly to the TV and there are so many changes that when I switch to the separate usage display and return to mirroring the monitor, the machine does not freeze!
in the image settings, you want to optimize the monitor for the LG TV at all costs! And so screen modes appear that the monitor cannot actually display because it is full HD!
No matter what I do, the monitor always goes back to the wrong resolutions! I've been using the machine this way for years and have never had a problem with it! And it still works fine under Windows10!

When I switch the amplifier input, e.g. From HDMI2 (The machine is connected to this input!) to HDMI3 or anything else! it also results in black screen and freezes! So, as soon as the machine loses connection with the TV, it immediately freezes!
Windows 10 works perfectly! So macOS is to blame!
I have read that Windows install can destroy the machine! How can you check that the ruin is not damaged?

 

[tsialex]

When I switch the amplifier input, e.g. From HDMI2 (The machine is connected to this input!) to HDMI3 or anything else! it also results in black screen and freezes! So, as soon as the machine loses connection with the TV, it immediately freezes!
Windows 10 works perfectly! So macOS is to blame!

This is very weird. Anyway, I stand by my advice, you should install a compatible GPU and make everything work with Mojave first, after that you can debug the issues with the RX 6600XT.

I have read that Windows install can destroy the machine! How can you check that the ruin is not damaged?

Yes, if you installed Windows via UEFI install. Windows UEFI SecureBoot signs the BootROM and this makes havoc inside the NVRAM volume of the BootROM. MacPro ancient EFI 1.10 is not capable of working around the mess SecureBoot makes inside the VSS stores and the NVRAM corrupts itself overtime, bricking the Mac Pro.

You could have other issues too since you have a cross-flashed early-2009, I'll send you a PM.

 

[Krisz]

This is very weird. Anyway, I stand by my advice, you should install a compatible GPU and make everything work with Mojave first, after that you can debug the issues with the RX 6600XT.



Yes, if you installed Windows via UEFI install. Windows UEFI SecureBoot signs the BootROM and this makes havoc inside the NVRAM volume of the BootROM. MacPro ancient EFI 1.10 is not capable of working around the mess SecureBoot makes inside the VSS stores and the NVRAM corrupts itself overtime, bricking the Mac Pro.

You could have other issues too since you have a cross-flashed early-2009, I'll send you a PM.

Thanks for always helping
Windows can only be installed from a DVD in efi mode, can't it? I created a USB installer using Rufus and installed Windows that way
Unfortunately, OpenCore does not want to install windows from a DVD
But doesn't opencore protect the machine from uefi windows installation?
I've already tried to install it in efi mode, but unfortunately I don't know how to do it
then maybe windows gets stuck at the logo because of the uefi installation?
Sorry for so many questions, but I can't find a solution to this anywhere
With versions after opencore 0.9.4, Windows stops loading at the logo!

 

[tsialex]

Thanks for always helping
Windows can only be installed from a DVD in efi mode, can't it? I created a USB installer using Rufus and installed Windows that way

Windows via USB = UEFI install = SecureBoot signing the BootROM
Windows via DVD = Legacy/CSM/BootCamp install = no SecureBoot

Unfortunately, OpenCore does not want to install windows from a DVD

OpenCore since 0.9.5 supports BootCamp/Legacy Windows installs and you can always use the Apple BootPicker to bypass OpenCore, even with your RX 6600XT (for this, EnableGop needs to be injected to the Mac Pro BootROM or to the GPU firmware).

But doesn't opencore protect the machine from uefi windows installation?

If you have ProtectSecureBoot enabled and more importantly, you never ever booted Windows UEFI directly.

Windows is known to frequently have boot coups while installing major updates and completely bypassing OC.

I've already tried to install it in efi mode, but unfortunately I don't know how to do it
then maybe windows gets stuck at the logo because of the uefi installation?

So, your BootROM is shot, for more than one reason. Cross-flashed early-2009s with problematic BootROM have this exact behaviour with Windows, is a BootBlock EFI issue. Get everything I've asked in the PM and I'll take a look.

Sorry for so many questions, but I can't find a solution to this anywhere
With versions after opencore 0.9.4, Windows stops loading at the logo!

Like I've written above, you can install Windows via BootCamp/CSM/Legacy to a SATA disk and never ever think again about UEFI issues.

Since 0.9.5 OC supports Legacy installs and you can always bypass OC completely via the Apple BootPicker.

 

[Krisz]

Now it seems that the display problem is solved! I have no idea what it is from and how long it will stay good
I pulled out all the HDMI cables and set the displays so that the monitor is the main screen!
Now, when I turn on the TV, it automatically switches to a separate display and when I turn off the TV, it goes back to the monitor and the real 1080p resolution is also visible in the system report!

I use a separate SSD for Windows and a separate one for MacOS!
The only way to install Windows with bootcamp is to share the SSD storage and create a partition, but I would like Windows to be on a separate SSD
Is it possible to get Boot Camp to install Windows on an empty SSD somehow?

 

[tsialex]

The only way to install Windows with bootcamp is to share the SSD storage and create a partition, but I would like Windows to be on a separate SSD
Is it possible to get Boot Camp to install Windows on an empty SSD somehow?

Yes, just install via Legacy mode, without BootCamp Assistant. Burn W10 to a 2-layer DVD and boot from it. After Windows is already installed, you can install all drivers via Brigadier.

You need a flashed GPU or EnableGop to do that.

 

[Krisz]

But Windows can only be installed from DVD without using opencore, if I start using the opencor bootloader again after installation, Windows will not be visible in the opencore boot menu
How can I make Windows visible using opencor?
I usually use the IObit Driver Booster application to install the Windows driver, it searches for and installs the drivers automatically

 

[tsialex]

But Windows can only be installed from DVD without using opencore, if I start using the opencor bootloader again after installation, Windows will not be visible in the opencore boot menu
How can I make Windows visible using opencor?
I usually use the IObit Driver Booster application to install the Windows driver, it searches for and installs the drivers automatically

Like I've written already, since 0.9.5 OpenCore supports Legacy OS installs via OpenLegacyBoot:

Implement legacy OS booting support by Goldfish64 · Pull Request #482 · acidanthera/OpenCorePkg

Adds support for booting of legacy OSes such as older versions of Windows or situations where legacy Windows must be used for proper functionality of hardware. Scope includes both Macs (via legacy ...

github.com

Manually Configured OpenCore on the Mac Pro

Yes, these drivers work. Their usage is explained in the reference manual: https://github.com/acidanthera/OpenCorePkg/blob/0.9.8/Docs/Configuration.pdf The purpose of OpenLegacyBoot is to boot legacy installations. Note that such installations are not possible for macOS. For Windows, the...

forums.macrumors.com

Anyway, again, you don't need OpenCore to boot a Legacy/CSM/BootCamp install, just bypass OpenCore completely via Apple native BootPicker (for this to work, EnableGop EFI module needs to be injected to the Mac Pro BootROM or to the GPU firmware).

 

[Dayo]

I would like Windows to be on a separate SSD

This method actually wants you to install on a separate disk:

Bare Metal Windows on cMP

PART 1 of 3 This is a guide to installing Windows 10 on Classic Mac Pros without Bootcamp or similar (Bare Metal). This is one of many ways to do this but is a straightforward method. This guide is for installing Legacy Windows, as opposed to UEFI Windows, but can also be used for installing...

forums.macrumors.com

 

[Krisz]

Like I've written already, since 0.9.5 OpenCore supports Legacy OS installs via OpenLegacyBoot:

Implement legacy OS booting support by Goldfish64 · Pull Request #482 · acidanthera/OpenCorePkg

Adds support for booting of legacy OSes such as older versions of Windows or situations where legacy Windows must be used for proper functionality of hardware. Scope includes both Macs (via legacy ...

github.com

Manually Configured OpenCore on the Mac Pro

Yes, these drivers work. Their usage is explained in the reference manual: https://github.com/acidanthera/OpenCorePkg/blob/0.9.8/Docs/Configuration.pdf The purpose of OpenLegacyBoot is to boot legacy installations. Note that such installations are not possible for macOS. For Windows, the...

forums.macrumors.com

Anyway, again, you don't need OpenCore to boot a Legacy/CSM/BootCamp install, just bypass OpenCore completely via Apple native BootPicker (for this to work, EnableGop EFI module needs to be injected to the Mac Pro BootROM or to the GPU firmware).

Unfortunately, this is very complicated for me
I'll try it, but I'm not sure if it will work

 

[Krisz]

This method actually wants you to install on a separate disk:

Bare Metal Windows on cMP

PART 1 of 3 This is a guide to installing Windows 10 on Classic Mac Pros without Bootcamp or similar (Bare Metal). This is one of many ways to do this but is a straightforward method. This guide is for installing Legacy Windows, as opposed to UEFI Windows, but can also be used for installing...

forums.macrumors.com

Thanks for the help

 

[Krisz]

Unfortunately, this is very complicated for me
I'll try it, but I'm not sure if it will work

I really don't want to bore you with my questions, but there is one more annoying thing that I don't know how to solve
It has happened several times that the icon and the name of the volume change in the boot menu!
When installing MacOS, I specified OSX as the volume name!
High Sierra is installed on another HDD so that there is a system that is supported and I can start it if there is a problem!
After I started it, the icon and volume name changed! But this also happens when I install an older Mac OS! eg mojave
Then the OSX location will be shown as OSX data!
It does not affect the operation of the system, but it is disturbing
How can I call it back to OSX and make the monterey icon appear?

 

[Dayo]

I had High Sierra. Stuff then got messed/mixed up.

This is a problem with running HiSierra and newer Mac OS together.

See here for how to sort it out:

High Sierra booting possibly corrupts newer Systems. Fix, description and a boot picker renamer

Summary: We discovered a serious bug: booting High Sierra without System Integrity Protection (csrutil disable) possibly corrupts another mounted (unsupported) APFS2* OS Preboot volume, even when on another drive. Consequently, the corrupted OS may appear as High Sierra and check for...

forums.macrumors.com

Do not disable SIP in HiSierra to avoid the issue.

 

[Krisz]

This is a problem with running HiSierra and newer Mac OS together.

See here for how to sort it out:

High Sierra booting possibly corrupts newer Systems. Fix, description and a boot picker renamer

Summary: We discovered a serious bug: booting High Sierra without System Integrity Protection (csrutil disable) possibly corrupts another mounted (unsupported) APFS2* OS Preboot volume, even when on another drive. Consequently, the corrupted OS may appear as High Sierra and check for...

forums.macrumors.com

Do not disable SIP in HiSierra to avoid the issue.

thanks for your help
I think I will try to sell this machine for parts because something is very wrong with it
I wanted to restart it and it froze! Then I had to turn it off and back on 3 times to get it to start!
there was no problem until the login screen, but after I entered the password it was just a black screen

 

[tsialex]

thanks for your help
I think I will try to sell this machine for parts because something is very wrong with it
I wanted to restart it and it froze! Then I had to turn it off and back on 3 times to get it to start!
there was no problem until the login screen, but after I entered the password it was just a black screen

Classic northbridge overheating. NMI kernel panics are 95% related to the heatsink not making contact anymore.

 

[Krisz]

Classic northbridge overheating. NMI kernel panics are 95% related to the heatsink not making contact anymore.

The original heatsink holder broke and I replaced it with a screw a long time ago!
I used a Thermal Grizzly Carbonaut sheet because, in principle, it cannot age
If the problem was caused by overheating, it would appear when I run some processor-demanding application, wouldn't it?
Recently, it has also happened that it came back from sleep mode with a black screen

 

[tsialex]

The original heatsink holder broke and I replaced it with a screw a long time ago!
I used a Thermal Grizzly Carbonaut sheet because, in principle, it cannot age
If the problem was caused by overheating, it would appear when I run some processor-demanding application, wouldn't it?

It's not so simple since not all heavily usage of CPU are also memory bound. The high northbridge usage is basically memory dependent.

You will have more issues at warm boot, when POST verify the RAM and does all the loading and when you have heavy usage of RAM/swap/DMA disk transfers.

Recently, it has also happened that it came back from sleep mode with a black screen

Did you verified the RTC battery voltage? KPs while sleeping and immediately after wakening are frequently caused by the RTC being stuck, so, the RTC battery voltage is the first thing to check.

Even if you replaced it recently, double check. Btw, a CR2032 will cook itself with the hot air from the GPU heatsink and self discharge completely over time.

You need to replace it with the factory installed BR0232, the different chemistry (Carbon monofluoride + Lithium) is tolerant up to 80ºC and have no problems with the heat from the GPU heatsink.

 

[Krisz]

I checked the battery today and the multimeter showed 3.0v
approx. I changed it 3 years ago
It's true that I haven't used Windows much recently, but it seems to work flawlessly!
It's like MacOS just doesn't want to work properly
However, a game has also become problematic on Windows since I reinstalled Windows
there is a game that worked flawlessly and since the reinstallation I start it and when it loads and the game is almost loaded the computer freezes but only turning it off and then on again helps!
I also thought that the video card is starting to fail or the error in the new radeon driver is causing the game to freeze
however, I tried other games under Windows and it lags
in the past it was like that sometimes it stuck, but now it's quite frequent
in principle, there is no overheating, but you wrote that the system does not indicate it in all cases