A little more detail for you all
I could have used your post 4 weeks ago when I encountered this exact same problem. I had to
shell out $$ to MS for this offical answer:
The CopyFileEx and CopyFile functions are used by all of the standard file-copy utilities that are included with Windows NT 4.0 and Windows 2000.? Because these functions use buffered I/O, the maximum size of a file that you can copy depends on the amount of paged-pool memory that is available at the start of the copy procedure and whether the Physical Address Extensions (PAE) kernel which allows access to memory above 4 gigabytes [GB] is in use. With the standard kernel, 1 kilobyte (KB) of paged pool is required for each megabyte (MB) of file size that is opened for buffered I/O. Because there are two files involved in a copy procedure, 2 KB of paged pool are required for each MB in the source file.
In our case we are transferring 85GB of data which will require 80MB if Paged Pool memory. As we are using the /3GB switch, the total paged pool memory available for the system is 128MB only. This is the reason why we are running out of paged pool memory. To resolve this issue, I recommend you to boot the server without the /3GB switch and perform the copy operation. Once the copy is finished, you can put the /3GB switch again and then boot the server and resume normal operation.
