10/3/2023 0 Comments OO ShutUp10 1803![]() ![]() Using a very simple interface, you decide how Windows 10 should respect your privacy by making recommendations and giving tips for which unwanted functions should be deactivated. Main driver from Gaming, then copy over the Pro OpenCL pieces by hand to make a hybrid driver combo that might do all of the things.O&O ShutUp10 means you have full control over which comfort functions under Windows 10 you wish to use, and you decide when the passing on of your data goes too far. I do wonder if there is some manual combination of components from the two drivers that would be Pro (full alloc) but add back the ability to tune power. I still haven't gotten the old aticonfig to work so no OverDrive tweaks, same boat there. Currently have to run ancient antique drivers to make them work with single allocation, similar to you having to run the Pro. Could also be why they tend to still work better on Terascale (opposite end of the spectrum), those seem to need multiple allocation to get all the memory, but more at a 350MB chunk size, and do not like multiple CL sessions. Perhaps the others were designed with a more complex memory manager already, so they didn't even need to deal with this issue. I believe xmr-stak would need a more complex internal memory manager to be able to workaround allocation issues while still using single host/CL session. ru/1553-zatknis-desyatka-tviker-dlya-windows-10-oo-shutup10.html. But I doubt the performance will get as high as the single host thread with proper 16GB and high intensity, it should gain, and work around the chunk-allocation limit. do-nakopitelnogo-obnovleniya-april-2018-update-versiya-1803-sborka-os-171341.html. The new version installs without issues over existing installations of the program configured tweaks should remain as they are, provided that the tweaks are still supported by the new version of the Windows operating system. You could try 4-5 host threads with max "3.5g" intensity in as many as possible and then whatever remainder in the last one. O&O ShutUp10 version was released on June 2, 2021. The issue with multiple host threads is it opens as many OpenCL sessions to the card. I would prefer to use xmr-stak so if there is any insight it would be greatly appreciated! NEW: O&O ShutUp10 Enhancements for WindRedstone 5 (Build 17763), new Command line parameter for config files and more Protect your privacy - free, no install, no crapware. Is there a reason that xmr-stak only allocates 3.5GB of memory? Is there a way to fully allocate it on the gaming drivers for Vega FE? I know this have been an issue for other Vega FE owners with gaming drivers. ![]() Cast-xmr allocates the full 16GB though (I haven't tested any other software yet). Because of this I have to lower the intensity and hashrate is not good. However, xmr-stak only allocates ~3.5GB of memory per GPU, instead of the full 16GB like it should. ![]() Now, changing to the 18.4.1 gaming driver I can use overdriventool and PPT voltages correctly apply. However, since I cannot use overdriventool my power consumption is through the roof (PPT voltages don't correctly apply either). Using the 18.4.1 Pro drivers xmr-stak fully allocates 16GB of memory for each GPU, so hashrate is as expected. Cast-xmr allocated the full 16GB on gaming drivers. Tldr: Xmr-stak only allocates ~3.5GB of memory instead of the full 16GB on gaming drivers (but allocates the full 16GB on pro drivers). xmr-stak 2.4.4 (complied version on github) with the following environment variables in a batch file before starting:.Windows 1803, with 90gb virtual memory and large page size enabled (gpedit). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |