Windows 10: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment =>...

Discus and support Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment =>... in Windows 10 BSOD Crashes and Debugging to solve the problem; I am looking for a way to safely change my instrument name within my session manager environment. Below is the pathway in windows... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Patrick Cap, Jan 23, 2024.

  1. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment =>...


    I am looking for a way to safely change my instrument name within my session manager environment. Below is the pathway in windows registry:Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment => InstrName ;Can I just edit this name via the windows registry?

    :)
     
    Patrick Cap, Jan 23, 2024
    #1
  2. vincepoy Win User

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\Windows - csrss.exe MaxRequestThreads= range?

    Greetings:

    I had been trying to search for documentation on this but does anyone know for the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\Windows registry key which involves csrss.exe, what is the range or limit for the MaxRequestThreads= variable?
     
    vincepoy, Jan 23, 2024
    #2
  3. vincepoy Win User
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\Windows - csrss.exe MaxRequestThreads= range?

    Many thanks, on my system being a notebook running 500 processes, it seems here is what happens:

    If I have the MaxRequestThreads=x

    where x is the default of 16, the CPU will have a utilization of under 50% for a few hours then stuck at 99% where the system will remain sluggish until rebooting

    when I increase this to 128, the CPU will have a utilization of under 50% for a day and then stuck at 99% the next day where the system will remain sluggish until rebooting

    I am currently trying 256 and so far, after 11 hours of uptime, the CPU usage is at 25%.

    So I am trying to figure out what is the maximum number one can use safely without triggering a BSOD as I am not sure if I can fix the BSOD if it is caused by a setting in the registry should it happen since I will no longer be able to boot the system if that happens. I had never tried 32 but it seem that number would not work well from my tests as mentioned above.

    I also have the following resource hacks:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\Windows

    Windows SharedSection=1024,20480,8192

    from

    Default Value: 1024,20480,768

    For GDI handles change the following Registry Keys:



    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota



    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota



    Change it to 65536

    Range: 256 - 65,536. Default value: 10000



    For USER handles change the following Registry Keys:



    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\USERProcessHandleQuota



    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows\USERProcessHandleQuota



    Change it to 18000

    Range: 200 - 18,000. Default value: 10000
     
    vincepoy, Jan 23, 2024
    #3
  4. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment =>...

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\Windows - csrss.exe MaxRequestThreads= range?

    I was wondering if someone could help me with resetting the Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent

    settings. There has been a change made and now I get an error that "Can't connect to this network" each time I try to connect to a wireless network. I have never had issues before the settings were changed in regedit.
     
    AshleyMcClanahan, Jan 23, 2024
    #4
Thema:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment =>...