New
#11
I'm testing it on the next reboot... Maybe they are talking about the fixit tool and not about the manual registry editing as I do have the problem with the system lagging even with 24GB of memory when I have too many Chrome browser tabs opened which wasn't there with Windows 7 HP even with 16GB of memory.
It's actually Microsoft Fix It that doesn't support Windows 10:
https://support.microsoft.com/en-us/..._and_uninstall
Hi,
I fully agree that WIN10 can exhibit some strange memory problems.
Even on machines with plenty of memory it may all of a sudden announce you to shut down some apps as it's running out of resources.
As far as I can tell this is not a memory problem, i.e. not RAM amount related as every time I check there's plenty left.
Now, as for the solution? I don't know. Strange thing is it seems to happen on some installation, never on others.
The reg hack is not going to help IMHO as there's no such string there and even if you'd create one it is not clear what figures for heap size to use for xxxx, yyyy or zzzz. Unless I missed something.
What I did discover however is that this problem seems to crop up when the install files are somehow corrupted. Once that's corrected the problem seems to vanish. At least so far and for the few occasions it occurred on my own machines.
Hope this helps,
Not too sure about that one because the registry entry exists in a machine that came with Windows 7 HP and I applied it on Windows 7 and it did work. My reboot ended up in the Start Menu not working so I need to fix that first before actually seeing if it makes a difference as I have 60 tabs running in Chrome, usually when it works, I will be able to open 100 tabs without problems.
I have the string in mines but perhaps it's because I came from Windows 7. As for X, Y, Z, it's experimental as you set it too high, it will BSOD on bootup which is why to test something like that, you really need two machines running the same OS so you can import the registry file and fix it before exporting it back. You're not supposed to touch the x, only change y and z and this is a different article that includes every Windows OS except Windows 10... The other article specifically tells you a value for y and z:
For 64-bit operating systems, increase the yyyy value to "20480";
Increase the zzzz value to "1024".
https://support.microsoft.com/en-us/kb/947246
Hi,
OK, fair enough. Mines are all clean installs so I can only guess what the xxxx value could be like.
FWIW, I re-imaged the install that gave me memory leak problems. Ran sfc /scannow which reported corruption.
DISM wouldn't mount the wim for some mysterious reason so I extracted it and reran it from there and now it's all clean as the proverbial.
Problem seems to have gone up in smoke and everything has been running smoothly ever since.
Could be purely coincidental though. (Hard to tell with Win 10 sometimes)
I've been using an all in one ISO (22 versions of Win 10 no less) and have noticed that they're all somewhat corrupted even after a fresh install. Windows doesn't complain, not even eventviewer (well nothing extraordinary anyway).
Hence, bottomline conclusion so far, first make sure the OS is healthy then you at least know that's not the culprit.
(Minor "features" aside that is )
Cheers,