10532 High memory usage?

As a follow on to my first thread about rolling back from 10532 due to problems, I wondered if anyone her has had the same thing.
As soon as I have installed 10532, memory usage rockets, even at initial boot up.
With 16Gb installed, on 10240 it idled at 15% used.
Once 10532 is installed that goes upto around 56%-70% at idle.
All the extra memory is in the non paged pool.

I initially thought it was an issue from upgrading from Windows 8.1 to Windows 10 then Build 10532.
However, the same occurs with a fresh install of 10240 when I update to 10532.

Someone at work mentioned 10532 changed the way the memory management worked, but I have not been able to find anything official to back that up.

As per my other post I am currently trying to get 10532 installed again so I can try running Windows Performance Toolkit, which was suggested by a poster on technet.

Any other ideas in the meantime?

Possibly this Windows 10 Memory Compression - Windows 10 Forums but as you didn't mention what process was using more memory can't really say. If it is System then this would explain it and it is (probably) a good thing.

High usage by Non Paged Pool is a very serious matter. Almost all other memory can be paged out at the memory managers discretion. But Non Paged Pool is locked in memory and the memory manager can't do anything about it. The same applies to any third party memory managers, optimizers that are sometimes suggested. Bad idea.

Processes can't use either the paged or no paged pool directly but system functions can allocate it for the process. Typically the usage for this is very small. High non paged pool usage is usually caused by a driver problem, not a process. Malware is also a possibility. Sorry I can't help you with that.

Thanks both for the replies.
Still not sure what the cause was as I was never able to get Build 10532 installed again, but, having now gone to Build 10547 the issue is no longer there, so presumably was some sort of driver conflict with that particular build?
Malware is unlikely as I ran a scan and the problem only happened when 10532 was installed, as soon as I rolled it back it was OK.