ID 221890 - Nuke 16 bit .exr renders differently than the Nuke tree

Problem summary
Nuke renders 16 bit .exr's differently to the active Nuke tree.

Customer reported version
nuke.9.0v8

Customer reported platform
windows7

Steps to reproduce

1) Open the attached Nuke script

2) Write out an exr 16bit file

3) On the read node, press reload

4) Look at the Merge difference node, there will be a significant difference between the active Nuke tree compared to the written file, see the screen shot below.

I also found if you render out a 32bit exr, then the problem is not present.

Reproduced by support
The problem has been reproduced in:

Nuke 10.0v3 - Windows 10 - CentOS 6.7 

Nuke 10.0v1 - Windows 10

Nuke 9.0v9 - Windows 10

Nuke 9.0v1 - Windows 10

Nuke 8.0v6 - Windows 10 - CentOS 6.7 

Expected behaviour
For the rendered image to be the same as the Nuke tree.

Actual behaviour
They were significantly different.