The thing is that SQL does not use the page file itself. The only way it can affect the page file is if the OS forces SQL's memory out to disk. If it does, there will be error messages in the log stating so. Are there?
If not, then what you may be seeing is a response to the SQL service. It uses memory and, as a result, the OS writes something else into the page file.
Have you checked the perfmon Process counters to see what processes are using the page file?
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