Hi, first post so I hope I explain this as I got lost trying to read and understand XP memory management on my Intel quad core PC.
I have my hard drives running on SATA. They have lots of files with some big video files. A persistent problem I have is with XP search. It starts, finds what I need then carries on until the App freezes and I have to do Ctrl/Alt/Del to shut it down. Until recently I saw no other hints of instability.
Then last week I had to copy a lot of 3-5Gb video transport stream files (400Gb total) from internal SATA to External SATA (but the problem is still there internal-internal). This was a heavy IO operation. The cpu cores were not showing anywhere near being maxed out.
The copy kept failing, but could be restarted. I had calculated the whole operation would take at least 2-3 hours but on each failure, I got Windoze 'out of resources errors'.
I started looking for memory leaks using poolmon.exe analyzed by Pool log analyzer tool. Yes I appear to see memory leaks and the paged pool tag increasing over time.
I decided to run MSconfig and put the system into diagnostic mode loading only XP's minimal drivers, anybody can do this.
Then I started a file search for file xz!@ whilst capturing the pool tags several times. This was only a short test, but mirrors what I see happening with longer file copying a steady increase in apparent pool paged memory.
Pool log analyzer says MmSt and NtfF are leaking. Can anybody else tell me if this is normal behaviour and leaking 'YES' means there is not a leak or what? If I suspected a 3rd party driver I would be looking for it and would not expect it to be loaded in diagnostics mode when only Windoze drivers should be present.
I have a working knowledge of XP systems, but memory management and how it works leaves me struggling.
Thanks
I have my hard drives running on SATA. They have lots of files with some big video files. A persistent problem I have is with XP search. It starts, finds what I need then carries on until the App freezes and I have to do Ctrl/Alt/Del to shut it down. Until recently I saw no other hints of instability.
Then last week I had to copy a lot of 3-5Gb video transport stream files (400Gb total) from internal SATA to External SATA (but the problem is still there internal-internal). This was a heavy IO operation. The cpu cores were not showing anywhere near being maxed out.
The copy kept failing, but could be restarted. I had calculated the whole operation would take at least 2-3 hours but on each failure, I got Windoze 'out of resources errors'.
I started looking for memory leaks using poolmon.exe analyzed by Pool log analyzer tool. Yes I appear to see memory leaks and the paged pool tag increasing over time.
I decided to run MSconfig and put the system into diagnostic mode loading only XP's minimal drivers, anybody can do this.
Then I started a file search for file xz!@ whilst capturing the pool tags several times. This was only a short test, but mirrors what I see happening with longer file copying a steady increase in apparent pool paged memory.
Pool log analyzer says MmSt and NtfF are leaking. Can anybody else tell me if this is normal behaviour and leaking 'YES' means there is not a leak or what? If I suspected a 3rd party driver I would be looking for it and would not expect it to be loaded in diagnostics mode when only Windoze drivers should be present.
I have a working knowledge of XP systems, but memory management and how it works leaves me struggling.
Thanks