- May 30, 2014
- ASUS WS X299 Sage 10G
- Vega 64
- Mobile Phone
Hey KGP, It's been a while since I'm busy working using my machine. I'm currently using 10.3.2 just fine, but noticed you updated to 10.3.3. Now I'm finding out about the new beta 10.3.4. I saw this link and wanted your thoughts about it:
Somebody might have shared something on here already about it and if they did, just let me know what post number it is and I'll go and read it. If not, then this might be something to talk about. I haven't looked into it much, but I hope it doesn't affect using apps like Photoshop, Illustrator, InDesign, Premier and like kind apps. Look forward to hearing your response, later...
PS - I see you reached 65,000+ on your GB score - GOOD FOR YOU! How'd you get there? Just curious.
My personal opinion to the topic addressed in the contribution you linked above is the following. As we passed already nearly a decade after introducing the first 64-bit systems, I think it is really time to start discarding 32-bit software for 64-bit systems. Apparently, 10.13.4 is just a first step towards this direction and still seems no to have any further major implications against running likely outdated 32-bit software on 64-bit systems, apart from a first simple warning that you are running 32-bit software instead of 64-bit software on a 64-bit system. I would rather interpret the latter in my opinion yet tiny novel implication as some clear signal of Apple towards all software developers. I just want to stress that all this is really my personal opinion and impression, which might be totally at odd with the opinion of other estimated users.
To your other question. After delidding my i9-7980XE and with my current water blocking system, I am successfully able to run the latter processor on my system @ 4.7GHz with "CPU Core Ratio" set to "Sync all Cores". All other related BIOS settings have been outlined just a few posts ago. However, I want to clearly advice against running the delidded i9-7980XE @ 4.8GHz, as occasionally intended during one of my benchmark runs. The latter might result in an exponential increase of the CPU Core Voltage and might result in a severe damage of either your CPU or mainboard. If at all, always increase the CPU Core Voltage stepwise and manually and take care that it never exceeds 1.25V by far. When running the CPU at @4.7GHz, a manual CPU Core Voltage of 1.22V seems sufficient. When applying OC, always carefully watch your CPU Temps! The CPU Temps might not only strongly depend on your water blocking implementation but also on the processor frequency and especially on the tightly related CPU Core Voltage implementation!
A good hacking and OC,