Why is server configuration 'min server memory' configured at 0, but running at 16 (sometimes 8)?

We started to monitor sql server instance non-active server configurations and find something interesting.
Why is server configuration 'min server memory' configured at 0, but running at 16 (sometimes 8)?
The instances use the default value. 0 is the default and we don't change it, but apparently something changes it when SQL Server starts.
If this is the default behavior why isn't this value (16 or 8) configured as default instead of 0?

Does anyone have an (official/documented) explanation to this behavior?

Why is server configuration 'min server memory' configured at 0, but running at 16 (sometimes 8)? The instances use the default value. 0 is the default and we don't change it, but apparently something changes it when SQL Server starts

When you leave 'Min Server Memory' to default value of 0 this does not means that Lowest possible value is 0. The lowest possible value would be 16 MB. This is documented in This Blog.msdn

For SQL Server 2008 R2

Sp_configureOption   DefaultSetting     LowesPpossibleValue     HighestPossiblevalue

Min server memory          0                 16                Less Than Max server memory

For SQL Server 2012

Sp_configureOption   DefaultSetting     LowesPpossibleValue     HighestPossiblevalue

Min server memory          0                 16                Less Than Max server memory

StackExchange Database Administrators Q#118299, answer score: 3