pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

[pastrychef]

Hi Pastrychef!
Long time no writing although I follow this thread on a daily basis.
I am very happy with this rig. Thanks for your awesome dedication, it runs steady ad nice.

I need help with some KP crashes but let me first update you on my hardware upgrades to the rig.

Wifi and bluetooth work prefect. Apple bluetooth keyboard runs wonderfully. I also got sound through DP on my LG widescreen once I deleted CodecCommader.
Everything has been running kinda smooth, it took me some time (newbee me) but I finally managed to set my OC (had to manually set VCCIO volt to 1.05 and SYS Agent volt to 1.1 or sys wouldn't boot).
I run it at 4'7 or it would get too hot in my mATX enclosure.
Then I added second fan (following your advice) to my Noctua NH-D15S.
At a 22ºC ambient temp. my idle temps are around 36-39ºC and when doing full 98% CPU usage rendering on Cinema it does get 85-90ºC.
Also added a second nVme 970 500gb drive which I paired with the 960 to configure a RAID0 superfast storage for my work stuff, system runs on an Crucial SSD.
970 runs 9ºC hotter than the 960, maybe cause it is closer to ram and RM650X psu.


But I am suffering some random crashes - KPs, mostly sporadic: system suddenly stutters and crashes back into reboot.
I might spend a few days with no issue or I can suffer various KP the same day for no apparent reason, these are mostly happening on some click (pen + Wacom CintQ22hd) on some app window but yesterday and today I got two system reboots while I was away from the computer and she was doing no heavy task, these did not render any byKP log.

I have attached a .txt file with a few lines of today´s system.log preceding the crash.

I don't believe these KPs are related to OC, I did try running the system without any OC and I did get a KP also.
Neither do I think they are related to the OS version, I checked my KPs archive to find I have suffered these KP with 17E202, 17G65 and 17G3025 (no previous record).
Right now I am on bios 1412 but also had them with 1002.


My 4.3.2 config.plist is attached below, only changes are serials (erased) and uia_exclude, I am using your .aml file. No other modification done to your design.

As I have no knowledge to interpret KP logs maybe you can shed some light into my issue?
I am getting to think it is related to my GTX 970 gpu or the Nvidia drivers but I am just guessing. Webdriver 387.10.10.10.40.108 and Cuda 410.130 (I don't believe After Effects or C4D use it now).
I wouldn't want to swap to AMD card as I might need to use in the future some GPU renderer like Octane or Redshift. I am thinking of maybe getting a better card like a 1080, for now I´ll be staying in HS.

I'll appreciate any help.
Thanks!.


Bold sections on this KP log extract are the ones that repeat almost exactly on most of the logs, cpu number varies and most of the backtrace section repeats almost exactly too:

Anonymous UUID: -----------------------------------

Wed Nov 28 12:38:11 2018

*** Panic Report ***
mp_kdp_enter(): 3839, 1, 12 TIMED-OUT WAITING FOR NMI-ACK, PROCEEDING
panic(cpu 8 caller 0xffffff8006cb0a89): "waitq deadlock - waitq=0xffffff805efb4f10, cpu=8\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.13/osfmk/kern/waitq.c:1825
Backtrace (CPU 8), Frame : Return Address
0xffffffa3be9fb6c0 : 0xffffff8006c6b1c6 mach_kernel : _handle_debugger_trap + 0x4c6
0xffffffa3be9fb710 : 0xffffff8006d93a74 mach_kernel : _kdp_i386_trap + 0x114
0xffffffa3be9fb750 : 0xffffff8006d85d44 mach_kernel : _kernel_trap + 0x4e4
0xffffffa3be9fb7c0 : 0xffffff8006c1d1e0 mach_kernel : _return_from_trap + 0xe0
0xffffffa3be9fb7e0 : 0xffffff8006c6ac3c mach_kernel : _panic_trap_to_debugger + 0x21c
0xffffffa3be9fb910 : 0xffffff8006c6a9fc mach_kernel : _panic + 0x5c
0xffffffa3be9fb970 : 0xffffff8006cb0a89 mach_kernel : _waitq_wakeup64_all_locked + 0xa09
0xffffffa3be9fba20 : 0xffffff8006cb0eff mach_kernel : _waitq_wakeup64_all_locked + 0xe7f
0xffffffa3be9fba90 : 0xffffff8006cb1668 mach_kernel : _waitq_wakeup64_one_locked + 0x5d8
0xffffffa3be9fbb30 : 0xffffff8006cb1a96 mach_kernel : _waitq_wakeup64_identify_locked + 0xc6
0xffffffa3be9fbbd0 : 0xffffff8006c51776 mach_kernel : _ipc_mqueue_post + 0x76
0xffffffa3be9fbc20 : 0xffffff8006c515df mach_kernel : _ipc_mqueue_send + 0x5f
0xffffffa3be9fbc60 : 0xffffff8006c4dbd7 mach_kernel : _ipc_kmsg_send + 0x257
0xffffffa3be9fbcb0 : 0xffffff8006c70f07 mach_kernel : _mach_msg_send_from_kernel_proper + 0xe7
0xffffffa3be9fbcf0 : 0xffffff7f87598945 com.nvidia.web.NVDAResmanWeb : _osGetCurrentTime + 0x4e0
0xffffffa3be9fbd30 : 0xffffff7f875eff71 com.nvidia.web.NVDAResmanWeb : _osSetEvent + 0x44
0xffffffa3be9fbd50 : 0xffffff7f876a84e6 com.nvidia.web.NVDAResmanWeb : _engineNonStallIntrNotify + 0xc6
0xffffffa3be9fbda0 : 0xffffff7f876ed9d4 com.nvidia.web.NVDAResmanWeb : _gpuPowerOn_IMPL + 0x61bf
0xffffffa3be9fbdc0 : 0xffffff7f87d5c628 com.nvidia.web.NVDAGM100HalWeb : __ZN12NVDAGM100HAL5probeEP9IOServicePi + 0x13b35a
0xffffffa3be9fbe10 : 0xffffff7f875f7164 com.nvidia.web.NVDAResmanWeb : _osIsISR + 0x424
0xffffffa3be9fbed0 : 0xffffff8007298e35 mach_kernel : __ZN22IOInterruptEventSource12checkForWorkEv + 0x105
0xffffffa3be9fbf30 : 0xffffff80072975a2 mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x1e2
0xffffffa3be9fbf70 : 0xffffff8007296bcc mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x2c
0xffffffa3be9fbfa0 : 0xffffff8006c1c557 mach_kernel : _call_continuation + 0x17
Kernel Extensions in backtrace:
com.nvidia.web.NVDAResmanWeb(10.3.3)[92230D7F-69C4-34B2-9B37-2BA3E8131CE1]@0xffffff7f87591000->0xffffff7f87c09fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[D02EA6D7-7A0E-3F9D-B179-75AC2228E449]@0xffffff7f87494000
dependency: com.apple.iokit.IONDRVSupport(519.21)[8E0EE518-0D53-38C0-B308-2C6CD9EC5B7B]@0xffffff7f87575000
dependency: com.apple.iokit.IOGraphicsFamily(519.21)[E5B53C5D-BF6E-3D72-9091-A80DFE5426C9]@0xffffff7f8751f000
dependency: com.apple.AppleGraphicsDeviceControl(3.20.14)[D3CF5F89-2DA6-3F73-995D-F5DDE191E192]@0xffffff7f87585000
com.nvidia.web.NVDAGM100HalWeb(10.3.3)[4A7D4AFA-6610-34D5-889F-70FDA958CEF6]@0xffffff7f87c20000->0xffffff7f87dc3fff
dependency: com.nvidia.web.NVDAResmanWeb(10.3.3)[92230D7F-69C4-34B2-9B37-2BA3E8131CE1]@0xffffff7f87591000
dependency: com.apple.iokit.IOPCIFamily(2.9)[D02EA6D7-7A0E-3F9D-B179-75AC2228E449]@0xffffff7f87494000

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0 -alcbeta shikigva=60 nvda_drv=1 -lilubetaall keepsyms=1 -disablegfxfirmware -wegbeta uia_exclude=HS08;HS09;HS10;HS11;HS12;HS13;HS14;SS07;SS08;SS09;SS10

Mac OS version:
17G3025

Kernel version:
Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64
Kernel UUID: 4C560F2C-3F3C-3423-B806-2C4D39D570A0
Kernel slide: 0x0000000006a00000
Kernel text base: 0xffffff8006c00000
__HIB text base: 0xffffff8006b00000
System model name: iMac18,3 (Mac-BE088AF8C5EB4FA2)


View attachment 368614 View attachment 368613
View attachment 368612

90C is right at TJMax and the CPU will start to throttle itself from that point forward. Watch to see if performance suffers even though your CPU clocks are higher. If it does, try seeing if you can dial back the voltage being applied to the CPU.

Your dual NVMe RAID sounds real nice. I'm envious. I would not worry about the temperature differences between the 960 and the 970. They are two entirely different models and should not be expected to operate at the same temps. If they start getting exceedingly hot (~70C or higher), you can get heatsinks for them.

That kernel panic clearly shows a problem with the Nvidia card. I don't know if it's the fault of the drivers or if there's a problem with the card itself. You will have to do some trial and error testing to find out which it is. The random nature of your crashes leads me to GUESS that it may be hardware.

If you are considering a new video card, here are a few things to think about:

• Apple is moving everything to Metal 2.
• OpenGL and OpenCL have already been officially depreciated and will be omitted in macOS 10.15.x.
• Whatever Mac apps you use will have to adapt or they will just not run right in future versions of macOS.
• Apple hasn't shipped a Mac with an Nvidia GPU in a very long time and the ones that did ship with an Nvidia GPU will probably lose support for future macOS updates soon.
• Nvidia still hasn't released any Mojave drivers.

With all this in mind, I think it would be foolish to invest in an Nvidia card for use with macOS at this point. Although some apps may run better today with Nvidia cards, I would have to think that moving forward, companies will concentrate in improving AMD performance more than putting efforts in to Nvidia since no real Macs are going to have Nvidia cards.

 

[Goiniro]

90C is right at TJMax and the CPU will start to throttle itself from that point forward. Watch to see if performance suffers even though your CPU clocks are higher. If it does, try seeing if you can dial back the voltage being applied to the CPU.

Your dual NVMe RAID sounds real nice. I'm envious. I would not worry about the temperature differences between the 960 and the 970. They are two entirely different models and should not be expected to operate at the same temps. If they start getting exceedingly hot (~70C or higher), you can get heatsinks for them.

That kernel panic clearly shows a problem with the Nvidia card. I don't know if it's the fault of the drivers or if there's a problem with the card itself. You will have to do some trial and error testing to find out which it is. The random nature of your crashes leads me to GUESS that it may be hardware.

If you are considering a new video card, here are a few things to think about:

• Apple is moving everything to Metal 2.
• OpenGL and OpenCL have already been officially depreciated and will be omitted in macOS 10.15.x.
• Whatever Mac apps you use will have to adapt or they will just not run right in future versions of macOS.
• Apple hasn't shipped a Mac with an Nvidia GPU in a very long time and the ones that did ship with an Nvidia GPU will probably lose support for future macOS updates soon.
• Nvidia still hasn't released any Mojave drivers.

With all this in mind, I think it would be foolish to invest in an Nvidia card for use with macOS at this point. Although some apps may run better today with Nvidia cards, I would have to think that moving forward, companies will concentrate in improving AMD performance more than putting efforts in to Nvidia since no real Macs are going to have Nvidia cards.

Thanks for your quick answer Pastrychef.

I forgot to mention my cpu core/cache voltage is manually set at 1'35v and Dram at 1.35 as by default bios setting.
I will try to get some time and see if I can tweak to higher clock speeds while dialling down cpu voltage. Maybe once I update to latest bios and if I get to solve this KPs.


NVMe is nice , look at the speeds I get. Temp doesn't get higher than 42ºC on the 970, it remains very stable all the time:

You might be right about the hardware issue. My first attempt to hacking was back in 2014 when I got an external eGPU enclosure for my late 2012 i7 16 Gb Mini. At first it worked fine with goalque's script but at some point in Yosemite it started to crash my system (when moving heavily dense Google 3D maps) so I had to forget about it. I though it was software related (some OS change), or maybe to the thunderbolt 1>sonnet>PCMCIA box's data transfer constraints. But the behaviour is very similar. Here is the top part from the last Mini's KP log:

Tue Jan 31 09:32:55 2017

*** Panic Report ***
panic(cpu 7 caller 0xffffff7faee56ebb): NVRM[0/195:0:0]: Read Error 0x00000200: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xa1000000 0xffffff922de44000 0x124020a1, D0, P3/4
Backtrace (CPU 7), Frame : Return Address
0xffffff92198236c0 : 0xffffff802e0d7b92
0xffffff9219823740 : 0xffffff7faee56ebb
0xffffff9219823800 : 0xffffff7faef326de
0xffffff9219823860 : 0xffffff7faf1d847e
0xffffff92198238d0 : 0xffffff7faf1ed0c4
0xffffff92198238f0 : 0xffffff7faefc80fe
0xffffff9219823960 : 0xffffff7faefc7a1e
0xffffff92198239d0 : 0xffffff7faefc76cb
0xffffff9219823a50 : 0xffffff7faefc7017
0xffffff9219823ba0 : 0xffffff7faf1b64cd
0xffffff9219823c20 : 0xffffff7faf1aff34
0xffffff9219823cf0 : 0xffffff7faf1b0262
0xffffff9219823d60 : 0xffffff7faf1b0516
0xffffff9219823db0 : 0xffffff7faf1f48dd
0xffffff9219823e20 : 0xffffff7faef5ff13
0xffffff9219823e40 : 0xffffff7faee5d3de
0xffffff9219823ef0 : 0xffffff802e6b2186
0xffffff9219823f40 : 0xffffff802e6afff1
0xffffff9219823f80 : 0xffffff802e6b00e6
0xffffff9219823fb0 : 0xffffff802e1c6537
Kernel Extensions in backtrace:
com.nvidia.web.NVDAResmanWeb(10.1.1)[F92F779E-492B-343B-94AC-ABC489021468]@0xffffff7faedf0000->0xffffff7faf0cffff
dependency: com.apple.iokit.IOPCIFamily(2.9)[274140D4-A37E-3A38-A9F2-27366EBF9421]@0xffffff7fae92c000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[4EB2843C-C821-3AD0-B333-575FD6ED6FB1]@0xffffff7faedd9000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[A360453D-2050-3C49-A549-AC0DD5E87917]@0xffffff7faed92000
dependency: com.apple.AppleGraphicsDeviceControl(3.12.9)[C5A263AD-4212-31A1-9DE2-A73A25F2ADC0]@0xffffff7faede9000
com.nvidia.web.NVDAGM100HalWeb(10.1.1)[FE6CEFA9-F93E-3BC0-840C-13786FDAE732]@0xffffff7faf0df000->0xffffff7faf2dbfff
dependency: com.nvidia.web.NVDAResmanWeb(10.1.1)[F92F779E-492B-343B-94AC-ABC489021468]@0xffffff7faedf0000
dependency: com.apple.iokit.IOPCIFamily(2.9)[274140D4-A37E-3A38-A9F2-27366EBF9421]@0xffffff7fae92c000

BSD process name corresponding to current thread: kernel_task
Boot args: nvda_drv=1

Mac OS version:
15G1217

Do you think running Etrecheck would help me see it is a faulty card? I have not used it yet.

This KPs are really a bugger and time eater, and make me sad because other than that your build is just wonderful and runs like a real iMac .

Thanks for the concentrated update on the gpus.
I've been also looking at some of the other forums on which Mac Pro users discuss it trying to understand whats coming upon us and maybe understand whats with my KPs.
Geez, its getting difficult to make a decision now, I agree it seems like a not so good option going for Nvidia. I might have to move from Cinema to Blender as its seems to be supporting AMD cards. Which would be the easiest to instal AMD card? I understand you tweaked yours but maybe thats to much hacking for me ¿?.

I found this ****** regarding metal tmp files and how deleting them seems to solve it for some users on Mac Pros. Take a peek if you can. I have not wanted to mess with that though without checking first with you.

 

[pastrychef]

Thanks for your quick answer Pastrychef.

I forgot to mention my cpu core/cache voltage is manually set at 1'35v and Dram at 1.35 as by default bios setting.
I will try to get some time and see if I can tweak to higher clock speeds while dialling down cpu voltage. Maybe once I update to latest bios and if I get to solve this KPs.


NVMe is nice , look at the speeds I get. Temp doesn't get higher than 42ºC on the 970, it remains very stable all the time:
View attachment 368650

You might be right about the hardware issue. My first attempt to hacking was back in 2014 when I got an external eGPU enclosure for my late 2012 i7 16 Gb Mini. At first it worked fine with goalque's script but at some point in Yosemite it started to crash my system (when moving heavily dense Google 3D maps) so I had to forget about it. I though it was software related (some OS change), or maybe to the thunderbolt 1>sonnet>PCMCIA box's data transfer constraints. But the behaviour is very similar. Here is the top part from the last Mini's KP log:

Tue Jan 31 09:32:55 2017

*** Panic Report ***
panic(cpu 7 caller 0xffffff7faee56ebb): NVRM[0/195:0:0]: Read Error 0x00000200: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xa1000000 0xffffff922de44000 0x124020a1, D0, P3/4
Backtrace (CPU 7), Frame : Return Address
0xffffff92198236c0 : 0xffffff802e0d7b92
0xffffff9219823740 : 0xffffff7faee56ebb
0xffffff9219823800 : 0xffffff7faef326de
0xffffff9219823860 : 0xffffff7faf1d847e
0xffffff92198238d0 : 0xffffff7faf1ed0c4
0xffffff92198238f0 : 0xffffff7faefc80fe
0xffffff9219823960 : 0xffffff7faefc7a1e
0xffffff92198239d0 : 0xffffff7faefc76cb
0xffffff9219823a50 : 0xffffff7faefc7017
0xffffff9219823ba0 : 0xffffff7faf1b64cd
0xffffff9219823c20 : 0xffffff7faf1aff34
0xffffff9219823cf0 : 0xffffff7faf1b0262
0xffffff9219823d60 : 0xffffff7faf1b0516
0xffffff9219823db0 : 0xffffff7faf1f48dd
0xffffff9219823e20 : 0xffffff7faef5ff13
0xffffff9219823e40 : 0xffffff7faee5d3de
0xffffff9219823ef0 : 0xffffff802e6b2186
0xffffff9219823f40 : 0xffffff802e6afff1
0xffffff9219823f80 : 0xffffff802e6b00e6
0xffffff9219823fb0 : 0xffffff802e1c6537
Kernel Extensions in backtrace:
com.nvidia.web.NVDAResmanWeb(10.1.1)[F92F779E-492B-343B-94AC-ABC489021468]@0xffffff7faedf0000->0xffffff7faf0cffff
dependency: com.apple.iokit.IOPCIFamily(2.9)[274140D4-A37E-3A38-A9F2-27366EBF9421]@0xffffff7fae92c000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[4EB2843C-C821-3AD0-B333-575FD6ED6FB1]@0xffffff7faedd9000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[A360453D-2050-3C49-A549-AC0DD5E87917]@0xffffff7faed92000
dependency: com.apple.AppleGraphicsDeviceControl(3.12.9)[C5A263AD-4212-31A1-9DE2-A73A25F2ADC0]@0xffffff7faede9000
com.nvidia.web.NVDAGM100HalWeb(10.1.1)[FE6CEFA9-F93E-3BC0-840C-13786FDAE732]@0xffffff7faf0df000->0xffffff7faf2dbfff
dependency: com.nvidia.web.NVDAResmanWeb(10.1.1)[F92F779E-492B-343B-94AC-ABC489021468]@0xffffff7faedf0000
dependency: com.apple.iokit.IOPCIFamily(2.9)[274140D4-A37E-3A38-A9F2-27366EBF9421]@0xffffff7fae92c000

BSD process name corresponding to current thread: kernel_task
Boot args: nvda_drv=1

Mac OS version:
15G1217

Do you think running Etrecheck would help me see it is a faulty card? I have not used it yet.

This KPs are really a bugger and time eater, and make me sad because other than that your build is just wonderful and runs like a real iMac .

Thanks for the concentrated update on the gpus.
I've been also looking at some of the other forums on which Mac Pro users discuss it trying to understand whats coming upon us and maybe understand whats with my KPs.
Geez, its getting difficult to make a decision now, I agree it seems like a not so good option going for Nvidia. I might have to move from Cinema to Blender as its seems to be supporting AMD cards. Which would be the easiest to instal AMD card? I understand you tweaked yours but maybe thats to much hacking for me ¿?.

I found this ****** regarding metal tmp files and how deleting them seems to solve it for some users on Mac Pros. Take a peek if you can. I have not wanted to mess with that though without checking first with you.

Hmm... I expected higher sequential reads and writes from your RAID... Here's me single 970 EVO.


This panic is also related to Nvidia.

I've never used Etrecheck. I don't know what it does...

The ****** thread suggests searching for "com.apple.metal" and deleting it. I've never had to do this... But if you want to try, you can use an app from the Mac App Store called EasyFind. It's free and works really well. It should be able to help you find all the files you need to delete. But there were a few on that thread who tried without success.

You can try stressing your video card in Windows to see if it causes crashes. The FurMark benchmark is torture on video cards.

 

[wing]

Hi all, I am a newbie to hackintosh and am stuck at boot on "End randomseed". Here are my specification:

• Asus Strix Z370-G
• Intel i7-8700
• Sapphire Radeon RX Vega 56
• G.Skill Trident 16GB
• Samsung 970 Evo 500GB NVMe M.2 SSD

I have followed the setup instructions and set the Bios as listed above except have boot/CSM disabled. For the USB installer I downloaded High Sierra and using UniBeast 8.1.0 and copied the EFI folder into the EFI partition after downloading and unzipping the "EFI unified 4.3.2 (High sierra) .zip" file. Can anyone please direct me towards solving this issue so that i can start the installation. Thank you.

Hi all, thanks to PastryChef I was able to install my Hackintosh properly to the build quoted above and almost everything is working fine except for my microphone. The sound part is working fine but after plugging in the microphone it was not registering any sound when I tested it in the control panel. I have another hard drive installed in the above system and it has Windows 10 installed in it and the same microphone was able to record sound. Can any please help me in diagnosing this problem? Thank you.

 

[pastrychef]

Hi all, thanks to PastryChef I was able to install my Hackintosh properly to the build quoted above and almost everything is working fine except for my microphone. The sound part is working fine but after plugging in the microphone it was not registering any sound when I tested it in the control panel. I have another hard drive installed in the above system and it has Windows 10 installed in it and the same microphone was able to record sound. Can any please help me in diagnosing this problem? Thank you.

I don't know why it's not working for you. I just tested on my end and it's working...

You can try changing Audio ID to 1 to see if it helps...

 

[wing]

I don't know why it's not working for you. I just tested on my end and it's working...

You can try changing Audio ID to 1 to see if it helps...
View attachment 368750

Hi Pastrychef, the change of Audio ID to 1 did the trick. The original figures was "2" and the microphone worked after I made the change and rebooted. Once again, thank you for your help!!

 

[Goiniro]

Hmm... I expected higher sequential reads and writes from your RAID... Here's me single 970 EVO.
View attachment 368657

This panic is also related to Nvidia.

I've never used Etrecheck. I don't know what it does...

The ****** thread suggests searching for "com.apple.metal" and deleting it. I've never had to do this... But if you want to try, you can use an app from the Mac App Store called EasyFind. It's free and works really well. It should be able to help you find all the files you need to delete. But there were a few on that thread who tried without success.

You can try stressing your video card in Windows to see if it causes crashes. The FurMark benchmark is torture on video cards.

RAID0: Might that be a system limitation on the max attainable speed? I just run the test again an gave me the same values 2500ish write and 3080ish read. The good thing about the raid is that as I already owned the 500GB 960 but needed to increase the available space so my only options were either sell my 960 500GB and get a 1T drive or buy another 500GB and add it to the volume.
It was super easy to configure (only hard thing given the super tiny room was securing the little screw that holds the 2nd M2 drive ). Speed is Ok for me so far, I can move full-res 2880x2160 anamorphic (5760x2160 px) around the After Effects timeline and play 24fps once frames they are loaded in the ram .
That's just perfect for me: it is even bigger than 4K UHD standard which I just started working on; and loooong time will pass before get to work in 8k UHD.

OMG I haven't seriously touched WINDOWS in 20 years+ I would have to setup a second startup drive, get into it again...
I´ll try to stay away from that path unless strictly necessary.
Is LuxMark not as good as FurMark?

Etrecheck (doesn't seem really worth, free version at least) is supposed to give you a report (extensive one not included in free version), only thing it reported is incomplete SIP state.
I guess it's part of the hackintoshing configuration? This is my state:

Last login: Fri Nov 30 09:34:27 on console
----iMack:~ ----$ csrutil status
System Integrity Protection status: enabled (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: enabled
DTrace Restrictions: enabled
NVRAM Protections: enabled
BaseSystem Verification: enabled
This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

I´ll have to write down everyday status and apps running and see if I discover which combination of programs-tasks make the system crash.
Thank you pastrychef! I´ll keep you posted of my progress.
Best regards.

 

[scottkendall]

I´ll have to write down everyday status and apps running and see if I discover which combination of programs-tasks make the system crash.

I was having crashes for a long time turned out to be the CPU though the errors all pointed to the video card. After I tried every other piece of hardware in the system I bought a super cheap I3 CPU and popped it in no issues since. Currently waiting on a RMA pack from Intel for the defective CPU.

 

[pastrychef]

RAID0: Might that be a system limitation on the max attainable speed? I just run the test again an gave me the same values 2500ish write and 3080ish read. The good thing about the raid is that as I already owned the 500GB 960 but needed to increase the available space so my only options were either sell my 960 500GB and get a 1T drive or buy another 500GB and add it to the volume.
It was super easy to configure (only hard thing given the super tiny room was securing the little screw that holds the 2nd M2 drive ). Speed is Ok for me so far, I can move full-res 2880x2160 anamorphic (5760x2160 px) around the After Effects timeline and play 24fps once frames they are loaded in the ram .
That's just perfect for me: it is even bigger than 4K UHD standard which I just started working on; and loooong time will pass before get to work in 8k UHD.

OMG I haven't seriously touched WINDOWS in 20 years+ I would have to setup a second startup drive, get into it again...
I´ll try to stay away from that path unless strictly necessary.
Is LuxMark not as good as FurMark?

Etrecheck (doesn't seem really worth, free version at least) is supposed to give you a report (extensive one not included in free version), only thing it reported is incomplete SIP state.
I guess it's part of the hackintoshing configuration? This is my state:

Last login: Fri Nov 30 09:34:27 on console
----iMack:~ ----$ csrutil status
System Integrity Protection status: enabled (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: enabled
DTrace Restrictions: enabled
NVRAM Protections: enabled
BaseSystem Verification: enabled
This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

I´ll have to write down everyday status and apps running and see if I discover which combination of programs-tasks make the system crash.
Thank you pastrychef! I´ll keep you posted of my progress.
Best regards.

I never really messed with RAID in macOS much. Maybe I'll play around with it and see if I can make some use out of some old, small SSDs I have laying around.

FurMark is the worst torture test for graphics cards that I know about. If you graphics card can survive FurMark, it can probably survive anything.

Yes, SIP often needs to be disabled to run unsigned kexts. This is a common thing in a hackintosh.

 

[Goiniro]

I was having crashes for a long time turned out to be the CPU though the errors all pointed to the video card. After I tried every other piece of hardware in the system I bought a super cheap I3 CPU and popped it in no issues since. Currently waiting on a RMA pack from Intel for the defective CPU.

Thanks for the info.
How did you get to find it was the CPU?
I wish mine not to be such case.
Right now I have been running the rig non stop since last KP yesterday at 10:41. It's very weird: not so many app in use combination/variations in my workflow...