1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

what tweaks do you do for your fresh win10 installs? (from gaming/performance perspective)

Discussion in 'Operating Systems' started by alexander1986, Apr 6, 2019.

  1. mbk1969

    mbk1969 Ancient Guru

    Messages:
    7,361
    Likes Received:
    3,879
    GPU:
    GeForce GTX 1070
    Excuse me for misleading you, but "Win32 API" is just a steady term for Windows API all programs use regardless of their bitness.
     
    Last edited: Apr 13, 2019
    386SX and akbaar like this.
  2. EdKiefer

    EdKiefer Ancient Guru

    Messages:
    2,206
    Likes Received:
    162
    GPU:
    MSI 970 Gaming 4G
    Ok, either way, I still never seen any improvement.
    I would be interested to see what others see if any benefit.
     
  3. disq

    disq Active Member

    Messages:
    54
    Likes Received:
    29
    GPU:
    GTX
    Do you also do that via perfmon.exe?
     
  4. Clawedge

    Clawedge Ancient Guru

    Messages:
    2,402
    Likes Received:
    579
    GPU:
    Radeon 570
    insp1re2600, akbaar and alexander1986 like this.

  5. mbk1969

    mbk1969 Ancient Guru

    Messages:
    7,361
    Likes Received:
    3,879
    GPU:
    GeForce GTX 1070
    In Event Viewer.
     
  6. EdKiefer

    EdKiefer Ancient Guru

    Messages:
    2,206
    Likes Received:
    162
    GPU:
    MSI 970 Gaming 4G
    could you give some pointers on how to disable some event messages, I looked and couldn't figure out how to do it.
    For one all those DistributedCOM ones are good to stop.

    Edit: Ok, I think I see you can edit "filter current log" and exclude event ID# with a "- ID# in the field and separated by commas for next ones.
    You can also alter the size of logs stored, I think the default is 20mb for most.
    The thing is I am not sure this stops logging or just stops view of that ID#, be nice to be able to stop writes to log for specific events.
     
    Last edited: Apr 13, 2019
    akbaar likes this.
  7. mbk1969

    mbk1969 Ancient Guru

    Messages:
    7,361
    Likes Received:
    3,879
    GPU:
    GeForce GTX 1070
    Filtering just shows not all events. We can`t stop individual events in Event Viewer, we can disable only whole logs. But we can remove providers of events from the log properties:
    [​IMG]
    1. Double click on corresponding event in System log, switch to "Details" tab in properties dialog, expand "System" root node to see the name (and Guid) of event`s provider.
    2. Launch perfmon.exe, expand "Data Collector Sets" root node, select "Startup Event Trace Sessions", double click on "EventLog-System" session, switch to "Trace Providers" tab in properties dialog, select corresponding provider in the list, press "Remove" and "Apply" buttons.

    That process removes events of removed provider from the log.

    PS I guess the removal will take effect on next boot. Also it can be that major Windows update can restore default list of providers in event log session.
     
    Last edited: Apr 13, 2019
  8. EdKiefer

    EdKiefer Ancient Guru

    Messages:
    2,206
    Likes Received:
    162
    GPU:
    MSI 970 Gaming 4G
    Thank you, I forgot about performance monitor.
     
  9. Mufflore

    Mufflore Ancient Guru

    Messages:
    11,178
    Likes Received:
    473
    GPU:
    Redacted by NDA
    I find a win7 sp1 disk and install that.
     
    alexander1986 likes this.
  10. zimzoid

    zimzoid Maha Guru

    Messages:
    1,429
    Likes Received:
    23
    GPU:
    2xEVGA980TiSC+(H20) Swift
    Lol not helpful as that os is from the olden days
     
    alexander1986 likes this.

  11. mbk1969

    mbk1969 Ancient Guru

    Messages:
    7,361
    Likes Received:
    3,879
    GPU:
    GeForce GTX 1070
    I just remembered some tweaks (executed in elevated PowerShell):
    Disable-MMAgent -ApplicationPreLaunch
    Disable-MMAgent -PageCombining
    Disable-MMAgent -MemoryCompression
     
    akbaar likes this.
  12. EdKiefer

    EdKiefer Ancient Guru

    Messages:
    2,206
    Likes Received:
    162
    GPU:
    MSI 970 Gaming 4G
    What's the difference between these, I remember you wrote a post on this and memory compression.
    ApplicationLaunchPrefetching :
    ApplicationPreLaunch
    Edit;https://docs.microsoft.com/en-us/powershell/module/mmagent/enable-mmagent?view=win10-ps

    here is memory compression one.
    https://forums.guru3d.com/threads/a-bit-detailed-info-about-memory-compression-in-win10.419260/
    https://forums.guru3d.com/threads/a-bit-detailed-info-about-memory-combining-in-win10.419262/
     
    Last edited: Jun 1, 2019
  13. mbk1969

    mbk1969 Ancient Guru

    Messages:
    7,361
    Likes Received:
    3,879
    GPU:
    GeForce GTX 1070
    "ApplicationPreLaunch" means pre-load frequently used apps.
    "ApplicationLaunchPrefetching" means pre-fetch the app`s stuff when it starts.
    Both seem to do with superfetch.
     
  14. Watcher

    Watcher Ancient Guru

    Messages:
    2,511
    Likes Received:
    150
    GPU:
    Gigabyte Windforce R9 380
    I use the following programs:

    Ultimate Windows Tweaker Windows 10 The Windows Club
    http://www.thewindowsclub.com/ultimate-windows-tweaker-4-windows-10

    SG TCP Optimizer
    https://www.speedguide.net/downloads.php

    These Registry entries:

    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
    "NtfsDisable8dot3NameCreation"=dword:00000001
    "Win31FileSystem"=dword:00000000
    "Win95TruncatedExtensions"=dword:00000001
    "NtfsDisableLastAccessUpdate"=dword:00000001
    "NtfsDisable8dot3NameCreation"=dword:00000001
    
    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Executive]
    "AdditionalDelayedWorkerThreads"=dword:0000000c
    "AdditionalCriticalWorkerThreads"=dword:0000000c
    
    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
    "NoLowDiskSpaceChecks"=dword:00000001
    "LinkResolveIgnoreLinkInfo"=dword:00000001
    "NoResolveSearch"=dword:00000001
    "NoResolveTrack"=dword:00000001
    "NoInternetOpenWith"=dword:00000001
    
     
    Last edited: Jun 9, 2019
  15. Watcher

    Watcher Ancient Guru

    Messages:
    2,511
    Likes Received:
    150
    GPU:
    Gigabyte Windforce R9 380
    This is the first time I have seen the following Games tweaks mentioned: "Priority"=dword:00000001 , "Scheduling Category"="High" and the "SFIO Priority"="High"

    On my Box these settings have improved the low end frame rates on the games I've tried. The frame rates don't seem to dip as far as they did before when these settings are used.

    Akbaar, thanks for posting this information.
     
    akbaar likes this.

  16. ESlik

    ESlik Ancient Guru

    Messages:
    2,405
    Likes Received:
    20
    GPU:
    EVGA x2 1080 Ti SC Black
    This is the BEST and most honest advice ever!
     
  17. EdKiefer

    EdKiefer Ancient Guru

    Messages:
    2,206
    Likes Received:
    162
    GPU:
    MSI 970 Gaming 4G
    You might want to read this, as according to MS some of those don't do anything like SFIO Priority, GPU Priority, Affinity.
    https://docs.microsoft.com/en-us/windows/desktop/procthread/multimedia-class-scheduler-service
     
    Watcher likes this.
  18. Watcher

    Watcher Ancient Guru

    Messages:
    2,511
    Likes Received:
    150
    GPU:
    Gigabyte Windforce R9 380
    @EdKiefer, Well that was an interesting read. According to this MS article, more then one of these settings aren't used at all. Its funny because I swear I did see an improvement in my low Frame Rates.
    I'll have to experiment to verify my conclusions. Thank you for the link to the article..
     
    Last edited: Jun 10, 2019
  19. Watcher

    Watcher Ancient Guru

    Messages:
    2,511
    Likes Received:
    150
    GPU:
    Gigabyte Windforce R9 380
    I found another reference to these settings:

    See URL: https://www.speedguide.net/articles/gaming-tweaks-5812
    A quarter of the way down the page under the section titled:
    More Gaming Tweaks

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Games]

    "Affinity"=dword:00000000 (DWORD, default: 0, recommended: 0. Both 0x00 and 0xFFFFFFFF indicate that processor affinity is not used)

    "Background Only"="False" (REG_SZ, default: "False", recommended: "False", possible values are True or False). Indicates whether this is a background task.

    "Clock Rate"=dword:00002710 (DWORD, default: 2710, recommended: 2710). The maximum guaranteed clock rate the system uses if a thread joins disk task, in 100-nanosecond intervals.

    "GPU Priority"=dword:00000008 (DWORD, default: 2, recommended: 8. range: 0-31). The GPU priority. Not used in Windows XP and 2003.

    "Priority"=dword:00000002 (DWORD, default: 2, recommended: leave alone if using "Scheduling Category" below, set to 6 otherwise for gaming, possible values are 1-8). The task priority, ranging from 1(low) to 8(high). Note for tasks with Scheduling Category of "High", this value is always treated as 2.

    "Scheduling Category"="High" (REG_SZ, default: "Medium", recommended: "High". possible values: Low, Medium, High)

    "SFIO Priority"="High" (REG_SZ, default: "Normal", recommended: "High") The scheduled I/O priority, possible values are Idle, Low, Normal, or High.

    Looks like this discussion has been around a while:

    https://forums.guru3d.com/threads/performance-tweaks.327922/page-19#post-4614136
     
    Last edited: Jun 10, 2019
  20. EdKiefer

    EdKiefer Ancient Guru

    Messages:
    2,206
    Likes Received:
    162
    GPU:
    MSI 970 Gaming 4G
    You will find these references all over the internet, I believe they came up around Windows Vista timeline.
    I know as a beta tester for Process lasso its been a tool added way back, I have never noticed any changes on the games and applications I used but it may work depending on the application.
    here link from PL on it.
    https://bitsum.com/docs/pl/Advanced Tools/advanced_tools.htm#vistammsc

    PS; Those settings seem more reasonable, but again some get contradicted by the MS article and that one is old too, who knows if things have changed.

    Edit: ""GPU Priority"=dword:00000008 (DWORD, default: 2, recommended: 8. range: 0-31). The GPU priority. Not used in Windows XP and 2003."
    I believe those values are backward, as the default for GPU priority is 8 AFAIK in the game key.
     
    Last edited: Jun 11, 2019

Share This Page