Just because the drivers are the latest available doesn't mean they are bug free. So please report this as a bug to the makers. And just because Adobe Reader is causing it, doesn't mean it is in error. (As a programmer I find it hard to imagine a programming error in the app which prints that could make this happen).
It would be interested to know the memory details before/after. In task manager under Performance, at the bottom. There are SIX figures in the left hand column, and in the right hand column, Commit followed by two numbers. All 8 might be interesting to understand what kind of memory is being used up.