A bit off topic but I stay away from using BCHR as a performance metric - It's extremely unreliable.
It's not that it's unreliable, it's that it can have a very high value even while the server is under severe memory pressure. In essence, the counter gives false negatives as an indication of memory pressure, it indicates that everything's fine when it's not.
If however it is very low (as in the OP's situation), then the server is exceedingly likely to be under horrid, severe memory pressure.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass