Maybe not for you but on my machine, even after booting up and just browsing, the system will lag badly until I add in the following registry changes and I have just tested this earlier today because every time I do a repair in-place upgrade install, it would reset things back to the defaults:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\Windows
SharedSection=1024,20480,8192 from the default of 1024,20480,768
This is covered in
Desktop heap limitation causes out of memory error - Windows Server
GDI and User Handles needs to be changed as well:
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
Decimal Value
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
Decimal Value
Change it to 18000
Range: 200 - 18,000. Default value: 10000
So a lot depends on what you have running as it might run fine for a few days before rebooting and you are right it can be a configuration issue but there are some things that cannot be changed without a BSOD like using the SharedSection, there sè no reference on what the maximum numbers allowed are.