Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Thanks a lot for all that testing!! :)
I saw similar behaviour with several different 32GB Ram modules under Win10Pro, High Sierra and Mojave, but didn't try Yosemite..
Just one thing: If I understood it correctly, @edgerider did run Hígh Sierra with 4x M393B4G70BM0-YH9, and 2x 16GB modules (160GB), on a 4,1 > 5,1..?
Anyway, I wasn't able to see a single M393B4G70BM0-YH9 under High Sierra or Mojave, also on 4,1 flashed to 5,1.
 
I have tested 1x 16GB + 1x 32GB modules on X5660 single CPU tray with Verbose mode this morning.
* macOS Catalina 10.15
** In EFI boot screen, the background is turned from white to black, a character cursor appears, but nothing is displayed.
* macOS Mojave 10.14.5
** It does not boot. The last message is "End RandomSeed".
* macOS High Sierra 10.13.6
** It boots, but recognizes only 16GB.
* macOS El Capitan 10.11.6
** It boots, but recognizes only 16GB.
* macOS Yosemite 10.10.5
** It boots, and recognizes all RAM modules as 48GB, but 32GB module is "Empty" at "About This Mac".

2019-06-16 08.57.03.jpg 2019-06-16 08.53.25.jpg Screen Shot 2019-06-16 at 9.06.40 AM copy.png Screen Shot 2019-06-16 at 9.06.51 AM.png Screen Shot 2019-06-16 at 9.57.34 AM copy.png Screen Shot 2019-06-16 at 9.57.41 AM.png
[doublepost=1560719749][/doublepost]
Just one thing: If I understood it correctly, @edgerider did run Hígh Sierra with 4x M393B4G70BM0-YH9, and 2x 16GB modules (160GB), on a 4,1 > 5,1..?
I searched the forum, but I could not find @edgerider 's post about High Sierra and 160GB.
Instead, I found the similar result at @Kon_Kipa 's post in this thread https://forums.macrumors.com/thread...nyone-tried-this.2046693/page-2#post-27168182
 
Last edited:
I searched the forum, but I could not find @edgerider 's post about High Sierra and 160GB.

Ah, right, my bad.. :)
I got mail contact via some hardware vendor, and did some nice talking, but was not sure about reading the very same person, here.. ;)
[doublepost=1560722848][/doublepost]...here's some stuff I saw myself, for what it's worth.. ;)
 

Attachments

  • GB4_256GB.PNG
    GB4_256GB.PNG
    51.9 KB · Views: 353
  • GB4_192GB.PNG
    GB4_192GB.PNG
    49 KB · Views: 371
  • screen 144GB RAM.PNG
    screen 144GB RAM.PNG
    46.1 KB · Views: 404
  • 32RAM_08apr19_unbox.jpg
    32RAM_08apr19_unbox.jpg
    1 MB · Views: 376
  • 32GB_mar19.jpg
    32GB_mar19.jpg
    715 KB · Views: 391
  • 32GB_unboxed.jpg
    32GB_unboxed.jpg
    2.1 MB · Views: 414
  • GB4_498EHz.jpg
    GB4_498EHz.jpg
    274.1 KB · Views: 374
  • ubuntu_256GB_screen_01.jpg
    ubuntu_256GB_screen_01.jpg
    1.1 MB · Views: 383
Kazkus, thanks a lot for these tests. ;)

It's weird that it works under Yosemite, Windows 10, Ubuntu, and not at all with the other versions of Mac OS.

I was thinking of buying a double CPU Tray, to expand the ram, now I'm hesitating, and I think I'll stay under Windows 10, with my two Nvidia GPU.

If we can use 96 or 128 GB with one X56XX CPU, it's really cool.
 
Still very curious how proper 2Rx4 PC3-10600R DDR3 1333MHz ECC 32GB sticks would behave in all these tests.
 
Still very curious how proper 2Rx4 PC3-10600R DDR3 1333MHz ECC 32GB sticks would behave in all these tests.
And where would someone find memory of this configuration?
I am curious, too, because we don't know why macOS 10.11 - 10.15 does not recognize M393B4G70BM0-YH9 32GB DDR3 4Rx4 ECC memory module.
It might be because of 32GB module or because of 4Rx4 (Quad-Rank).
If we have 2Rx4 (Dual-Rank) DDR3 32GB memory module, we should have some idea.
Instead, does somebody know if macOS 10.11 - 10.15 supports 16GB 4Rx4 (Quad-Rank) DDR3 memory module ?
 
I am curious, too, because we don't know why macOS 10.11 - 10.15 does not recognize M393B4G70BM0-YH9 32GB DDR3 4Rx4 ECC memory module.
It might be because of 32GB module or because of 4Rx4 (Quad-Rank).
If we have 2Rx4 (Dual-Rank) DDR3 32GB memory module, we should have some idea.
Instead, does somebody know if macOS 10.11 - 10.15 supports 16GB 4Rx4 (Quad-Rank) DDR3 memory module ?

4Rx4 works, but just may have some adverse effect (depends on the actual memory config), e.g. the memory speed will be decreased.
 
Still very curious how proper 2Rx4 PC3-10600R DDR3 1333MHz ECC 32GB sticks would behave in all these tests.
me to because i think the problem is here. 2rx4 ok but 4rx4 not ok with 3rd slot shared with 4th.
cant find 32gb 2rx4, hynix apparently had done some but i cant find any sku
 
does somebody know if macOS 10.11 - 10.15 supports 16GB 4Rx4 (Quad-Rank) DDR3 memory module ?

It most certainly does work in 10.11 and 10.13 as I have two machines here using 4Rx4 16GB modules.

One is a single CPU machine, and one a dual, and they work fine as long as you only populate the first 3 slots on any CPU. If you try and use 4Rx4 in all 4 slots then 'bad things happen' as it gets grumpy about two lots of 4Rx4 in the 3/4 shared channel slots.

The only 32GB modules I have available are currently in use in our ESX hosts so not able to pull them out and test, and I'm 99% sure they're also 4Rx4.

It would definitely be interesting to try some 2Rx4 32G modules if someone could lay their hands on any...
 
yeah i think thats the problem you cant have 8 dimm on 4rx4.
I had some issue like this back in the day populating all 12 slot on the xserve with 2gb modules ... I had to match brands from side to side and some dimm where recognized alone or with just 2 of them, but not seen when all slot where populated...
now i understand :
http://www.dataram.com/blog/?p=32
xeon56xx can only access 12 rank in total per cpu so 6x2r or 3x4r or 2x4r+2x2r

so if anyone stumble on a 2Rx4 32gb dim try to get the reference, but i’m not sure it exists in pc10600... if someone have both a macpro 6.1 with 32tb 2R4 stick and a cMP it would be interesting to see if the ddr3 of the 6.1 get recognized on the cMP normally it should and be working at 1333mHz.
I am almost sure that ddr3 ecc registred 1933mhz 32gb 2Rx4 dim exist .
 
Last edited:
ok so i duno if it is a typo or if it is for real but 32gb 2Rx4 module apparently does exist :

https://hpecas.com/memorias-para-se...m-715166-b21-717901-001-716112-081_41251.html

But, and it is a major « but » it looks like they are around 700€ a stick...

and very hard to find.
if they are compatible we would be able to go up to 256 gb...

but more importantly we could have 192 gb at full speed like when you do the 6x16gb=96gb that is faster in real life that 8x16=128gb ....

and more importantly for those who have 1 cpu the ability to have 96gb at full speed!

who is going to be the first to pull the trigger ?
[doublepost=1560859834][/doublepost]all is now crystal clear :

https://www.google.fr/amp/s/deinosc...l-nehalem-memory-architecture-connection/amp/
 
So if i'm reading that article correctly, if i fill my empty Slot 3 & 6 with identical 2Rx4 ram sticks, i should still be running at 1333MHz? And if i keep going Slot 4 & 8 filled will drop everything down to 800MHz?
 
ok so i duno if it is a typo or if it is for real but 32gb 2Rx4 module apparently does exist :
https://hpecas.com/memorias-para-se...m-715166-b21-717901-001-716112-081_41251.html
But, and it is a major « but » it looks like they are around 700€ a stick...
For NMD4G7G31G0BHD10A4HM,
I found that an eBay shop sells only one used module at $395,
but that price is more than 8 modules of my M393B4G70BM0-YH9 ...
[doublepost=1560870831][/doublepost]
So if i'm reading that article correctly, if i fill my empty Slot 3 & 6 with identical 2Rx4 ram sticks, i should still be running at 1333MHz? And if i keep going Slot 4 & 8 filled will drop everything down to 800MHz?
I am not sure about 32GB modules,
but according to my experience with 16GB 2Rx4 modules M393B2G70BH0-YH9,
* single
3x16GB -> 1333MHz
4x16GB -> 1333MHz
* dual
6x16GB -> 1333MHz
8x16GB -> 1066MHz
 
  • Like
Reactions: VaZ
I have tested 1x 16GB + 1x 32GB modules on X5660 single CPU tray with Verbose mode this morning.
* macOS Catalina 10.15
** In EFI boot screen, the background is turned from white to black, a character cursor appears, but nothing is displayed.
* macOS Mojave 10.14.5
** It does not boot. The last message is "End RandomSeed".
* macOS High Sierra 10.13.6
** It boots, but recognizes only 16GB.
* macOS El Capitan 10.11.6
** It boots, but recognizes only 16GB.
* macOS Yosemite 10.10.5
** It boots, and recognizes all RAM modules as 48GB, but 32GB module is "Empty" at "About This Mac".

View attachment 843251 View attachment 843252 View attachment 843253 View attachment 843254 View attachment 843255 View attachment 843256
[doublepost=1560719749][/doublepost]
I searched the forum, but I could not find @edgerider 's post about High Sierra and 160GB.
Instead, I found the similar result at @Kon_Kipa 's post in this thread https://forums.macrumors.com/thread...nyone-tried-this.2046693/page-2#post-27168182
With your post Yosemite tests, did you ever tried to force the re-detection of the SPD, flashing a clear NVRAM from a BootROM reconstruction or the generic MP51.fd before installing the 32GB modules?

If not, and you still have interest in doing so, I can explain what is needed.
 
With your post Yosemite tests, did you ever tried to force the re-detection of the SPD, flashing a clear NVRAM from a BootROM reconstruction or the generic MP51.fd before installing the 32GB modules?
If not, and you still have interest in doing so, I can explain what is needed.
I have not tried that, and it sounds interesting.
Can you explain me how to do that?
 
I have not tried that, and it sounds interesting.
Can you explain me how to do that?
I'll send you a PM later today with instructions on how to do a BootROM reconstruction, it's safer than just dump/flash generic MP51.fd.
 
  • Like
Reactions: kazkus
I'll send you a PM later today with instructions on how to do a BootROM reconstruction, it's safer than just dump/flash generic MP51.fd.
Thanks to @tsialex, I could flash a clean BootROM to my testing MacPro5,1 yesterday morning, but I have not had enough time yesterday, so I did some testing of 32GB memory module with X5660 single CPU tray.

Basically, I got the same result as last weekend for all memory configurations that I tested.
However, I happened to test 8GB module in the 1st slot and 32GB module in the 2nd slot,
then it went beyond "End RandomSeed" message, and actually loaded macOS Mojave kernel,
but it died with kernel panic with "PHYSMAP_PTOV bounds exeeded".
Without Verbose mode, the progress bar appeared below the Apple logo, and a little bit progressed.
I remember that I got the same kind of message when I tried 192GB on OS X Yosemite last weekend.

Since it was kernel panic, I removed 32GB module, and booted macOS, in order to get the Problem Report.

*** Panic Report ***
panic(cpu 4 caller 0xffffff800a23b378): "PHYSMAP_PTOV bounds exceeded, 0xfffffe994acdd000, 0xfffffe9600000000, 0xfffffe9900000000"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4903.261.4/osfmk/i386/pmap.h:515
Backtrace (CPU 4), Frame : Return Address
0xffffff813c3db910 : 0xffffff800a1aea2d
Screen Shot 2019-06-19 at 1.43.29 PM.png
 
32GB memory module : Samsung M393B4G70BM0-YH9 1333MHz 4Rx4
16GB memory module : Samsung M393B2G70BH0-YH9 1333MHz 2Rx4
8GB memory module : Micron MT36JSZF1G72PZ-1G4D1DD 1333MHz 2Rx4

macOS Mojave 10.14.5
8GB+32GB : kernel panic PHYSMAP_PTOV bounds exceeded
16GB+32GB : End RandomSeed
32GB : End RandomSeed
32GB+8GB : End RandomSeed
32GB+16GB : End RandomSeed
8GB+8GB+8GB+32GB : LED for 3rd and 4th modules on POST, macOS boots with 16GB
8GB+8GB+32GB+32GB : POST failed? nothing happened.

Also, I tried Ubuntu Desktop 18.04.2, Windows 10 Pro, and MemTest86 V8.2 with only one 32GB module yesterday.
It was not stable yesterday. It sometime freezes during boot, or after 10 minutes yesterday.
But I remember that MemTest86 ran with 4 modules for a couple of hours last weekend.
(*) Updated on 2019-06-20 : X5660 single CPU tray looks broken. https://forums.macrumors.com/thread...nyone-tried-this.2046693/page-6#post-27481928 The above some results might be caused by broken CPU tray.

Here is output of dmidecode and lshw commands on Ubuntu with 3 modules.

Screenshot 2019-06-19 22.56.24.png Screenshot 2019-06-19 22.56.58.png Screenshot 2019-06-19 23.14.57.png
 
Last edited:
it would be very interesting to submit a bug report to apple about the 32GB DIMMs not working properly
I know they dont officially support it, but would be interesting to see what they say :)
In my understanding, when macOS kernel died, "aapl,panic-info %f0%b0;" was written to NVRAM as follows:
Code:
aapl,panic-info %f0%b0;=F%8d%e1u%10%0d4%0e%b3%d9e9%08%867%9b%cdf%b3%19%07%83%85e3%f1%ec%86K%e9@"(2;m%06%a1_(%f5i%05%89%dfu7y%0e*%e3%c7%e52%b9Lf%81`x%b3%d9l6%97s9ZxL&%c3`0%16%08%867%9b%cdfs9g%83%c1`0%18%0c%06c%81`x%b3%d9l6%97s9%18%0c%06%83%c1`0%11%f0%25%ac%a7%d9d%e9%fbM%7f1%d3byX%9e%7f%0d%c3cty%fe%1a%bf%db%ae0%1c%ce.%bb%f0%e2%f9k%fa%ae%cb%c7%e5%f9%0b%ef%ae%bf%f0%eez%8b%96%83%cd\2[%ccE{%bd%e7%e6%f6%fa%95%9e%e1l/x;%0cw%a1u%b5XM!%0c%8f%d7tyx\%06%a1%86%d0*%88%96b%81%8c%f2p%bb%0c%d2%81%a4ez]%ee%06%05%c9dyy>W%c0%f0f%b3%d9l6%e3b%b3%f1%8c,%ce%c5` %1d%08%867%9b%cdf%b3%19%07%83%85c%e1rXF%06)`x%b3%d9l6%9bq%b1%d9xF%16%e7l0%90%0e%04%c3%9b%cdf%b3%d9%8c%83%c1%c2%b2r%ae%9c%ab%81%140%bc%d9l6%9b%cd%b8%d8l<#%8bsa%18H%07%82%e1%cdf%b3%d9l%c6%c1`a%19Y|%83%85A%0a%18%del6%9b%cdf\l6%9e%91%c5%e1%18%0c%a4%03%c1%f0f%b3%d9l6%e3`%b0p%ac&%16%d3` %05%0co6%9b%cdf3.6%1b%cf%c8%e2%f0%0c%06%d2%81`x%b3%d9l6%9bq0X8%16.%d3h7%90%02%867%9b%cdf%b3%19%17%9b%8dgd%b1%b8%06%03%e9@0%bc%d9l6%9b%cd8%18,%1c%0b%97e%b9%19H%01%c3%9b%cdf%b3%d9%8c%8b%cd%c63%b2X<%86%81t %18%del6%9b%cdf%1c%0c%16%96%cd%c4%b3%1b%0e%a4%80%e1%cdf%b3%d9l%c6%c5f%e3%19Y,6%c3@:%10%0co6%9b%cdf3%0e%06%0b%cbfa%189%06R%c0%f0f%b3%d9l6%e3b%b3%f1%8c,&%d3` %1d%08%867%9b%cdf%b3%19%07%83%85e%b3%f18%16%06)`x%b3%d9l6%9bq%b1%d9xF%16%9bc0%90%0e%04%c3%9b%cdf%b3%d9%8c%83%c1%c22%b2%98%0c%0b%83%140%bc%d9l6%9b%cd%b8%d8l<#%8b%cda%18H%07%82%e1%cdf%b3%d9l%c6%c1`%e1XM%1c%a6%99A%0a%85pJ%04%c1%e5%efqy>%07%b9%c3%ed2h%fc%96%cb%cbs%f8%dbMN%bb%cf %fa%1b4%ae%cb%e5e7%1dDG%cb%cba%b2%0e%c4%0e%d7%ddc4Y!|%bf%e9%a0%b0%fc<%d7%81Zv%85%a2%19%1e%83%9eS%90%bd,%9f%a7%dfn%9d%c2%f9%a6%83%f2e:h^%a6+%14%cb%b2%dc]f%83%ece%f9<%fdv%eb%14%c4%b0%fc%9ev%83%96e%b9%bb%cc%06Y%cb%f2y%fa%ed%06%c5p.%9b%0b%a6%03Q%d1uP%10.%07%c9j %d9L%17%b3%e9d7%10%94H%05%c9`%b1%dc%0e$%7f%bf%e9:%bc%bb%de%a2%e5`3%97%cc%16s%d1%fc%b2%97%b4%c8,%06%a7%c5/%16g%fb%dah%8aeY%ee.%b3A%d5j%92%a8%03%dd%868%a1%d06%b3%b5%8a%b5%dc%ac5%1b%16i-\M%86k%e5%84D%19-h%c3%e1p%b5%98bY%96%bb%cbl%d0%9c%9d&%97u %10%08%04%82%e1a0%18%0c%06%83%c1`%b92%0c%06%83%c1%14%cb%b2%dc]f%83%e8e<%1d$%0e%cf%cb:%10%0co6%9b%cdf3%0e%06%0b%c3`0%18%0c%a6%f8~%91I!%08D/%e3%e9 qx^%d6%81`x%b3%d9l6%9bq0X%ce%0c%83%c1`0%c54?%a7%97%db%a0%f6%9b\f%83%dc%e1vY%07j%86%c7P%f9%bb%c6%8a%81P%cd%f0%b8e%94%c9b%c2%e2%10%97R(%a6%f99%bd%dc%06%d5%e1%f4t%bb%0cJ%bbA%ee%b0%fb=/%8f%dfn%f2\%07%b2%d5r%b6\%0d%06%8b%d1%14%ec%f0%9c%0eb%bf%c3%e42%19%b4.%e3%e9%a00%1dT%a3%c9p2%1a%0c%87%cb%e9@@s%9a]%9e%e7%e7%f4r{%ee%0a%c3%cd%f3D%8eVs%c9l0%d7%0d%84%0a%93%c9r%10%0co6%9b%cdf%f3%cd%8c%13%d7%cc9%18%0c%c6%02%cd%d3%fa2(%16%93%c9f0ZJ%c1~%87%c9e2h]%c6%d3%e
After removing 32GB module, macOS booted, but the bug report consists of two parts, one is the panic report based on NVRAM, and another is the current configuration without 32GB memory module such as:
Code:
Model: MacPro5,1, BootROM 144.0.0.0.0, 6 processors, 6-Core Intel Xeon, 2.8 GHz, 8 GB, SMC 1.39f5
Graphics: kHW_NVidiaGeForceGT120Item, NVIDIA GeForce GT 120, spdisplays_pcie_device, 512 MB
Memory Module: DIMM 1, 8 GB, DDR3 ECC, 1333 MHz, 0x802C, 0x33364A535A4631473732505A2D3147344431
Bluetooth: Version 6.0.12f1, 3 services, 26 devices, 1 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
PCI Card: NVIDIA GeForce GT 120, Display Controller, Slot-1
PCI Card: PXS4, USB eXtensible Host Controller, Slot-4
Serial ATA Device: Samsung SSD 850 EVO 500GB, 500.11 GB
so Apple does not understand that panic of "PHYSMAP-PTOV bounds exceeded" was caused by 32GB memory module.
 
In my understanding, when macOS kernel died, "aapl,panic-info %f0%b0;" was written to NVRAM as follows:
Code:
aapl,panic-info %f0%b0;=F%8d%e1u%10%0d4%0e%b3%d9e9%08%867%9b%cdf%b3%19%07%83%85e3%f1%ec%86K%e9@"(2;m%06%a1_(%f5i%05%89%dfu7y%0e*%e3%c7%e52%b9Lf%81`x%b3%d9l6%97s9ZxL&%c3`0%16%08%867%9b%cdfs9g%83%c1`0%18%0c%06c%81`x%b3%d9l6%97s9%18%0c%06%83%c1`0%11%f0%25%ac%a7%d9d%e9%fbM%7f1%d3byX%9e%7f%0d%c3cty%fe%1a%bf%db%ae0%1c%ce.%bb%f0%e2%f9k%fa%ae%cb%c7%e5%f9%0b%ef%ae%bf%f0%eez%8b%96%83%cd\2[%ccE{%bd%e7%e6%f6%fa%95%9e%e1l/x;%0cw%a1u%b5XM!%0c%8f%d7tyx\%06%a1%86%d0*%88%96b%81%8c%f2p%bb%0c%d2%81%a4ez]%ee%06%05%c9dyy>W%c0%f0f%b3%d9l6%e3b%b3%f1%8c,%ce%c5` %1d%08%867%9b%cdf%b3%19%07%83%85c%e1rXF%06)`x%b3%d9l6%9bq%b1%d9xF%16%e7l0%90%0e%04%c3%9b%cdf%b3%d9%8c%83%c1%c2%b2r%ae%9c%ab%81%140%bc%d9l6%9b%cd%b8%d8l<#%8bsa%18H%07%82%e1%cdf%b3%d9l%c6%c1`a%19Y|%83%85A%0a%18%del6%9b%cdf\l6%9e%91%c5%e1%18%0c%a4%03%c1%f0f%b3%d9l6%e3`%b0p%ac&%16%d3` %05%0co6%9b%cdf3.6%1b%cf%c8%e2%f0%0c%06%d2%81`x%b3%d9l6%9bq0X8%16.%d3h7%90%02%867%9b%cdf%b3%19%17%9b%8dgd%b1%b8%06%03%e9@0%bc%d9l6%9b%cd8%18,%1c%0b%97e%b9%19H%01%c3%9b%cdf%b3%d9%8c%8b%cd%c63%b2X<%86%81t %18%del6%9b%cdf%1c%0c%16%96%cd%c4%b3%1b%0e%a4%80%e1%cdf%b3%d9l%c6%c5f%e3%19Y,6%c3@:%10%0co6%9b%cdf3%0e%06%0b%cbfa%189%06R%c0%f0f%b3%d9l6%e3b%b3%f1%8c,&%d3` %1d%08%867%9b%cdf%b3%19%07%83%85e%b3%f18%16%06)`x%b3%d9l6%9bq%b1%d9xF%16%9bc0%90%0e%04%c3%9b%cdf%b3%d9%8c%83%c1%c22%b2%98%0c%0b%83%140%bc%d9l6%9b%cd%b8%d8l<#%8b%cda%18H%07%82%e1%cdf%b3%d9l%c6%c1`%e1XM%1c%a6%99A%0a%85pJ%04%c1%e5%efqy>%07%b9%c3%ed2h%fc%96%cb%cbs%f8%dbMN%bb%cf %fa%1b4%ae%cb%e5e7%1dDG%cb%cba%b2%0e%c4%0e%d7%ddc4Y!|%bf%e9%a0%b0%fc<%d7%81Zv%85%a2%19%1e%83%9eS%90%bd,%9f%a7%dfn%9d%c2%f9%a6%83%f2e:h^%a6+%14%cb%b2%dc]f%83%ece%f9<%fdv%eb%14%c4%b0%fc%9ev%83%96e%b9%bb%cc%06Y%cb%f2y%fa%ed%06%c5p.%9b%0b%a6%03Q%d1uP%10.%07%c9j %d9L%17%b3%e9d7%10%94H%05%c9`%b1%dc%0e$%7f%bf%e9:%bc%bb%de%a2%e5`3%97%cc%16s%d1%fc%b2%97%b4%c8,%06%a7%c5/%16g%fb%dah%8aeY%ee.%b3A%d5j%92%a8%03%dd%868%a1%d06%b3%b5%8a%b5%dc%ac5%1b%16i-\M%86k%e5%84D%19-h%c3%e1p%b5%98bY%96%bb%cbl%d0%9c%9d&%97u %10%08%04%82%e1a0%18%0c%06%83%c1`%b92%0c%06%83%c1%14%cb%b2%dc]f%83%e8e<%1d$%0e%cf%cb:%10%0co6%9b%cdf3%0e%06%0b%c3`0%18%0c%a6%f8~%91I!%08D/%e3%e9 qx^%d6%81`x%b3%d9l6%9bq0X%ce%0c%83%c1`0%c54?%a7%97%db%a0%f6%9b\f%83%dc%e1vY%07j%86%c7P%f9%bb%c6%8a%81P%cd%f0%b8e%94%c9b%c2%e2%10%97R(%a6%f99%bd%dc%06%d5%e1%f4t%bb%0cJ%bbA%ee%b0%fb=/%8f%dfn%f2\%07%b2%d5r%b6\%0d%06%8b%d1%14%ec%f0%9c%0eb%bf%c3%e42%19%b4.%e3%e9%a00%1dT%a3%c9p2%1a%0c%87%cb%e9@@s%9a]%9e%e7%e7%f4r{%ee%0a%c3%cd%f3D%8eVs%c9l0%d7%0d%84%0a%93%c9r%10%0co6%9b%cdf%f3%cd%8c%13%d7%cc9%18%0c%c6%02%cd%d3%fa2(%16%93%c9f0ZJ%c1~%87%c9e2h]%c6%d3%e
After removing 32GB module, macOS booted, but the bug report consists of two parts, one is the panic report based on NVRAM, and another is the current configuration without 32GB memory module such as:
Code:
Model: MacPro5,1, BootROM 144.0.0.0.0, 6 processors, 6-Core Intel Xeon, 2.8 GHz, 8 GB, SMC 1.39f5
Graphics: kHW_NVidiaGeForceGT120Item, NVIDIA GeForce GT 120, spdisplays_pcie_device, 512 MB
Memory Module: DIMM 1, 8 GB, DDR3 ECC, 1333 MHz, 0x802C, 0x33364A535A4631473732505A2D3147344431
Bluetooth: Version 6.0.12f1, 3 services, 26 devices, 1 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
PCI Card: NVIDIA GeForce GT 120, Display Controller, Slot-1
PCI Card: PXS4, USB eXtensible Host Controller, Slot-4
Serial ATA Device: Samsung SSD 850 EVO 500GB, 500.11 GB
so Apple does not understand that panic of "PHYSMAP-PTOV bounds exceeded" was caused by 32GB memory module.
If I remember correctly, the info part of the dump is generated post the crash, when the OS reads the crash dump from the NVRAM, post reboot.
 
If I remember correctly, the info part of the dump is generated post the crash, when the OS reads the crash dump from the NVRAM, post reboot.
I think you are right.

* macOS kernel crashed with 8GB+32GB during boot.
* 32GB module was removed in order to boot macOS.
* macOS booted, and the info part has just "Memory Module: DIMM 1, 8 GB, DDR3 ECC, 1333 MHz, 0x802C, 0x33364A535A4631473732505A2D3147344431" but no 32GB module information.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.